Tried everything, factory reset, set up with and without sensors, router, smartphone, sensors and station right next to eachother. Put way too many hours into this and prefer not to waste the cost of the station and 4 sensors. Help!
@jacmika it would need shell escaping and it is missing the initial D. I would try something like
--extra-cxxflags="-DMY_RF24_BASE_RADIO_ID=0x00,0xFC,0xE1,0xA8,0xA8
If I recall correctly, the output of make will show which defines are activated, and what values they have. That's what I usually use to check if I got it right.
I think I've narrowed it down to encryption, disabling it on the GW and the feather seems to make everything work ok. I've double checked that the key is identical but still won't work.
Encryption works when I use the ESP32 as "client" instead of the Feather M0. I thought the AES encryption was done in the radio (rfm69) and not the microcontroller (ie. ESP32/Arduino etc.).
Also, there's really no log message that indicates wrong encryption key or anything related to an encryption problem in the communication?
@fixjunk this configuration will be supplied to your gateway from a controller.
Source: https://www.mysensors.org/download/serial_api_20
When your MySesnors node boots up, sends a I_CONFIG request to your controller, your controller has to respond to this request [response can be either (M)etric or (I)mperal ]
AFAIK, This metric change will not affect your sensor measurement units. You have to convert yourself in your sketch.
@mfalkvidd can confirm this.
I added a new node(ralay id:50), again home assistant(HA) was not added. How can I send a new value from the Relay?
You need to send a message at least once for it to appear in Home Assistant. Use something like this:
bool initialMessageSent = false;
void loop() {
if (!initialMessageSent) {
send(msgRelay.set(currentRelayState));
initialMessageSent = true;
}
}
After you manually injected a message via MYSController, Home Assistant started to list the new entity in the UI. So yes, that's exactly what Home Assistant required. If you take care of that within the sketch as shown above, you don't need to do it manually.
But It seems to be disconnected from the network every time a command comes from HA.
do you think this is normal?
No, I wouldn't consider that normal. What do you mean by "disconnected"? Does the node stop working completely after receiving a message from HA? Doesn't it respond to consecutive commands?
Does the debug output (using #define MY_DEBUG in the relay node sketch) hint at something? Sharing your sketch may help us find the issue.
Hi all, discovered today this thread while i was searching for a problem of message received twice.
Even though i've been using mySensors for several years, this is the first time i encounter this.
I was not aware there is no guarantee that a message is sent only once....
Unfortunatly, the message is sent to an actuator to tell to "toggle" the light: so if received twice, the effect is not very efficient.
I will have to implement something...
