Packet timeouts are a limited number of times retried but should not occur with a stable connection.
Announcement
Collapse
No announcement yet.
RFXCOM lan device
Collapse
X
-
The problem of the errors where because of a wrong setting in the ser2net config. I have noticed that the connection is lost about two or three times a day. Considered the wifi connection I don't think this is to bad.
But after reconnecting the rfxtrx the RFXCOM plug-in does't update the device status correct. See attachment.
Homeseer log:
29 (aConnectEnd) transceiver #2 reconnected.
Jan-17 11:10:09 RFXCOM 29 (InitTRX) Connect Transceiver #2 on TCP 192.168.1.62,10001
Jan-17 11:10:09 RFXCOM Error: 29 (Reconnect) transceiver #2 stopped due to comm failure, try to reconnect.
Jan-17 11:10:09 RFXCOM 29 (CheckTransceivers) transceiver #2 ping senddata with errorflag, reconnect done?
Jan-17 11:09:25 RFXCOM Error: 29 (SockDataArrival) TCP error
Comment
-
Originally posted by b_weijenberg View PostThe RFXLAN is no longer in the catalogue. Maybe later.
You use an RFXrec433, RFXtrx315 or RFX433E and connect it to a Raspberry PI with socat.
Linux cmd: socat tcp-listen:10001,fork,reuseaddr file:/dev/rfxcom,raw &
You can now connect the RFXCOM over LAN port 10001
Comment
Comment