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 the node ID 0, you can see in the image both sensors.
I guess there is a problem since the node ID "0" is only for the gateway, and the ID is assigned by the controller not by the gateway.

Could it be a problem on the domoticz version?

Thanks in advance.

Looking at the MySensors implementation in domoticz, it should not return 0 or 255

int MySensorsBase::FindNextNodeID()

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;0;0;106.8
18/01/2016 19:02:17 RX 0;5;1;0;0;27.4
18/01/2016 19:02:17 RX 0;3;1;0;0;23.0
18/01/2016 19:02:40 RX 0;2;1;0;0;107.8
18/01/2016 19:02:40 RX 0;5;1;0;0;27.0
18/01/2016 19:02:40 RX 0;3;1;0;0;21.6
the first number in the message is the node ID, in this case is 0.
It's very strange, I only have 1 node and an ethernet gateway, so there is no possibility of confusion.
Any ideas about the issue?
THX

As far as I know the node only requests an ID at the very first start and safes it to it's eeprom. You could try to clear the eeprom bei flashing the sketch found in \libraries\MySensors\examples\ClearEepromConfig. This way the node is forced to request a new ID from Domoticz.

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