I have 5 pop thermostats running and 3 switches. It works fine for 18 days with no updates or changes. Only the 5 thermostats to test the config. But after 18 days the system gets errors. After a restart of the service or an reboot of the system the error arrived after a few hours. And won’t go away.
So when this happend i can reboot every two ours to keep up the zwave stick and binding running. Only a new install solved the problem for a few days.
Im using a Aeon stick plus. And a RPI3 with raspbian 2.1.0-1 (Release Build) on it. My anel relays binding works stil fine and the squeezebox binding also. Rfxcom binding is no problem with usb. Only the zwave gets I/O errors.
Is it an option to run openhab at an other device as an RPI3?
Otherwise i must buy a tado system with new thermostats. To have a heating home with no worries and a happy wife And do everything with openhab accept zwave.
2017-10-31 09:25:40.068 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2017-10-31 09:25:45.073 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2017-10-31 09:25:45.078 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
I switched already to an Xtreamer nuc / pc and installed not an openhabian installation but a plain openhab.
So i can’t give you the log anymore. Otherwise i have now also a lot of problems with switches and popp thermostats. Everything what communicate with ip from openhab to another device (like the Anel PwrHut relais) works perfect.
Squeezebox works fine. Only zwave is an difficult chapter… I use Qubino Flush 2 relay, Qubino dimmer dinrail and Popp zwave radiator knop. But i’m thinking to buy a Tado heating set. Then is the heating system standalone.
But stil the zwave problem remains with the dimmer en relais. After a couple of times to pair the device. All the items wil work. Sometimes it doesn’t report the enery level. Or the temprature or the manual switch command won’t be updated to openhab.
This is a VERY long thread where security features are developped. Please can you be specific about the problem. ZWave currently has around 650 devices included in the binding - it’s quite complex, and for sure there will be some things that don’t work with every device when there are so many devices to support.
I’m afraid I don’t actually know what the problem is that you are describing? If you can provide a description of the problem, and a debug log to show what is happening, then I’m happy to look at it, but a general statement like this is really hard to comment on I’m afraid.
You seem to be a very experienced openHAB’er, so my apologies if the following is an obvious or stupid suggestion.
In the past two years that I have been running openHAB on an RPI3, I have experienced relatively infrequent, seemingly random problems and crashes. Sometimes the problems were repeatable enough that I could definitely correlate them with a specific release (I have been running 2.2.0SNAPSHOT releases for some time now.) Other times I could not correlate the issues with a specific OH2 SNAPSHOT release, rather I found that I needed to move most of my USB devices off of a direct connection to the RPI3 and onto an externally powered USB hub connected to my RPI3. On at least two separate occasions, this change to my system took care of the problem. I now have three devices connected via the powered USB hub:
I realise this is a very old thread. I’m using a 2.5.0 snapshot Zwave binding which works well, however on a Intel NUC box after a number of days (generally when we are away from home for a few days) the following error occurs:
2020-05-18 17:08:27.073 [WARN ] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
A restart fixes it. It appears the controller goes offline after a while, this doesnt seem to happen when the system is used daily when we are home.
Any thoughts as to why this would occur? The Aeotec Z Stick is directly connected into the NUC and the NUC is mains powered.