If you want to use library functions outside the main sketch, you can also just include the core header, e.g.
#include "core/MySensorsCore.h"
If you want to use library functions outside the main sketch, you can also just include the core header, e.g.
#include "core/MySensorsCore.h"
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
I haven't tested it, but this one seems to fit what you need
https://github.com/mycontroller-org/serial2mqtt/blob/master/README.adoc
@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 should move the define for the node ID before you include mysensors.h
Exactly. Better to ask then waste many hours
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.
I am using the Pinchange interrupts to wake up from sleeping.
Maybe this helps?
See code snippets below.
#include <PinChangeInt.h> //include PinChange lib from MySensors utilities
in setup()
attachPinChangeInterrupt(BotLeft_PIN, BotLeft_ISR, CHANGE);
and in the ISR
void BotLeft_ISR() {
_wokeUpByInterrupt = 0xFE; // work-around to force MS lib to handle this interrupt
// more code here
}
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
@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
You should only include the relevant header file in the file Gestion_Porte.hpp, not Mysensors.h
For example
#include <core/MyTransport.h>
There are two drivers on the RFM69 which aren't compatible. Check if you are using the same one on nodes and gateway.
MY_RFM69_NEW_DRIVER
Also the radio settings have to match.
https://www.mysensors.org/apidocs/group__RFM69SettingGrpPub.html
You need to send the initial state of the sensor
https://www.home-assistant.io/integrations/mysensors/
@dbemowsk You can also use google and add mysensors before the search phrase
If the message is retained, it will show up already when you connect MQTT explorer to the broker, without HA sending a message yet
Could it be the MQTT message is retained? You can use a tool like MQTT explorer to see this
With some logic in home assistant like in an automation or node red, this is possible. Use a helper function to set the state, and request that status from the node
If you are building a presence sensor, take a look at the LD2410.
Also check the review from Andreas Spiess:
https://m.youtube.com/watch?v=dAzHXpP3FcI&vl=en
600000ms is 10 minutes
Perhaps messages gets lost in the other room?
Mysensors is a protocol on its own, so it will not decode your doorbell signal.
An Arduino nano can't be reached over SSH no, the Arduino has a usb connection which gives out serial data to the raspberry