Ikea Trådfri motion sensor (E1745) not working
Closed this issue · 17 comments
Outline
New Ikea Trådfri motion sensors (E1745) not working. Discovery works and things can be added through PaperUI.
Debug show OnWithTimedOffCommand, when sensor is triggered, but channels are not triggering.
Configuration
| Configuration | Description |
|---|---|
| Coordinator used | Telegesis Zigbee USB Stick |
| openHAB version | 2.5.0-M3 |
| Hardware | Orangepi PC+ |
| Memory | 1GB |
| Java version | Zulu Embedded 8.25.0.76-linux-aarch32hf (build 1.8.0_152-b76) |
| Devices | 3 Ikea Trådfri motion sensors E1745 |
Logs
[DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: OnWithTimedOffCommand [On/Off: 4991/1 -> 0/1, cluster=0006, TID=0C, onOffControl=1, onTime=1800, offWaitTime=0]
[DEBUG] [transaction.ZigBeeTransactionManager] - notifyTransactionCommand: OnWithTimedOffCommand [On/Off: 4991/1 -> 0/1, cluster=0006, TID=0C, onOffControl=1, onTime=1800, offWaitTime=0]
@ascona78 thanks - can I ask you to provide a slightly longer log. I'd like to see the two lines that come just before the one starting with RX CMD - there should be RX ZCL and RX APS from memory.
Thanks.
Of course!
I attached slightly longer log from before and after those lines.
By the way.. What do you think about RX Telegesis Data line between RX ZCL and RX CMD. Does it look ok to you?
I'm not too familiar with zigbee.
Thanks.
I don't see anything wrong with the telegesis data. The telegesis protocol isn't super nice and it doesn't necessarily print well, so maybe that's what you're seeing. If you think something is an error then please post the line and I can comment.
Ok..
I thought these character in 08: EB part might be ok, because message data looks good.
But thanks for clarifying.
IIRC, I had a problem with a Tradfri motion sensor, where there was no solution. The sensor did not provide a motion channel to the network, in stead it used a direct link to the light bulb to control it.
IIRC, I had a problem with a Tradfri motion sensor, where there was no solution. The sensor did not provide a motion channel to the network, in stead it used a direct link to the light bulb to control it.
For me Trådfri also provides only switch channel and not motion. Sometimes also batterylevel and batteryvoltage are provided.
For me Trådfri also provides only switch channel and not motion.
Is that a problem? Please remember that the binding looks at the services that the device provides - if the device doesn't provide the motion sensor features, then you don't get that. That doesn't make it a bug in the binding does it?
If you think there's a bug, then please be clear as to what the issue is so we can look at it.
Binding is still not triggering channel.
Attached log when motion sensor was triggered.
And now binding is not announcing "ZigBee command receiveds OnWithTimedOffCommand" (which you also corrected to "received")
There has not been any change to the binding, so I don't really expect to see anything different.
Little update:
I have 3 E1745 motion sensors and now only one has 4 channels (switch, battery level, battery voltage and battery alarm). Other two have only switch.
If I restart that "4 channel" motion sensor by pressing down two of three buttons on back, it makes channel to update OFF. But movement doesn't make channel to trigger.
Those two other motion sensors do nothing even when restarting by pressing buttons on back.
In the very beginning of log I restarted sensor by pressing buttons.
zigbee-e1745-after-pr481-2-restarted-sensor-snippet.txt
Yes, sorry.. I should have mentioned I tested PR 481.
#481 won't change the way the channels are detected - it just handled the timed command. I think your issues are likely just problems with the discovery. I'll try and look at your log, but it won't be tonight as I'm trying to get some ZWave stuff done.
I managed a quick look at the log.
Is 54603 the sensor? It's the only device where any commands are received in the log. The log isn't an initialisation log so I can't commend on why channels may not be available.
Given the binding doesn't seem to be receiving OnWithTimedOffCommand, this isn't related to #481 since that simply adds processing of that command.