deconz-rest-plugin: Update to 2.05.84 breaks Aqara/Opple switch event x003 in Ubuntu on x86 hardware.
Update 2.05.84 breaks the Aqara/Opple x003 event running Ubuntu 18.04 on x86 hardware. Downgrading to 2.05.81 and everything is OK again. Is it the same issue as before that has come back or is it a new bug?
Based on the feedback so far, it’s looking like a compiler bug or at least something relating to the CPU architecture.
That appears to be the most plausible explanation, as I remarked earlier.
The only explanation I can think of would be a compiler bug.
The erratic expression seems to be: https://github.com/dresden-elektronik/deconz-rest-plugin/blob/2a26b78f4139a179968e61aa0e0caf3fd1917162/de_web_plugin.cpp#L3586
zclParam0 is a quint16; zclFrame.payload() returns a QByteArray. QByteArray::at() returns a char. So we’re comparing an unsigned 16-bit integer value of 255 with an, I assume, 8-bit, possibly signed, char value. I suppose that is asking for trouble.
The only other place in the button maps where we use a zclParam0 value of 255 is for the 1002 (sharp right turn) of the IKEA dimmer. Care to guess what we see there? Hint: #2787. Maybe we were a bit premature calling out the dimmer to be cursed?
@manup, what’s your take on this?
_Originally posted by @ebaauw in https://github.com/dresden-elektronik/deconz-rest-plugin/issues/2061#issuecomment-634866512_
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 23
guys a false alarm on my part, apparently Martin really hasn’t updated the containers yet … and I was knocked off the right track by yesterday’s update of the stable branch …
@manup yesterday I was talking 'bout wrong version of phoscon… I think this is related my post 'bout docker. so I’m sorry for this. I need to be more careful next time - but yesterday’s updates to containers and the stable branch are to blame, it just confused me.
Confirmed all working in the 2.05.86. Thanks a lot for the fast fixing
That’s why it’s a Beta! Thanks for testing this. I’ll try to get in touch with some Devs to get this fixed. After that i’ll try to get a hotfix.