Admin
@dpcons you can have as many nrf24l01 MySensors networks as you like.
They are differentiated by channel and base radio id.
The reason for multiple networks may be more control, isolation, lab/test/production network, approaching the limit (255) of the number of nodes in a single network, separate network for high-traffic devices, different versions of MySensors, interference, range problems, and more.
@dpcons there can only be one MySensors gateway in a MySensors network.
You can have as many MySensors networks as you like.
A MySensors network can exist of only a gateway (no other MySensors nodes required)
If that's not the case, is there a point to having one, if I already have an esp8266 WIFI gateway with a nRF24L01.
There can be points. I don’t know your needs.
If a radio is required on the MQTT, does that mean another nRF24L01 can be connected to the system? Is that possible?
No radio is required on the mqtt gateway.
A mqtt gateway can have a nrf2l01.
I guess what you're saying is that you only need one 2.4G network, be it wifi, mqtt or serial. True?
Could you elaborate on what you mean by ”one 2.4G network”? Do you mean one MySensors nrf24l01 network? Or one 2.4GHz wifi network? Or something else?
Haha. Yeah!. You're always welcome to revisit over some beers and bbq!
@dpcons sensor nodes can not post a mqtt message. Sensor nodes can’t even be aware that they talk to a mqtt gateway: the nodes don’t know if the gateway is wifi, mqtt, serial or any other type.
With that said, sensor nodes can send any message to a gateway, and the gateway will forward the message on mqtt (if it is a mqtt gateway). Simplest example is probably something like https://github.com/mysensors/MySensors/blob/development/examples/BatteryPoweredSensor/BatteryPoweredSensor.ino or https://github.com/mysensors/MySensors/blob/development/examples/BinarySwitchSleepSensor/BinarySwitchSleepSensor.ino
@dpcons try changing unsigned long in your sketch to uint32_t
Could be that the override needs to have an exact match.
I think the relevant code is here:
https://github.com/mysensors/MySensors/blob/e298769eb73ba2da781a34d66cae345c6840b7c0/core/MySensorsCore.cpp#L473
but I can’t see anything that looks broken.
@dpcons it could be that the gateway code for receiving time is (unintentionally) broken. I noticed that the other thread you found also was about a gateway.
I have never used receivetime myself but I am pretty sure I have seen it working for other people on regular nodes.
The received message looks like this:
Received Message
Sender: 0
Last Node: 0
Destination: 6
Sensor Id: 255
Command: INTERNAL
Message Type: I_TIME
Payload Type: P_STRING
Payload Length: 10
Signing: 0
Payload: 1740594416
1740594416 is Thu, 27 Feb 2025 11:56:37 GMT which looks reasonable.
So question is, why doesn’t the node print the received time?
