Ezmotion issue basic Set and multi encapsulated #647
Comments
|
I'd need logs without any of the modifications you made to see whats going on. Manually adding CommandClasses shouldn't be necessary unless its really buggy. Please send logs to the mailing list |
|
Any update on the logs? |
|
Now that i have a special plateform with ozwcp. I will.give you the exact log you need |
|
''' Here is the inclusion LOG The only way i made it work is with this in the config file But this is not persistant the 0x20 CC is removed when OZW restarts |
|
Did the device really go to sleep at 2015-11-02 12:10:50.882? Could you redo the log and wake up the device if it goes to sleep. Its strange though, as it sends the response at 2015-11-02 12:10:50.925 Looking at it, the controller reports no ACK at 882, this means that the stick sent the message out to the network, but it didn't ACK the message back to the controller, but at 925, it sends the response to the "unacked" message. Because of this, we never send out the MultiInstace Capabilities for Instance 3+ (unless a WAKEUP message comes in later), hence things wont be "setup" correctly. Can you confirm the above behavior is consistent (ie, we always get the No ACK - Device Asleep flow?) |
|
Any update? |
|
normally this config |
|
you can close after PR: |
Hi Justin,
I have both Ezmotions (The first one with IDs [0x001e] [0x0002] [0x0001] and the Ezmotion + version with ids [0x001e] [0x0002] [0x0002])
The second one works perfectly with
But the first one as some issues :
in fact setting doesn't work as OZW doesn't give any 48 CC only 49 CC.
The only way i made it work was using this in the config file
This is not clean but it works pretty well. But after an OZW restart the command CC 32 disappears with some errors in the log : "Invalid ValueID passed to GetValueAsBool and so on) and the command is removed.
I think this is expected.
Do you have any idea to make this device work (i can send you one if you want, i own 5 of them)
I think the initial problem is only related to bad multiencapasulated mappings.
I also tried
setting an endpoint to CC 48 it worked but it caused some dropping command issues in the log and the device stops from responding.
Do you have any idea (do you want one device ?).
Thank you
PS : we also noticed some lots of strange behaviour with lots of device with multi encapsulated and multi-instances). But we will mail you some informations (its is systematic on some Qubino devices)
Thank you for reading
The text was updated successfully, but these errors were encountered: