@sglue Thanks for replying but that does not work in Domoticz. Just as mentioned in the thread. Domoticz only acknowledge that a sensor is alive if it sends new data. Not by sending a status that it has received earlier.

For now I have solved it by a dummy switch in my sketch that alternates on and off at every heartbeat, but I don't think that is a very nice solution. And I have to have two different script checking my sensors in Domoticz. One for the ones that heart beats is working in (ie X10) and one for my MySensors nodes.

Did some more research. And it seems to me now that it was Domoticz that somehow messed up the ID. Even after clearing the EEPROM and flashed the node with a new sketch specifying what ID to use, it did not show up in Domoticz. So I had a look in Domoticz database. And in the table "MySenors" everything looked as it should, but in table "MySensorsChilds" there was children to nodes not existing in the first table or in reality.
By removing those lines in the database, it started working again.

Can be that I have been adding children to this new node between tests?

Anyway; my conclusion is that it is safer to manually assign ID myself, when building and testing new nodes.

@gohan Ok. Then I will try your suggestion. I will first have to learn how to replace the bootloader..

Hello!

Anyone here using sendHeartbeat() and can confirm it works with Domoticz?
I have just build my first motion and door sensor, and I can not get Domoticz to update the "last seen" for them.

If I read on Domoticz forum @sundberg84 asked for this feature in january 2016, and as I understand it it was implemented in february.
But in another thread someone else is asking again for it. And this is in september 2017.

I am running version 3.8153 dated 2017-07-30.

If someone can confirm that it is working in latest stable 4.9700 I will update my server, otherwise not. I have always had allot of troubles on my previous updates. And now it has been working perfect for a year.

@mfalkvidd That is perfect. Thank you!
I will start with adding this to my nodes to prevent this from happening again, and messing up my controller (Domoticz).

When I think back to what happened was that at the time of when the old node changed ID, I was removing the battery from this this node, to reset it. Until now I thought it changed ID before this. The reason for restarting the node was that my controller had not got an status for several hours from the node. But of course it could be for some other reason. Radio interference or something else.
And then as I understand it, when I restarted the old sensor, some how Domoticz (if I have read up correctly it is the controller not the GW) assigned the ID of the new node I was playing with.

@gohan Well. I could try that. But it sounds strange to me that it will all the sudden change behavior. It was running fine without battery drain for a couple of weeks, and then all the sudden started draining the batteries.

@bjacobse
Changed the whole board. I have it laying here in my workshop, but haven't got the time yet to investigate more.
It's shore sounds like @sundberg84 was right about a leaking capacitor.

The node that changed ID all by it self yesterday was a battery powered node, with about 3 week old batteries. Reporting 100% battery.

And if I understand your answer correct this is just a coincidence that the change of ID on the old node was at time I was messing with my new node. And also that it got the same ID as the new one.

I don't have a programmer. So I will reprogam the old one.

New question:
If I define a manual ID (MY_NODE_ID), will this ID be rewritten to EEPROM every time the node starts? Or is it a one time operation, at first start.
By other words; will this prevent this that just happened to me from happening again?
Meaning: If I define MY_NODE_ID and the node corrupts the EEPROM in the future, all I have to do then is restart/reset the node.

Background:
I have 3 nodes running for a couple of month now.
Yesterday I built my 4th node. And when trying to load my sketch to it I had some strange errors output. I searched the internet without any luck. The node seemed to be working (except one sensor on the node), and I could see it in my controller. It had node id 4. I have not manually assigned any ID in my sketch.
To day I tried again with an updated code. With new errors. But the node still worked and the sensor still didn't work. Now it had node id 5.
I found out that the thing that caused the errors while downloading the sketch to the Arduino was because I was feeding power from a seperate source than the FTDI interface.
And tried again with new code for the sensor that did not work. Still node id 5.

Problem:
Sometime today when I was trying different codes on my new node (after or before I realized the problem with the errors when uploading the code) that one of my running node had changed id from 2 to 5. The same ID that this new node has. The new node and the old node both has a sensor on child id 0 that is a temperature sensor.
So this is all messed up.

Questions:

1. How can a node change id when running just out of the blue?
2. Is there a way to change it back, without clearing the EEPROM and reprogram it?

So. Forgot to get back.
But it was the Arduino it self that had gone bad. I switched the Arduino to a new, and everything was back to normal.