@sharpy

It looks like your sensor does not find the gateway.
What does your sensor sketch look like?
What interface do you use to OpenHab? Openhab binding?
Did you set a node-ID manually in the sketch? OH does not assign node-IDs automatically as far as I know.

@neo-mod
To me, the log seems to indicate that the radio connection is not working.
If the HW is identical (with capacitor on the radio power connection) then I can see two causes:

1. Faulty nRF24. Try switching the radion module
2. Distance between node 2 and GW too far or something blocking the radio transmission. Try moving node closer to GW.

@crankycoder
Interesting!
I am using a mobile broadband connection and it seems to have some issues with drop-outs in the connection. I'll pursue this path first.
Power should not be an issue. I have a 2.5 A wall-wart supplying the Pi.

I suspect the OS or maybe hardware as well. When this happens remote ssh is also broken so difficult to know what is going on. I'll try another RPi. Or maybe an ESP.

I have built an MQTT GW on an RPi model A based on the sketch provided on the MySensors Build page.
The settings are as follows:

./configure --my-gateway=mqtt --my-controller-url-address=m24.cloudmqtt.com --my-port=18784 --my-mqtt-client-id=sjovsensors --my-mqtt-user=xxxxx --my-mqtt-password=xxxxx --my-mqtt-publish-topic-prefix=sjov-out --my-mqtt-subscribe-topic-prefix=sjov-in --my-transport=rf24 --my-rf24-ce-pin=22 --my-rf24-cs-pin=24 --my-leds-err-pin=12 --my-leds-rx-pin=16 --my-leds-tx-pin=18

It all works fine for a while but after an hour or so, no more mqtt messages are transmitted to the broker. The logs do not provide any useful information. Either they show that messages are received and relayed to the broker although they are not, or I am not able to log in to the RPi at all. SSH connection refused. I have tried both cable connect and WLAN connection to the router. The router incidentally is a 3G mobile data connection.

I suspect that the RPi somehow has lost the link to the broker or the router for a short while and then is unable to reconnect but otherwise I have no clue.

Ideas welcome!

@ElCheekytico
I cannot find that you set your NODE_ID in the beginning of the sensor sketch.
Since OpenHAB does not hand out node-id as far as I know (I do not use the MySensors binding in OpenHAB since I connect over mqtt) you have to set NODE_ID manually.

Note: The GW does not assign node id either.

In your sensor sketch, start by adding

#define MY_NODE_ID   5

for example and see if you are able to connect.

@patrickl When looking at the log it seems like your sensor with ID=1 is sending data at quite irregular intervals. Looking at the time stamps transmissions happen sometimes 30 seconds apart then one minute, sometimes 3 minutes.

Measurements seem to come in pairs, humidity and temperature?

What does your sensor code look like? Is there something that makes the sensor go wild from time to time and send bursts of measurements, overloading the Vera?

My two cents worth:

I have been battling this issue as well for the last couple of days.
I am now using the master version on an Rpi 1, a really old one. It did work for a few hours, 1 - 10 and then stopped communicating.

The discovery I made today was that I goofed up and built the mqtt version of the gw with the option --my-rf24-irq-pin=15 set in the config file. All well only if I had not forgotten to connect the IRQ from the rf24 to pin 15 on the RPi. Stupid!

So, I rebuilt the gw today without this option and it is still running well after a few hours. We'll see tomorrow.

Hi @Homer
The reason that the controller does not reflect the status of the relay is that you are not telling it that the status has changed.

This is a snippet of how I have coded the same thing:

void receive(const MyMessage &message) {
  if (message.type == V_STATUS) {   
      state = message.getBool();          // Change relay state
      setRelayState(RELAY_PIN, state);    
      saveState(CHILD_ID_RELAY, state);        // Store state in eeprom
      // Write some debug info
      printStateChangedDebug(CHANGE_STATE_SOURCE_RADIO, CHILD_ID_RELAY, state);
  }
} 

// Set status of relay pin
void setRelayState(byte relayPin, bool value) {
  digitalWrite(relayPin, value ? RELAY_ON : RELAY_OFF);
  send(msgSW.set(state), false);           // acknowledge new state to controller, no ack requested
}

When the message is received, I first change the relay, then I confirm the status with the send-message.

Is there any documentation available about what different "error-blinks" mean in the MySensors MQTT gateway?

I just built one based on an RPi A and it works just fine. Now and then I get error blinks, different number of red blinks. They signal failure in some way but what failure? Collision, bad reception or what?