GUI not showing values for all devices

[VinceRMP]

It seems the GUI does not show all values for all devices. I tried it with the latest version as of today on Windows, OSX and the new allinone build which is linux based.
I have 60+ devices added to the controller, these devices are all functioning correctly and showing up in mqtt with all the correct values. It is also possible to change them from there and Home Assistant and use them.
The values are not visible in the GUI for the first 17 devices, but the following 45 do show all the values as expected. I tried a refreshnodeinfo on the nodes that are not displaying correctly. After the refresh the node moved to the bottom of the list and shows the values, but the first 17 nodes still don't show any values. So there is a new node which did show the values and after refreshing another node it now doesn't show it anymore.

Somehow it looks like it is only possible to show values for the last 45 added nodes.
I hope the problem is clear and if not please let me know.

[Fishwaldo]

I've just added some additional logging. If you can try the allinone build 9 or 10 (not sure which build the changes will end up in) and later post the results of the config/logs/ozwadmin.log file here please?

[VinceRMP]

See the attached log file. I must say the new ozwadmin uses 100% of the cpu and hangs after a while within docker but also using osx. I tried clicking around a few nodes. So I hope you can use the information.

Edit: Above problem was on my side, don't know what happened but it seems to have settled.
I attached a new log file. Node 19 and higher show the values everything below 19 doesn't.
ozwadmin.log

[Fishwaldo]

Can you give it another go with the allinone build-12 (should be there in a hour or so)

[VinceRMP]

I tried it again with the image openzwave/ozwdaemon:allinone-amd64-12
It gives the same result, see attached log file:
ozwadmin.log

[Fishwaldo]

Hi,
I added a lot more logging again - Could you try with AllInOne-13 (Builds starting soon).

[VinceRMP]

Hi, thanks for the active support!
I attached the log file (Zipped this time, logging is indeed insane :) )
ozwadmin.log.zip

[Fishwaldo]

Indeed something is very broken..... You say the MQTT Topics are all valid?

Any chance you can try a "local" copy of ozw-admin (meaning you connect to the USB device instead of over the network)

That will just help me narrow down the where the problem lies (either in the wrapper from OZW, or the "network" code to transfer the data to a remote application)

[Fishwaldo]

(I just committed back a update to turn the logging down again)

[VinceRMP]

Yeah they seem fine. All devices work as expected. In ozwadmin I can't see the current states at all or change them. This works fine from Homeassistant or the mqtt topic to change device parameters.

If you want to I can upload the ozwdaemon.log file? It shows that the values are present.

Regarding the local copy. I can do that I guess, but can I use/copy the cache file? I have quite a few battery powered devices and it takes a lot of time or effort to get them to show up without the file. Also it would be from a Windows system, but that shouldn't be a problem, right?

[Fishwaldo]

Actually - If you can wait till the Windows Client Build 128 works (should start soon) and test that version (no need to bump the ozwdaemon version)

http://bamboo.my-ho.st/bamboo/browse/OZW-OZW-WB-128/artifact