I am having a couple of problems I hope someone can point me through…
The first is most (but not all) of my battery-powered devices are being reported as mainline devices. This is messing up availability scans and marking battery devices offline.
The second issue is if I try to enable rtscts Z2M fails to find my adaptor. I had to enable this via the dip switch on the adaptor or my Lutron Aurora dimmers wouldn’t send events. Everything seems to work properly even with it not being configured in Z2M, but I’d rather have it set up correctly.
I have converted over all my zigbee lights to run off of a zigbee coordinator for some time now. Hue bridge is completely shutdown. I am experiencing 2 annoying things.
The transition to turn on/off the lights are abrupt. When running with hue bridge it was a smooth on/off motion.
The lights will not turn on from previous state. Example. If the lights were turned off at 10% dim. The next day or later when I turn it back on, it seems it is not on, but I can see from HA gui that is it on, but the light itself is not physically on. The only way is to use the slider in gui to turn it to 100%.
When on the hue bridge, I didn’t see any issue with these. I am tempted to revert back to the hue bridge, but kinda burnt out of having to mess with Ha on a daily basis.
OK I am struggling a bit. I have tried to add an Ikea Praktlysing blind to my zigbee2mqtt system and it is showing as unsupported (this goes for the remote, the repeater and the blind. Even though it says it is supported in herdsman I cant figure out how to get it to identify it. I am using Zigbee2MQTT Version 1.32.1-1 and have tried several times and full resets on the Ikea devices and still to no avail.!
According to zigbee-herdsman-converters it is supported but having read through a lot of this forum it appears that the herdsman convertors are already installed with the main zigbee2mqtt but I just am not able to see the files/folders. Am I missing something.
How do I get these ikea products recognised (i.e. shown as supported and exposing items?)
Running on a rasp pi 4
Home Assistant 2023.7.2
Supervisor 2023.07.1
Operating System 10.3
Frontend 20230705.1 - latest
I presume by model number you mean of blind?
It is an Ikea Praktlysing E2102, Type E1746 Tradfri Repeater & Trafri Remote E1766.
Not sure how I find the firmware versions.
Logs when I try to pair the Repeater,
error 2023-07-15 15:45:06: Failed to interview '0xb4e3f9fffe52a4f1', device has not successfully been paired
info 2023-07-15 15:45:06: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xb4e3f9fffe52a4f1","ieee_address":"0xb4e3f9fffe52a4f1","status":"failed"},"type":"device_interview"}'
info 2023-07-15 15:45:06: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_failed","meta":{"friendly_name":"0xb4e3f9fffe52a4f1"},"type":"pairing"}'
So does this mean I have bigger issues as it failed the interview and hence didnt pair even though it is showing up online in the devices list but just unsupported?
The device is sitting adjacent to the co-ordinator which is on a 2m USB lead away from the rpi4. In fact now despite the red flashing lights on the remote it wont pair at all now!
I am wondering if the remote is actually faulty but still doesnt explain the repeater showing as unsupported.
OK so I have reset all of the blinds, remotes, repeaters and have proven that as a standalone until all of the IKEA devices are working and the remote controls the blind. I then started to follow the advice here It starts to try to pair and it still shows up as unsupported. The logs showed just as they did in my post above.
The Co-ordinator was sitting right next to the Ikea repeater on a 1.5m lead / distance from the raspberry pi. The repeater shows as online still on the zigbee2MQTT devices page but unsupported. Any ideas what else I can try as I am tearing my hair out.
With the IKEA E2201 Rodret, it has the ability to send a simulated_brightness command by holding down the on button.
How do I get the IKEA E2201 the brightness updates (action_brightness_delta) in an automation (not brightness_move_up as that is a one time event, but the action_brightness_delta commands)?
Info <small>2023-08-10 11:41:43</small>`MQTT publish: topic 'zigbee2mqtt/Master Bedroom Fan Remote/action', payload 'brightness_move_up'`
Info <small>2023-08-10 11:41:43</small>`MQTT publish: topic 'zigbee2mqtt/Master Bedroom Fan Remote', payload '{"action_brightness_delta":20,"battery":100,"brightness":155,"last_seen":"2023-08-10T15:41:43.929Z","linkquality":131,"update":{"installed_version":16777287,"latest_version":16777287,"state":"idle"},"update_available":null}'
Would the fact I am running on channel 26 zigbee be a possible cause? I dont really want to try changing it unless I HAVE to as it means I have to re-pair all the devices again…
Well in theory it should work as the Ikea spec for the blind says 2400-2483.5 MHz. Channel 26 being 2480 MHz So most probably not that.
Product announcement 