Welcome to the forum!

Tagging @sundberg84 who created this pcb.

Thanks for reporting @Honk

@hek has fixed the cert issue now

It is the receiver's eeprom that needs to be cleared. In most MySensors networks, the receiver is the gateway. But since MySensors supports node to node communication (for example a button node sending a message to a relay node), any node can be a receiver. So in the example, the eeprom of the relay node would also need to be cleared.

I have not used signing myself, but I think you’ll need to wipe eeprom of all nodes.

See https://www.mysensors.org/apidocs/group__SigningSettingGrpPub.html#gaf44407e0f498eca7069adf5e59ffe052

Nice work @Aymeric, thanks for reporting back!

@Aymeric are you sure the node isn’t sleeping for 5 seconds? WUP=-1 means it woke up by timer.

Check using an external clock, and/or turn on timestamps on the Arduino IDE log.

Nice work @Branther

The disadvantage is that the node won’t be performing all the stuff that normal nodes do. But since you don’t want that stuff for this particular node, there is no real disadvantage.

Hi Branther. Great to see you back!

These topic give some info on what can be done:
https://forum.mysensors.org/topic/9879/setup-for-the-fastest-sensor-startup-time/
https://forum.mysensors.org/topic/8827/serial-gateway-nrf24-with-sleep-mode-enabled-there/

Check if these help, and post any follow-up questions you might have.

I read an interesting take on AI and IoT today: https://tinkeriot.com/esp32-mcp-llm-ai-integration/

I don’t have time to tinker these days, but mcp looks like a nive way to interact with IoT sensors. I wonder how hard it would be to build a mcp for MySensors and if it would make sense.

With the amount of spammers, it would need some sort of moderation. Otherwise it would just be filled with spam and affiliate links.

But a lot of people have earned reputation on the forum, so that could probably be used to give access.

11.3mA according to the datasheet

But 13.5mA when in receive mode.

The bew error you got is discussed in https://forum.mysensors.org/topic/11448/config-h-39-first-defined-here/4

Easiest way is probably to switch to the development branch of mysensors.

Run git checkout development and then start over from the configure step. Or follow the step ”To use the development version with the latest updates” on the raspberry pi gateway build page.

The key is here:

hal/architecture/Linux/drivers/core/interrupt.cpp:33:10: fatal error: stropts.h: No such file or directory
33 | #include <stropts.h>
| ^~~~~~~~~~~
compilation terminated.
make: *** [Makefile:99: build/hal/architecture/Linux/drivers/core/interrupt.o] Error 1

See https://forum.mysensors.org/topic/11138/mysensors-build-problem-on-ubuntu-20-04-rpi-or-tinker-board/2 for a possible workaround. Then restart from the make step.

Mysgw will only be created after successful make.

Nice work @goblin

Could you share all commands you ran and the entire output, including the configure, build and test steps?

Also, I don’t think Domoticz can use the gateway as a client. You should probably omit the --my-controller-ip-address=127.0.0.1 argument.

Hello @goblin, welcome to the forum.

You probably had installed the raspberry pi gateway, which supports serial (usb), ethernet (LAN) and mqtt.

Instructions: https://www.mysensors.org/build/raspberry

Easiest is probably ethernet.

@OldSurferDude the max number of nodes is 253, as with any MySensors gateway.

The esp-12f has a lot more resources than an atmega328.

Thers is actually support for pjon as transport in MySensors: https://github.com/mysensors/MySensors/pull/1278

I don’t know how it works though.

@fsgraz you might want to use the tcp option for the ethernet gateway then. See https://www.mysensors.org/about/overview and https://www.mysensors.org/build/select_gateway

Thanks @OldSurferDude

I have notified the team

@tnick STM32F1 2019.12.8 (stm32duino) is the version that was active when the latest MySensors release was made. Later versions may or may not work; nobody would know until they tried.