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

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.

@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

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

You should do the same for requestTime();

@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.

Did you try this?

https://forum.mysensors.org/search?term=ets_update_cpu_frequency&in=titlesposts&matchWords=all&sortBy=relevance&sortDirection=desc&showAs=posts

@mfalkvidd said in Strange behavior on MQTT Gateway Reset:

MySensors does set the retain message on I_BATTERY_LEVEL messages (but no other messages)

If the define MY_MQTT_CLIENT_PUBLISH_RETAIN is used, all messages are retained. But that is not active by default, so probably not used in this case. Just to be complete

@stkilda you can already gain quite some power saving if you take off the led and sleep the node, activate it when there is something to do.

you could have a look at this example for inspiration:
https://www.mysensors.org/build/pulse_power

@mhkid the value you see is the millis() timer, so doesn't show the actual time.
There are serial monitors that can add a timestamp in front of each line. YAT for example

Now you are sending the message every second, even if the state didn't change.
If you check to the previous state, and then send when the state changed it would be more efficient

Radar doesn't go through metal, so aluminium foil should already do the trick

The long sleeps in between your send functions are not really needed, if you would like some time to charge the capacitor (this is done in milliseconds), a delay will also do.
But that doesn't explain the duplicate messages. Can you post debug log for both situations? If you suspect the drivers, it could be better to open an issue on GitHub

Could you post your code? You say you have added sleep statements, I'm wondering where you placed them.
If you see duplicate messages, the hardware ack as sent by the gateway is not received by the module. So you should check the gateway also. Power supply, antenna, these kind of things

@dzjr
I use node-red and it is really stable. Mysensors gateway is ESP32 based with MQTT.
In the past I had some stability issues, but these were caused by plugins of Node-red. Perhaps this is a cause for your stability problems also? I don't know Domoticz, but I do know it is used very frequently so should be stable. Also corrupt SD cards can cause stability issues

Are you sure the node can reach the gateway? So is the connection okay?

How is your memory usage?

@un4 did you try it without the sleep function enabled?