so i just setup OpenHAB with a rfxcom443E but it seems to lock up while being idle for a day.
i enabled debug logging for org.openhab.binding.rfxcom in karaf but nothing shows up in the log then press the buttons on my 443 MHz.
But i get the transceiver status = online message.
Im using OpenHAB 2 on Debian 8, running under virtualbox with the rfxcom attached as a usb device.
What could be causing this?
Does it work again if you restart openHAB? If yes did you test the logging after a restart? Do items pop up in your inbox in th paper ui
i went into the gui and switched on a lamp and then all hell broke loose in the log but i have no idea what it means…
2017-02-24 21:03:56.709 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge ONLINE for thing rfxcom:lighting2:usb0:22741606_3
2017-02-24 21:03:56.709 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged ONLINE for thing rfxcom:lighting2:usb0:22741606_0
2017-02-24 21:03:56.709 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge ONLINE for thing rfxcom:lighting2:usb0:22741606_0
2017-02-24 21:03:56.709 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged ONLINE for thing rfxcom:lighting2:usb0:22741606_1
2017-02-24 21:03:56.709 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge ONLINE for thing rfxcom:lighting2:usb0:22741606_1
2017-02-24 21:03:56.710 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged ONLINE for thing rfxcom:lighting2:72d6f725
2017-02-24 21:03:56.710 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge ONLINE for thing rfxcom:lighting2:72d6f725
2017-02-24 21:03:56.710 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged ONLINE for thing rfxcom:lighting2:6ff54375
2017-02-24 21:03:56.710 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge ONLINE for thing rfxcom:lighting2:6ff54375
2017-02-24 21:03:56.710 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Transmitting message 'Raw data = unknown, Packet type = LIGHTING2, Seq number = 79, Sub type = AC, Device Id = 56780000.1, Command = ON, Dim level = 0, Signal level = 0'
2017-02-24 21:03:57.408 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Message received: Raw data = 0402014F00, Packet type = TRANSMITTER_MESSAGE, Seq number = 79, Sub type = RESPONSE, Response = ACK
2017-02-24 21:03:57.409 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Transmitter response received: Raw data = 0402014F00, Packet type = TRANSMITTER_MESSAGE, Seq number = 79, Sub type = RESPONSE, Response = ACK
2017-02-24 21:03:57.409 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Command successfully transmitted, 'ACK' received
2017-02-24 21:03:57.410 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - Received channel: rfxcom:lighting2:14c64232:command, command: ON
2017-02-24 21:03:57.411 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Transmitting message 'Raw data = unknown, Packet type = LIGHTING2, Seq number = 80, Sub type = AC, Device Id = 56780000.2, Command = ON, Dim level = 0, Signal level = 0'
2017-02-24 21:04:00.948 [WARN ] [ore.internal.events.OSGiEventManager] - Dispatching event to subscriber 'org.eclipse.smarthome.core.thing.internal.ThingManager@4c441587' takes more than 5000ms.
2017-02-24 21:04:00.948 [WARN ] [ore.internal.events.OSGiEventManager] - Dispatching event to subscriber 'org.eclipse.smarthome.core.thing.internal.ThingManager@4c441587' takes more than 5000ms.
2017-02-24 21:04:00.949 [WARN ] [ome.core.thing.internal.ThingManager] - Handler for thing 'rfxcom:lighting2:14c64232' takes more than 5000ms for processing event
2017-02-24 21:04:00.950 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - Received channel: rfxcom:lighting2:72d6f725:command, command: ON
2017-02-24 21:04:01.715 [WARN ] [ome.core.thing.internal.ThingManager] - Handler for thing 'rfxcom:lighting2:72d6f725' takes more than 5000ms for processing event
2017-02-24 21:04:02.419 [WARN ] [g.rfxcom.handler.RFXComBridgeHandler] - No response received from transceiver
2017-02-24 21:04:02.419 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR) for thing rfxcom:lighting2:b5b18ef2
2017-02-24 21:04:02.419 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge OFFLINE for thing rfxcom:lighting2:b5b18ef2
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR) for thing rfxcom:lighting2:14c64232
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge OFFLINE for thing rfxcom:lighting2:14c64232
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR) for thing rfxcom:lighting2:usb0:24205746_0
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge OFFLINE for thing rfxcom:lighting2:usb0:24205746_0
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR) for thing rfxcom:lighting2:usb0:22741606_2
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge OFFLINE for thing rfxcom:lighting2:usb0:22741606_2
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR) for thing rfxcom:lighting2:usb0:22741606_3
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge OFFLINE for thing rfxcom:lighting2:usb0:22741606_3
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR) for thing rfxcom:lighting2:usb0:22741606_0
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge OFFLINE for thing rfxcom:lighting2:usb0:22741606_0
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR) for thing rfxcom:lighting2:usb0:22741606_1
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge OFFLINE for thing rfxcom:lighting2:usb0:22741606_1
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR) for thing rfxcom:lighting2:72d6f725
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge OFFLINE for thing rfxcom:lighting2:72d6f725
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR) for thing rfxcom:lighting2:6ff54375
2017-02-24 21:04:02.420 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge OFFLINE for thing rfxcom:lighting2:6ff54375
2017-02-24 21:04:02.420 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Message received: Raw data = 0402015000, Packet type = TRANSMITTER_MESSAGE, Seq number = 80, Sub type = RESPONSE, Response = ACK
2017-02-24 21:04:02.420 [DEBUG] [g.rfxcom.handler.RFXComBridgeHandler] - Transmitter response received: Raw data = 0402015000, Packet type = TRANSMITTER_MESSAGE, Seq number = 80, Sub type = RESPONSE, Response = ACK
2017-02-24 21:04:02.422 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged ONLINE for thing rfxcom:lighting2:b5b18ef2
2017-02-24 21:04:02.422 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge ONLINE for thing rfxcom:lighting2:b5b18ef2
2017-02-24 21:04:02.423 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged ONLINE for thing rfxcom:lighting2:14c64232
2017-02-24 21:04:02.423 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge ONLINE for thing rfxcom:lighting2:14c64232
2017-02-24 21:04:02.423 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged ONLINE for thing rfxcom:lighting2:usb0:24205746_0
2017-02-24 21:04:02.423 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - initializeBridge ONLINE for thing rfxcom:lighting2:usb0:24205746_0
2017-02-24 21:04:02.423 [DEBUG] [binding.rfxcom.handler.RFXComHandler] - bridgeStatusChanged ONLINE for thing rfxcom:lighting2:usb0:22741606_2
After that it worked as expected again, but its not the first time it locks up…
As i have no idea why its locking up im just going with some random things.
Instead of attaching the RFXCom as i USB device in VirtualBox im now forwarding the Serial port it seems to end up as /dev/ttyUSB0 so no configuration changes on the guest OS was required after that change.
Sadly changing to a serial port had no effect its still bugging out
I have no idea what could be wrong.
Since i die not see any reports about this before I think I might be because of virtual box and the serial port. Do you have the option to run it straight in your hardware instead of via a virtual machine.
I found this link which could possibly be related https://forums.virtualbox.org/viewtopic.php?f=3&t=57227
Thanks for the response ill look at it but, id rather not install java on my host but ill give it some more consideration.