v0.7.26.5-beta
- Minor bugfix related to "ghost" devices.
Thanks to @SuperDupe for helping gather data to track this down.
v0.7.26.5-beta
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...
@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?
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:
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.
Release v0.8.27.5-beta
Note: In the next release, I am planning to cleanup some old code, which will likely limit support to HE 2.3.8+
As always, let me know here if there are any issues found.
I find this app extremely stable and extremely useful. Thank you!!!
Don't you think its about time to bring this app out of Beta and give it a 1.0 release?????
@dean Good question. Thanks for asking. I actually do have plans to release 1.0 later this year. It is a work in progress with a few new features and a some improvements to the user experience. Hopefully more details will be provided soon.
All software is a "work in progress". But if it is stable and provides the basic functionality expected, it should be considered a "Production" release.
Your software is stable (no crashes or error messages) and provides sooooo much information about my Z-Wave devices. The "beta" designation and "0," release, implies some instability which your app does not have.
Thank you, again, for a great app.
Amazing tool, so much more helpful than the built-in table in the settings!
One question: I want to reset the data, and I can't find a way to do it. I see a "Clear All" button on the top right, but it's disabled. How do I reset the measurements?
Reboot the hub. It pulls all the data from the hub endpoints and they are cleared when you reboot.
Quick Note: A recent platform change disabled the job that was updating the Z-Wave Statistics periodically. I am working on a solution to refresh the stats from within this app and hope to have a new release out soon (it maybe after the holidays).
In the mean time, the official method to get the Z-Wave statistics updated is to use the "Refresh Statistics" button on the Settings -> Z-Wave Details screen.
Thanks so much, Tony, for this great tool!
Latest release: v0.9.1.1
Possibly a candidate for a separate post but it relates in part to this app...Feel free to split it to a separate thread if necessary.
After a reboot of the hub or update, many of my devices show 'unknown' for 'LWR RSSI' and 'RTT Avg'. Understandably that's because the hub has not yet sent a command to those devices in order to calculate a value. A number of my devices are not used in any automations and so remain 'unknown'. It seems as though I get a lot of funky routing until they've populated a value. My fix for that was to turn the device on or off from a dashboard to immediately update it. I've since found that simply clicking the 'refresh' button on each device page has the same effect. I'm wondering if there's any custom app available that can execute a 'refresh' on each device rather than me doing them all manually. I guess I could do it in RM but thought I'd ask here first.
I have used Device Activity Check to do this before, install a separate instance of the app with a 1 minute threshold, add them all to the refresh list. You can run it manually from the app or setup a button/switch to trigger it. Sort of overkill but it got the job done for whatever I was testing.
Thanks Jeff. I noticed in RM there's an action for 'refresh' but it doesn't allow metering. So I'm doing a rule with 'custom action' and using 'refresh' as the command to send as that allows metering. I'll probably set a trigger of system start and have the first action as wait for x minutes (settle time in case the hub is busy)
I actually looked at adding some network-wide refresh capability to this Tool. The problem is that i couldn't find a good way to do this that would work effectively as a general feature without building a whole new app just for this.
There are just too many variables when it comes to the variety of device types, drivers, capabilities, network sizes, topologies, etc., and it became clear that any general approach, especially when it comes to z-wave networks, needs to be careful to avoid unexpected problems, network floods, etc
v1.1.34