@tony.fleisher, found an edge case bug with a hub migrated from a C5 and nodes 02-05 are actually devices and not the reserved nodes. If you scroll up on this thread you will see the screenshots of the neighbor table.
1 Like
It has been a crazy year for me, but I am finally getting back to this (and finally picked up a C-8, too). If all goes well, I am expecting to have a new release hopefully before the end of the year with a few bug fixes and maybe even a few new features/wishlist items as well.
13 Likes
Awesome... Looking forward to it...
That would be nice.
Hmmm appears my app is not picking up the devices anymore, any suggestions? I am on C-8 Beta 2.3.7.112. Any one else?
He is aware. I notified him on the last beta and he has a fix to do.
v0.7.26-beta
- Support updated zwave details ui
- Fix bug with some zwave devices wrongly being labeled as HUB
- Bug fixes
3 Likes
Hey @tony.fleisher
I have a weird ghost issue that I think is affecting the loading of device details page.
I was trying to kill a failed outlet ghost by using a z-stick. For some reason, the hub would not pair with the stick and after a few attempts, it created three ghosts for the stick...
After getting the stick to finally pair, it does not show the ghost nodes in PC Controller... I'm having a hard time getting rid of them and I believe they are causing an issue with opening your app.
I'm getting this error:
Error
TypeError: Cannot read properties of undefined (reading 'deviceNetworkId')
I don't see a way to remove the ghosts as of right now, but I'd like to get the app working...
Any ideas?
How you powered off the hub fully removed power for 10+ seconds?
The zwave radio could be in a weird state, and the ghosts may be already gone.
Yes sir. Have done that twice. No change…
Weird you mention them possibly being gone. When I first go into z-wave settings, and the devices are lined up in order of nodes, the three ghosts do not show up. When I sort by name, the three show up at the bottom… a-z with the ghosts being at the bottom because they have no name. I’m guessing. With nodes assigned to them.
I thought about the idea maybe they really don’t exist and not worry about them, but they or something else is preventing me from opening the z-wave details app.
The errors in opening the app only happened after the ghosts and failed pairings, so I’m fairly sure they are what’s causing the error.
If you can provide a screenshot of the logs, it might help me track this down.
My guess is that you authorized z-wave devices in the app and then removed one of the devices. I will try to make this more resilient in a future releases. You can check if this is the issue by going into the authorization page, and reselect the devices.
Hey Tony,
I tried going in and re-authorizing the devices... Still get the error. Here is all that is put into the logs.
I really think its picking up those ghosts. This started when they happened.
app:23942023-12-06 18:40:12.344errorzwaveInfo: Error getting zwave Info: TypeError: Cannot read properties of undefined (reading 'deviceNetworkId')
app:23942023-12-06 18:39:53.409errorzwaveInfo: Error getting zwave Info: TypeError: Cannot read properties of undefined (reading 'deviceNetworkId')
Hey Tony,
I tried removing the app and adding back. I then went in and authorized all of my Z-Wave devices again. Still getting the error.
I believe this error is being caused by the z-stick ghosts created when I tried to add my Zooz ZST10 stick to remove another ghost. That ZST10 would not pair and every time I tried, it created a new ghost... I was able to add the ZST39, but that stick when added doesn't show the ghosts created by the ZST10.
In any event, I can't use your app because it thinks those ghost nodes are there and it throws the error.
Trying to get rid of those z-stick controller ghosts has been a real pain and nothing has worked so far. I'm relying of your app to help me with some devices on the edge of my mesh. Seeing their neighbor routing will help me with repeater placement... However, I can't use your app with this ghost issue.
v0.7.26.5-beta
- Minor bugfix related to "ghost" devices.
Thanks to @SuperDupe for helping gather data to track this down.
Hey @tony.fleisher, I literally just got my ghost issues fixed this morning before you put up the new version. I was on the beta firmware, but had to roll back to 2.3.6 so I could use your app. Your app ultimately helped me get rid of the ghosts using the hub and the old shutdown, kill power method. I also had to do a few other things that your app helped with.
For anyone else who comes across this, I got some ghosts with failed parings of a external USB stick. Because they were "controller" nodes, PC Controller couldn't see them and so I had to use the hub to get rid of them.
For the life of me, nothing worked until I noticed, using this app, that the ghost nodes had neighbors and those same neighbors, showed the ghost nodes as neighbors also.
I ended up removing those devices and re-adding them back into the hub to remove any history they had of the ghost node neighbors. When I did that, I was able to remove the ghosts by powering off and cutting all power to the hub, powering on and immediately trying the remove...
That worked and I am ghost free... Since I was beta testing the 2.3.7 version, I will be switching back to that... But I no longer have the ghosts to test for you...
1 Like
@tony.fleisher Just a random idea and maybe you could add it to your tool as well?
Would be nice to see somehow if the device is disabled on the list. Strikeout text maybe, similar to the devices list?
3 Likes
When I launch the app I get this error:
DataTables warning: table id=mainTable - Requested unknown parameter 'label' for row 6, column 3. For more information about this error, please see 4. Warning: Requested unknown parameter
Any ideas?
@user6410 My best guess on this is that there is an unexpected entry in the zwave table (perhaps an entry with no device attached?).
If this is still occurring, please provide the following details to help diagnose the problem:
- Which model hub are you using?
- What is the hub platform version?
- Can you provide a screen capture of the Z-Wave Details page from settings?
Thanks for the reply.
The cause was a Ghoast device - I was able to remove the device and the error message no longer persists.
Thanks.
1 Like
