I haven't tested it, but this one seems to fit what you need
https://github.com/mycontroller-org/serial2mqtt/blob/master/README.adoc

You can remove these lines, the declaration is already done in the MySensors framework. For presentation() it is needed because you write code there, that is in the function. Now you only call the function, and the code is already in the framework.

Exactly. Better to ask then waste many hours

If you use an ISP programmer, you can reprogram the fuses and use it on lower voltages also. Upto 1.8v but also 3.3v

@skywatch said in Auto resend on NACK:

@electrik & @Marek - Are you both sure about that? It seems to me that both those statements are doing what was intended.

Now that I see it again, I'm not so sure anymore actually.

In your code you used the variable msg. That should be one of msgFgeHum, msgFgeTemp, msgFzrHum, msgFzrTemp.
That is why the compiler complains msg is unknown.

You also enabled the ack message, this is just a software acknowledge, while the send function returns the status of the hardware acknowledge. So if you check with

if (send(msgFgeHum.set(fgehum),true))
{
// this is sent ok
}
else
{
// sending failed
}

you check if the hardware acknowledge was successful. The software ack should be tested differently and some more logic is needed for it.

Hope this helps

@skywatch still if you use wait(), the rest of the code in the loop is not executed during the waiting time. Only the mysensors core is executed

@niclas comment the

#define MY_DEBUG

In your gateway sketch

@harrdy You don't have to use a stepdown board, you can just use a resistor divider to lower the voltage.
With one diode you will still not have a DC signal yet, better to use two diodes or a bridge rectifier. After the rectifier place a capacitor and the resistor divider.

@martim Did you read this thread?
https://forum.mysensors.org/topic/9431/solved-esp8266-mysensors-2-2-0-problem-with-static-ip-configuration

@jocke4u said in Migrating from openHAB to Home Assistant:

But get in logs a lot of:
2020-05-26 17:32:30 WARNING (MainThread) [mysensors] Node 49 is unknown
2020-05-26 17:32:40 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-26 17:32:50 WARNING (MainThread) [mysensors] Node 49 is unknown
2020-05-26 17:33:10 WARNING (MainThread) [mysensors] Node 49 is unknown
2020-05-26 17:33:30 WARNING (MainThread) [mysensors] Node 49 is unknown
2020-05-26 17:33:39 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-26 17:33:50 WARNING (MainThread) [mysensors] Node 49 is unknown
2020-05-26 17:34:10 WARNING (MainThread) [mysensors] Node 49 is unknown
2020-05-26 17:34:13 WARNING (MainThread) [mysensors] Node 3 is unknown
2020-05-26 17:34:13 WARNING (MainThread) [mysensors] Node 3 is unknown
2020-05-26 17:34:14 WARNING (MainThread) [mysensors] Not a valid message: value must be float between 0.0 and 100.0 for dictionary value @ data['payload']
2020-05-26 17:34:30 WARNING (MainThread) [mysensors] Node 49 is unknown
2020-05-26 17:34:33 WARNING (MainThread) [mysensors] Node 4 is unknown

These are caused by the nodes not correctly being presented to home assistant.
Check https://www.home-assistant.io/integrations/sensor.mysensors/ for some examples of what the sketch should do so it is recognised by home assistant.
Mainly presenting the sensors and sending a value to the controller.

This sensor is used here also

https://github.com/rikki78/AirQuality

To me the errors look like you have connected the gateway to your home assistant controller, and that home assistant is configured for a serial gateway.
Home assistant is processing the debug output as the data it is expecting.
I think you should check your configuration

There are many examples...
https://forum.mysensors.org/topic/3764/p1-smart-meter-nta8130-readout-using-mysensors/7

Or on GitHub, needs some tinkering to integrate in mysensors

https://github.com/search?l=C%2B%2B&q=P1+meter&type=Repositories

Edit
There is also a library available
https://github.com/matthijskooijman/arduino-dsmr

These timeouts depend on the Arduino framework, not on the mysensors framework I guess.

@NeoX said in Unblocking loop when DHCP fails:

but then framework is waiting for connection to MQTT server.

Does your MQTT server have a IP at that moment?

I believe this delay is caused by requesting the IP address from your DHCP server. This request has a timeout and the framework waits for this timeout to be completed before continuing with the rest of the code.
Maybe you could try a static IP address instead of DHCP?

@Adam-Slowik said in CAN bus transport implementation:

20:30:09.340 -> 2097 !TSM:FPAR:NO REPLY

This means the node doesn't get an answer from the gateway on the find parent request. If that occurs three times, the transport is reinitialised

Like @mfalkvidd said, if you use the new driver, you have to use it on all of the nodes and the gateway, as it doesn't work together with the old one.
You said your code is a mess, maybe it is better to step back and use examples for both the node and the gateway and start from there. If that is working you can add your code. Just to exclude something is overlooked.

@scalz
Could you explain how to read these rssi reports, and how to adjust the configuration of the nodes so the reliability goes up?
I know there is a setting RFM69_TARGET_RSSI_DBM but it is not clear for me how to use this exactly.

@hakha4 said in Help needed to setup a RFM69 & ESP8266 Gateaway on Adafruit Feather Huzzah:

There is another version named 'HW' which give a higher transmission output (+20 dBM).

There is a black spot on the PCB after "69H" and after the "W" so this is the RFM69HW

The modules correspond to what it should be.
It looks like your ground is connected to the ANT pin on the picture, on the bottom side of the PCB?