[bug] Aeotec Smart Switch 6 - Fails to complete Interview #1369
Labels
Comments
|
Weird, mine appear to be fine though I’ll rediscover them later and confirm. Can you verify what firmware version you have? |
|
Managed to get the following: I'll also throw this corresponding driver log which shows something about invalid data received (and not sure it is from node 6). |
|
cc @AlCalzone |
|
That invalid message looks like a security encapsulated command which fails to deserialize. Could be due to incorrect network key, could be something else. |
|
@tommyjlong Could it be you added the device with a network key and then you changed it? |
|
I went back to OZW and captured its logs to confirm that my Smart Switch 6 does not use security keys (nonce is not used). @AlCalzone I will send you separate info to help figure out the deserialization issue |
@tommyjlong You should set loglevel to |
|
I set it to silly, |
|
Node 6 claims it supports Z-Wave+ CC, but does not respond when we query that CC's info. This is something that keeps popping up. I'm gonna discuss the generic issue with a contact who has in-depth knowledge - maybe we can solve it once and for all. |
|
As a reference/FYI, when I do the same thing in zwave2mqtt using OZW, OZW also does not get a response on zwaveplus info, but seems to keep on going; getting to what I think is its final state of "Complete": |
|
I would like to try out this fix. I have a question on installation with zwavejsmqtt using npm (install, run build). I just installed zwavejs2mqtt tagged version 1.0.1 and it appears that it installs the zwavejs tagged v6.1.0 driver which does not contain this fix. Is there a way I can use npm to get zwavejs2mqtt to install the zwavejs driver from main (with the fix) instead of the tagged v6.1.0 branch? Sorry I am not familiar with nodejs very much. |
|
If you go into the zwavejs2mqtt repo and open the docs there you should find a description. |
|
Thanks. I've looked all through the docs. Closest I found was docs on using a custom docker build but couldn't find anything on custom npm install. If you come across something and can provide a pointer, it would be much appreciated. |
|
It took a while to get the install procedure worked out, and I am happy to say, that node-zwavejs v6.1.1 solved this problem and my Smartswitch 6 completed the interview process!! Thanks :) |
|
Is this fix in the latest (zw js to mqtt 0.6.0 addon and ha 21.3.0) release? It does not seem to be working for me. I have two SS6 which do not interview; the ones that were already on the zstick did interview and work fine. If I try add them via HA nothing at all happens, if i add them on the stick directly, they add fine, but HA doesn't interview them (other devices added this way DO work fine). in the excerpt below, it is for node 135. 021-03-03 19:23:15.539 INFO ZWAVE: Node 11: value updated: 50-0-deltaTime-66817 0 => 0 |
|
Please open a new issue and fill in the requested info. That log snippet is not nearly enough to say anything. |
|
Hi PS: i finally found the zw version in the integration, if it was fixed in 6.1.1 has it regressed? Network Connected |
🤷🏻♂️ I really need to see the detailed log. |
|
I understand, I'll try and provide it as soon as I can. The aeotec smart switch 6 are the worst RF devices in my network, see very few neighbours . They see 1-4 where an immediately adjacent fibaro, or even older aeotec smart switch 2 will see 20-30 neighbours. |
|
Okay, I managed to remote in and run an interview - node 135 is the new node, today at 10 am you can see it fail - interestingly if you search for Node 135, yesterday at 150734 node 135 did a partial interview but seemed to fail - nothing in the UI, and also 136. Node 11 is another switch, but already in the node list, at the risk of losing it I reinterview, and it completed okay. hopefully this log points out the issue(s) |
|
PS: If you need this in a different ticket I am out of time today but can try move/recreate it over the weekend |
|
As I suspected: The affected nodes do not acknowledge the commands we send them. That usually indicates a connectivity problem. I can see NoAck a few times for nodes 100, 112, 135, 136 in your log. |
|
For reference, node 11 is 15m away through two double-brick walls and a stud wall, node 135/6 are 4m and 3m, respectively, LOS. I can try moving them within 1m next week as I have gone away for the long-weekend local holiday (mini break). |
|
Try doing a network heal. I'm lately seeing many issues that can be explained by bad routes (meaning the devices don't know how to reach the controller). |
|
Thankyou. Will try after a stick backup. Last heal I did killed the network and had to revert to a 2 month old archive. |
|
How's that even possible? You can't change the routes on nodes with a backup. |
|
If they mean a backup of their docker or something maybe poor connectivity and they restored an old cache, thereby requiring less interviewing? I agree a backup of the stick would do little. |
|
I can add, that my Smart Switch 6 from a networking/RF point of view was both bad and good. I initially wanted to use in on the 1st floor of my house, but the range was very bad (less than 7m through 1 wall). I moved it to my 2nd floor much further away through more walls and it worked very well. Fortunate for me it was where my washing machine was located, so I use it strictly as an energy meter. I have not had any issues since this problem was fixed, but I am still on 1.0.1/6.1.1. I will try and upgrade in the next day or two just to confirm it still works. |
The stick became unresponsive in ha after an attempted heal. It was effectively dead in ha -even after snapshot rollback. So I zensys restored the stick. I didn’t care about the routes. It worked and could talk to it with ha again. So I always backup the switch before trying to heal. Ps. The neighbours are stored on the stick -they are visible in the zensys matrix view |
921 MHz over the house is very good but added two repeaters anyway. I did purchases a USB loop back tester made in Australia and it found errors on the USB extension I was using. Annoying as it was expensive. But using a test passing cable now. |
|
PS: I moved the controller within 10 cm of the node in question (135) and it interviewed okay. |
|
That confirms my initial suspicion that the node does not have correct routes. The only way to get that corrected is to heal it while the controller is at its usual location. Another workaround (assuming that it can even be included where it is) would be:
|
|
I would love to heal them, but the command has no effect on the nodes. The neighbour list remains unchanged (and I've tried single healing 4 other different types of devices with neighbours). Maybe I need to raise an issue for that... |
|
Then maybe the devices really don't see any other neighbors. You (or I) should be able to see in a log what happens exactly. But let's track that in a separate issue. |
|
I see this issue as closed so I am not sure if I am doing something wrong, but I am experiencing the same issue with Aeotec Smart Switch 6. Exactly after inclusion in the interview stage, the node is stuck in "NodeInfo":
|
|
Got a log? |
|
Sorry I'm pretty new to HomeAssistant/Z-Wave JS since I am moving from SmartThings. I will figure out how to get the log file and attach it soon |
|
If you open a new issue, you should find some hints in the issue template. It looks like you're using zwavejs2mqtt, so https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report?id=export-logs could help you aswell. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
1.0.0-alpha.2.51f715c
Build/Run method
zwavejs2mqtt version: 1.0.0-alpha.2.51f715c
Describe the bug
After a few hours, all my devices have reached "Complete" but
the Aeotec Smart Switch 6 still never reaches "Complete".
Note: This is a case of transitioning from OZW/zwave2mqtt to zwavejs2mqtt.
Note: The Smart Switch 6 has been operational with OZW/zwave2mqtt.
The Smart Switch 6 reports power/energy meter updates about every 60 sec.
To Reproduce
Steps to reproduce the behavior:
(With "Log to file" set to on)
The following zwave-js2mqtt logs:
Logs
The text was updated successfully, but these errors were encountered: