maxwellhadley
commented
6 years ago It's not the Pi that is overloaded, it's the RFXtrx433E!
The RFXCOM: ACK - transmit delayed (1) message is one of the possible response codes of the RFXtrx433E to a command message sent to it from the Pi. I have never seen one happen myself, but as I understand it, it means that the command message has been received OK, and is no longer in the (400-byte-ish) RFXtrx433E serial input buffer, but it cannot be transmitted yet because the radio channel is not clear - either the RFXtrx433E is hearing other devices transmitting, or previously-received commands are still being transmitted by the RFXtrx433E itself. This should be OK, it is not an error. Presumably, the message is transmitted eventually...
The RFXCOM: Timed out waiting for response (6) message is generated by my software if the Pi has not received a response from the RFXtrx433E in reply to a message (generally a command message, but there are a couple of other message types this applies to as well) after 10 seconds. In theory, this should never happen, but it is possible the RFXtrx433E may fail to respond in the time allowed if the channel is very busy. My software never sends more than 3 messages to the RFX433E at a time: it will wait for either a response, or for the timeout, before sending the 4th message. This avoids over-running the RFXtrx433E's serial input buffer. Everything should just recover by itself after a timeout, but it is possible the message that was not responded to didn't get processed correctly by the RFXtrx433E - which would be a firmware bug.
If you have the 'retransmit after a delay' option enabled on your rfx-lights-out node, that will of course increase the number of transmitted messages, making it more likely.
Mastiffen
I keep getting a bunch of these, plus some "RFXCOM: Timed out waiting for response (6)". Do you have any idea what this can be? I have 20 temp sensors that sends, and I am sending out AC commands to six switches. Is it because this is too much? I did not have any problems with this when I had the RFXtrx connected directly to EventGhost. I am now running a Pi setup with the RFX, Tellstick and Z-Stick controlled by Node-RED and then MQTT to EventGhost, where the "hevy lifting" of the scripts is done (pretty heavy, my heating control script is 600 lines). In Node-RED it's just this script to convert Viking sensors to MQTT messages:
`var protocol = "Viking";
var tmp = msg.payload.temperature.value;
var id = msg.topic.split('/')[1].split('x')[1];
id = parseInt(id, 16);
msg.payload = protocol+','+id+','+tmp;
return msg;` (Without the extra line feeds, for some reason the code view insisted to putt everything on one line here with only one LF between the lines.) And then a small script that changes the MQTT messages from EG to Node-RED into signals to the AC switches. So there really should be no reason to think that the Pi is overloaded.