Noob : Cant get Sensor talking to gateway

[angeloS]

@r-nox AWESOME! thank you!

Nice to see this OS library is well supported... cool

[angeloS]

@manutremo , you hit it bang on.. The NODE_ID wasnt being sent, setting a node id to a number using
#define MY_NODE_ID 42
worked.

Curious, so I can debug this myself in the future, which line indicated the NODE_ID was blank?
was it this line?
mysgw: TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:

[manutremo]

@Angelo-Santagata happy to know that you got it working. Yes I think that's the line which in the log parser showed an empty payload. It would be interesting to know why the gw is returning an empty payload when an ID is requested, though, since that's not usual behavior with the default settings. Let us know what you find out!

[gohan]

If there is no controller assigning an ID, the gw can't make up one out of nothing. 😀

[manutremo]

That's certainly the most probable cause, Angelo didn't mention any controller so I assumed there is one... which controller are you using (if any) Angelo?

[gohan]

There could be a controller but if it is not assigning any ID is it just as it wasn't any 😁

[manutremo]

Yes, the fact that it works with a static node id seems to point in that direction - should that not be the case, i sincerely wouldn't have a clue on where to look at.

[angeloS]

Hi all,

ok this is the embarrassing bit, no the controller wasnt attached.. Im using home assistant and what I didnt realise that was that a) the controller sends the IDs and b) the controller couldnt talk to the Gateway..

BTW Why do we need a controller to assign the unique sensor IDs? I thought the Gateway would do this?

[mfalkvidd]

@Angelo-Santagata the gateways are designed to be stateless. The stateless design makes it easy to implement a gateway on low-power hardware. It also makes it easier to correctly implement and verify the gateway functionality, and to troubleshoot if there are problems. If gateways had to remember which ids had been assigned, they would no longer be stateless.

[angeloS]

@mfalkvidd thanks, very impressive this mySensors stuff BTW

[mfalkvidd]

@angeloS thanks. I agree. I can't take credit for it though, most of the stuff was designed before I found the project :)

[manutremo]

Mistery solved :satisfied:

[mfalkvidd]

Does anyone have suggestions on a clearer log message? One that would make it easy to understand what is happening? If we could make the log clearer, other people could understand the reason quicker, saving time and frustration.

[angeloS]

@mfalkvidd In my case I think if the log had said, No Controller provided SensorID, that would have been my first clue

[manutremo]

@angeloS Fully agree - a warning instead of just sending a message with an empty payload would have been easier to spot. Maybe something to propose in Github?

[mfalkvidd]

@manutremo which message are you referring to?

[gohan]

We could add a sample message, in the troubleshooting guide, when the node has no Node ID and the gateway is responding an empty message, so a Node ID must be defined in the sketch

[manutremo]

@mfalkvidd Without being an specialist in the MySensors protocol, it could be something like

• a debug message at some point in the gateway log when a node ID is requested and there is no ID to provide (no controller available),

• something similar in the node log when an empty ID is provided form the gw

• additionally, a warning in the log parser to check the controller when the payload is empty.

[mfalkvidd]

@gohan and @manutremo when does the gateway respond with an empty message? I am not able to find that in the logs posted earlier in this thread.

[manutremo]

@mfalkvidd Just reviewed the gw log and you're right, the gw just doesn't answer... I guess in this case it's just not possible to separate the cases when the gateway doesn't have a controller, or is off, or communication didn't arrive, or... in all cases, the node seems to end up with a ID=255.

As I said, not familiar with the protocol...