@ctodor You are very welcome

Hm, maybe the problem is that your rPI has a short interruption in the WIFI connection, the MQTT TCP connection is interrupted and does not autostart again. Maybe there is something in the logs. Maybe you can find something about reconnects in one of these: journalctl --unit=systemd-networkd journalctl --unit=wpa_supplicant You could try to run wpa_cli in daemon mode to react to disconnects and connects. Create a script like this: #!/bin/bash case "$2" in CONNECTED) <your command to start the gateway>; ;; DISCONNECTED) <your command to stop the gateway>; ;; esac then, start wpa_cli in deamon mode: wpa_cli -a /path/to/your/script #use sudo if your gateway commands need sudo If that helps, you could create a service from this command. Regards, Edi

IT WORKS I got a first working version, using an ATmega1284P running on MightyCore 2.2.2 (as soon as I began developement, they switched from Optiboot to Urboot in version 3.0.0, whicht does not include the copy_flash_pages function anymore, but I'm working on a work around there). Only thing I could not solve is to do a CRC check of the image after download... You can try it out here: https://github.com/eiten/MySensors/tree/FOTAInternalFlashTest It's not beautiful yet with much Serial.prints in it, but maybe it helps you if you find errors.

We are of like minds, Don't like the cloud based controls (that's another discussion). In my case I have a Bryant/Connex system, heat pump, variable speed fan and 4 zones. There's a lot going on: the 4 zones creates 16 profiles. The fan speed for a profile will depend on the indoor and outdoor temperature. The thermal fluid pump also has to be controlled. A profile will have an optimal air pressure, so there's a sensor there. The controller works just fine not being connected to the cloud. But I want to set the parameters remotely, Bryant/Connex can do this. I also wnat the status of the various actuators and sensors to show up in Home Assistant. The signals sent over the RS422 are proprietary. My plan was to reverse-engineer the signals. After doing this I'll have to experiment to get the right mix of air pressue, fan speed and thermal fluid flow for each profile. I'd like to do the same for my AO Smith heat pump water heater. I'd like to follow your progress. OSD

I bought the Every because it implied it was backward compatible with the nano. No, it's not, as we found out. Be that as it may, any word on a getting the Every working with mySensors?

Don't ask me why, but now it works. I changed nothing! Went to my girl over the weekend, coming back, the node was registred. Maybe a jammer went away?

Hi @CyborgAndy many thanks for providing the binding update for MySensors 4.0.4! I upgrade my OpenHAB 3.4.4 a few minutes ago to 4.0.4 successfully with your binding update. I use a USB connected serial-gateway. The OpenHAB manual installation upgrade works perfect. I need to do afterwards the following steps in the Karaf console, to get the gateway online again, after the update: feature:install openhab-transport-serial feature:install openhab-core-io-transport-mqtt feature:install openhab-core-io-transport-serial-javacomm Many thanks again! kerberos

@Mizar03 sorry for the late response. getStream() only works for firmware transfers. I'd suggest getString(), this should also work for all types of payloads, as they are normaly ASCII and not binary data.

@eiten I haven't yet made any progress on finding a good VOC sensor, but along the way I did find out something interesting regarding CO2: namely, if you sleep with your bedroom door closed at night, then the odds are good that the CO2 levels rise to surprisingly high and unhealthy levels. The better CO2 sensors are factory calibrated and never again need recalibration for the life of the sensor (usually around 10 years or so), because they are used in HVAC systems to control fresh air intake to guarantee indoor air quality. As a for instance, here is one such CO2 sensor: https://www.digikey.com/en/products/detail/senseair/006-0-0008/15790694 At around $50 for just the sensor element itself, it's not exactly cheap, but then again, I'd say it's worth it, because who wants to be burdened by remembering to calibrate their CO2 sensors? Ideally, I'd like to find a sensitive VOC sensor that also will never require calibration. Nearly all, and maybe all, of the off-the-shelf IAQ montoring stuff that you might buy for, say, $300 or less seems to require periodic calibration. For that reason, this might be one of those occasions where build is rather than buy.

I don't know if any of you guys are still around and using this stuff - I moved and am reviving a few of these 51/52 boards that I had built. Prior to moving I had decent luck with all these fixes though I don't quite remember where I was with any of this stuff seeing as it was 3 years ago. I had a few motion sensors and some temp/humd based on these fixes and they were working great, no dips. Not sure any of you will ever see this but hey it all worked.

I found procedure gatewayTransportInit(), it works great. However, I cannot find a procedure that will enable detection of a network connection at level mysensors. I noticed that disconnecting the network plug or resetting the W5500 (37 pin to ground) changes the device's IP address to 0.0.0.0 - then I call gatewayTransportInit() - but mysensor's library must have such procedures - please tell me how to diagnose ethernet connection.

hello, I just deleted the eeprom but I still have the problem. [image: 1698703321335-capture.png]

Solved. Issue with power supply. Added a capacidade to power source.

You should only include the relevant header file in the file Gestion_Porte.hpp, not Mysensors.h For example #include <core/MyTransport.h>

@nekitoss I used 3.3V pro mini with regulator removed and powered by Vin pin. Also removed leds from the pro mini. I used minicore bootloader. I used the small pir sensors and again removed the regulator to power directly from the pro mini outputs. After that sleep the node and trigger on interrupt. Send battery level once a day. Use inbuilt battery level monitor and not external components that constantly drain power to get battery level. 1.8V is 0% on the graph (not visible yet!) but I have had nodes working below 1.7V It's a matter of luck with that it seems. Hope this helps you on the right track. I'll try and help if you want. [image: 1697446591518-1ed.jpg] This is the latest image and still going strong after 18 months. Voltage is at 2.903V Here is photo of the test example - I need to make a case and produce more of them over winter..... [image: 1697446939496-20231016_095845.jpg] Here is the same build/code of a window sensor. Similar time frame but hardly triggered..... [image: 1697447658685-2ed.jpg]

Hi all, Should anyone face the same problem, I found the root cause: brownout threshold. I burned a new bootloader (Optiboot 8.0) without such trigger and the node has been working with used batteries (~2.7V) since May. Hope this helps.

I'm afraid, the MYSbootloader is only available for the AVRs.