Current update instructions for popular hubs:
Home Assistant (ZHA)
Zigbee2MQTT
Hubitat
April 22, 2024 / v2.18 / 0x01020212
Fixed incorrect calls to speed and ramp rate configuration.
March 28, 2024 / v2.17 / 0x01020211
Parameter Related Changes:
-
Modifying P55&P56,Add P120,P121,P129,P130,P131,P132,P133,P134
-
55- Range is now 2-255. 255 = send On command
-
56- Range is now 0-255. 255 = send Off command
-
120- Change how a single tap on the switch works. 0 = Old method, 1 = Single tap cycles through speeds, 2 = same as 1, but down is always off
-
121- Fan Timer Mode
0 = Off
1 = On
See Button Related Changes for more info -
130- Config button binding mode. 0 = Disabled, 1 = Multi Tap (1x = low, 2x = medium, 3x = high, hold = off), 2 = Cycle mode
-
131- Low speed for config button binding mode
-
132- Medium speed for config button binding mode
-
133- High speed for config button binding mode
-
134- LED color for config button binding mode
Button Related Changes:
- When in the local protection state, you can also restore the factory settings by the usual method
- Combo Button To Change the switch single tap mode
Single Tap Old Method = Hold Up + Tap Config 12x = LED Pink
Single Tap New Method = Hold Down+ Tap Config 12x = LED Cyan - Combo Button To Enable Initiator Mode (used to bind this device to the new fan + light module)
Hold “up” + press “config” 2x: EP2 enters Initiator Mode, LED pulsing in purple. If binding is successful, LED flashes green 3 times; if unsuccessful, LED flashes red 3 times.
Hold “up” + press “config” 3x: EP3 enters Initiator Mode, LED pulsing in cyan. If binding is successful, LED flashes green 3 times; if unsuccessful, LED flashes red 3 times - If Fan Timer Display Enable(P121 = 1)
Tap Up 1x = Fan Turns On
Tap Up 2x = 5 minute timer
Tap Up 3x = 10 minute timer
Tap Up 4x = 15 minute timer
Tap Up 5x = 30 minute timer
Tap Down 1x = Fan Turns Off (timer is cancelled if it is still on)
Device Function Changes:
- Add a new Endpoint Dimmer Switch(Exactly the same as EP2)
Endpoint id: 3
Device id : 0x0104
Cluster list:
Basic(id : 0x0000 ,Server)
Identify(id : 0x0003 ,Server&Client)
Groups(id : 0x0004 ,Server)
Scenes(id : 0x0005 ,Server)
OnOff(id : 0x0006 ,Server)
Level(id : 0x0008 ,Server)
Private Cluster (id:0xfc31 ,Server, mfg-code:0x122f)
Command Changes:
- Modify the private command BindInitiator [cmd id: 0x04] to BindInitiator (endpoint) [cmd id: 0x04]. The endpoint supports input parameters of 0x02 and 0x03. 0x02 indicates EP2 enters Initiator, and 0x03 indicates EP3 enters Initiator.
Other Changes:
- Changed the behavior of keep alive cluster to stop using keep alive cluster when hub does not support it (Related to Hubitat bug).
- Fixed the inability to use Hold up/hold down to adjust the level of the binding device in OnOff + Remote Control Mode
- Removed the ability to add EP2 to a group to multicast commands to group members
- Match 2-1 red ramp rate behavior
July 24, 2023 / v2.15 / 0x0102020F
We have put a pause on firmware 2.14. Please see the below post.
Please wait for the switch update to complete. It will sometimes take up to 10 minutes after the green firmware update notification finishes before the firmware file is verified and installed on the switch. Please do not cut power to the switch during this process.
If you have any problems with the update, please reach out to support so we can assist you with any issues.
April 11, 2023 / v2.14 / 0x0102020E
2.10
Add parameters P54(Double down to value of P56)
Add parameter option 3 to P22(Switch Type) - Single-Pole Full Sine Wave
Add Disable Remote Control as special cluster command. Mfg specific command 0x10 (0x00 Enable Remote Control, 0x01 Disable Remote Control)
Fix the duty cycle value of dimming will be less than the Max Level value (miscalculation of max level when that setting is set)
Fix bug that was making set level “duration” not work correctly
Fixed excessive broadcast Report Attributes
2.11
Lower min levels are now allowed (only have neutral)
Fix Ramp Rate Remote Sometimes Not Being Applied
Add trailing edge dimming in some cases. Trailing Edge dimming improves switch buzz and led bulb flicker,
Note: It is best to toggle Leading/Trailing Edge dimming in the Off state,
If you cannot control the switch under Trailing Edge conditions, power it on again or reduce the value of P10(max level)
When leading vs trailing will be used:
non-neutral + single pole (P22 = 0) Leading Edge
non-neutral + 3way(AUX) (P22 = 2) Leading Edge
neutral + 3way(dumb) (P22 = 1) Leading edge
neutral + single pole (P22 = 0) Trailing Edge
neutral + 3way(AUX) (P22 = 2) Trailing Edge
neutral + OnOff Mode + full wave (P22 = 3) full wave
2.12
Add parameters P55(Double Up to level)
Add parameters P56(Double Down to level)
Fixed incorrect behavior of P5
Adjust the output voltage under non-neutral
Optimize compatibility with dimmable bulbs
The mode is not automatically switched to “dimmer” when the user selects smart bulb mode.
Reduce unnecessary zigbee broadcasts
Optimize zigbee messaging network processing
2.13
Further optimized zigbee messaging
2.14
Add P25 (Increase non-neutral power output. This may cause flickering or aux switch problems with some bulbs. Adjust max level to fix this)
Modify P56 range 0 to 254 (allow double tap to turn device off)
Add P100(LED Scaling ) 0- VZM31 ; 1- LZW31
Add P123(Use different scene numbers via the aux switch)
Add P125(Send “move to level on/off” to bound devices that matches default level remote and local)
Optimized dimming flicker problem
January 18, 2023 / v2.10 / 0x0102020A
Note: We haven’t officially announced 2.10, but it is available on Hubitat servers for our beta testers. It may have an issue with binding when you have a master and a slave Inovelli device (virtual 3-way). Please wait to update until we have the issue figured out.
November 11, 2022 / v2.08 / 0x01020208
Note: We are waiting for a PR to go through for HA before releasing it there. Should be released on Hubitat soon. Bump ZHA quirks lib to 0.0.86 by dmulcahey · Pull Request #81966 · home-assistant/core (github.com)
- Fix the ability to send commands to a group binding.
November 8, 2022 / v2.07 / 0x01020207
Note: It looks like 2.07 introduces a bug with group binding control and it is currently required that you use individual device binding. I’ll post an update when this gets resolved.
- Remove the sending of multicast commands to avoid switches that would accidentally control other devices within a group.
- Fix the wrong destination endpoint used when sending some commands.
November 7, 2022 / v2.06 / 0x01020206
- Fix for devices that are bound to the switch not using speed parameters 1-8.
November 4, 2022 / v2.05 / 0x01020205
- Add parameter 262: Disable the “double tap” to clear notifications feature. Users can make it so family members do not clear notifications at the switch. (2.02)
- Improve the speed of sending power reports when load changes from on-to-off or off-to-on. (2.02)
- Added LED notifications: “falling”, “rising”, “aurora single”, and others. (2.02)
- Fix the bug that changes Philips Hue color temperature when dimming down. (2.03)
- Fix for device binding to Innr and possibly other devices. (2.05)
- Ability to change max level in On/Off 3-way dumb mode to accommodate special scenarios. (2.05)
Just make sure your logging is set to debug if you want to see the update progress in system logs, otherwise you’ll get a visual indicator of progress on the switch’s LED bar.