Troubleshooting

@fdlou147 According to my personal experience, I'd recommend to split up Gateway and Node funktionality and use two seperate mcu's. Wrt. to the code itself: you only set up a debouncer on one of the pins (finally: Pin 5), as you always redefine the same "flags" over and over again. Perhaps have a look at this imo excellent multi relay/button sketch by korttoma here. This one should be not to hard to adopt to your needs (still, I'd recommend two mcu's).

@Stab power failure can be a reason, so this can be a good test. If it fails again, then we are sure that it is not the 3.3V from the pro mini who is to weak. If it fails not, we have the solution :-) If I understand correctly, the door bell button is connected directly to the pin 3 of the arduino. When pushed it takes the pin 3 to the ground GND? How long are the wires between the button and the arduino? Are they shielded? Long wires can act as antenna's and inject directly faults into the pins of the arduino causing crashes of the Arduino or even the dead of the Arduino. The best way to avoid these problems is to use an optocoupler. Search on Google on the keywords "button optocoupler arduino" and you will find a schema. You can find a good explication on: https://www.electronics-tutorials.ws/io/input-interfacing-circuits.html If an optocoupler is a bridge to far, you can also start with putting a little 100nF capacitor directly between Pin3 and the ground, as close to the arduino as possible. It will act as a high frequency killer. I don't see strange things in your sketch, so it should be oké. Must the node act as a repeater? If not, set the define in comment to have the bare minimum.... On a pro mini, there is no standard serial connection, I think. Otherwise you could directly connect a laptop to see the debugging messages.

@ramwal I'm sorry for my late response. And I'm glad you solved your problem. In my case, the board just kept giving problems and problems. It started with aberrant readings from the sensors. I sent it back only to be told that the board was perfect. When it came back I had a condenser failure and after the fix, intermittent serial bus fail (all leds on and hangs at simple debug prints)... ...until one day, it mysteriously jumped into a rain puddle (while still connected to the battery pack, from a considerable height). So I said bye and never look back. :blush:

@Jan-Spies From what I know - MySController only works with serial and/or Ethernet. Mqtt is not supported. May you can try with Ethernet only gateway.

Hello everybody, i found the reason for the issue... I connected already a BMP280 to the I2C pins of the Feather M0 board. To check one thing after another i did not yet connect the power supply to the BMP280. It works if i solder disconnect the BMP280 from SDA&SCL and also if i connect the 3,3V of the BMP280. It seems that the not powered BMP280 is confusing the I2C-bus so badly that the EEPROM library can not handle it. In my opinion should this kind of "mistake" in the wiring not lead to a complete black-out. Is the external EEPROM usage in general for SAMD hardware okay? In my case i use the Feather M0 which has no external EEPROM connected. Somehow i think that it was done for the Sensebender board? I would suggest to add a debug message at the beginning of the hwInit in the mysensor library that everybody can see that the library starts to works put the external EEPROM functionality in a #define switch or better use some internal EEPROM function By the way is something with the clock also wrong. My Serial is running at 9600 - but the Software says #define MY_BAUD_RATE (115200ul).. i am not very familiar with github and how to use it. If it is welcome that a mechanical guy tries to implement something like above in the library, contact me for a try ;-) best regards Jens

Hi @Sebex , I followed @BearWithBeard advise (thank you) and customised the entity in home assistant. And now it shows as numbers. [image: 1588090357996-39b5668a-ba4f-4bca-b6b0-1115e7f7eb11-image.png]

@myrandow you can change the loop to something like this: void loop() { // Read digital motion value bool tripped = digitalRead(DIGITAL_INPUT_SENSOR) == HIGH; static bool sentValue = false; if(tripped != sentValue){ // The state of the motion sensor has changed Serial.println(tripped); sentValue=tripped; send(msg.set(sentValue?"1":"0")); // Send tripped value to gw } } If you want the sensor to send updates every 2 minutes even if the state has not changed, you'll need to add some additional logic.

I can't tell yet. The node I'm now using is a wall switch, operating on a CR2032 battery. No idea yet how long it lasts.

So after running this weather station for a few weeks i decided to switch out the lux sensor for a soil moisture sensor without modifying the code.... The readings are working but they are very up and down.... they are not a steady decline..... how are people measuring the analog values of soil moisture ?

@mfalkvidd I plugged my soldering iron in and you were right, the problem reappears. I only have that one wall socket in thqt corner of the apartment so I can't plug the switch into another wall socket, unfortunately. Would one of those multi plugs work that come with an extra fuse to guard against lightning strike induced fluctuations? /edit: forgot to mention I am using the official charger for the pi 4. I'll try to find a different one.

@JCH https://www.mysensors.org/build/connect_radio

@ramwal Thanks for the hint, it made the trick here too!

@mfalkvidd ah! Thank you! :-)

@mortommy What type of unit is "sleep_seconds_between_measures"? Post the full code! Did you select the right type and clock speed when flashing the nano? 2.2.0 is an older version, current is 2.3.2, I suggest upgrade of all nodes and gateways to this latest standard.

@biffhero List of sketches on the folder eg Node8BoilerT3vWNrtc3 tells me it's Node 8, BoilerT tells me it's the Central Heating Boiler temperature monitor, 3vWN is the voltage and Node device, rtc means it has one, and finally the version number 3. By embedding the sketch name and version number in the sketch, Domoticz always holds the current sketch and version it's programmed with, as at one point I was switching programs around and lost track which one was on it. :confounded: So, some old sketches I retain as they feature a different technique or method which may come in useful later, but usually old versions are deleted if satisfied with the final. It's easy enough to find the sketch in the folder as they follow in sequence. Just my methodology but hope this helps...

Anyone got a working sketch for a pulse anenometer? I printed this. https://www.thingiverse.com/thing:2523343 I used it with ESPHome as testing it and I got OK values. Now i would like to use it with mysensors. I tried @AWI s sketch but I get stange readings. Sometimes I get a very high value when is turns slow.

@Mathea90 did you find a solution for this? After enabling MY_RX_MESSAGE_BUFFER_FEATURE my Serial gateway stops receiving messages. it usually takes about 8 to 12 hours. i'm using NRF24L01+LNA+PA and arduino nano. when i added the buffer feature, i felt like my nodes were working better so i would like to keep using it, however with lockup it makes it useless. thanks

Hi Roland, yes in the end I managed to finish compiling without error. I tried with a Windows-10 machine, a Linux Ubuntu laptop and a RaspberryPi-4 and various versions of Arduino IDE, MySensors and NodeManager. Unfortunately, thereafter I got problems running the sketch and because of too little understanding of the NodeManager programming gave up for the time being. I dismantled my setup and cannot remember which combination of soft/hardware gave me compiling success in the end. It now seems that at least part of my problems may be due to the fact that I did not yet have a NRF24L01 hooked up to the ESP8266 so I will give things another try in the future.