New status update: IT WORKS!
I have to implement sleep and ATC, then I will upload it to GitHub for testing, if anyone is iterested...

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

@NeverDie Did you check out the assembly instructions? There they use a fuse with a rather high current in this place
The explanation why it is polarized is because in fact, it used to be a diode in older revisions, check out Step 7 here.

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.

Hello Henrik,

In your scenario, I would not use a RPi. Maybe a ESP32 with BLE is already enough as a controler, if you don't need to log too much data or add an SD card. You could even combine two NRF52 (see below) and use one for BLE and the other for MySensors.
For your sensoirs, you could use a Keywish RF Nano or an NRF52 module like (this one)[https://www.aliexpress.com/item/32974237147.html] which combines a NRF24L01 and an ARM cortex M cpu and have very low sleep current.
Maybe it's best for you to use passive nodes when not using the RPi, so you don't have to care about address management and so on on the gateway.

Regards, Edi

Hi everyone,
After the good comments by @Yveaux and @mfalkvidd in this thread i started over again. After some sleepless nights, a SSD-crash destroying about 12h of coding and tons of soft drinks, I just uploadated my github repository with the SX126x drivers and the ASR650x hal.
What is different to the things I mentioned in the thread above:

• Everything is rebased to the developement branch as suggested by @mfalkvidd
• CubeCell hal byebye, welcome SX126x hal. As inspired by @Yveaux, I abandoned the CubeCell drivers in favor of SX126x drivers which should work on other SX126x based modules as well. Feel free to test. The code should work for the SX1261 as well as the SX1262, but as I only have CubeCell boards, only SX1262 is tested.
• ATM, I really dont feel like writing down all the defines, but everything is documented in MyConfig.hand in ```SX126x.h`` If you got questions. please ask.

During developement, I found another nasty bug in ASR650x Arduino regarding IRQ handling. You should take the latest version from ASR650x github if you encounter strange freezes on a CellCube board.

Have fun, I gotta get some sleep

Well, battery level is an attribute in Home Assistant, so you can only see it as a byproduct of a reading. Workaround is to open the persistence file, there, you can see the battery level even in no reading is shown in the frontend:

Oh sorry, my fault. It was a bit late. We have a return true in there, where we exit the loop as soon as we got an ack. You are right!

@Eme said in MySensors Raspberry Pi Gateway + Domotics Controller:

TSF:CKU:OK,FCTRL

Uplink OK, flood control prevents pinging GW in too short intervals

Hello @HJ_SK

Could you please post the whole sketch in code tags or as an attachement?
Does it work stable with just one sensor node?
Could you #define MY_DEBUG, attach at least one sensor to a PC and post the log after they hang?

Regards, Edi

Wow @Nicklas-Starkel congrats, that sounds great! And thanks for the feedback. Would you mind sharing your setup?
Regards, Edi

@kamilb85 said in Forum Search not working?:

No, search is not working

Confirmed, it's not working for me either...

Well, I can only imagine that they try to send at the same time. Did you try with slightly different interval times?

Hello @HJ_SK

Could you please post the whole sketch in code tags or as an attachement?
Does it work stable with just one sensor node?
Could you #define MY_DEBUG, attach at least one sensor to a PC and post the log after they hang?

Regards, Edi

Hey @OldSurferDude
I think we have a missunderstanding here. I have my gateways running on ESP32. When I add the integration I can enter the IP in this dialog:
If you want to change the IP number of the gateway (or the MQTT topic or the serial port), there is no way to do this:

Sorry @se-O-matic , but I can't see any problem. Does the temperature recover with time? I only can imagine that you have a collision on air.

Hi @se-O-matic

can you please post your source code of the node in question?
You only restarted Home Assistant, not the nodes, correct?

Thanks and regards, Edi

Hey @OldSurferDude

thanks for the info. But I want to know where I can change the IP of the MySensors-TCP-Gateway.

Regards, Edi

@bgunnarb Thank you for your feedback. I'm very happy that I could help you. And thank you very much for the beer.

@bgunnarb are you on the master or de development branch? In the development brancht, TLS is implemented (check out this) :

/*
 * Modified by Eric Grammatico <eric@grammatico.me>
 *
 * Added support to secured connexion to mqtt server thanks to WiFiClientSecure class.
 * Please see comments in code. You can look for WiFiClientSecure, MY_GATEWAY_ESP8266_SECURE,
 * MY_MQTT_CA_CERT, MY_MQTT_FINGERPRINT and MY_MQTT_CLIENT_CERT in the code below to see what has
 * changed. No new method, no new class to be used by my_sensors.
 *
 * The following constants have to be defined from the gateway code:
 * MY_GATEWAY_ESP8266_SECURE    in place of MY_GATEWAY_ESP8266 to go to secure connexions.
 * MY_MQTT_CA_CERTx            Up to three root Certificates Authorities could be defined
 *                              to validate the mqtt server' certificate. The most secure.
 * MY_MQTT_FINGERPRINT           Alternatively, the mqtt server' certificate finger print
 *                              could be used. Less secure and less convenient as you'll
 *                              have to update the fingerprint each time the mqtt server'
 *                              certificate is updated
 *                              If neither MY_MQTT_CA_CERT1 nor MY_MQTT_FINGERPRINT are
 *                              defined, insecure connexion will be established. The mqtt
 *                              server' certificate will not be validated.
 * MY_MQTT_CLIENT_CERT           The mqtt server may require client certificate for
 * MY_MQTT_CLIENT_KEY            authentication.
 *
 */

Regards, Edi