I have recently released a series of smaller versions, so the latest version is currently 0.0.12 (
https://github.com/AaronLionsheep/ShellyMQTT/releases). There is no need to update the plugin through each version. You should be able to upgrade from version 0.0.7 directly to 0.0.12
Changes in 0.0.8- Devices report when their reported firmware has changed. This indicates that a firmware update has been successfully performed instead of simply seeing the device go offline and come back online.
- The plugin keeps track of new devices that you have not added, but that are announcing themselves. This can help when adding a new device because some device info will already be available.
Changes in 0.0.9- Support for the Shelly 4Pro (needs physical validation)
Changes in 0.0.10- Support for Shelly RGBW2 (needs physical validation) with both "Color" and "White" modes. These are two separate devices (color version and white version) because each mode requires a different physical setup.
- Fixes a bug that resulted in color changes not being picked up for the Shelly Bulb into Indigo
Changes in 0.0.11- Devices can now be individually muted to suppress info and debug logging. All devices will always report errors and warning regardless, but you can specify that a device shouldn't log info and debug messages
Changes in 0.0.12- Shelly devices can be displayed in a table to get an overview all devices and their information. This table is displayed in the log and can be run from the plugin menu using "Print Shelly Devices Overview"
- The "Discover Shellies" action has been updated to provide more feedback when the plugin has not detected any Shelly devices yet (usually right after a plugin restart)
Print Shelly Devices Overview Example:
- Code: Select all
ShellyMQTT Shelly devices connected to ActiveMQ (11)
ShellyMQTT +-------------------------------------------+-----------------+-------------------------------------------+-------------------------------------------+------------------+-------------------------------------+
ShellyMQTT | Name | IP Address | MQTT Address | Host Device | Update Available | Current Firmware |
ShellyMQTT +-------------------------------------------+-----------------+-------------------------------------------+-------------------------------------------+------------------+-------------------------------------+
ShellyMQTT 1 | Aaron's Bedroom Lamp | 192.168.1.111 | shellies/ShellyBulbDuo-D0CF67 | N/A | No | 20200320-123338/v1.6.2@514044b4 | 1
ShellyMQTT 2 | Air Compressor Purge | 192.168.2.20 | shellies/shelly1-B8F69F | N/A | No | 20200206-083100/v1.5.10@e6a4205e | 2
ShellyMQTT 3 | Landscape Lighting | 192.168.2.19 | shellies/shelly1pm-B98153 | N/A | No | 20200312-124223/v1.6.1@112262fd | 3
ShellyMQTT 4 | Landscape Lighting Outdoor Temperature | 192.168.2.19 | | Landscape Lighting | | | 4
ShellyMQTT 5 | Refrigerator Probe | 192.168.1.91 | shellies/shellyht-E0100C | N/A | Yes | 20190821-095211/v1.5.2@4148d2b7 | 5
ShellyMQTT 6 | Window Candle | 192.168.2.18 | shellies/shelly1pm-B9825D | N/A | No | 20200206-083604/v1.5.10@e6a4205e | 6
ShellyMQTT 7 | Workshop Lights | 192.168.2.10 | shellies/shellyswitch25-76D77A | N/A | No | 20200206-083126/v1.5.10@e6a4205e | 7
ShellyMQTT +-------------------------------------------+-----------------+-------------------------------------------+-------------------------------------------+------------------+-------------------------------------+
This has helped identify: the refrigerator probe (Shelly HT) needs to be updated and a few devices are connected to the wrong WiFi network.
Future Plans0.0.12 is the last 0.0.x release as I feel the plugin has reached a point that it supports most Shelly devices and has a decent amount of "helping" utilities. Barring any critical bugs that would necessitate 0.0.13,
0.1.0 is the next planned version and will be published to the plugin store. Right now, 0.1.0 has no new features, but is meant to improve stability. I am implementing unit-testing, which might be overkill for an Indigo plugin, but it is a good way to find bugs, prevent old bugs from being reintroduced, and allow for confidence when changing a core component. The design of this plugin has meant that almost all devices rely on "base" device implementations, so changing these base devices could break other devices without the developer (me at the moment) realizing it. Every code push to GitHub is run against these tests, so any future contributors can have their code validated too.