@Flyer Sorry, but I can't remember if I had any more problems after I manually fixed the database.

And just a couple months after I had this problem I switched to Home Assistant instead.

So I have been reading up alot. And yesterday I finally managed to upload a new bootloader to this ProMini. It was the optiboot that @bjacobse linked to. All worked fine without any errors.

But I must have been doing something wrong, because I am not able to upload any sketch to the Arduino after that. I only get not in sync errors.

Unfortunately I don't have time to continue on this until late next week...

Well. It was the radio that caused this false triggers. The final placement of the node must be in a radio shaddow.

I really "funny" thing is that I solved this problem by changing the radio. I had a NRF24L01+PA+LNA for better range. This was for future project (node in my greenhouse) which would need this node as a repeater for shore.
But by replacing the radio to a "normal" NRF24L01+ made the problem go away. I did not change the location!

@pjr I am still a noob when it comes to C. And I have not had the time to examine the Domoticz source code. But at first glance those lines seems as V_PERCENTAGE, V_SCENE_OFF, V_STOP and V_RGBW that updates the last seen on heartbeat.

I have had my node running now for 2 days just checking this heartbeat. And I can for shore sasy that is only working for the door sensor. Which presents it self as S_DOOR and sends V_TRIPPED messages.
It is not working for the motion sensor presenting it self as S_MOTION and also sends V_TRIPPED messages.

And one more really strange thing is that it is only working on the door sensor when the door is open. Not closed!

Update: It seems as heartbeat works in 4.9701 for S_DOOR, but not for S_MOTION or S_BINARY.

This is strange...

Last 24 hours I have had the node standing almost next to the gateway, and no false motion has been detected. So:

• Close to the gateway there is no false indication.
• Testing area in garage is no false indication.
• Final place in garage there is false indication.

PIR sensor is driven from 5V USB charger. All sensors are connected to the 5V charger as well as the Pro Mini. The radio is NRF24L01+PA+LNA connected to a AMS1117 5V-3.3V converter.
USB charger is capable to deliver 700mA. And if I calculate correct the node has a maximum of about 270 mA consumption.
So there should be more than enough power.

And why is it different due to location of the node? Does power consumption differs from radio depending on the quality of the radio connection to the gateway?

@yveaux Yes. I have understood that by reading up. But what I can't understand is that it not happens every time I use the radio. As it seems now it is only when the gateway is sending the discovery broadcast. Not when the node is sending data from the other sensors on the node, or when I send data to the node for operating the relays. Strange...

@electrik I disconnected the extender wires for reed. And it has been running all night like this. But no difference. So it can not be due to the extender wires.

@ahmedadelhosni Yes. This is a 5V sensor powered from a phone charger.

Hello,

I have been testing my latest node for a couple weeks. It's a node with a double relay, a DHT22, one reed switch and one motion sensor (HC-SR501), with repeater function. It is intended for maneuvering my garage door. And should be situated in my garage (of course) and the reason for repeater function is that I also have a temp node at my fridge in the garage that some times is not reaching my gateway. This new node is placed halfway between the gateway and fridge node.

It has been standing in the garage at the same distance as final mounting place and I have been logging the function. And all have been working perfectly.
But yesterday I mounted it and connected the garage door to the relay and extended the reed wires (4 meters), and now the motion sensor (not changed at all) is reporting motion every 20 minutes.

So last night I found this thread:
New nodes, new problems :/ Motion sensor [Solved]
wich reports the exact same behavior.

But @xydix solved the problem with replacing the PIR from another model to the one I am using. Others suggest it is a power problem.
So I thought it was due to the reed switch. That was not tested at "closed" for a longer period under testing. Drawing current when the switch was closed.
But I disconnected it again, and no change. Still reporting motion every 20 minutes.

So:
Any one having any ideas what I should do next?
The only remaining differences from testing period is location. I was standing on a shelf before, and now it is placed in the sealing, with the same distance to the gateway (about 7 meters)

And if it is power issue due to radio radio transmissions (as suggested in the earlier mentioned thread) why is it only on discover request broadcast, and not when the node is sending data from DHT22 or reed, or when I send data to the node for maneuvering the relays?

@mfalkvidd Thanks! Don't think I found that page before. Found a lot of pages about this subject but not this page. But if I understand it correct I still need to buy a new Arduino. I only have a big supply of Pro Minis. No other models.

@bjacobse So it's time for a new raid with this project. I have been trying to read up on how to change bootloader. And if I understand it correct I need a programmer. And I only have a FTDI for uploading my code to my arduinos.
But somewhere I found that I can use a Arduino Uno instead.

So is this correct? If I buy a Uno will I be able to change to the new bootloader?

Answering my self for info to others that finds this thread.

I finally did the upgrade anyway and:
It is NOT working in v4.970.

@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.