innovaphone wiki - User contributions [en]

Howto:RoomStatus with XML Script

2026-09-10T15:24:18Z

Kwa:

This description is limited to the "Room Status" service. The integrated wake-up service during Check-out is described separately and is typically installed in the same folder and scenario.

Enjoy reading.
==Applies To==
innovaphone PBX, V16 or higher

==More Information==
In hotels, there is an operational division between service extensions (reception, back-office, bar, kitchen, etc.) and rooms. The reception also acts as an operator console routing incoming calls and features an innovaphone IP phone with a graphic display and function keys. Hereafter, "Reception" refers to all service extensions authorized to modify the Room Status (which may also include Smartphones).

* '''Activation:''' The Room Status service can be activated by the reception on behalf of a room or set directly from the room phone.
* '''Extension Control:''' The system prevents Room Status activation on a service extension by automatically detecting whether an extension is a room or not. This is handled via a PBX setting, matching the Room Status configuration itself. Relying directly on the PBX configuration prevents misalignments and synchronization needs, ensuring all parameters are retained even after a reboot.
* '''Security:''' To prevent guests from modifying the status, the service can be protected by a PIN or code (prefix). Room phones (analog, innovaphone IP, third-party IP) can be of any type.
* '''Management &Monitoring:''' The service can be managed entirely via telephone,while the room statuses are displayed in the reception's myApps lamp field.

[[Image:SpiegaItem.png|388x388px|spiegaitem.png/|spiegaitem.png/]]

==Service Access==

Access to the service requires a dedicated prefix for the reception and a specific prefix dialed from the rooms (by service staff). The caller hears a menu listing available options. If no selection is made, the service disconnects after 30 seconds. Users do not need to wait for the main menu announcement to finish; they can select the desired option immediately.

* '''Reception Dialing:'''Receptionists must also dial the room number. If room numbers have a uniform length (e.g., strictly 2 or 3 digits), the service activatesautomatically after the last digit, followed by a confirmation and disconnection.
* '''Hash Confirmation:'''If the room number length is not configured, users must press thehash key (#) after the room number. The voice menu automatically indicateswhether the hash key is required. If no input is provided after 12 seconds, the system assumes the entered number is confirmed.
* '''Confirmation Prompt:'''Upon activation, the system repeats the room number and the service status. Users do not need to wait for the message to end since thestatus is already active; they can disconnect immediately.

===Reception===

The reception sets statuses for the rooms. If the selected extension is not a room, the message "Room not found" plays. This message also plays if non-configured internal extensions are dialed.

Calling the service plays the main menu: ''"Dial zero for check out, one for check in, two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order, seven for do not disturb, eight to cancel do not disturb, asterisk for room status, followed by the room number."'' If room number length is not set, it adds: ''"and confirm with hash."''

If function keys for these services are configured on the reception phone, the menu is bypassed (as the service type is already selected). In this case, simply press the function key followed by the room number (with or without hash as described above).

[[Image:I112 Checkinout.png|181x181px|i112_checkinout.png/|i112_checkinout.png/]]

===Reception-Only Services===

====Check IN (1)====
The room is opened to telephone traffic. "Open" means the room can make calls using hotel lines. Allowed destination numbers can be restricted (e.g., emergency only, national landlines only, Europe only, etc.). After a check-in, the myApps lamp field below the room displays '''"OCC"''' (occupied).

====Check OUT (0)====
Telephone traffic from the room is blocked. Similar to check-in, the restriction level is configurable (total, internal only, emergency only, local/national only, etc.). Check-out sets the status to '''"LIB"''' (free) and '''"Sporca"''' (dirty). After a check-out, the myApps lamp field displays '''"LIB-Sporca"'''. Any active "Do Not Disturb" setting is automatically cleared, and any active innovaphone wake-up calls are removed, leaving the room ready with no active DND or wake-up calls for the next guest.

====Do Not Disturb (7)====
All calls to the room are forwarded to reception. Reception sees the caller and the room that attempted to call. Only reception can call the room (overriding DND). The myApps lamp field displays an "X" instead of a "-"; (e.g., '''"OCCxPulito"''').

====Cancel Do Not Disturb (8)====
This happens automatically at check-out but can also be manually set by reception for a room. The myApps lamp field displays a "-" instead of an "X"; (e.g., '''"OCC-Pulito"''').

====Room Status (*)====
Announces the current room status (Check in/out, Room status, and any active Do Not Disturb setting).

===Shared Services (Reception and Rooms)===

These statuses can be set by reception or directly from the room phone, regardless of whether the room is checked-in or checked-out, and with or without DND active. Dialing the service from a room plays the main menu: ''"Dial two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order"''.

====Clean Room (2)====
Indicates a dirty room has been cleaned. Reception sees in real-time that the room is clean and available. myApps lamp field displays '''"Pronta"'''.
====Dirty Room (3)====
Set automatically upon check-out or manually. myApps lamp field displays '''"Sporca"'''.
====Room Makeup (4)====
Cleaning staff can set this when starting housekeeping tasks, making staff traceable by calling the room. myApps lamp field displays '''"Makeup"'''.
====Maintenance Requested (5)====
Indicates the need for maintenance. myApps lamp field displays '''"xxx-Manuten"'''.
====Out of Order (6)====
Indicates a room unavailable for guests. myApps lamp field displays '''"xxx-NonDis"'''.

===Installation===

The entire package must be installed in a folder named <code>Files</code>. If the wake-up service is also active, install it within the wake-up folder.

* '''XML Files:''' Two XML files are included: "CheckInOut.xml" (manages the reception side) and "RoomStatus.xml" (called by rooms).
* '''Audio Files:''' All audio files are located in the "AudioRS" subfolder and are provided exclusively in '''G.711a''' format to ensure high quality. Therefore, this codec must be set as exclusive in the command line, for example: ''<nowiki>http://apps.test.local/test.local/files/root/Hotel/CheckInOut.xml</nowiki>'''?$_pbxcoder=g711a'''''
* '''Parameter Text Files:'''
** "RoomLenght.txt" Set the length of room numbers, e.g. "3" for 3-digit rooms. If set to "0", left empty, or deleted, the system requires the hash key after entering the number.
** "reception.txt" Set the reception extension number where calls will be forwarded if Do Not Disturb is activated.
* '''PBX Filters:''' The system distinguishes rooms from non-rooms using an associated filter. Ensure that all rooms are assigned either the '''CheckOUT''' or '''CheckIN''' filter in their configuration. Create these two filters (PBX > Filters) with those exact names and configure their rules for the respective states. It is convenient to configure a template for rooms and associate it with them, then assign one of these two filters directly in the user setup (this will serve as the initial system state for that user). Once functional, proceed to configure the reception function keys (direct dial).

==Localization==

This script is delivered with Italian prompts, but you can produce your own prompts and wordings. How see the link at the end of this page.
The filename and prompts are the following:

{| class="wikitable"
|'''File Name'''
|'''Content / Message'''
|-
|x.g711a
|Digits 0 to 59
|-
|NoRoom.g711
|"Room not found"
|-
|NumRoom.g711a
|"Room number"
|-
|InvalidC.g711a
|"Invalid command"
|-
|CheckedIN.g711a
|"Check IN"
|-
|CheckrdOUT.g711a
|"Check OUT"
|-
|RoomStat.g711a
|"Room status"
|-
|MMenu.g711a
|"Dial zero for check out, one for check in, two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order, seven for do not disturb, eight to cancel do not disturb, asterisk for room status, followed by the room number"
|-
|RoomToClean.g711a
|"Dirty room"
|-
|RoomClean.g711a
|"Clean room"
|-
|RoomMakeup.g711a
|"Room makeup"
|-
|RoomMaint.g711a
|"Maintenance requested"
|-
|RoomOOO.g711a
|"Out of order"
|-
|InvalidNumber.g711a
|"Invalid number"
|-
|DNDon.g711a
|"Do not disturb set"
|-
|DNDoff.g711a
|"Do not disturb cleared"
|-
|MroomSt.g711a
|"Dial two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order"
|}

== Download ==
[[Media:RoomStatus.zip|RoomStatus.zip]]
== Related Articles ==
[[Howto:WakeUp App - Installation and Configuration|WakeUp App - Installation_and_Configuration]]

[[Howto:Creating fine announcements and music on hold|Creating fine announcements and music on hold]]

[[Category:Howto|{{PAGENAME}}]]
[[Category:Sample|{{PAGENAME}}]]

Howto:RoomStatus with XML Script

2026-09-10T15:13:46Z

Kwa:

This description is limited to the "Room Status" service. The integrated wake-up service during Check-out is described separately and is typically installed in the same folder and scenario.

Enjoy reading.
==Applies To==
innovaphone PBX, V16 or higher

==More Information==
In hotels, there is an operational division between service extensions (reception, back-office, bar, kitchen, etc.) and rooms. The reception also acts as an operator console routing incoming calls and features an innovaphone IP phone with a graphic display and function keys. Hereafter, "Reception" refers to all service extensions authorized to modify the Room Status (which may also include Smartphones).

* '''Activation:''' The Room Status service can be activated by the reception on behalf of a room or set directly from the room phone.
* '''Extension Control:''' The system prevents Room Status activation on a service extension by automatically detecting whether an extension is a room or not. This is handled via a PBX setting, matching the Room Status configuration itself. Relying directly on the PBX configuration prevents misalignments and synchronization needs, ensuring all parameters are retained even after a reboot.
* '''Security:''' To prevent guests from modifying the status, the service can be protected by a PIN or code (prefix). Room phones (analog, innovaphone IP, third-party IP) can be of any type.
* '''Management &Monitoring:''' The service can be managed entirely via telephone,while the room statuses are displayed in the reception's myApps lamp field.

[[Image:SpiegaItem.png|388x388px|spiegaitem.png/|spiegaitem.png/]]

==Service Access==

Access to the service requires a dedicated prefix for the reception and a specific prefix dialed from the rooms (by service staff). The caller hears a menu listing available options. If no selection is made, the service disconnects after 30 seconds. Users do not need to wait for the main menu announcement to finish; they can select the desired option immediately.

* '''Reception Dialing:'''Receptionists must also dial the room number. If room numbers have a uniform length (e.g., strictly 2 or 3 digits), the service activatesautomatically after the last digit, followed by a confirmation and disconnection.
* '''Hash Confirmation:'''If the room number length is not configured, users must press thehash key (#) after the room number. The voice menu automatically indicateswhether the hash key is required. If no input is provided after 12 seconds, the system assumes the entered number is confirmed.
* '''Confirmation Prompt:'''Upon activation, the system repeats the room number and the service status. Users do not need to wait for the message to end since thestatus is already active; they can disconnect immediately.

===Reception===

The reception sets statuses for the rooms. If the selected extension is not a room, the message "Room not found" plays. This message also plays if non-configured internal extensions are dialed.

Calling the service plays the main menu: ''"Dial zero for check out, one for check in, two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order, seven for do not disturb, eight to cancel do not disturb, asterisk for room status, followed by the room number."'' If room number length is not set, it adds: ''"and confirm with hash."''

If function keys for these services are configured on the reception phone, the menu is bypassed (as the service type is already selected). In this case, simply press the function key followed by the room number (with or without hash as described above).

[[Image:I112 Checkinout.png|181x181px|i112_checkinout.png/|i112_checkinout.png/]]

===Reception-Only Services===

====Check IN (1)====
The room is opened to telephone traffic. "Open" means the room can make calls using hotel lines. Allowed destination numbers can be restricted (e.g., emergency only, national landlines only, Europe only, etc.). After a check-in, the myApps lamp field below the room displays '''"OCC"''' (occupied).

====Check OUT (0)====
Telephone traffic from the room is blocked. Similar to check-in, the restriction level is configurable (total, internal only, emergency only, local/national only, etc.). Check-out sets the status to '''"LIB"''' (free) and '''"Sporca"''' (dirty). After a check-out, the myApps lamp field displays '''"LIB-Sporca"'''. Any active "Do Not Disturb" setting is automatically cleared, and any active innovaphone wake-up calls are removed, leaving the room ready with no active DND or wake-up calls for the next guest.

====Do Not Disturb (7)====
All calls to the room are forwarded to reception. Reception sees the caller and the room that attempted to call. Only reception can call the room (overriding DND). The myApps lamp field displays an "X" instead of a "-"; (e.g., '''"OCCxPulito"''').

====Cancel Do Not Disturb (8)====
This happens automatically at check-out but can also be manually set by reception for a room. The myApps lamp field displays a "-" instead of an "X"; (e.g., '''"OCC-Pulito"''').

====Room Status (*)====
Announces the current room status (Check in/out, Room status, and any active Do Not Disturb setting).

===Shared Services (Reception and Rooms)===

These statuses can be set by reception or directly from the room phone, regardless of whether the room is checked-in or checked-out, and with or without DND active. Dialing the service from a room plays the main menu: ''"Dial two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order"''.

====Clean Room (2)====
Indicates a dirty room has been cleaned. Reception sees in real-time that the room is clean and available. myApps lamp field displays '''"Pronta"'''.
====Dirty Room (3)====
Set automatically upon check-out or manually. myApps lamp field displays '''"Sporca"'''.
====Room Makeup (4)====
Cleaning staff can set this when starting housekeeping tasks, making staff traceable by calling the room. myApps lamp field displays '''"Makeup"'''.
====Maintenance Requested (5)====
Indicates the need for maintenance. myApps lamp field displays '''"xxx-Manuten"'''.
====Out of Order (6)====
Indicates a room unavailable for guests. myApps lamp field displays '''"xxx-NonDis"'''.

===Installation===

The entire package must be installed in a folder named <code>Files</code>. If the wake-up service is also active, install it within the wake-up folder.

* '''XML Files:''' Two XML files are included: "CheckInOut.xml" (manages the reception side) and "RoomStatus.xml" (called by rooms).
* '''Audio Files:''' All audio files are located in the "AudioRS" subfolder and are provided exclusively in '''G.711a''' format to ensure high quality. Therefore, this codec must be set as exclusive in the command line, for example: ''<nowiki>http://apps.test.local/test.local/files/root/Hotel/CheckInOut.xml</nowiki>'''?$_pbxcoder=g711a'''''
* '''Parameter Text Files:'''
** "RoomLenght.txt" Set the length of room numbers, e.g. "3" for 3-digit rooms. If set to "0", left empty, or deleted, the system requires the hash key after entering the number.
** "reception.txt" Set the reception extension number where calls will be forwarded if Do Not Disturb is activated.
* '''PBX Filters:''' The system distinguishes rooms from non-rooms using an associated filter. Ensure that all rooms are assigned either the '''CheckOUT''' or '''CheckIN''' filter in their configuration. Create these two filters (PBX > Filters) with those exact names and configure their rules for the respective states. It is convenient to configure a template for rooms and associate it with them, then assign one of these two filters directly in the user setup (this will serve as the initial system state for that user). Once functional, proceed to configure the reception function keys (direct dial).

==Localization==

This script is delivered with Italian prompts, but you can produce your own prompts and wordings. How see the link at the end of this page.
The filename and prompts are the following:

{| class="wikitable"
|'''File Name'''
|'''Content / Message'''
|-
|x.g711a
|Digits 0 to 59
|-
|NoRoom.g711
|"Room not found"
|-
|NumRoom.g711a
|"Room number"
|-
|InvalidC.g711a
|"Invalid command"
|-
|CheckedIN.g711a
|"Check IN"
|-
|CheckrdOUT.g711a
|"Check OUT"
|-
|RoomStat.g711a
|"Room status"
|-
|MMenu.g711a
|"Dial zero for check out, one for check in, two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order, seven for do not disturb, eight to cancel do not disturb, asterisk for room status, followed by the room number"
|-
|RoomToClean.g711a
|"Dirty room"
|-
|RoomClean.g711a
|"Clean room"
|-
|RoomMakeup.g711a
|"Room makeup"
|-
|RoomMaint.g711a
|"Maintenance requested"
|-
|RoomOOO.g711a
|"Out of order"
|-
|InvalidNumber.g711a
|"Invalid number"
|-
|DNDon.g711a
|"Do not disturb set"
|-
|DNDoff.g711a
|"Do not disturb cleared"
|-
|MroomSt.g711a
|"Dial two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order"
|}

== Download ==
[[index.php?title=Media:RoomStatus.zip|RoomStatus.zip]]
== Related Articles ==
[[Howto:WakeUp App - Installation and Configuration|WakeUp App - Installation_and_Configuration]]

[[Howto:Creating fine announcements and music on hold|Creating fine announcements and music on hold]]

[[Category:Howto|{{PAGENAME}}]]
[[Category:Sample|{{PAGENAME}}]]

Howto:RoomStatus with XML Script

2026-09-10T15:12:05Z

Kwa:

=DRAFT=

This description is limited to the "Room Status" service. The integrated wake-up service during Check-out is described separately and is typically installed in the same folder and scenario.

Enjoy reading.
==Applies To==
innovaphone PBX, V16 or higher

==More Information==
In hotels, there is an operational division between service extensions (reception, back-office, bar, kitchen, etc.) and rooms. The reception also acts as an operator console routing incoming calls and features an innovaphone IP phone with a graphic display and function keys. Hereafter, "Reception" refers to all service extensions authorized to modify the Room Status (which may also include Smartphones).

* '''Activation:''' The Room Status service can be activated by the reception on behalf of a room or set directly from the room phone.
* '''Extension Control:''' The system prevents Room Status activation on a service extension by automatically detecting whether an extension is a room or not. This is handled via a PBX setting, matching the Room Status configuration itself. Relying directly on the PBX configuration prevents misalignments and synchronization needs, ensuring all parameters are retained even after a reboot.
* '''Security:''' To prevent guests from modifying the status, the service can be protected by a PIN or code (prefix). Room phones (analog, innovaphone IP, third-party IP) can be of any type.
* '''Management &Monitoring:''' The service can be managed entirely via telephone,while the room statuses are displayed in the reception's myApps lamp field.

[[Image:SpiegaItem.png|388x388px|spiegaitem.png/|spiegaitem.png/]]

==Service Access==

Access to the service requires a dedicated prefix for the reception and a specific prefix dialed from the rooms (by service staff). The caller hears a menu listing available options. If no selection is made, the service disconnects after 30 seconds. Users do not need to wait for the main menu announcement to finish; they can select the desired option immediately.

* '''Reception Dialing:'''Receptionists must also dial the room number. If room numbers have a uniform length (e.g., strictly 2 or 3 digits), the service activatesautomatically after the last digit, followed by a confirmation and disconnection.
* '''Hash Confirmation:'''If the room number length is not configured, users must press thehash key (#) after the room number. The voice menu automatically indicateswhether the hash key is required. If no input is provided after 12 seconds, the system assumes the entered number is confirmed.
* '''Confirmation Prompt:'''Upon activation, the system repeats the room number and the service status. Users do not need to wait for the message to end since thestatus is already active; they can disconnect immediately.

===Reception===

The reception sets statuses for the rooms. If the selected extension is not a room, the message "Room not found" plays. This message also plays if non-configured internal extensions are dialed.

Calling the service plays the main menu: ''"Dial zero for check out, one for check in, two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order, seven for do not disturb, eight to cancel do not disturb, asterisk for room status, followed by the room number."'' If room number length is not set, it adds: ''"and confirm with hash."''

If function keys for these services are configured on the reception phone, the menu is bypassed (as the service type is already selected). In this case, simply press the function key followed by the room number (with or without hash as described above).

[[Image:I112 Checkinout.png|181x181px|i112_checkinout.png/|i112_checkinout.png/]]

===Reception-Only Services===

====Check IN (1)====
The room is opened to telephone traffic. "Open" means the room can make calls using hotel lines. Allowed destination numbers can be restricted (e.g., emergency only, national landlines only, Europe only, etc.). After a check-in, the myApps lamp field below the room displays '''"OCC"''' (occupied).

====Check OUT (0)====
Telephone traffic from the room is blocked. Similar to check-in, the restriction level is configurable (total, internal only, emergency only, local/national only, etc.). Check-out sets the status to '''"LIB"''' (free) and '''"Sporca"''' (dirty). After a check-out, the myApps lamp field displays '''"LIB-Sporca"'''. Any active "Do Not Disturb" setting is automatically cleared, and any active innovaphone wake-up calls are removed, leaving the room ready with no active DND or wake-up calls for the next guest.

====Do Not Disturb (7)====
All calls to the room are forwarded to reception. Reception sees the caller and the room that attempted to call. Only reception can call the room (overriding DND). The myApps lamp field displays an "X" instead of a "-"; (e.g., '''"OCCxPulito"''').

====Cancel Do Not Disturb (8)====
This happens automatically at check-out but can also be manually set by reception for a room. The myApps lamp field displays a "-" instead of an "X"; (e.g., '''"OCC-Pulito"''').

====Room Status (*)====
Announces the current room status (Check in/out, Room status, and any active Do Not Disturb setting).

===Shared Services (Reception and Rooms)===

These statuses can be set by reception or directly from the room phone, regardless of whether the room is checked-in or checked-out, and with or without DND active. Dialing the service from a room plays the main menu: ''"Dial two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order"''.

====Clean Room (2)====
Indicates a dirty room has been cleaned. Reception sees in real-time that the room is clean and available. myApps lamp field displays '''"Pronta"'''.
====Dirty Room (3)====
Set automatically upon check-out or manually. myApps lamp field displays '''"Sporca"'''.
====Room Makeup (4)====
Cleaning staff can set this when starting housekeeping tasks, making staff traceable by calling the room. myApps lamp field displays '''"Makeup"'''.
====Maintenance Requested (5)====
Indicates the need for maintenance. myApps lamp field displays '''"xxx-Manuten"'''.
====Out of Order (6)====
Indicates a room unavailable for guests. myApps lamp field displays '''"xxx-NonDis"'''.

===Installation===

The entire package must be installed in a folder named <code>Files</code>. If the wake-up service is also active, install it within the wake-up folder.

* '''XML Files:''' Two XML files are included: "CheckInOut.xml" (manages the reception side) and "RoomStatus.xml" (called by rooms).
* '''Audio Files:''' All audio files are located in the "AudioRS" subfolder and are provided exclusively in '''G.711a''' format to ensure high quality. Therefore, this codec must be set as exclusive in the command line, for example: ''<nowiki>http://apps.test.local/test.local/files/root/Hotel/CheckInOut.xml</nowiki>'''?$_pbxcoder=g711a'''''
* '''Parameter Text Files:'''
** "RoomLenght.txt" Set the length of room numbers, e.g. "3" for 3-digit rooms. If set to "0", left empty, or deleted, the system requires the hash key after entering the number.
** "reception.txt" Set the reception extension number where calls will be forwarded if Do Not Disturb is activated.
* '''PBX Filters:''' The system distinguishes rooms from non-rooms using an associated filter. Ensure that all rooms are assigned either the '''CheckOUT''' or '''CheckIN''' filter in their configuration. Create these two filters (PBX > Filters) with those exact names and configure their rules for the respective states. It is convenient to configure a template for rooms and associate it with them, then assign one of these two filters directly in the user setup (this will serve as the initial system state for that user). Once functional, proceed to configure the reception function keys (direct dial).

==Localization==

This script is delivered with Italian prompts, but you can produce your own prompts and wordings. How see the link at the end of this page.
The filename and prompts are the following:

{| class="wikitable"
|'''File Name'''
|'''Content / Message'''
|-
|x.g711a
|Digits 0 to 59
|-
|NoRoom.g711
|"Room not found"
|-
|NumRoom.g711a
|"Room number"
|-
|InvalidC.g711a
|"Invalid command"
|-
|CheckedIN.g711a
|"Check IN"
|-
|CheckrdOUT.g711a
|"Check OUT"
|-
|RoomStat.g711a
|"Room status"
|-
|MMenu.g711a
|"Dial zero for check out, one for check in, two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order, seven for do not disturb, eight to cancel do not disturb, asterisk for room status, followed by the room number"
|-
|RoomToClean.g711a
|"Dirty room"
|-
|RoomClean.g711a
|"Clean room"
|-
|RoomMakeup.g711a
|"Room makeup"
|-
|RoomMaint.g711a
|"Maintenance requested"
|-
|RoomOOO.g711a
|"Out of order"
|-
|InvalidNumber.g711a
|"Invalid number"
|-
|DNDon.g711a
|"Do not disturb set"
|-
|DNDoff.g711a
|"Do not disturb cleared"
|-
|MroomSt.g711a
|"Dial two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order"
|}

== Download ==
[[Media:RoomStatus.zip|RoomStatus.zip]]
== Related Articles ==
[[Howto:WakeUp App - Installation and Configuration|WakeUp App - Installation_and_Configuration]]

[[Howto:Creating fine announcements and music on hold|Creating fine announcements and music on hold]]

[[Category:Howto|{{PAGENAME}}]]
[[Category:Sample|{{PAGENAME}}]]

Howto:RoomStatus with XML Script

2026-09-10T15:10:23Z

Kwa:

=DRAFT=

This description is limited to the "Room Status" service. The integrated wake-up service during Check-out is described separately and is typically installed in the same folder and scenario.

Enjoy reading.
==Applies To==
innovaphone PBX, V16 or higher

==More Information==
In hotels, there is an operational division between service extensions (reception, back-office, bar, kitchen, etc.) and rooms. The reception also acts as an operator console routing incoming calls and features an innovaphone IP phone with a graphic display and function keys. Hereafter, "Reception" refers to all service extensions authorized to modify the Room Status (which may also include Smartphones).

* '''Activation:''' The Room Status service can be activated by the reception on behalf of a room or set directly from the room phone.
* '''Extension Control:''' The system prevents Room Status activation on a service extension by automatically detecting whether an extension is a room or not. This is handled via a PBX setting, matching the Room Status configuration itself. Relying directly on the PBX configuration prevents misalignments and synchronization needs, ensuring all parameters are retained even after a reboot.
* '''Security:''' To prevent guests from modifying the status, the service can be protected by a PIN or code (prefix). Room phones (analog, innovaphone IP, third-party IP) can be of any type.
* '''Management &Monitoring:''' The service can be managed entirely via telephone,while the room statuses are displayed in the reception's myApps lamp field.

[[Image:SpiegaItem.png|388x388px|spiegaitem.png/|spiegaitem.png/]]

==Service Access==

Access to the service requires a dedicated prefix for the reception and a specific prefix dialed from the rooms (by service staff). The caller hears a menu listing available options. If no selection is made, the service disconnects after 30 seconds. Users do not need to wait for the main menu announcement to finish; they can select the desired option immediately.

* '''Reception Dialing:'''Receptionists must also dial the room number. If room numbers have a uniform length (e.g., strictly 2 or 3 digits), the service activatesautomatically after the last digit, followed by a confirmation and disconnection.
* '''Hash Confirmation:'''If the room number length is not configured, users must press thehash key (#) after the room number. The voice menu automatically indicateswhether the hash key is required. If no input is provided after 12 seconds, the system assumes the entered number is confirmed.
* '''Confirmation Prompt:'''Upon activation, the system repeats the room number and the service status. Users do not need to wait for the message to end since thestatus is already active; they can disconnect immediately.

===Reception===

The reception sets statuses for the rooms. If the selected extension is not a room, the message "Room not found" plays. This message also plays if non-configured internal extensions are dialed.

Calling the service plays the main menu: ''"Dial zero for check out, one for check in, two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order, seven for do not disturb, eight to cancel do not disturb, asterisk for room status, followed by the room number."'' If room number length is not set, it adds: ''"and confirm with hash."''

If function keys for these services are configured on the reception phone, the menu is bypassed (as the service type is already selected). In this case, simply press the function key followed by the room number (with or without hash as described above).

[[Image:I112 Checkinout.png|181x181px|i112_checkinout.png/|i112_checkinout.png/]]

===Reception-Only Services===

====Check IN (1)====
The room is opened to telephone traffic. "Open" means the room can make calls using hotel lines. Allowed destination numbers can be restricted (e.g., emergency only, national landlines only, Europe only, etc.). After a check-in, the myApps lamp field below the room displays '''"OCC"''' (occupied).

====Check OUT (0)====
Telephone traffic from the room is blocked. Similar to check-in, the restriction level is configurable (total, internal only, emergency only, local/national only, etc.). Check-out sets the status to '''"LIB"''' (free) and '''"Sporca"''' (dirty). After a check-out, the myApps lamp field displays '''"LIB-Sporca"'''. Any active "Do Not Disturb" setting is automatically cleared, and any active innovaphone wake-up calls are removed, leaving the room ready with no active DND or wake-up calls for the next guest.

====Do Not Disturb (7)====
All calls to the room are forwarded to reception. Reception sees the caller and the room that attempted to call. Only reception can call the room (overriding DND). The myApps lamp field displays an "X" instead of a "-"; (e.g., '''"OCCxPulito"''').

====Cancel Do Not Disturb (8)====
This happens automatically at check-out but can also be manually set by reception for a room. The myApps lamp field displays a "-" instead of an "X"; (e.g., '''"OCC-Pulito"''').

====Room Status (*)====
Announces the current room status (Check in/out, Room status, and any active Do Not Disturb setting).

===Shared Services (Reception and Rooms)===

These statuses can be set by reception or directly from the room phone, regardless of whether the room is checked-in or checked-out, and with or without DND active. Dialing the service from a room plays the main menu: ''"Dial two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order"''.

====Clean Room (2)====
Indicates a dirty room has been cleaned. Reception sees in real-time that the room is clean and available. myApps lamp field displays '''"Pronta"'''.
====Dirty Room (3)====
Set automatically upon check-out or manually. myApps lamp field displays '''"Sporca"'''.
====Room Makeup (4)====
Cleaning staff can set this when starting housekeeping tasks, making staff traceable by calling the room. myApps lamp field displays '''"Makeup"'''.
====Maintenance Requested (5)====
Indicates the need for maintenance. myApps lamp field displays '''"xxx-Manuten"'''.
====Out of Order (6)====
Indicates a room unavailable for guests. myApps lamp field displays '''"xxx-NonDis"'''.

===Installation===

The entire package must be installed in a folder named <code>Files</code>. If the wake-up service is also active, install it within the wake-up folder.

* '''XML Files:''' Two XML files are included: "CheckInOut.xml" (manages the reception side) and "RoomStatus.xml" (called by rooms).
* '''Audio Files:''' All audio files are located in the "AudioRS" subfolder and are provided exclusively in '''G.711a''' format to ensure high quality. Therefore, this codec must be set as exclusive in the command line, for example: ''<nowiki>http://apps.test.local/test.local/files/root/Hotel/CheckInOut.xml</nowiki>'''?$_pbxcoder=g711a'''''
* '''Parameter Text Files:'''
** "RoomLenght.txt" Set the length of room numbers, e.g. "3" for 3-digit rooms. If set to "0", left empty, or deleted, the system requires the hash key after entering the number.
** "reception.txt" Set the reception extension number where calls will be forwarded if Do Not Disturb is activated.
* '''PBX Filters:''' The system distinguishes rooms from non-rooms using an associated filter. Ensure that all rooms are assigned either the '''CheckOUT''' or '''CheckIN''' filter in their configuration. Create these two filters (PBX > Filters) with those exact names and configure their rules for the respective states. It is convenient to configure a template for rooms and associate it with them, then assign one of these two filters directly in the user setup (this will serve as the initial system state for that user). Once functional, proceed to configure the reception function keys (direct dial).

==Localization==

This script is delivered with Italian prompts, but you can produce your own prompts and wordings. How see the link at the end of this page.
The filename and prompts are the following:

{| class="wikitable"
|'''File Name'''
|'''Content / Message'''
|-
|x.g711a
|Digits 0 to 59
|-
|NoRoom.g711
|"Room not found"
|-
|NumRoom.g711a
|"Room number"
|-
|InvalidC.g711a
|"Invalid command"
|-
|CheckedIN.g711a
|"Check IN"
|-
|CheckrdOUT.g711a
|"Check OUT"
|-
|RoomStat.g711a
|"Room status"
|-
|MMenu.g711a
|"Dial zero for check out, one for check in, two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order, seven for do not disturb, eight to cancel do not disturb, asterisk for room status, followed by the room number"
|-
|RoomToClean.g711a
|"Dirty room"
|-
|RoomClean.g711a
|"Clean room"
|-
|RoomMakeup.g711a
|"Room makeup"
|-
|RoomMaint.g711a
|"Maintenance requested"
|-
|RoomOOO.g711a
|"Out of order"
|-
|InvalidNumber.g711a
|"Invalid number"
|-
|DNDon.g711a
|"Do not disturb set"
|-
|DNDoff.g711a
|"Do not disturb cleared"
|-
|MroomSt.g711a
|"Dial two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order"
|}

==Known Problems==

== Download ==
[[Media:RoomStatus.zip|RoomStatus.zip]]
== Related Articles ==
[[Howto:WakeUp App - Installation and Configuration|WakeUp App - Installation_and_Configuration]]

[[Howto:Creating fine announcements and music on hold|Creating fine announcements and music on hold]]

[[Category:Howto|{{PAGENAME}}]]
[[Category:Sample|{{PAGENAME}}]]

File:RoomStatus.zip

2026-09-10T15:07:09Z

Kwa:

Howto:RoomStatus with XML Script

2026-09-10T15:02:38Z

Kwa:

=DRAFT=

This description is limited to the "Room Status" service. The integrated wake-up service during Check-out is described separately and is typically installed in the same folder and scenario.

Enjoy reading.
==Applies To==
innovaphone PBX, V16 or higher

==More Information==
In hotels, there is an operational division between service extensions (reception, back-office, bar, kitchen, etc.) and rooms. The reception also acts as an operator console routing incoming calls and features an innovaphone IP phone with a graphic display and function keys. Hereafter, "Reception" refers to all service extensions authorized to modify the Room Status (which may also include Smartphones).

* '''Activation:''' The Room Status service can be activated by the reception on behalf of a room or set directly from the room phone.
* '''Extension Control:''' The system prevents Room Status activation on a service extension by automatically detecting whether an extension is a room or not. This is handled via a PBX setting, matching the Room Status configuration itself. Relying directly on the PBX configuration prevents misalignments and synchronization needs, ensuring all parameters are retained even after a reboot.
* '''Security:''' To prevent guests from modifying the status, the service can be protected by a PIN or code (prefix). Room phones (analog, innovaphone IP, third-party IP) can be of any type.
* '''Management &Monitoring:''' The service can be managed entirely via telephone,while the room statuses are displayed in the reception's myApps lamp field.

[[Image:SpiegaItem.png|388x388px|spiegaitem.png/|spiegaitem.png/]]

==Service Access==

Access to the service requires a dedicated prefix for the reception and a specific prefix dialed from the rooms (by service staff). The caller hears a menu listing available options. If no selection is made, the service disconnects after 30 seconds. Users do not need to wait for the main menu announcement to finish; they can select the desired option immediately.

* '''Reception Dialing:'''Receptionists must also dial the room number. If room numbers have a uniform length (e.g., strictly 2 or 3 digits), the service activatesautomatically after the last digit, followed by a confirmation and disconnection.
* '''Hash Confirmation:'''If the room number length is not configured, users must press thehash key (#) after the room number. The voice menu automatically indicateswhether the hash key is required. If no input is provided after 12 seconds, the system assumes the entered number is confirmed.
* '''Confirmation Prompt:'''Upon activation, the system repeats the room number and the service status. Users do not need to wait for the message to end since thestatus is already active; they can disconnect immediately.

===Reception===

The reception sets statuses for the rooms. If the selected extension is not a room, the message "Room not found" plays. This message also plays if non-configured internal extensions are dialed.

Calling the service plays the main menu: ''"Dial zero for check out, one for check in, two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order, seven for do not disturb, eight to cancel do not disturb, asterisk for room status, followed by the room number."'' If room number length is not set, it adds: ''"and confirm with hash."''

If function keys for these services are configured on the reception phone, the menu is bypassed (as the service type is already selected). In this case, simply press the function key followed by the room number (with or without hash as described above).

[[Image:I112 Checkinout.png|181x181px|i112_checkinout.png/|i112_checkinout.png/]]

===Reception-Only Services===

====Check IN (1)====
The room is opened to telephone traffic. "Open" means the room can make calls using hotel lines. Allowed destination numbers can be restricted (e.g., emergency only, national landlines only, Europe only, etc.). After a check-in, the myApps lamp field below the room displays '''"OCC"''' (occupied).

====Check OUT (0)====
Telephone traffic from the room is blocked. Similar to check-in, the restriction level is configurable (total, internal only, emergency only, local/national only, etc.). Check-out sets the status to '''"LIB"''' (free) and '''"Sporca"''' (dirty). After a check-out, the myApps lamp field displays '''"LIB-Sporca"'''. Any active "Do Not Disturb" setting is automatically cleared, and any active innovaphone wake-up calls are removed, leaving the room ready with no active DND or wake-up calls for the next guest.

====Do Not Disturb (7)====
All calls to the room are forwarded to reception. Reception sees the caller and the room that attempted to call. Only reception can call the room (overriding DND). The myApps lamp field displays an "X" instead of a "-"; (e.g., '''"OCCxPulito"''').

====Cancel Do Not Disturb (8)====
This happens automatically at check-out but can also be manually set by reception for a room. The myApps lamp field displays a "-" instead of an "X"; (e.g., '''"OCC-Pulito"''').

====Room Status (*)====
Announces the current room status (Check in/out, Room status, and any active Do Not Disturb setting).

===Shared Services (Reception and Rooms)===

These statuses can be set by reception or directly from the room phone, regardless of whether the room is checked-in or checked-out, and with or without DND active. Dialing the service from a room plays the main menu: ''"Dial two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order"''.

====Clean Room (2)====
Indicates a dirty room has been cleaned. Reception sees in real-time that the room is clean and available. myApps lamp field displays '''"Pronta"'''.
====Dirty Room (3)====
Set automatically upon check-out or manually. myApps lamp field displays '''"Sporca"'''.
====Room Makeup (4)====
Cleaning staff can set this when starting housekeeping tasks, making staff traceable by calling the room. myApps lamp field displays '''"Makeup"'''.
====Maintenance Requested (5)====
Indicates the need for maintenance. myApps lamp field displays '''"xxx-Manuten"'''.
====Out of Order (6)====
Indicates a room unavailable for guests. myApps lamp field displays '''"xxx-NonDis"'''.

===Installation===

The entire package must be installed in a folder named <code>Files</code>. If the wake-up service is also active, install it within the wake-up folder.

* '''XML Files:''' Two XML files are included: "CheckInOut.xml" (manages the reception side) and "RoomStatus.xml" (called by rooms).
* '''Audio Files:''' All audio files are located in the "AudioRS" subfolder and are provided exclusively in '''G.711a''' format to ensure high quality. Therefore, this codec must be set as exclusive in the command line, for example: ''<nowiki>http://apps.test.local/test.local/files/root/Hotel/CheckInOut.xml</nowiki>'''?$_pbxcoder=g711a'''''
* '''Parameter Text Files:'''
** "RoomLenght.txt" Set the length of room numbers, e.g. "3" for 3-digit rooms. If set to "0", left empty, or deleted, the system requires the hash key after entering the number.
** "reception.txt" Set the reception extension number where calls will be forwarded if Do Not Disturb is activated.
* '''PBX Filters:''' The system distinguishes rooms from non-rooms using an associated filter. Ensure that all rooms are assigned either the '''CheckOUT''' or '''CheckIN''' filter in their configuration. Create these two filters (PBX > Filters) with those exact names and configure their rules for the respective states. It is convenient to configure a template for rooms and associate it with them, then assign one of these two filters directly in the user setup (this will serve as the initial system state for that user). Once functional, proceed to configure the reception function keys (direct dial).

==Localization==

This script is delivered with Italian prompts, but you can produce your own prompts and wordings. How see the link at the end of this page.
The filename and prompts are the following:

{| class="wikitable"
|'''File Name'''
|'''Content / Message'''
|-
|x.g711a
|Digits 0 to 59
|-
|NoRoom.g711
|"Room not found"
|-
|NumRoom.g711a
|"Room number"
|-
|InvalidC.g711a
|"Invalid command"
|-
|CheckedIN.g711a
|"Check IN"
|-
|CheckrdOUT.g711a
|"Check OUT"
|-
|RoomStat.g711a
|"Room status"
|-
|MMenu.g711a
|"Dial zero for check out, one for check in, two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order, seven for do not disturb, eight to cancel do not disturb, asterisk for room status, followed by the room number"
|-
|RoomToClean.g711a
|"Dirty room"
|-
|RoomClean.g711a
|"Clean room"
|-
|RoomMakeup.g711a
|"Room makeup"
|-
|RoomMaint.g711a
|"Maintenance requested"
|-
|RoomOOO.g711a
|"Out of order"
|-
|InvalidNumber.g711a
|"Invalid number"
|-
|DNDon.g711a
|"Do not disturb set"
|-
|DNDoff.g711a
|"Do not disturb cleared"
|-
|MroomSt.g711a
|"Dial two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order"
|}

===Known Problems===

== Download ==

*[http://wiki.innovaphone.com/index.php?title=Howto:Wiki_Sources#checkinout Download] the complete file package of scripts and files described in this article.

== Related Articles ==

[[Howto:Creating fine announcements and music on hold|Creating fine announcements and music on hold]]

[[Category:Howto|{{PAGENAME}}]]
[[Category:Sample|{{PAGENAME}}]]

File:I112 Checkinout.png

2026-09-10T14:42:55Z

Kwa:

Howto:RoomStatus with XML Script

2026-09-10T14:42:19Z

Kwa: Created page with "=DRAFT= This description is limited to the "Room Status" service. The integrated wake-up service during Check-out is described separately and is typically installed in the same folder and scenario. Enjoy reading. ==Applies To== innovaphone PBX, V16 or higher ==More Information== In hotels, there is an operational division between service extensions (reception, back-office, bar, kitchen, etc.) and rooms. The reception..."

=DRAFT=

This description is limited to the "Room Status" service. The integrated wake-up service during Check-out is described separately and is typically installed in the same folder and scenario.

Enjoy reading.
==Applies To==
innovaphone PBX, V16 or higher

==More Information==
In hotels, there is an operational division between service extensions (reception, back-office, bar, kitchen, etc.) and rooms. The reception also acts as an operator console routing incoming calls and features an innovaphone IP phone with a graphic display and function keys. Hereafter, "Reception" refers to all service extensions authorized to modify the Room Status (which may also include Smartphones).

* '''Activation:''' The Room Status service can be activated by the reception on behalf of a room or set directly from the room phone.
* '''Extension Control:''' The system prevents Room Status activation on a service extension by automatically detecting whether an extension is a room or not. This is handled via a PBX setting, matching the Room Status configuration itself. Relying directly on the PBX configuration prevents misalignments and synchronization needs, ensuring all parameters are retained even after a reboot.
* '''Security:''' To prevent guests from modifying the status, the service can be protected by a PIN or code (prefix). Room phones (analog, innovaphone IP, third-party IP) can be of any type.
* '''Management & Monitoring:''' The service can be managed entirely via telephone, while the room statuses are displayed in the reception's myApps lamp field.

[[Image:SpiegaItem.png|388x388px]]

==Service Access==

Access to the service requires a dedicated prefix for the reception and a specific prefix dialed from the rooms (by service staff). The caller hears a menu listing available options. If no selection is made, the service disconnects after 30 seconds. Users do not need to wait for the main menu announcement to finish; they can select the desired option immediately.

* '''Reception Dialing:''' Receptionists must also dial the room number. If room numbers have a uniform length (e.g., strictly 2 or 3 digits), the service activates automatically after the last digit, followed by a confirmation and disconnection.
* '''Hash Confirmation:''' If the room number length is not configured, users must press the hash key (#) after the room number. The voice menu automatically indicates whether the hash key is required. If no input is provided after 12 seconds, the system assumes the entered number is confirmed.
* '''Confirmation Prompt:''' Upon activation, the system repeats the room number and the service status. Users do not need to wait for the message to end since the status is already active; they can disconnect immediately.

===Reception===

The reception sets statuses for the rooms. If the selected extension is not a room, the message "Room not found" plays. This message also plays if non-configured internal extensions are dialed.

Calling the service plays the main menu: ''"Dial zero for check out, one for check in, two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order, seven for do not disturb, eight to cancel do not disturb, asterisk for room status, followed by the room number."'' If room number length is not set, it adds: ''"and confirm with hash."''

If function keys for these services are configured on the reception phone, the menu is bypassed (as the service type is already selected). In this case, simply press the function key followed by the room number (with or without hash as described above).

[[Image:I112_Checkinout.png]]

'''Reception-Only Services'''

'''Check IN (1)'''

The room is opened to telephone traffic. "Open" means the room can make calls using hotel lines. Allowed destination numbers can be restricted (e.g., emergency only, national landlines only, Europe only, etc.). After a check-in, the myApps lamp field below the room displays '''"OCC"''' (occupied).

'''Check OUT (0)'''

Telephone traffic from the room is blocked. Similar to check-in, the restriction level is configurable (total, internal only, emergency only, local/national only, etc.). Check-out sets the status to '''"LIB"''' (free) and '''"Sporca"''' (dirty). After a check-out, the myApps lamp field displays '''"LIB-Sporca"'''. Any active "Do Not Disturb" setting is automatically cleared, and any active innovaphone wake-up calls are removed, leaving the room ready with no active DND or wake-up calls for the next guest.

'''Do Not Disturb (7)'''

All calls to the room are forwarded to reception. Reception sees the caller and the room that attempted to call. Only reception can call the room (overriding DND). The myApps lamp field displays an <code>x</code> instead of a dash <code>-</code> (e.g., '''"OCCxPulito"''').

'''Cancel Do Not Disturb (8)'''

This happens automatically at check-out but can also be manually set by reception for a room. The myApps lamp field displays a dash <code>-</code> instead of an <code>x</code> (e.g., '''"OCC-Pulito"''').

'''Room Status (*)'''

Announces the current room status (Check in/out, Room status, and any active Do Not Disturb setting).

l112_Checkinout.png

'''Shared Services (Reception and Rooms)'''

These statuses can be set by reception or directly from the room phone, regardless of whether the room is checked-in or checked-out, and with or without DND active. Dialing the service from a room plays the main menu: ''"Dial two for clean room, three for dirty, four for makeup, five for maintenance request, six for out of order"''.

* '''Clean Room (2):''' Indicates a dirty room has been cleaned. Reception sees in real-time that the room is clean and available. myApps lamp field displays '''"Pronta"'''.
* '''Dirty Room (3):''' Set automatically upon check-out or manually. myApps lamp field displays '''"Sporca"'''.
* '''Room Makeup (4):''' Cleaning staff can set this when starting housekeeping tasks, making staff traceable by calling the room. myApps lamp field displays '''"Makeup"'''.
* '''Maintenance Requested (5):''' Indicates the need for maintenance. myApps lamp field displays '''"xxx-Manuten"'''.
* '''Out of Order (6):''' Indicates a room unavailable for guests. myApps lamp field displays '''"xxx-NonDis"'''.

===Installation===

The entire package must be installed in a folder named <code>Files</code>. If the wake-up service is also active, install it within the wake-up folder.

* '''XML Files:''' Two XML files are included: <code>CheckInOut.xml</code> (manages the reception side) and <code>RoomStatus.xml</code> (called by rooms).
* '''Audio Files:''' All audio files are located in the <code>AudioRS</code> subfolder and are provided exclusively in '''G.711a''' format to ensure high quality. Therefore, this codec must be set as exclusive in the command line, for example: <code><nowiki>[http://apps.test.local/test.local/files/root/Hotel/CheckInOut.xml?$_pbxcoder=g711a]</nowiki>(<nowiki>http://apps.test.local/test.local/files/root/Hotel/CheckInOut.xml?$_pbxcoder=g711a</nowiki>)</code>
* '''Parameter Text Files:'''
** <code>RoomLenght.txt</code>: Set the length of room numbers, e.g., <code>3</code> for 3-digit rooms. If set to <code>0</code>, left empty, or deleted, the system requires the hash key after entering the number.
** <code>reception.txt</code>: Set the reception extension number where calls will be forwarded if Do Not Disturb is activated.
* '''PBX Filters:''' The system distinguishes rooms from non-rooms using an associated filter. Ensure that all rooms are assigned either the '''CheckOUT''' or '''CheckIN''' filter in their configuration. Create these two filters (PBX > Filters) with those exact names and configure their rules for the respective states. It is convenient to configure a template for rooms and associate it with them, then assign one of these two filters directly in the user setup (this will serve as the initial system state for that user). Once functional, proceed to configure the reception function keys (direct dial).

===Localization===
This script is delivered with Italian prompts, but you can produce your own prompts and wordings. How see the link at the end of this page.
The filename and prompts are the following:

Filename: Prompt

CheckedIN: “Checked in”

CheckedOUT: “Checked out”

NoRoom: “No room”

NoValidNumber: “No valid number”

InvalidC: “Invalid command”

RoomStatus: “RoomStatus”

Mmenu: “Press 0 for check-out, 1 for check-in or * for status, followed by the room number and confirm with #”

===Known Problems===

== Download ==

*[http://wiki.innovaphone.com/index.php?title=Howto:Wiki_Sources#checkinout Download] the complete file package of scripts and files described in this article.

== Related Articles ==

[[ Howto:Creating_fine_announcements_and_music_on_hold |Creating fine announcements and music on hold]]

[[Category:Howto|{{PAGENAME}}]]
[[Category:Sample|{{PAGENAME}}]]

File:SpiegaItem.png

2026-09-10T14:28:01Z

Kwa:

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-09-24T12:59:58Z

Kwa:

{{DISPLAYTITLE:Howto:Integrating Shelly IoT Devices with the Buttons App}}

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''Buttons App'''.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', '''Shelly Pro2''' and '''Shelly Pro RGBWW''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png|sh01.png/|sh01.png/]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png|sh02.png/|sh02.png/]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png|sh03.png/|sh03.png/]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png|sh04.png/|sh04.png/]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in mind''': You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png|sh05.png/|sh05.png/]]

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png|sh06.png/|sh06.png/]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png|sh07.png/|sh07.png/]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png|sh08.png/|sh08.png/]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png|sh09.png/|sh09.png/]]

Update the Shelly to the current stable firmware version.

After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png|sh10.png/|sh10.png/]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png|sh11.png/|sh11.png/]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png|sh12.png/|sh12.png/]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png|sh13.png/|sh13.png/]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png|sh14.png/|sh14.png/]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/buttons," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png|sh15.png/|sh15.png/]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png|sh16.png/|sh16.png/]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png|sh17.png/|sh17.png/]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png|sh18.png/|sh18.png/]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png|sh19.png/|sh19.png/]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png|sh20.png/|sh20.png/]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png|sh21.png/|sh21.png/]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png|sh22.png/|sh22.png/]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png|sh25.png/|sh25.png/]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png|sh23.png/|sh23.png/]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Shelly RGBWW PM ==
This model is similar to the Shelly Pro 2 (DIN rail mount, LAN), but it has five inputs instead of two and is powered by 24V DC. If you are operating the system on 220V, you will need a transformer.

[[Image:Sh42.png|sh42.png/]]

It is important to note that the external switches connect the 0V line (minus) to the inputs (indicated by the ground symbol in the diagram).

[[Image:Sh41.png|sh41.png/]]

This model has several operating variants, for example, to control colored LED strips. You can set this under Device profile (scroll all the way down), we tested the 5 input operating mode.

[[Image:Sh40.png|sh40.png/]]

The individual inputs (Input 0–4) should be set to Button and Single input. In the Button app, the usual numbering from Serial-0 to Serial-4 will be used.

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png|sh24.png/|sh24.png/]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-08-08T13:04:20Z

Kwa: /* Shelly RGBWW PM */

{{DISPLAYTITLE:Howto:Integrating Shelly IoT Devices with the Buttons App}}

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''Buttons App'''.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', '''Shelly Pro2''' and '''Shelly Pro RGBWW''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png|sh01.png/|sh01.png/]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png|sh02.png/|sh02.png/]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png|sh03.png/|sh03.png/]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png|sh04.png/|sh04.png/]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in mind''': You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png|sh05.png/|sh05.png/]]

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png|sh06.png/|sh06.png/]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png|sh07.png/|sh07.png/]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png|sh08.png/|sh08.png/]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png|sh09.png/|sh09.png/]]

Update the Shelly to the current stable firmware version.

After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png|sh10.png/|sh10.png/]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png|sh11.png/|sh11.png/]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png|sh12.png/|sh12.png/]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png|sh13.png/|sh13.png/]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png|sh14.png/|sh14.png/]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/buttons," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png|sh15.png/|sh15.png/]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png|sh16.png/|sh16.png/]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png|sh17.png/|sh17.png/]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png|sh18.png/|sh18.png/]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png|sh19.png/|sh19.png/]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png|sh20.png/|sh20.png/]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png|sh21.png/|sh21.png/]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png|sh22.png/|sh22.png/]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png|sh25.png/|sh25.png/]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png|sh23.png/|sh23.png/]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Shelly RGBWW PM ==
This model is similar to the Shelly Pro 2 (DIN rail mount, LAN), but it has five inputs instead of two and is powered by 24V DC. If you are operating the system on 220V, you will need a transformer.

[[Image:Sh42.png]]

It is important to note that the external switches connect the 0V line (minus) to the inputs (indicated by the ground symbol in the diagram).

[[Image:Sh41.png]]

This model has several operating variants, for example, to control colored LED strips. You can set this under Device profile (scroll all the way down), we tested the 5 input operating mode.

[[Image:Sh40.png]]

The individual inputs (Input 0–4) should be set to Button and Single input. In the Button app, the usual numbering from Serial-0 to Serial-4 will be used.

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png|sh24.png/|sh24.png/]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-08-08T13:02:48Z

Kwa: /* Introduction */

{{DISPLAYTITLE:Howto:Integrating Shelly IoT Devices with the Buttons App}}

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''Buttons App'''.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', '''Shelly Pro2''' and '''Shelly Pro RGBWW''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png|sh01.png/|sh01.png/]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png|sh02.png/|sh02.png/]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png|sh03.png/|sh03.png/]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png|sh04.png/|sh04.png/]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in mind''': You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png|sh05.png/|sh05.png/]]

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png|sh06.png/|sh06.png/]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png|sh07.png/|sh07.png/]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png|sh08.png/|sh08.png/]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png|sh09.png/|sh09.png/]]

Update the Shelly to the current stable firmware version.

After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png|sh10.png/|sh10.png/]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png|sh11.png/|sh11.png/]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png|sh12.png/|sh12.png/]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png|sh13.png/|sh13.png/]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png|sh14.png/|sh14.png/]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/buttons," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png|sh15.png/|sh15.png/]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png|sh16.png/|sh16.png/]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png|sh17.png/|sh17.png/]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png|sh18.png/|sh18.png/]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png|sh19.png/|sh19.png/]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png|sh20.png/|sh20.png/]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png|sh21.png/|sh21.png/]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png|sh22.png/|sh22.png/]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png|sh25.png/|sh25.png/]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png|sh23.png/|sh23.png/]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Shelly RGBWW PM ==
This model is similar to the Shelly Pro 2 (DIN rail mount, LAN), but it has five inputs instead of two and is powered by 24V DC. If you are operating the system on 220V, you will need a transformer.

[[Image:Sh42.png]]

It is important to note that the external switches connect the 0V line (minus) to the inputs (indicated by the ground symbol in the diagram).

[[Image:Sh41.png]]

This model has several operating variants, for example, to control colored LED strips. You can set this under Device profile (scroll all the way down).

[[Image:Sh40.png]]

The individual inputs (Input 0–4) should be set to Button and Single input. In the Button app, the usual numbering from Serial-0 to Serial-4 will be used.

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png|sh24.png/|sh24.png/]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-08-08T13:02:32Z

Kwa: /* Introduction */

{{DISPLAYTITLE:Howto:Integrating Shelly IoT Devices with the Buttons App}}

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''Buttons App'''.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', '''Shelly Pro2''' and '''Shelly Pro RGBWW'''models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png|sh01.png/|sh01.png/]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png|sh02.png/|sh02.png/]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png|sh03.png/|sh03.png/]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png|sh04.png/|sh04.png/]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in mind''': You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png|sh05.png/|sh05.png/]]

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png|sh06.png/|sh06.png/]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png|sh07.png/|sh07.png/]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png|sh08.png/|sh08.png/]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png|sh09.png/|sh09.png/]]

Update the Shelly to the current stable firmware version.

After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png|sh10.png/|sh10.png/]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png|sh11.png/|sh11.png/]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png|sh12.png/|sh12.png/]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png|sh13.png/|sh13.png/]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png|sh14.png/|sh14.png/]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/buttons," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png|sh15.png/|sh15.png/]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png|sh16.png/|sh16.png/]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png|sh17.png/|sh17.png/]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png|sh18.png/|sh18.png/]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png|sh19.png/|sh19.png/]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png|sh20.png/|sh20.png/]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png|sh21.png/|sh21.png/]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png|sh22.png/|sh22.png/]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png|sh25.png/|sh25.png/]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png|sh23.png/|sh23.png/]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Shelly RGBWW PM ==
This model is similar to the Shelly Pro 2 (DIN rail mount, LAN), but it has five inputs instead of two and is powered by 24V DC. If you are operating the system on 220V, you will need a transformer.

[[Image:Sh42.png]]

It is important to note that the external switches connect the 0V line (minus) to the inputs (indicated by the ground symbol in the diagram).

[[Image:Sh41.png]]

This model has several operating variants, for example, to control colored LED strips. You can set this under Device profile (scroll all the way down).

[[Image:Sh40.png]]

The individual inputs (Input 0–4) should be set to Button and Single input. In the Button app, the usual numbering from Serial-0 to Serial-4 will be used.

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png|sh24.png/|sh24.png/]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-08-08T13:01:53Z

Kwa: /* Shelly Pro 2 */

{{DISPLAYTITLE:Howto:Integrating Shelly IoT Devices with the Buttons App}}

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''Buttons App'''.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', and '''Shelly Pro2''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png|sh01.png/|sh01.png/]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png|sh02.png/|sh02.png/]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png|sh03.png/|sh03.png/]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png|sh04.png/|sh04.png/]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in mind''': You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png|sh05.png/|sh05.png/]]

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png|sh06.png/|sh06.png/]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png|sh07.png/|sh07.png/]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png|sh08.png/|sh08.png/]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png|sh09.png/|sh09.png/]]

Update the Shelly to the current stable firmware version.

After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png|sh10.png/|sh10.png/]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png|sh11.png/|sh11.png/]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png|sh12.png/|sh12.png/]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png|sh13.png/|sh13.png/]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png|sh14.png/|sh14.png/]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/buttons," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png|sh15.png/|sh15.png/]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png|sh16.png/|sh16.png/]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png|sh17.png/|sh17.png/]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png|sh18.png/|sh18.png/]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png|sh19.png/|sh19.png/]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png|sh20.png/|sh20.png/]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png|sh21.png/|sh21.png/]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png|sh22.png/|sh22.png/]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png|sh25.png/|sh25.png/]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png|sh23.png/|sh23.png/]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Shelly RGBWW PM ==
This model is similar to the Shelly Pro 2 (DIN rail mount, LAN), but it has five inputs instead of two and is powered by 24V DC. If you are operating the system on 220V, you will need a transformer.

[[Image:Sh42.png]]

It is important to note that the external switches connect the 0V line (minus) to the inputs (indicated by the ground symbol in the diagram).

[[Image:Sh41.png]]

This model has several operating variants, for example, to control colored LED strips. You can set this under Device profile (scroll all the way down).

[[Image:Sh40.png]]

The individual inputs (Input 0–4) should be set to Button and Single input. In the Button app, the usual numbering from Serial-0 to Serial-4 will be used.

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png|sh24.png/|sh24.png/]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

File:Sh42.png

2025-08-08T12:59:38Z

Kwa:

File:Sh41.png

2025-08-08T12:59:26Z

Kwa:

File:Sh40.png

2025-08-08T12:59:13Z

Kwa:

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-08-08T12:29:26Z

Kwa:

{{DISPLAYTITLE:Howto:Integrating Shelly IoT Devices with the Buttons App}}

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''Buttons App'''.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', and '''Shelly Pro2''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png|sh01.png/|sh01.png/]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png|sh02.png/|sh02.png/]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png|sh03.png/|sh03.png/]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png|sh04.png/|sh04.png/]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in mind''': You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png|sh05.png/|sh05.png/]]

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png|sh06.png/|sh06.png/]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png|sh07.png/|sh07.png/]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png|sh08.png/|sh08.png/]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png|sh09.png/|sh09.png/]]

Update the Shelly to the current stable firmware version.

After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png|sh10.png/|sh10.png/]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png|sh11.png/|sh11.png/]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png|sh12.png/|sh12.png/]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png|sh13.png/|sh13.png/]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png|sh14.png/|sh14.png/]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/buttons," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png|sh15.png/|sh15.png/]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png|sh16.png/|sh16.png/]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png|sh17.png/|sh17.png/]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png|sh18.png/|sh18.png/]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png|sh19.png/|sh19.png/]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png|sh20.png/|sh20.png/]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png|sh21.png/|sh21.png/]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png|sh22.png/|sh22.png/]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png|sh25.png/|sh25.png/]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png|sh23.png/|sh23.png/]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png|sh24.png/|sh24.png/]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-07-17T08:20:06Z

Kwa:

{{DISPLAYTITLE:Howto:Integrating Shelly IoT Devices with the Buttons App}}

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''Buttons App'''.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', and '''Shelly Pro2''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC. We have not tested this setup and will not describe it in this guide.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png|sh01.png/|sh01.png/]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png|sh02.png/|sh02.png/]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png|sh03.png/|sh03.png/]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png|sh04.png/|sh04.png/]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in mind''': You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png|sh05.png/|sh05.png/]]

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png|sh06.png/|sh06.png/]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png|sh07.png/|sh07.png/]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png|sh08.png/|sh08.png/]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png|sh09.png/|sh09.png/]]

Update the Shelly to the current stable firmware version.

After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png|sh10.png/|sh10.png/]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png|sh11.png/|sh11.png/]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png|sh12.png/|sh12.png/]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png|sh13.png/|sh13.png/]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png|sh14.png/|sh14.png/]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/buttons," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png|sh15.png/|sh15.png/]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png|sh16.png/|sh16.png/]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png|sh17.png/|sh17.png/]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png|sh18.png/|sh18.png/]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png|sh19.png/|sh19.png/]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png|sh20.png/|sh20.png/]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png|sh21.png/|sh21.png/]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png|sh22.png/|sh22.png/]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png|sh25.png/|sh25.png/]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png|sh23.png/|sh23.png/]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png|sh24.png/|sh24.png/]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-07-17T08:19:05Z

Kwa:

{{DISPLAYTITLE:Howto:Integrating Shelly IoT Devices with the Buttons App}}
{{DISPLAYTITLE:Howto:Integrating Shelly IoT Devices with the Buttons App}}

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''Buttons App'''.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', and '''Shelly Pro2''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC. We have not tested this setup and will not describe it in this guide.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png|sh01.png/|sh01.png/]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png|sh02.png/|sh02.png/]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png|sh03.png/|sh03.png/]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png|sh04.png/|sh04.png/]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in mind''': You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png|sh05.png/|sh05.png/]]

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png|sh06.png/|sh06.png/]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png|sh07.png/|sh07.png/]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png|sh08.png/|sh08.png/]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png|sh09.png/|sh09.png/]]

Update the Shelly to the current stable firmware version.

After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png|sh10.png/|sh10.png/]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png|sh11.png/|sh11.png/]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png|sh12.png/|sh12.png/]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png|sh13.png/|sh13.png/]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png|sh14.png/|sh14.png/]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/buttons," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png|sh15.png/|sh15.png/]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png|sh16.png/|sh16.png/]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png|sh17.png/|sh17.png/]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png|sh18.png/|sh18.png/]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png|sh19.png/|sh19.png/]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png|sh20.png/|sh20.png/]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png|sh21.png/|sh21.png/]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png|sh22.png/|sh22.png/]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png|sh25.png/|sh25.png/]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png|sh23.png/|sh23.png/]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png|sh24.png/|sh24.png/]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-07-17T08:18:10Z

Kwa:

{{DISPLAYTITLE:Howto:Integrating Shelly IoT Devices with the Buttons App}}

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''Buttons App'''.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', and '''Shelly Pro2''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC. We have not tested this setup and will not describe it in this guide.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png|sh01.png/]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png|sh02.png/]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png|sh03.png/]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png|sh04.png/]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in mind''': You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png|sh05.png/]]

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png|sh06.png/]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png|sh07.png/]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png|sh08.png/]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png|sh09.png/]]

Update the Shelly to the current stable firmware version.

After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png|sh10.png/]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png|sh11.png/]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png|sh12.png/]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png|sh13.png/]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png|sh14.png/]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/buttons," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png|sh15.png/]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png|sh16.png/]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png|sh17.png/]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png|sh18.png/]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png|sh19.png/]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png|sh20.png/]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png|sh21.png/]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png|sh22.png/]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png|sh25.png/]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png|sh23.png/]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png|sh24.png/]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-07-17T08:02:43Z

Kwa:

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''Buttons App'''.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', and '''Shelly Pro2''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC. We have not tested this setup and will not describe it in this guide.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in mind''': You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png]]

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png]]

Update the Shelly to the current stable firmware version.

After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/buttons," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-07-16T15:33:37Z

Kwa:

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the innovaphone Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the innovaphone Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''innovaphone Buttons Ap'''p.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', and '''Shelly Pro2''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an innovaphone application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC. We have not tested this setup and will not describe it in this guide.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in mind''': You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png]]

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png]]

Update the Shelly to the current stable firmware version.

After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/buttons," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Reference15r1:Concept Buttons App

2025-07-16T14:32:25Z

Kwa:

[[Category:Concept|Apps]]
[[Category:Concept App Service Buttons]]
== Applies To ==

* innovaphone from version 15r1

== Overview ==

The myApps Buttons App is an open source app that deals with the integration of IoT devices and PBX features as triggers. In principle, it is about linking certain input triggers to various output actions

== Installation ==
Go to the '''Settings App''' (PBX manager) and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''
* In the search field located on the top right corner of the store, search for '''"Buttons"''' and click on it
* Select the proper firmware version, for example '''"Version 15r1"''' and click on install
* Tick "I accept the terms of use" and continue by clicking on the install yellow button
* Wait until the install has been finished
* Close and reopen the '''Settings App''' (PBX manager) again in order to refresh the list of the available colored AP plugin
* Click on the '''"Buttons"''' and click on '''" + Add an App"''' and then on the '''"Buttons"''' button.
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: Buttons, SIP: buttons''
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good

'''Buttons User'''

* You also need a separate User Object in the pbx which is used from the buttons app. The app will register on this object for...
** '''calls'''
*** an incoming call to this user will be used as trigger. therefor the incoming '''cgpn''' and sip of the internal caller and the '''cdpn''' as destination is used.
*** Triggernumber '''"99"''' is reserved for Working Toggle. All other destination can be defined per user.
*** you can setup MWI-Function keys to the number of the buttons-user + append own number checkmark.
**** in the MWI Key example you will see the 8599 which combines the number of the buttons user "85" with the triggerbumber "99" for working toggle
** '''chat'''
*** if you want to use outgoing chats from the app you have to assign the chat app to this user
*** place "chat" in the Home Screen Apps. Just type it in like this.

[[File:Buttons-mwi-working.png|thumb|none|/Buttons-mwi-working.png|/Buttons-mwi-working.png]]
[[File:Buttosapp user chat.png|thumb|none|/Buttosapp_user_chat.png|/Buttosapp_user_chat.png]]

== Buttons App - Overview ==
Every mentioned Input Trigger can be multiple combined wit output actions.

[[Image:Buttons overview.png|700px|/Buttons_overview.png|/Buttons_overview.png]]

=== Input trigger ===
===== PhoneKeys / Dial In =====
The Buttons app can be made available for calls via a dial-in number. This involves a comparison of the caller (cgpn, sip) and the number called (cdpn).

===== myApps Windows Client (Hotkey) =====
In the '''myApps Windows Launcher''', buttons can be assigned a hotkey. To do this, append the parameter <code>?hotkey=[number]</code> to the name of the app object.

'''Example:'''

If your app object is named '''"buttons"''' and you want to assign hotkey number '''1''', the entry would be: buttons?hotkey=1

===== Shelly Devices =====
Shelly devices can be used as trigger devices in the Buttons app. To do this, the app opens another web socket below the app path. The path name is “/shelly ”

For example: [https://your-app-platforn-dns/domain.com/buttons/shelly wss://your-app-platforn-dns/domain.com/buttons/shelly]

Most Devices that can establish an outgoing websocket are supported. You can also work with BLE devices if you have a BLE gateway or other Shelly device that is capable of both BLE and Websocket, so that it could work as gateway for BLE signals.

You can also take a look to this video. https://www.youtube.com/watch?v=lkMEf7CpXHo

====== Buttons ======
We have tested with Shelly BLU Button1 and Shelly BLU Gateway, but you can also use an other Shelly PRO or PLUS Device to handle BLE signals.

====== Windows-/ Door Sensor ======
We have tested with Shelly BLU Door/Window and Shelly BLU Gateway

====== Motionsensor ======
We have tested with Shelly BLU Motion and Shelly BLU Gateway

====== Webhook (''RestApi'') ======
In the SettingsPlugin (PbxManager), you can define an '''http-path''' and an '''http-api-key''' that can be used by general systems to perform general actions (e.g., monitoring). The idea is that server-based communication is combined with dynamic output actions, which are not triggered by user interaction.

The path and api-key a added to the reachable base url of the buttons app + /extapi. So, if your base url looks like this [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/] and you api-key is "Secretkey1234", the url looks like this, to do a Post to Connect App via Buttons App.

* Example: [https://APP-PLATFORM/domaine.de/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234 https://app-dnsname/test.local/buttons/extapi/mypath?key=Secretkey1234&msg=Test&dst=atlantis&type=connect&tags=abcd,1234]

======''Webhook Get Parameters''======

* key: your http-api, which you can define via SettingsPlugin
* type: type of output. at the moment only "connect" is possible.
* dst: destination for the action
* tags: tagging parameters for Connect Post
* msg: the content for your action.
* callto: (in case of Connect Post), also a call to a destination can be trigged
* srcqueue: the Waiting Queue Object, which should be used for the outgoing call. (you have to define it in the buttons-admin before).
* numbers:in case of call, a comma separated list of numbers can be placed, which should be get the call from the Waiting Queue Object

=== Output actions ===
===== Chat =====
Buttons allow you to send a chatmessage to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send.

===== Notify =====
Buttons allow you to a notify a to a reachable user. Simply enter the SIP (or H.323) name of the destination and the message you wish to send. A Notifiy is just a notification to the client and works with the notification policies of the used client.

===== Chat + Notify =====
This is a combination of both in one rule.

===== Presence =====
You can set the presence of users. In case of the buttons-user app, it's to the own user.

===== Phonemessage =====
Similiar to Chat, but it sends messages to innovaphone DesktPhones. As destination you can use the number or the name.

===== Phonecall =====
You need to assign a Waiting Queue via Buttons-Admin App. After that, this Waiting Queue is used to perform outgoing calls and stream the announcement. The Waiting Queue needs a special configuration. => '''<u>Alert Timout = 0</u>''' otherwise it would not work.

===== Connect App=====
If the Connect App is assigend to the buttons-user AppObject, buttons is able to create ConnectPosts. Also if you combine ConnectPosts and Calls with the same trigger actions, also interactions of the phonecalls are presented to the Connect Post.

===== Working App=====
If the Working App is assigned to the buttons-user AppObject, buttons is able to control your Working App. Also the Dial In Number "99" is reservered for Working Toggle. So, if your dial in number for buttons is 85, you can call 8599 from your extension and your working status is toggled.

You can also create own rules for working-start or working-stop

== Buttons App - Configuration ==

We have created a short configuration tutorial on youtube.

https://www.youtube.com/watch?v=ut3NI59BNl4

== Troubleshooting ==

== Related Articles ==

[[Howto:Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-07-16T14:08:51Z

Kwa:

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the innovaphone Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the innovaphone Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''innovaphone Buttons Ap'''p.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', and '''Shelly Pro2''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an innovaphone application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC. We have not tested this setup and will not describe it in this guide.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in mind''': You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png]]

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png]]

Update the Shelly to the current stable firmware version.

After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/buttons," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-07-16T14:04:03Z

Kwa:

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the innovaphone Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the innovaphone Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''innovaphone Buttons Ap'''p.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', and '''Shelly Pro2''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an innovaphone application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC. We have not tested this setup and will not describe it in this guide.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in mind''': You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png]]

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png]]

Update the Shelly to the current stable firmware version. After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/button," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-07-16T14:00:55Z

Kwa:

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the innovaphone Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the innovaphone Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App.

It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''innovaphone Buttons Ap'''p.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', and '''Shelly Pro2''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an innovaphone application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the Buttons concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC. We have not tested this setup and will not describe it in this guide.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in min'''d: You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png]]

Here's a refined and improved English version of the entire text you provided, covering initial setup, connection details, and specific Shelly models, along with debugging.

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png]]

Update the Shelly to the current stable firmware version. After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/button," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-07-16T13:54:13Z

Kwa:

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the innovaphone Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the innovaphone Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App. It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''innovaphone Buttons Ap'''p.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', and '''Shelly Pro2''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an innovaphone application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC. We have not tested this setup and will not describe it in this guide.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in min'''d: You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png]]

Here's a refined and improved English version of the entire text you provided, covering initial setup, connection details, and specific Shelly models, along with debugging.

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png]]

Update the Shelly to the current stable firmware version. After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/button," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Shelly i4 (3rd Generation) ==
This model features 4 digital inputs (ON/OFF).

[[Image:Sh19.png]]

In the Shelly App, you'll see 4 "devices" (which is actually just one physical device), and each contact will be treated as if it were a single device.

The Shelly i4 Gen3 has 4 inputs (from port 0 to port 3, corresponding to SW1 to SW4), and all messages will be sent with the same serial number.

To add a Shelly i4 port to the Buttons App, press "Add Device," then under "New Device," select "Button" as the type, and enter the serial number followed by a hyphen "-" and the port number:

[[Image:Sh20.png]]

In the example above, we've created the connection with the first port (SW1); the second port (SW2) will be device e4b063d6a588-1, and so on.

== Shelly Plus 1 ==
The Shelly Plus 1 has one input and one output.

[[Image:Sh21.png]]

Similar to the Shelly i4, the input port should be indicated with "-0":

[[Image:Sh22.png]]

In the example above, the serial number for the Shelly Plus 1 is 78ee4ccf5930.

== Shelly Pro 2 ==
The Shelly Pro differentiates itself from other Shelly devices as it's designed exclusively for DIN rail mounting in electrical cabinets:

[[Image:Sh25.png]]

It also features a LAN port, allowing it to connect to an Ethernet network even without Wi-Fi or Bluetooth (though both are onboard). It doesn't require an internet connection, but it can be useful for initial setup and firmware updates.

It has two inputs and two outputs, all designed exclusively for 220V circuits (110-240 VAC 50/60 Hz).

It's configured similarly to the other Shelly devices described above, but with the key difference that triggering by the Buttons App occurs on the '''outputs'''. The Buttons App therefore reacts to changes in the state of the outputs, regardless of whether they are switched via the web or other settings. If you want to transmit the state of the inputs (as in the case of the other Shelly models described), you'll need to configure the Shelly Pro 2 for its outputs to follow the state of its inputs.

Here's an example of this setting, where the input port (input 0) controls the output port (output 0):

[[Image:Sh23.png]]

Note that in the setup above, even after a restart, the output will follow the current state of the input (which is usually the desired behavior).

Once you've set the Ethernet parameters (Client, Server, and Static IP modes are available), you can disable Wi-Fi settings, cloud settings, and "Access Point" mode (which also disables "Range extender" mode).

'''Note''': With Wi-Fi disabled, you will no longer be able to access the Shelly Pro 2 from the Shelly App. However, the application remembers the settings you configured before disabling Wi-Fi access. This can be helpful if, for example, you want to check the IP address (unless it has been changed via LAN access).

== Debugging ==
Traffic between the Shelly and the Buttons App (once registered) can be monitored in the Buttons App's Log.

In the Application Platform (where you retrieved the path before), clear the Log, perform a contact closure or opening operation, and then select "Display" from the dropdown menu. A new page will open in your browser:

[[Image:Sh24.png]]

In the example above, you can see that the Shelly Device model "shellypro2" with serial number "ec626091d3f4" is sending a detected change on input and output "0" and activating "Trigger Switch 6," which sets user 'kwa's presence to "busy."

'''Note''': Changing the presence status is the simplest way to verify proper functionality and requires no additional setup.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-07-16T13:46:50Z

Kwa:

'''DRAFT'''

Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the innovaphone Buttons App.

The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions. That's because the innovaphone Buttons App allows you to assign a series of parallel actions to any specific event.

In this document, we'll walk you through every step of integrating your Shelly devices with the Buttons App. It's surprisingly straightforward - let's get started!

==Applies To==
• myApps V15r3 or higher

• Buttons App V15r4 or higher

Note: Tests with Shelly devices were conducted using Shelly firmware version 1.6.2.


==Introduction==
This article provides a straightforward explanation of the basic concepts needed to integrate '''Shelly devices''' with the '''innovaphone Buttons Ap'''p.

Please note: We are not Shelly specialists. For detailed information, consult the manufacturer's documentation, as well as the many forums and videos available online on this topic.

In this guide, we will specifically cover the integration of digital inputs (contacts) for the '''Shelly i4''', '''Shelly Plus1''', and '''Shelly Pro2''' models.

While motion sensors and the Shelly USB dongle can also be integrated, they are not covered in this article. However, as Shelly products share similar characteristics, you'll likely find useful insights applicable to other models as well.

Each Shelly device comes with its own mounting instructions; here, we will only briefly touch upon a few key details.

I'''t is crucial to read and strictly adhere to all safety guidelines.'''

These devices are typically powered by hazardous voltages (usually 220V in Europe). Installing a residual current device (RCD), also known as a ground-fault circuit interrupter (GFCI) in some regions, upstream in the electrical circuit is highly recommended and, in some countries, legally required.

===Overview===
The Buttons App is an innovaphone application that lets you link specific input events to various output actions. Examples of input events include calls, function keys on innovaphone IP phones, and other applications, as well as the messages received from Shelly devices. Output actions can be calls, notifications, chats, messages, or applications.

For a comprehensive description of the Buttons App itself and a complete list of supported input and output devices, refer to the concept article (link at the end of this document).

===Electrical Connections===
The Shelly models discussed in this article are powered by 110 to 240 Volt AC, 50/60 Hz. Please be aware that these voltages are hazardous. Never work on electrical networks without a residual current device (RCD/GFCI) installed. Before mounting or connecting any device, ensure that all wires (not just the live wire, but also the neutral) are disconnected.

Some models can also be powered by 12V or 24-48V DC. We have not tested this setup and will not describe it in this guide.

Third-generation Shelly devices feature polarity protection on the AC side. This means the Shelly will function correctly even if the live (L) and neutral (N) wires are inverted.

'''Important Note''': In networks with delta connections, both wires carry voltage.

For intrinsic safety reasons, it's often common practice to switch the neutral wire, which typically carries no voltage during normal operation. The drawback of this approach is that troubleshooting a potential interruption becomes more difficult (whereas with the live wire, a simple voltage tester suffices to follow the line). Both wiring variants are functional.

'''Note''': Shelly devices typically have the wiring diagram silk-screened directly on them, as shown in this example for the Shelly i4:

[[Image:Sh01.png]]

It represents the connections to the outside world, not the internal operation of the device, as further highlighted in the instructions:

[[Image:Sh02.png]]

'''Note''': As per the diagram, the Live (L) phase is connected to the output towards the contacts. If installed within the same electrical network, it's also possible to power the inputs directly from the live phase, rather than using the Shelly's output. However, in this case, ensure the polarity matches the diagram (L and N as shown). If inverted, you'll need to switch the neutral.

'''Note''': On Shelly Pro devices, the silk-screened diagram corresponds exactly to what's detailed in the instructions.

[[Image:Sh03.png]]

===Contacts===
Shelly devices are incredibly versatile, reacting to both the '''closing and opening''' of a contact. What's more, they send messages for various interactions like a quick '''click''' (fast open-close), '''double-click''', '''triple-click''', and even a '''prolonged closure''' (a "Long" press). This "Long" event is also sent for a static closure after a timeout, making it perfect for sustained button presses. The Buttons App can handle all these event types, individually or in combination, giving you immense flexibility.

In safety circuits, contacts are typically normally closed and open in the event of an alarm. This design ensures that a broken wire will also trigger a detection, enhancing safety.

Both Shelly and the Buttons App can be used with circuits featuring:

• Normally open contacts that close and remain closed.

• Normally closed contacts that open and remain open.

• Momentary contacts that close or open (like a push-button).

All transitions, meaning the change from one state to another, will be signaled and can be utilized for various actions.

If a Shelly device restarts, its current status is immediately reported to the Buttons App. Should the contact state change during a restart or while the device is powered off, this new state will be transmitted to the Buttons App, which will then react accordingly.

===Mounting===
For their "home" models, which are designed for installation in standard electrical boxes (typically for light switches), Shelly offers a DIN rail adapter. This allows for easy mounting in electrical cabinets:

[[Image:Sh04.png]]

The adapter features an opening on the back, allowing access to the reset button.

'''Keep in min'''d: You can only press this button if no other devices are installed close by on the DIN rail. The adapter can be mounted 180 degrees, making the reset button accessible from either the right or left side. Once configured, you typically won't need to use the physical reset button, as a reset can also be performed via the app or web interface if the device is reachable by IP. After a restart, the device's status is also refreshed.

In contrast, '''Pro models''' are designed exclusively for DIN rail mounting and have their reset button conveniently located on the front, accessible even with the cover closed. They also offer options to customize the behavior of the reset button.

[[Image:Sh05.png]]

Here's a refined and improved English version of the entire text you provided, covering initial setup, connection details, and specific Shelly models, along with debugging.

==Configuration==

===First Steps with Shelly Configuration===
Once a Shelly device is powered on, it starts up and is ready for use in approximately 5 seconds.

Shelly devices can be accessed via Wi-Fi or Bluetooth. The "Pro" family of devices can also be reached via an Ethernet connection.

'''Note''': Some products are also accessible via USB dongles, but this is not covered here.

For initial configuration, you'll need to install the manufacturer's '''Shelly Smart Control app''' on your smartphone. Afterward, you'll establish a Wi-Fi or Bluetooth connection between your smartphone and the Shelly device. For our application, Bluetooth is primarily used for the initial setup; subsequently, the device will connect to a local Wi-Fi network or, in the case of Pro models, your local area network (LAN).

Download and install the Shelly Smart Control application from your respective app store (Google Play or Apple App Store):

[[Image:Sh06.png]]

If you don't already have one, create a Shelly account (it is free).

You'll be prompted to set up the parameters for your local Wi-Fi network, which the device will then connect to. To make the device discoverable by your smartphone, press the reset button on the Shelly device for 10 seconds. Follow the app's instructions to add the device to your list.

'''Important Note''': A device initially registers with the Shelly manufacturer's platform, where its serial number is apparently stored. Once a device has been registered to one account, it '''cannot be registered to another account''', even after a factory reset of the Shelly. If a device is registered to your account, no one else can use it unless you first delete it from your account. This is presumed to be a security feature designed to protect a specific device from unauthorized use.

In the Shelly ecosystem, the '''serial number and MAC address are the same'''. Each Shelly device will register with its unique address to the Buttons App. If a device has multiple inputs or outputs, it will still have a single address, and the interface number will be contained within the message itself, even if they appear as distinct devices in the Shelly App.

===Initial Setup===
After adding your Shelly devices to your application, you can access the individual installed models. The example below shows the page for a Shelly i4, which offers four inputs:

[[Image:Sh07.png]]

At this stage, you can observe the opening and closing of contacts directly in the app; the display shows the status changes in real time. In the example above, contacts (inputs) 2 and 3 are closed, while contacts 1 and 4 are open. This test is convenient for verifying inputs but is not strictly necessary.

Clicking on any of the Shelly devices opens its configuration page. Here, you'll find the IP address at which the device is accessible via a web browser:

[[Image:Sh08.png]]

Access now the device via your browser, select "Settings," then "Firmware":

[[Image:Sh09.png]]

Update the Shelly to the current stable firmware version. After the required restart, return to the home page and select an input, for example, "Input(0)," and then "Input/Output settings":

[[Image:Sh10.png]]

If you have a '''Plus or i4 model''', select "Button" (the default setting is "Switch"). Repeat this setting for all inputs.
If you have a Pro model, this setting is different and described in its dedicated section below.

===Connecting Shelly and the Buttons App===
Shelly devices must register with the Buttons App to send status messages. Therefore, each Shelly device needs to be configured with the destination path to the Buttons App.

This path is configured on the Shelly in the menu "Settings," then "Outbound websocket":

[[Image:Sh11.png]]

Check "Enable," then under "Connection Type," select "TLS no validation."

The path is configured in the "Server:" field.

The format is: “'''wss:// + destination + /shelly'''”.

Here's how to securely and easily determine the "destination":

Open the PBX advanced interface (devices) and then the "PBX" page. In the "DNS" field, you'll find the name of your PBX:

[[Image:Sh12.png]]

Make a note of this name, as it's the first part of your destination. Now, open the Application Platform and select the Buttons App.

'''Note''': If the Buttons App isn't installed, now is the time to install it on your Application Platform:

[[Image:Sh13.png]]

Clicking on "Buttons" will reveal the Webserver path:

[[Image:Sh14.png]]

Notice that the path ends with "buttons".

The complete path to enter into the Shelly will be composed of these two names.

For example, if your PBX DNS is "testpbx.com" and the Buttons App Webserver path is "butt.mypbx.com/button," the complete destination path to set in the Shelly will be:
“wss://testpbx.com/butt.mypbx.com/buttons/shelly”

Once correctly configured and put in the Server input field, the Shelly device will be registered with the Buttons App and start sending messages.

To verify registration, open the Buttons Admin App:

[[Image:Sh15.png]]

Clicking on the "Connected devices" button will display the name and serial number of the connected and registered Shelly devices:

[[Image:Sh16.png]]

In the example above, three Shelly devices (Plus 1, Pro 2, and i4) are connected.

This screen also shows the Shelly's serial number, which you'll need later to set up the Buttons App. You can also find the Shelly serial number on the Shelly's "Wifi" page:

[[Image:Sh17.png]]

'''Cautio'''n: The address shown in the Shelly's "Bluetooth" menu is different and will not be used by the Buttons App. For the Shelly Pro, the serial number is visible on the "Ethernet" page:

[[Image:Sh18.png]]

'''Note''': You can copy and paste the serial number into the Buttons App even with colons; they will be automatically discarded by the Buttons App.

'''Note''': You can also retrieve the serial numbers directly from the logging, as explained in the relevant section.

== Related Articles ==

[[Reference15r1:Concept_Buttons_App]]

[[Category:Howto|Integrating_Shelly_IoT_Devices_with_the_innovaphone_Buttons_App]]

File:Sh10.png

2025-07-16T13:40:46Z

Kwa:

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-07-16T13:31:47Z

Kwa:

Howto:Integrating Shelly IoT Devices with the innovaphone Buttons App

2025-07-16T13:11:48Z

Kwa: Created page with "'''DRAFT''' Shelly, a European (Bulgarian) manufacturer, offers a wide range of Internet of Things (IoT) sensors and actuators. This article will guide you through setting up and using Shelly digital inputs (contacts) to interact seamlessly with the innovaphone Buttons App. The possibilities are truly endless! Imagine triggering a phone call when a door contact closes, sending an instant message, initiating time tracking, or even setting up complex conditional actions...."

File:Sh25.png

2025-07-16T13:01:20Z

Kwa:

File:Sh24.png

2025-07-16T13:01:06Z

Kwa:

File:Sh23.png

2025-07-16T13:00:57Z

Kwa:

File:Sh22.png

2025-07-16T13:00:46Z

Kwa:

File:Sh21.png

2025-07-16T13:00:36Z

Kwa:

File:Sh20.png

2025-07-16T13:00:25Z

Kwa:

File:Sh19.png

2025-07-16T13:00:16Z

Kwa:

File:Sh18.png

2025-07-16T13:00:04Z

Kwa:

File:Sh17.png

2025-07-16T12:59:52Z

Kwa:

File:Sh16.png

2025-07-16T12:59:40Z

Kwa:

File:Sh15.png

2025-07-16T12:59:31Z

Kwa:

File:Sh14.png

2025-07-16T12:59:20Z

Kwa:

File:Sh13.png

2025-07-16T12:58:59Z

Kwa:

File:Sh12.png

2025-07-16T12:58:49Z

Kwa:

File:Sh11.png

2025-07-16T12:58:15Z

Kwa:

File:Sh09.png

2025-07-16T12:57:55Z

Kwa:

File:Sh08.png

2025-07-16T12:57:44Z

Kwa:

File:Sh07.png

2025-07-16T12:57:30Z

Kwa: