I cannot send orders through paperui to any zwave device for eample turninig a z-wave switch on:
(thisis an eample!!! i doen´t work on any device)
lsdev /tty is o.k.
z-stick is correct implemented
In the meantime i downgrade to 2.5.6-2 !
Now most of the devices are back on function (i have now not the time to check everything!
BTW when i clear all cache as often descript in the forum and delete all unworing an deleted notes from the z-wave-stick as descripted with the zensys ZWaveController tool in the early days all these devices are gone when you do a rescan after rebooting (or restarting) openhab. Until 2.5.3 the devices aren´t delete they come up all the time! how can i get rite of these?
Background on every update i lose contact to devices and get thme only back by delete and reset to fdactory and then reinitial to openhab … and it is not only one… so after a few updates you have more unworking nodes in the discovery then new ones… and mark them unseen is ignored after a reboot
Due to your post I did the upgrade from 2.5.6 to 2.5.7 now (OH was shut down for that). After the first start of OH the logs grew very fast with a lot of exceptions. I let the system settle down a while, then stopped it again, deleted the logs and restarted OH. Everything worked again. For testing I changed the state of a switch (as Bruce correctly suggested not in Paper UI but in a sitemap, rendered with Basic UI. It worked fine.
Althought a bit of a nuisance, the procedure to restart once or twice after an upgrade is “normal”. You should go through that process in the first run before considering “everything broke” due to the update. We will see, whether that will improve in OH3.
I seem to recall after the update completed, it said openhab2 was not running, therefore was not going to restart it. (however, it actually was running). So i performed a manual restart of the pi.
Then my memory usage was very high, so i performed another reboot and things leveled out and after some time came back working. Not a big deal.