Topics created by Neo Mod

@neo-mod To me, the log seems to indicate that the radio connection is not working. If the HW is identical (with capacitor on the radio power connection) then I can see two causes: Faulty nRF24. Try switching the radion module Distance between node 2 and GW too far or something blocking the radio transmission. Try moving node closer to GW.

After a long troubleshooting (and thanks to the DEBUG activation) I think I have found at least one problem: the DHCP lease renewal was interfering with correct ESP8266 operation. Every time the router renewed the lease the board was unable to report/reconnect correctly to the MQTT Broker. I have also discovered that in some occasions even though the connection between Gateway and Broker was re-established correctly, the Controller was not acknowledging data received from Broker. In that case a simple “reboot” of the controller was sufficient to establish a new connection. (with Domoticz it was a simple matter of disabling and then enabling the MySensors Hardware). With a DHCP Lease Time set to “Infinity” this specific problem has disappeared, but I still feel the project is quite unstable: I will continue working on it with “debug mode” and hopefully I will write an update on my findings. Thank you once again for the precious support!

@neo-mod said in [SOLVED] MySensors and DHT22 - difficoulties in getting started: I'm using a NRF24L01+PA+LNA and with BME280 I had an overlapping pin ( I followed the "How to connect the radio" official page). I'll open a new thread asking for advice, quite clearly I'm missing something. I checked my code, and I'm using the BME280 in i2c mode. The i2c pins on Pro Mini are different from the SPI pins so there is no overlap. On esp8266, D1 and D2 are used for i2c which means the CE pin must be moved using MY_RF24_CE_PIN but if you do that it should work.

Thank you so much! You just saved me (a certified n00b, I know xD) from countless hours of headache! @mfalkvidd said in ESP8266 MQTT Gateway: Can't Subscribe from Domoticz with Mosquitto running on Pi 3: Just a guess: maybe all you need is to use the rpi3 ip instead of the esp8266 ip?

@Yveaux thank you for your help! yes, that makes a lot of sense actually. My ignorance on the matter kicked-in once again... sorry What I'm missing so is how to create a sensor node which can be operated on battery and take measurements every "x" seconds/minutes/hours: shall I leave the Gateway always on and then configure differently another Node-MCU to act as a Sensor Node ? Edit: In fact all of this was meant, for me, to be a "test run" bedore developing the whole system. I got a little off-road with the deepSleep and Battery thing, but I wanted to have a real-word-test of my sensor left for a day in the soil while sending reliable data to controller. As I'm reading even more documents and forum post, it's getting clear to me that the best thing would be "ask to the comunity" their experience with HW nodes, thus I can decide which one is best for my case.

@mfalkvidd thank you! I didn't noticed that among the whole log, my ignorance about this just kicked-in. Thank you again fo your help, I'll read on how to set the beta library and compile again.

Thank you so much! Well, I just made the first order for components and I have installed a test enviroment for HomeAssistant on a spare ARMBIAN board I had. I'll keep reading the forum and try to prepare myself..then I hope to be back with more practical questions Thank you again for your precious help!