-
Notifications
You must be signed in to change notification settings - Fork 0
Recommended Trigger Configurations
Depending on the number of Shelly devices, you may want to optimize your triggers. At the moment, this number is unknown.
Assuming the default Shelly configuration (devices connect to shellies/<their_unique_identifier>), a single trigger can handle your entire Shelly ecosystem. (This assumes they are all on the same Broker)
You will configure the trigger to listen for any messages that are on the shellies/ base topic. This will capture all device activity including announce messages used for auto-discovery. This trigger will queue every message with the same message type. All of your Shelly devices in Indigo will be configured to use this single message type.
This requires a configuration change from within the Shelly interface (via the web interface or mobile app). Instead of having all devices on shellies/<their_unique_identifier>, you could modify this to categorize devices into smaller groups.
You have multiple Shelly devices in different rooms in a house. There are 5 devices in the Living Room, 4 devices in the Master Bedroom, 2 devices in the Laundry Room, and 8 that control outdoor devices.
This is a total of 19 active devices in 4 rooms or "zones". You could modify the devices individually to include the zone in the topic. So you would configure the custom MQTT prefix's as:
shellies/living_room/<unique_identifier>shellies/master_bedroom/<unique_identifier>shellies/laundry_room/<unique_identifier>shellies/outdoors/<unique_identifier>
All devices would still publish their announce messages to shellies/announce.
You would need to setup 5 different triggers. Each trigger would trigger on the above topics and would queue the messages using different message types. Each message type would correspond to the different zones. The Indigo devices would be configured to use the shared announce message type, but use their "zoned" message types.
This will reduce the traffic that the Indigo devices must individually process because there will be a lesser volume of messages in that zone.
This is less than ideal because this requires that you create a new trigger for each new device you add. If this is the desired option, then you ARE able to have a single trigger that will queue the "announce" messages. Each Indigo Shelly device requires that you provide a message type, but also allows you to specify a different message type for receiving announce messages.