Replies: 10 comments
-
|
I have the same problem unfortunately. I have two remotes, both on firmware 2.4.11. any thoughts? Can i reverse to a previous firmware, somehow? Zigbee2MQTT: 1.39.0-1 |
Beta Was this translation helpful? Give feedback.
-
|
Does reconfiguring the device via the z2m frontend fix the issue? Press the yellow refresh icon and make sure to wakeup the device right before doing so |
Beta Was this translation helpful? Give feedback.
-
|
I just rejoined the remotes. I now use an automation to switch a light. Previous setup was with a direct binding to the light. |
Beta Was this translation helpful? Give feedback.
-
|
Reconfiguring does not resolve the issue. Here are the logs and binding:
|
Beta Was this translation helpful? Give feedback.
-
|
Problem is back. Reconfiguring reported to be ”succesfull”. But there was no change. So reconfiguring does not help. The actions for the buttons is as descibed in the opening post. I did not use this remote for about a day and then got this change of behaviour. |
Beta Was this translation helpful? Give feedback.
-
|
I started an experiment. I have an older model Trädfri hub. I have bound a remote and a lightbulb. |
Beta Was this translation helpful? Give feedback.
-
|
As I have configured the buttons for different functions in Home Assistant, such as playing radio through a speaker, pairing with the hub doesn't work for me. After researching, I found the following information to downgrade the remotes:
...
},
{
"fileVersion": 65572,
"fileSize": 194002,
"manufacturerCode": 4476,
"imageType": 4555,
+ "force": true,
"sha512": "732ed02c39087dfffbe1d6e7adaf23851ff8dc695fe1e0c85daa5b7e1a3bea85796181d6da02b695685bc35470cf0c69cb06cd73c4bb51c67f89a198b1dac78f",
"url": "http://fw.ota.homesmart.ikea.net/global/GW1.0/01.19.026/bin/10078031-zingo_kt_styrbar_remote-1.0.024.ota.ota.signed"
}
}
ota:
zigbee_ota_override_index_location: index.json
disable_automatic_update_check: true
{
zigbeeModel: ['Remote Control N2'],
model: 'E2001/E2002',
vendor: 'IKEA',
description: 'STYRBAR remote control',
+ ota: ota.zigbeeOTA,
extend: [
(0, ikea_1.ikeaConfigureStyrbar)(),
(0, modernExtend_1.identify)({ isSleepy: true }),
(0, ikea_1.styrbarCommandOn)(),
(0, modernExtend_1.commandsOnOff)({ commands: ['off'], bind: false }),
(0, modernExtend_1.commandsLevelCtrl)({ commands: ['brightness_move_up', 'brightness_move_down', 'brightness_stop'], bind: false }),
(0, ikea_1.ikeaArrowClick)({ styrbar: true, bind: false }),
(0, ikea_1.ikeaBattery)(),
- (0, ikea_1.ikeaOta)(),
],
},
We have tested this on three remotes, and it has been working since yesterday. We have additional Styrbar remotes and can reinstall the latest firmware version if needed to further debug the issue if someone with more expertise is available. Hope this information is useful for anyone. |
Beta Was this translation helpful? Give feedback.
-
|
I have 2 styrbar remotes, both were on firmware 2.4.11. Recently I noticed that one wasn't behaving according to the blueprint automation I was using. On further investigation it shows the same behaviour as described by the OP. I see from the release notes that as of 8th August there is a firmware 2.4.16 available. I updated the device that wasn't working and it now behaves as expected. Should be worth trying to update firmware to this version rather than revert to a previous version. |
Beta Was this translation helpful? Give feedback.
-
|
I have z2m 1.40.1 and unfortunatelly upgraded my styrbar bound to a group of bulbs from version 1.x to 2.4.16. Now styrbar is not working at all. I removed it from z2m and repaired (it wasn't easy). Last seen hasn't updated so far, even if I press the buttons or remove/reinsert batteries. Battery and action fileds are N/A. Tried to bind to bulbs separately, but got errors all the time. |
Beta Was this translation helpful? Give feedback.
-
|
I have latest z2m running with styrbar 2.4.16. It stopped working around 28.11. for unknown reason. I can force-remove the device and join it again to z2m, but after initial connection, it's not reacting. Tried several times, replaced batteries. No blinking when buttons are pressed, no events on z2m. Any tips what I can share to debug? |
Beta Was this translation helpful? Give feedback.
-
After updating our Styrbar remote control to version 2.4.11 (Firmware build date 20240408), they started strange behaviour. When briefly pressing the brightness up or brightness down buttons, they no longer trigger the "on" status. Instead, they alternately send "brightness_move_up" and "brightness_stop" commands, even though the buttons are not being held down. The same issue occurs with other buttons; for example, the "arrow_left_hold" and "arrow_left_release" states are triggered, but not the "arrow_left_click".
Additionally, we noticed that if the last status was a "hold" state, no other button presses are recognized until the same button is pressed again to trigger the "release" state.
Here are the steps I have already taken to resolve the issue:
These measures temporarily resolve the issue for a few hours, but the remote controls revert to the described behavior.
We currently have seven Styrbar remote controls in use, and it would be unfortunate if we had to return them to Ikea.
I am unsure how to proceed. I have considered downgrading to the previous version, but I have not found any information on how to do this.
I would greatly appreciate any help or suggestions.
Zigbee2MQTT version: 1.38.0
Coordinator: Home Assistant SkyConnect, EZSP 7.4.2.0 build 0
Beta Was this translation helpful? Give feedback.
All reactions