Hi, and thanks for the quick response.
I tried the roll back but found that the Lolin S2 Mini was not an option in that version. I tried the Wemos D1 ESP32 and it would compile but the upload failed "Chip is unknown ESP32".
I am going to try and use an external FTDI to avoid issues with USBCDC. If that does not work I will just use the D32 module.
Thanks for the great body of work and support. I cannot even imagine how much work it must be to try and cover all the different chips and modules.
The integration with Home Assistant makes this a breeze!

Thanks for the quick response.
Yep! When I updated the IDE I forgot to modify the settings (915 MHz) in the new myconfig.h file.
Doh!
All good now.

When I enable debug logging in the MySensors Home Assistant integration I notice I get a fair amount of entries that seem to have nothing to do with MySensors. This includes notification updates, WiFi connection failures, etc.. Is this normal?

Thanks for the quick response.
Yep! When I updated the IDE I forgot to modify the settings (915 MHz) in the new myconfig.h file.
Doh!
All good now.

I have 3 remote nodes working off one gateway. The gateway is a ModeMCU 1.0 and remotes are Arduino Pro Minis. Radios are RFM69s. All 3 remotes have run great for about a year.

Yesterday I made a minor change in the code that reads an analog voltage on one of the remote units. I compiled the new code and received an error message that “RFM69_getReceivingRSSI()” statement should be changed to “transportGetReceivingRSSI()” so I made that changed and the code compiled.
I uploaded the new code and now that node will not connect to the gateway. The serial monitor log shows repeated TSM:FPAR:NO REPLY and then TSM:FPAR:FAIL. The other two remotes are still operating normally.

I tried the troubleshooting steps including clearing the eeprom, and double checked the IDE settings, but still cannot connect. I also powered down the two working remotes and checked with MySController and all I see in the event log is
“Gateway startup complete” and “2.3.2” messages. No other nodes.

I had updated my Arduino IDE since the last programming was done about a year ago, and I did not track which versions I was using then. Current versions are IDE – 2.2.1, Pro Mini board – 1.8.6, and NodeMCU board – 3.1.2, MySensors library 2.3.2.

I then decided to try monitoring one of the working remotes so I uncommented the debug statement and compiled (got the same warning about “RFM69_getReceivingRSSI()”). Now that remote will not connect either.

I appears that the problem is related to my IDE but I cannot determine what it may be.

Does anyone know what change would have triggered the “RFM69_getReceivingRSSI()” error and is it possible that that change is also causing the newly compiled code to not connect?

Thanks! Thought I was losing it.

Is the Forum Search feature broken?
I am logged in and It does not matter what I enter in the search field, or the search settings, the result is always "no matches found"!

Thanks for the response. Can you be more specific about how to request the status from the node?
My understanding is the request format is:
request (Child_ID, VariableType);
But if the Home Assistant entity that I want to request the status of is not a MySensors entity it will not have a Child_ID. So how do I format the request statement?

I am trying to use a battery powered node to control a window blind. The sleep function does not cooperate well with a control entity due to the sleep delay interfering with the acknowledgement timing.
I saw in another post that there is no "optimistic" mode available with the MySensor integration.

Does anyone know if it is possible for a node to request the status of home assistant entity that is not defined as part of the MySensor integration?

Thanks, the 600000 was a typo. Should have read 300000.
I finally got time to set up a terminal on my laptop so I could capture the serial monitor output from the node and then processed that with the log parser.
I could see the node repeatedly attempting to find parent, failing, and incrementing the "transport failure counter", waiting 10 seconds, then trying again. There was also a sequence where 4 failed find parent attempts incremented a "consecutive failure counter". And another where it incremented a "failed uplink counter". I also saw the node initiating the 5 minute sleep interval however the pre-sleep message also failed and hence the node never did get to snooze, it just went back to finding parent. After a fair amount of analysis I was not able to determine what was "special" about the instance when it actually connected or why it occurred at roughly 5 times the normal sleep interval.
I reviewed the MyTransport section of the API documentation but could not find any details that helped.
In the end I lost interest as I decided to just reduce the modem bit rate to the point where the radio would connect reliably. I was surprised to see the node connecting with RSSI as low as -106 dB ( at a bit rate of 2400/4800).

And just to add a clarification, do not modify MyConfig.h. Put the define statement into the sketch for your node (somewhere before line: #include <MySensors.h>), and don't forget to modify your gateway code as well.
0

Working great! Thanks very much!