I just got my first shipment of 5 Blues. I installed one last week and have been happy with how it is working.
Today I installed some others and have noticed that using the same blueprint, the switches aren’t responding well to single up and down actions. When I look in the HA logbook, I see an extra event of “turn on” in addition to up paddle. Physically at the switch, the switches having the issue go through their little light-up animation when paddle up, and their light-down animation when paddle down. It’s almost like my automation is doing stuff while the switch is also trying to do its own thing.
All switches are in smart bulb mode.
The switch I installed last week is on firmware 0x0102020b, the two switches I installed today that are having this issue are on firmware 0x0102020f.
If there is something else different about my setup, I cannot for the life of me determine what it is.
I’d like to try downgrading these switches to 0x0102020b, but cannot find any instructions on how I would do that.
So multiple requests:
- Any advice on what could be causing the inconsistent behavior on the up / down paddles?
- How do I change firmware?
The switches on new firmware display this event, which seems to correspond with the switches little on (or off) light show.
My older firmware switch doesn’t show this in the logs, and doesn’t have issues with the single press up or down.
Listening to events from both switches shows the following differences.
Newer firmware (single up click):
event_type: zha_event
data:
device_ieee: b4:3a:31:ff:fe:35:03:be
unique_id: b4:3a:31:ff:fe:35:03:be:2:0xfc31
device_id: 5a2e9f80ae5a6521c5d8131bc2ce2407
endpoint_id: 2
cluster_id: 64561
command: button_2_press
args:
button: button_2
press_type: press
command_id: 0
params: {}
origin: LOCAL
time_fired: "2023-08-23T16:15:30.276502+00:00"
context:
id: 01H8HJVYF4P3D6VJDXBT28VXQK
parent_id: null
user_id: null
event_type: zha_event
data:
device_ieee: b4:3a:31:ff:fe:35:03:be
unique_id: b4:3a:31:ff:fe:35:03:be:2:0x0008
device_id: 5a2e9f80ae5a6521c5d8131bc2ce2407
endpoint_id: 2
cluster_id: 8
command: move_to_level_with_on_off
args:
- 254
- 0
params:
level: 254
transition_time: 0
origin: LOCAL
time_fired: "2023-08-23T16:15:30.265006+00:00"
context:
id: 01H8HJVYES2MBMMC3RT07R9NNR
parent_id: null
user_id: null
event_type: zha_event
data:
device_ieee: b4:3a:31:ff:fe:35:03:be
unique_id: b4:3a:31:ff:fe:35:03:be:2:0x0006
device_id: 5a2e9f80ae5a6521c5d8131bc2ce2407
endpoint_id: 2
cluster_id: 6
command: "on"
args: []
params: {}
origin: LOCAL
time_fired: "2023-08-23T16:15:30.254957+00:00"
context:
id: 01H8HJVYEE5VE8R6SBFNDKGF37
parent_id: null
user_id: null
Older firmware (single up click):
event_type: zha_event
data:
device_ieee: b4:3a:31:ff:fe:33:fe:09
unique_id: b4:3a:31:ff:fe:33:fe:09:2:0xfc31
device_id: 7190dccc6f64e2345e655039201169b6
endpoint_id: 2
cluster_id: 64561
command: button_2_press
args:
button: button_2
press_type: press
command_id: 0
params: {}
origin: LOCAL
time_fired: "2023-08-23T16:10:38.365999+00:00"
context:
id: 01H8HJK1CX5VRAXW0WX90E2FY9
parent_id: null
user_id: null
1 Like
FYI in case anyone else is encountering similar behavior / issues.
I went through the laborious process to setup my switches with individual device automation triggers vs a blueprint, and for whatever reason, that seems to have improved things.
I still get the extra events firing, but up and down at least work reliably now.
If I was more savvy with blueprints I’d re-write to try to mimic how the device automations listen and then maybe the blueprint would work, but I’m getting by for now.
I don’t think it is firmware related, but it almost seems like the device got a binding created from ep2 to the hub for level control and on / off. I’m not sure how that would have happened, but it is usually a type of binding that would be created from the switch to a zigbee bulb.
