Yes, clear the eprom is a good solution, In fact I think it is the only way to solve it. The question is how to prevent it to happen again, and more important, what caused this issue.
I will change the node ID from AUTO to a fix one.
Thanks
Search found 3 matches
- Tuesday 19 January 2016 17:54
- Forum: MySensors
- Topic: Wrong ID assigned to a node after updating Domoticz.
- Replies: 4
- Views: 1024
- Monday 18 January 2016 19:12
- Forum: MySensors
- Topic: Wrong ID assigned to a node after updating Domoticz.
- Replies: 4
- Views: 1024
Re: Wrong ID assigned to a node after updating Domoticz.
Yes, It shoudn't be "0" but the node is sending messages to gateway like these: 18/01/2016 19:01:31 RX 0;5;1;0;0;27.0 18/01/2016 19:01:31 RX 0;3;1;0;0;21.6 18/01/2016 19:01:54 RX 0;2;1;0;0;106.3 18/01/2016 19:01:54 RX 0;5;1;0;0;27.4 18/01/2016 19:01:54 RX 0;3;1;0;0;21.1 18/01/2016 19:02:17 RX 0;2;1 ...
- Monday 18 January 2016 11:37
- Forum: MySensors
- Topic: Wrong ID assigned to a node after updating Domoticz.
- Replies: 4
- Views: 1024
Wrong ID assigned to a node after updating Domoticz.
Hi, last week I upgraded domoticz to version 2.4116 using te command "git pull" and then compiling on ubuntu 15.04 Before that upgrade, I had a mysensors node with the node ID set to AUTO and taking alwais ID:7, it was running well for some months. After upgrading I restarted the node, but it took ...