Gateway Ready message with sensor id 0 [V 1.6 beta]
-
I'm getting gateway ready message as 0;0;3;0;9;Starting gateway (RNNGA-, 1.6.0-beta)
Here nodeId and sensorId shows as 0, I believe sensorId should be 255?
-
The gateway always has nodeid 0
-
@mfalkvidd said:
The gateway always has nodeid 0
@mfalkvidd I'm fine with nodeId, but sensorId should be 255 right? It should not be 0. As we can assign 0 to some other sensor.
-
Sorry about that. I believe you can use child-sensor-id 0 for any sensor that is not a gateway. Since any other child sensor will have a different node id, there will be no collision.
-
@hek For internal message gateway device using sensor id 0. I hope it should be 255.
0;0;3;0;9;send: 0-0-2-2 s=1,c=1,t=2,pt=0,l=1,sg=0,st=ok:0
-
Yes, internal messages uses sensor-id 255.
-
@hek said:
Yes, internal messages uses sensor-id 255.
but I'm getting sensor-id 0 for internal messages
For now I have identified for I_GATEWAY_READY and I_LOG_MESSAGE
-
That's plain wrong. Created a PR here:
-
Suggested Topics
-
Code for beta-testing?
Controllers • 24 Mar 2014, 20:48 • andriej 9 Aug 2014, 10:44 -
RFM95W sleep() directly after send() often doesn't sleep radio
Bug Reports • 1 Jan 2023, 18:41 • prawnpie 8 Jan 2023, 05:36 -
sleep(0) in V2.1 doesn't sleep indefinitely anymore. Used to powerdown and sleep in V1.5
Bug Reports • 22 Nov 2019, 00:35 • GaryStofer 15 Apr 2023, 05:50 -
Missing "__libc_init_array();" wenn using samd without USB
Bug Reports • 6 Jul 2022, 08:36 • ltigges 7 Jul 2022, 22:43 -
some differences between serial- and tcp-gateways.
Bug Reports • 15 Mar 2023, 09:26 • Branther 30 Mar 2023, 15:40 -
ACK -aka ECHO beeing missed by Serial Gateway with RF24 radios. V2.3.2
Bug Reports • 15 Apr 2023, 06:27 • GaryStofer 21 Apr 2023, 17:34
