Development

Thanks for the answer. I meant that Mysensors has ESP32 support but only in terms of WIFI. It supports e.g. stm32 with ENC or W5500 modules - and the question is whether and how to add ESP32 support with LAN8720 module. I am not considering using ESPHOME or MQTT - I want to have native communication with the controller that implements my control schemes on its side. I try to program KC868-A16 but it does not matter - the question is whether such support can be added in a simple way.

Thanks, I'll keep this in mind if I decide to debug it. I realized that I am also tired of patching the gateway through to the doctor container inside an LXC so now I am looking at creating an esp gateway. Just need to check if I can find a pcb on here. Thanks again!

@bgunnarb I like @eiten 's solution for you. Personally, I am not a fan of using cloud/public brokers. Thus I am curious about your system and there is something about it from which I can learn. I would like to understand why you cannot deploy your own mosquitto broker. I see your set up as 3 sensor groups defined by the channel used #define MY_RF24_CHANNEL ChannelOfSensorGroup Each sensor group has some number of sensors and one MQTT GW on ESP8266. On the MQTT side, do you distinguish between gateways by using a different host name? Something like: #define MY_MQTT_PUBLISH_TOPIC_PREFIX "mygateway-nOf3-out" #define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mygateway-nOf3-in" #define MY_MQTT_CLIENT_ID "mysensors-nOf3" #define MY_HOSTNAME "ESP8266_MQTT_GW_nOf3" //#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 68 #define MY_CONTROLLER_URL_ADDRESS "test.mosquitto.org" #define MY_PORT 1883 I must assume your controller (aka Home Assistant) discriminates between through which gateway the data is to flow by way of the different topic names. If my "something like" is correct, then changing brokers is changing the IPaddress/URL in your gateways and in your controller (though if the controller is Home Assistant, it may be a bother because the device-id's may change which will make a mess of all the work you've done in HA. This is why I like @eiten 's solution.) I hope it's all working for you again. OSD

@OldSurferDude well, the ESP8266 is limited to 4 TCP clients in arduino IDE. This can't be really increased. I did som experiments and you can set it up to 15, but after the 5th client on my web server, I got a freeze. Maybe you got something wrong. #define MY_GATEWAY_MAX_CLIENTS 2 defines how many controllers (eg Home Assistant) can connect to the gateway, not how many sensors/MySensors devices. And yes, you can have multiple TCP gateways in HomeAssistant. I got an NRF24, an RFM95 long range and a RFM95 short range gateway (all based on ESP32) on the same Home Assistant. Regards, Edi

Just for completeness: the right way to do this is to add the json under ~/.platformio/boards and the other files as described in https://community.platformio.org/t/how-use-a-same-chip-but-with-different-environment/18082/4

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.

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]

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

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

No. For RFM69 you need Sensbender bootloader and external flash. Then it works.

@Dan-Mincu Hello I am looking for help because I have the same problem. Can you show me the code you use to set power down radio?

Thx for the hint. Unfortunately this didn't help me to find a solution for the compilation error. I simply don't understand the lines 105 and 106 in (MyHwLinuxGeneric.h). Can anyone explain me the C magic going on there? #define ATOMIC_BLOCK for ( ATOMIC_BLOCK_CLEANUP, __hwLock(); \ __atomic_loop ; __atomic_loop = 0 ) I think the problem is the "new"/different compiler version being used on the OrangePi 5. On my Raspberry Pi the code compiled without any problem.

Depending what's connected to a relay, I wouldn't make it go on or off depending on the controller state. It can lead to dangerous behaviour and it's prohibited by law in my country. In all honesty I have my Sensors running for a long long time. It's stable and more reliable than anything else I have running in my home. But like @eiten says yo could write a sketch that queries for a variable. But I think I'd go for a controller side solution. That would "ping" my node and send a nottfication to my phone whenever the node can't be reached.

I searched on the forum how to use ID255 but found nothing practical https://forum.mysensors.org/topic/8941/mysensors-get-temperature-value-from-another-node-through-the-gateway?_=1684325843882&lang=fr https://github.com/mysensors/MySensors/blob/development/examples/PingPongSensor/PingPongSensor.ino