ShellyMQTT

Fixes

• Creating or modifying triggers previously caused errors in the log
• #96 Removes repeated logging when an RGBW2 (White) device reports an off state
• #97 Removes repeated logging when an RGBW2 (Color) device reports an off state
• #98 Removes logging for Shelly relays when the sw-input state changes

Adds

• #73 Support for Shelly Gas

Known Issues

• Creating and modifying triggers might show errors in the log. This is resolved in ShellyMQTT v0.3.0

Fixed

• #86 Shelly relay devices now support the correct input events (falsely supported advanced events previously)
• #90 Other EM/3EM Meter devices can be used for templates of other Meter devices

Known Issues

• Creating and modifying triggers might show errors in the log. This is resolved in ShellyMQTT v0.3.0

Fixed

• #81 Device discovery works correctly when setting up the very first device
• #88 Topics are no longer automatically subscribed to, so a simple wildcard subscription will make the broker UI cleaner (users should ensure they are manually subscribing to the wildcard that will capture all shelly traffic: shellies/#)
• #89 Detailed logging can be disabled with the option to select which logging levels to show in the log

Added

• #56 Low-battery events
• #74 Support for the Shelly Door/Window2
• #75 Support for the Shelly Button1

Fixed

• #87 Event counts are now properly handled on device restarts

Added

• #76 Support for Shelly i3
• #78 All devices now read input events which can be triggered from (ex: single press, double press, etc.)

Fixed

• #83 Device name changes are properly handled without requiring a device restart

Added

• #77 Devices with power limits will report the requested power draw that triggered an overpower event. Overpower events are able to be triggered upon on a global or per-device basis using the new trigger events

Fixed

• #79 The Shelly 1PM config interface was updated to add a missing divider

Possible Breaking Changes

• #80 The Shelly Door/Window device definition is updated from a "custom" device to a "sensor" device. No changes are visible in the interface, but triggers may need to be updated as the status state is no longer available. The change should be automatic, but unexpected behavior can be fixed by changing the device type to another type (for example, the Shelly Flood) and then changing back to the Shelly Door Window.

Added

• #62 Better labeling for RGBW2 channel selection in "white" mode
• #67 Devices can be created based on the data of existing devices of similar types
• #68 Device configuration validation
• #69 The address column can now be populated for add-on devices

Fixed

• #65 RGBW2 devices have excessive logging when controlled from outside of Indigo
• #66 Corrected the way temperature units are presented for add-on-on devices
• #70 Reduced the amount of announcements that occur when devices start
• #72 Add-on devices are properly restarted the their host is restarted

Fixes

• Config UI issue that affected the Shelly HT, Shelly Flood, Shelly EM, and Shelly 3EM

Known Issues

The config UI is unable to be opened for the Shelly HT, Shelly Flood, Shelly EM Meter, and Shelly 3EM Meter. This has been resolved in release 0.1.1

Added

• Ability to create a device based on an already discovered device
• Shelly Detached Switch Add-on device to represent the state of the switch
• Devices are commanded to announce their information more frequently to capture up-to-date information

Fixed

• Missing energy state data for some devices
• Shelly Dimmer/SL previously ignored inputs from the switch
• Devices could be logged with an incorrect name until the plugin was restarted
• Action menu wording
• Shelly EM Meter not responding to status request commands
• Devices properly handle receiving invalid data
• Shelly RGBW2 failed to handle power values of 0
• Shelly RGBW2 in white mode was supplied with an invalid command topic