I have:
You might try on discord to get some quick helpâŠ
Iâm sorry I donât use âaddonâ so someone else can be better help
How can I get to discord? Whatâs that?
I just got the ozw-admin console to work and mine looks exactly as Troys. I had to add 1983 (instead of ânullâ) as the host under the configuration tab of the OpneZwave addon and restart it.
Have you seen my screenshot above? exactly alike.
Ah. Missed that. Then I cannot help.
Iâm not good at Discord but I guess this link should let you find the discussionsâŠ
I have not downloaded any client. It runs fine in the browser.
Then we are not talking about the same zwave here! openzwave (beta) does NOT run in a browser!?
EDIT: you meant discord in the browser 
@mattsjo beat me to it â but there is nothing you need to be good at⊠itâs basically on line chat â community members helping each other out. Itâs better for having a conversation when you need some help
I have not downloaded any client. It runs fine in the browser.
he means discord â not OpenZwave (beta)
EDIT: For these related question I think want to ask in the #zwave channel
Yes⊠Discord in a browser⊠
Install Build #96.
The version of ozwdaemon installed by the addon is not currently compatible with newer versions of OZW Admin. Add addon installed a fixed version of ozwdaemon which is too old.
Can you rephrase, dont get you
The version of OZW Admin that you posted in your screen shot is not compatible with the OpenZWave Addon.
Also, the screen shot version is not Build 96.
This is what Build 96 looks like:
Newer versions that are incompatible with the addon look like this:
Notice the menubar at the top. Build 96 does not have the ability to add or remove nodes.
So, currently. Having the 2 latest versions they are not compatible?
Node Naming/Node Location âsavingâ is sort of a âanti-featureâ - as Freshcoast mentioned, most devices donât support the NodeName CommandClass (unfortuantly!) and it just happened to get saved to the cache file and thus âpersistâ across reboots.
In the âCoreâ ozw library - There is no persistence at all, just the cache file to speed up reboots and we have always held the âyou donât need ozwcache_.xml or previously zwcfg_.xmlâ to run. At the library level, any âpersistenceâ needs to happen on the application.
That being said - Node Name/Node Location is moving away from a â1st class citizenâ in OZW 1.7, meaning it will only be âexposedâ if a device supports it and can store it. If a device doesnât support NodeNaming CC - It wont be available.
I may look into adding some persistence in ozwdaemon in the future (not in the core library) and we can look at it - But essentially, what is working today may not work the same in 0ZW 1.7.
There are âtwoâ options to install ozwdaemon docker image - The one via the HA interface - And unfortunately thatâs running a older version of the ozwdaemon, and running the docker image from the OZW project: https://hub.docker.com/r/openzwave/ozwdaemon thats build everytime I submit a fix etc.
To run the latest version of ozw-admin - you need the docker image from OpenZWave.
This is mainly a transient issue right now - As mentioned above, ozw-admin is very much âalphaâ quality - Lots of work going into it and adding additional functionality. As that functionality is added, I have to add some support to ozwdaemon as well. Once ozw-admin gets âstableâ or feature complete, we should have less issues with version compatibility.
Is there a way to roll back the OpenZwave addon to the previous version?
My network doesnât work with the 0.3.0 version as the controller gets stuck and only queries one node, constantly. Could it be the discovery feature that is causing the problem? Can it be disabled? I upgraded yesterday and everything seems be ok at the beginning with all nodes being queried and so on but at some point it all breaks and get stuck. I have restarted a number of times but the same problem occurs.
The zwave addon is also consuming a lot of CPU time⊠It used to be very low in the list, not at the top.
The log scrolls away very fast. Is it possible to get the entire log somewhere so that I can do some analysis myself to see if I can find out where the problem starts?
Thanks for an excellent job by the way. The new addon (used to) work a lot better than the old built in version.
I managed to roll back the addon using an old snapshot. But it turned out that the same problem occurred in the old addon⊠So I turned off the offending node and Iâm now back at the latest addon and everything runs perfectly again.
Not sure where feature requests for this should go, so will drop a request here. Itâd be good to be able to see the node id as a unique attribute of the device within HA. Especially useful for already created networks with multiple devices of the same type (that you wish to rename without hunting down each device in the house), and bridges the information gap if using tools like ozw-admin.
Iâve run into similar issues running the standard non-beta integration; what I believe is OZW v1.4. I had two different Homeseer MS-100+ motion sensors (I liked them for the microUSB power option) that at times would take down my entire network. It was like a DoS type of attack in effect, but was likely something much less glamorous like lousy chips or buggy firmware. Anyway I had six of those things. Threw them all out.
I know little to nothing about the code that goes into OZW, and perhaps there are already things like this in place, but it seems like routines which are specifically meant to mitigate the non-dead and very chatty devices could go a long way toward network reliability.