Hi jason12, I'd be happy to send any firmware updates to a Hubitat developer or release manager so they can be rolled out via Hubitat. If someone can give me contact details we'll arrange it.
I saw that above version 1.6.22 was mentioned. That version has the following changes w.r.t. version 1.4.3:
- The limits for the overload protection feature have been stretched by 3% to account for the worst-case deviation of the measurement chip, as follows:
- SP 240 (EU): undervoltage went from 176 V to 167 V, overvoltage from 253 V to 261 V, and overcurrent from 16800 mA to 17304 mA.
- SP 242 (UK): undervoltage went from 176 V to 167 V, overvoltage from 253 V to 261 V, and overcurrent from 13700 mA to 14060 mA.
- SP 244 (US): undervoltage went from 96 V to 87 V, overvoltage from 132 V to 136 V, and overcurrent from 16000 mA to 16223 mA.
- Scene table format fixed. NB: due to a change in the SDK in the scene table format, after an update from version 1.4.3 to this version, the device will lose all its Zigbee scenes. Zigbee groups are unaffected.
Sorry we couldn't help the loss of scenes, the SDK did not provide enough handles to convert them.
There is a newer version 1.7.22 with the following changes:
- Fixed attribute reporting not working after power cycle; binding table is now persisted.
- Attribute 0x0000 CurrentSummationDelivered of the Metering cluster 0x0702 was mentioned by some as not reporting, but our testing showed the attribute is reported if requested: interested devices (such as a bridge) must create a binding to cluster 0x0702 and send command ConfigureAttributeReporting for the attribute. The binding is now also persisted so it keeps working after a power cycle.
- Added possibility to disable voltage over/underload protection:
Keep button pressed between 15 and 20 seconds, then release. After 5 seconds, the LED will start quick-blinking; keep the button pressed. After 10 seconds, blinking stops; keep the button pressed. After 15 seconds, the LED will start quick-blinking again. Now release the button. The LED will slow-blink twice to indicate success. Every on/off action, local with the button or by remote command, will now double-blink the LED before assuming final state; this to indicate that the voltage over/underload protection is disabled. Enable again in the same way. Enabled/disabled state is persisted over power-cycles, even if not paired to a bridge. Note that the current overload protection will remain active.
And then there is version 1.7.23 with a minor fix:
- When the smart plug is not paired to a network, power-cycling it always turned it on. This fix corrects that issue, the plug now always assumes its last state when power-cycled (unless it is in a network and a client device changes the behavior by setting the StartUpOnOff attribute).
