#Diagnosing stuff
1 messages · Page 1 of 1 (latest)
On the network map would be easiest. Red lines = 9.6k, Yellow lines = 40k, Green lines = 100k
We didn't suffer the number of "why didn't that work? why is that light still on?" events that we are now seeing in the house while using Fibaro.
I presume you're using a 700 series controller now? Personally I haven't had a good experience with them, and there are other users who share this sentiment.
Either 500 series or 800 series for me.
'd be keen to hear any insights this log might have to the issues the network is having talking to the devices I tested.
The tests seem to get interrupted by spamming devices.
Node 4 seems to be one of the culprits, I haven't identified others yet, but you should be able to do so by looking at the commandsRX number in the node statistics (hover the arrows):
In your log, I count nearly 8000 incoming reports from node 4
I’ve decommissioned node 4 as it was continually motion triggering over night. I think it must be faulty now.
I’ll look thru the RX numbers.
If I buy an 800 series, can I move the zwave network config to the new controller without exclude/include on every device? (Doing that once in a year is enough 😊)
If I get a response like this, is that an indication that the module is failing, there is interference, or it is just to far from another powered module?
(oh - how do I add images to this chat?)
I probably have higher permissions - you'll have to upload the image somewhere
OK, URL: https://shorturl.at/r9YyE
This is the important question for me right now:
If I buy an 800 series, can I move the zwave network config to the new controller without exclude/include on every device? (Doing that once in a year is enough )
Yeah. Use Z-Wave JS UI, do an NVM backup of the old stick, swap sticks, configure Z-Wave JS UI to use the new stick, restore the NVM backup
There's a UI bug where the controller's label is wrong until you restart. It's purely cosmetical though.
Can't see it, it's asking for login credentials
So that's a connectivity problem in at least one direction. I'm assuming the link is 40k or even 9.6k?
I think the controller drops down to 9.6k, which results in a good SNR margin, so it can reach the node and hear its acknowledgements.
In the reverse direction, there is trouble. Either the pings don't reach the controller, or the controller's acknowledgements don't reach the node.
Is this node using a direct route?
Distinguishing which of the two problems it is may require a Zniffer though:
https://zwave-js.github.io/zwave-js-ui/#/usage/zniffer
This is the map view
This is a link to the folder (rather than individual files) https://shorturl.at/0TIWY
I have added a shot of the whole map to give a feel for the whole mesh
Is there a way to stop the map objects moving?
As I expected, 9.6k speed for that route.
Unfortunately not
Lots of red, lots of yellow. It's hard to see on the full map if the link from the controller to Front Steps Thread is green or red. If it is green, the issue is probably between that device and Water Feature. If it is red, I'd look at the connection to Front Steps Thread first.
What 800 series controller would u recommend?
We did range tests yesterday, so I have fresh info.
If you need one now, https://shop.homeseer.com/products/homeseer-smartstick-g8-800-series-z-wave-usb-stick
The Zooz ZSt39 is also good, but has a bit less range than the HomeSeer.
If you can wait, Nabu Casa has one coming up that blows the others out of the water https://www.home-assistant.io/blog/2024/05/08/zwave-is-not-dead/#range-testing-our-z-wave-stick-prototype
Cheers. Any timeline on the Nabu Casa one?
Are there none that have a decent external antenna?
Does the photo in the last link actually show an external antenna on the Nabu Casa stick?
Razberry 7 Pro. I'd prefer an 800 series controller though.
That's an early prototype, but it's likely going to have one
I'm very tempted to wait for the NC stick.
@versed pivot Is there any update on the release date of the Nabu Casa zwave adaptor?