@martinhjelmare No problem, I'll try to get some more data. Regarding HA version, I'm always on the latest version (with one or two days delay).

@martinhjelmare Have you looked into this? I've been noticing delays very frequently :/
I don't have those delays with other components, and also had not had them when using Pimatic instead of HA.

@martinhjelmare How cool! That solves my problem! You developed the component for HASS? Great work dude! Really, thanks for it.

I hope to be able to contribute more in the future, for now I've only done some small PRs.

@martinhjelmare :O that is great!
So if I have, say, a switch and turn it ON on HA, when the node sends an heartbeat HA will send the ON command to the node? :D

I want to make a relay/switch which needs to be battery powered. Because of that it can't be constantly listening for messages. Since it is not critical for it to be instant, I was thinking that the node could be sleeping for like 60 seconds, and the send and heartbeat (or other message) to the gateway and wait for a reply. When receiving that, the gateway would send the current state to the node, and the node would then return to sleep. It would be similar to the option that exists in MYSController, that waits for a node to speak to send it a message.

Is this possible to do using Home Assistant?

Thanks. I've been debugging it, and it seems that sometimes "self.handle_queue()" in run() takes one or two seconds. It is not very frequent, but it seems to be the cause of my issues.
Also, my node is sending the message twice sometimes (I have yet to check why), and that increases the time also.

@martinhjelmare have you found anything? I've had a quick look at the code and found nothing relevant. The 1 second timeout you're referring to is just a connection timeout, right? It shouldn't affect communication after connecting I guess.
I'll try to add some debug prints to see if I find anything.

@martinhjelmare yes, I'm using the serial gateway. It should be possible to make it better, since I had no issues with the same gateway on Pimatic. I'll try to have a look at the code and let you know if I also find anything

Sometimes I notice that there is some delay in Home Assistant processing or receiving MySensors messages.
For example, I have a node with two switches. I press switch A and right after switch B. Looking at the debug logs from HA's MySensors component, switch B state is updated about a second after switch A.

I have never noticed this delay when using Pimatic instead of HA.

@martinhjelmare great idea! Thank you.

Is there any way to set the state of a motion sensor (binary_sensor) to "off" from Home Assistant?
My sensor sends a TRIPPED=0 when there's no movement, but if the message is lost or the sensor goes out of battery, I want it to appear as "off" in HA after some time.

@martinhjelmare I just updated to the latest version and now they appear correctly after rebooting! Thank you very much.

@exxamalte The sensor appears correctly after sending values. Also, the .json file is correctly filled with the sensor data.

@martinhjelmare Well, I'm using 0.33.4! I'll try updating and report back :) Thanks.

After restarting Home Assistant, my motion and light sensors do not show up until they send values again. They are being correctly saved on the persistence .json file, so I expected them to show up.

@n3ro Couldn't you power the step-up from one of the arduino's digital pins? Then set the pin to HIGH/LOW to power the sensor on/off?
Maybe it draws too much power?

@LastSamurai Here is the code for my PIR and Light sensore node:
https://github.com/abmantis/MySensors-Sketches/blob/master/MotionLightSensor/MotionLightSensor.ino

It is a bit complex, sorry. Also, ignore the temperature parts since that is a WIP and is untested.

@Boots33 But for my node it should be connected in 5 seconds. Range is not a problem. The problem happened because I had to reboot my raspberry, and someone pressed the switch :P

Lets say it looses connection for some reason. The next time I press the switch (and the gateway is on), it will have 5 seconds to reconnect, which should be enough. If the gateway is still of, I can just press the switch again when it is turned on.

My code is a little different, since I only send 0 when the PIR reports 0, instead of sending it right after 1.

If you want I may post the code later.

Thanks for the help and explanation.

I suggest the following:

if(!isTransportOK()){
    wait(5000); // transport is not operational, allow the transport layer to fix this
 }
 sleep(30000);  // transport is OK, node can sleep

That way, if it still can't connect during those 5 seconds it will sleep, and try again the next time.

@Boots33 Yeah, my node sleeps! It may be that. I see that the development branch has a fix for that already. Is it ok to use that branch?