Hi
I have found a problem with homeseer and zwave.
I am using a usb zwave interface that i have connected through usb device server from Silex that is connected to the network.
This works great mostly.
But if the network goes down for only 1-2 seconds trouble begins.
The silex device server is connecting directly when network is back and everythings looks ok there.
And the usb zwave has connected to a virtual comport.
But Homeseer stops working and zwave will not go up again.
I get this in log.
Zwave: Cannot open COM port COM3, exiting. Ex=Porten COM3
Zwave: Error, the Z-Wave API Transmit Queue is not empty after waiting 20 seconds - the interface may be disconnected or not operational (Zwave).
There is no other solution to get this to work again without restarting the homeseer service.
This is very bad !!!
I think homeseer should automatically sense that something is wrong with zwave and try to restart zwave or something to get it working again.
I don't know if there already exists a solution to this but if ther is i really want to know.
Is there anybody who know a solution on this ?
Maybe some kind of watchdog to check that everything is ok.
Best regards
I have found a problem with homeseer and zwave.
I am using a usb zwave interface that i have connected through usb device server from Silex that is connected to the network.
This works great mostly.
But if the network goes down for only 1-2 seconds trouble begins.
The silex device server is connecting directly when network is back and everythings looks ok there.
And the usb zwave has connected to a virtual comport.
But Homeseer stops working and zwave will not go up again.
I get this in log.
Zwave: Cannot open COM port COM3, exiting. Ex=Porten COM3
Zwave: Error, the Z-Wave API Transmit Queue is not empty after waiting 20 seconds - the interface may be disconnected or not operational (Zwave).
There is no other solution to get this to work again without restarting the homeseer service.
This is very bad !!!
I think homeseer should automatically sense that something is wrong with zwave and try to restart zwave or something to get it working again.
I don't know if there already exists a solution to this but if ther is i really want to know.
Is there anybody who know a solution on this ?
Maybe some kind of watchdog to check that everything is ok.
Best regards
Comment