Unable to Open ozw-admin version 0.4.4

[schildgenb]

I updated the OpenZwave addon to version 04.4 and now I am unable to open the ozw-admin in all the methods as it keeps killing the add-on and stating connection refused. Below is the log:

1592494485: Socket error on client qt-openzwave-1, disconnecting.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
1592494485: mosquitto version 1.6.8 terminating
1592494485: Saving in-memory database to /data/mosquitto.db.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

[schildgenb]

I was able to get a screenshot of an error that occured:

[Kurisutian]

Same here. Any known solutions exist yet?

[kpine]

Did you try changing the configuration setting as described in the error message?

[Kurisutian]

How? Couldn't find the option to set in the configuration.

[kpine]

Go to File -> Preferences -> Network in the tool.

[Kurisutian]

Well, I was so focused on the configuration of the addon itself, I didn't check the UI... thanks for the hint. Unfortunately when going there the VNC screen gets disconnected right away. Can't get it to open the settings.

[kpine]

Are you using version 0.4.4 of the addon?

[Kurisutian]

Are you using version 0.4.4 of the addon?

Yes, I just updated. Worked with 0.4.3

[schildgenb]

It happens the same here with the addon webui it disconnects right away. I tried the OZW-ADMIN tool download and it works with that one when I change the settings. I am also on 0.4.4.

[natekspencer]

Same issue here. 0.4.3 worked, but 0.4.4 results in this error. Can't change settings in the web-ui, but I can change the setting in the downloaded tool and get it to work.

[kpine]

There was a bug that would result in the application crashing if opening preferences before connecting, kind of sounds like that, but the fix was included in 0.4.4, so I guess not. I don't use the addon, but the allinone docker image, and it works OK.

[kahnman]

I too am getting the "Please Increase the Network Cache Size in the Configuration. Current Setting: 1000 Remote Max Records: 1294" error.

I am also unable to change the cache size because just like @Kurisutian, VNC disconnects immediately after clicking on "Preferences" with the error: "Connection reset by peer (10054)". I am using version 0.4.4 of the Add-On.

[kahnman]

With the help of freshcoast in the zwave channel on the Home Assistant Discord, we found a work around for this issue.

Download the OpenZWave Admin program. I downloaded the Windows version (OpenZwave Admin-0.1.0-installer.exe). Version 0.1.63 didn't seem to work for me.

In Home Assistant, on the configuration tab of the OpenZWave addon, make sure that the host value for "ozw-admin port" is changed from "null" to "1983". That opens port 1983 on the addon container.

Open the OpenZWave Admin program.
Click File > Preferences
Click the Network tab
Change the value of "Network Object Cache" to a number higher than the error you're getting. My error said "Remote Max Records: 1294" so I changed Network Object Cache to 2000.
Click OK.
The program will close.
Reopen the OpenZWave Admin program.
Click "Open"
Type the IP address or host name of your Home Assistant instance in the "Remote Host" field.
Set the port field to "1983".
You should likely leave the Authentication Key field blank.
Click Start

[Veldkornet]

I have the same problem, and then my OpenZWave add-on immediately crashed right after.

[Fishwaldo]

The crash on clicking Ok on the preferences/config window has been fixed upstream.

As for the actual message about increasing the Cache Size - its a work around for a upstream bug. Until thats fixed, you have to manually adjust the value in the "File" -> "Preferences" -> Network window and restart ozwadmin

[SirDeadlystrike]

Same issue, but I can't edit the settings. If i click "File" -> "Preferences" the vnc viewer disconnects immediately every time

Edit: nvm - didn't read high enough. Guess I need to use the desktop version

[jef-pearlman]

Just a me too post.

I get the same error and configuration menu option crashes the app in 0.4.4. I was already using a Windows ozwadmin sometimes, and was able to update that configuration and make it work, but the windows client is not always available to me for other reason. Thanks!

[abmantis]

With 0.5 (#1444) I'm now able to access the Preferences menu and increase the cache size.

[wrkn4alivn]

Just updated to 0.5, and I can also report that the Preferences menu now works. I increased the network cache size and can successfully connect to the remote daemon. However, as soon as the admin UI populates, VNC disconnects the session (Error: Network connection lost). This happens whether I use the Supervisor web client or separate VNC client to port 5900. Are there logs I can check for this, and/or should I file a separate bug?

Edit: also FYI for those going that path for now, it appears that the OpenZWave Admin 0.1.0 for Windows does not work with 0.5, you'll need to update it (0.1.74 works).

[MartinHjelmare]

I'll close here since it now works to access preferences and change cache size to get the admin running. The background to this workaround is an upstream bug, as per #1415 (comment).

Please open new issues for any other problems.