Hello, I am a beginner in node red and would like to save the data from the dht22 sensor in mysql and display via chart. I have already tried a lot but unfortunately without success.
Thank you for swift reply.
Given the problem takes place in ~20% of cases it seems the problem is really caused by forcing echo. Since MySensors can cope with 80% of triple messages I believe cutting the number of messages by half would solve the problem. I do not observe issues during presentation though my heaviest node has 9 children.
It also seems to be a better way than engaging in multicast feature.
So the problem becomes more Home Assistant related... Given the ack (Enhaced Shockburst) mechanism, forcing echo seems to be redundant. Instead, the failure of message sending should be reported by the gateway - is there any mechanism possible? I only noticed the send() function returns bool as an advice but did not notice an equivalent returning feedback from gateway via ehternet/serial/mqtt.
The documentation says there is an 'optimistic' option, where "Home Assistant will assume any requested changes (turn on light, open cover) are applied immediately without waiting for feedback from the node", so I believe HA does not require echo.
Unfortunately when trying to set that nothing really changes , and I get the following HA log:
optimistic option for mysensors is deprecated. Please remove optimistic from your configuration file
I will post a suggestion to HA forum to restore this option, unless you know a (good) reason for removing optimistic from HA?
@FlyingSaucrDude
What great timing (for me anyway), only this week I purchased the Adafruit RFM95 Bonnet version, and this thread is the only thing returned in a quick search. Your solution works for RFM95 also.
I didn't need to comment out the code that prevented toggling the CS_PIN, but I'm using the development version as the main branch dose not seem to build on Pi OS Bullseye.
./configure --my-transport=rfm95 --my-rfm95-frequency=868 --my-gateway=ethernet --my-port=5003 --my-rfm95-cs-pin=26 --my-rfm95-irq-pin=15 --extra-cxxflags="-DMY_RFM95_RST_PIN=22" --spi-spidev-device=/dev/spidev0.1 --spi-driver=SPIDEV
Thanks to your post I got this working in a few min of trying, would have taken me much longer otherwise, so thank you for posting to an ancient thread.
I have an almost identical issue with me ESP MQTT gateway no longer connecting to nodes. Similar issues to start with in that it was good for a number of months then would stop, restart ok, then multiple restarts to begin working. I have now resorted to changing out the 24RF01 module and the ESP to try and locate the issue. Will let you know how I get on.
Hi @frapell,
does the network id (MY_RFM69_NETWORKID) used on the node and the gateway match? Also other communication parameters like MY_RFM69_MODEM_CONFIGURATION, for example.
If, for example, your node has the following parameters...
#define MY_RFM69_NETWORKID 123
#define MY_RFM69_MODEM_CONFIGURATION RFM69_FSK_BR55_5_FD50
... you should pass the same parameters to the configure statement:
--extra-cxxflags="-DMY_RFM69_NETWORKID=\(123\) -DMY_RFM69_MODEM_CONFIGURATION=RFM69_FSK_BR55_5_FD50"
Also check if encryption settings match, if encryption is enabled.
another update:
another (same) board found, and tested... problem persists.
"Verify fail" starts between 670 and 690 message received ...
it looks like something get full and nonce is not included in hmac generation.
Hi there,
Thanks for your response! It turns out I needed a better 3.3V power supply because I was powering the NRF24L01 from the Nano's 3.3V pin which is derived from the CH340 USB-Serial converter and is not ideal. Upgrading the supply to an AMS1117 3.3V supply solved the issue completely!
Sorry for the late reply and thanks so much for your tips! Will try them out if issues crop up in the future.
