Node sleeping as a selectable option for every node

[louis]

Hi Gene,

I'm having some issues with some nodes which are always awake.

For some reason, i guess a message isn't arriving at the controller, the node is flagged as sleeping, while the node is in fact not sleeping.

This causes the system to ignore a lot of actions i do on this node, as it is flagged sleeping.

For example a basic.get will not be performed :-(

Hope you can help me on this one.

I would realy like an option to disable this sleeping flag on a specific node.

TIA

Louis

[Zen]

I completely agree with Louis. I can't configure parameters for some of my Z-Wave devices because HomeGenie thinks they are sleeping. An option that user could choose would be great. Thanks.

[louis]

Hi Gene,

For now i have created my own ZWavelib and disabled the sleeping option, for the time being i can life with this workaround 

Hope you will find the time to create a solution for this problem.

TIA

kind regards

Louis

[Zen]

Could you share your zwavelib? Thanks.

[Gene]

this option is coming with next release:

- Added "Set node as always awake" option to Z-Wave Query on WakeUp program

g.

[louis]

Hi Gene,

That's great

Thanks alot !!

For the time being Zen, here's a temp solution.

Louis

[Zen]

Thank you Louis and Gene!

[louis]

Hi Gene,

I'am very sorry, but this solution doesn't seem to do the trick.

The problem is that I stil get timeouts which cause the ZWaveLib to flag this node sleeping.
I guess it's a hardware problem. As another sensor (binairy Fibaro just a meter away) doesn't have this problem.

After 20 to 30 minutes the node gets flagged due to a timeout (AEON Multisensor 1.18).
If i restart hg he's working again for some 20 to 30 minutes.

I use these nodes to turn on some lights, and as i sometimes miss a message i query the nodes every 15 seconds.
If he's flagged the query is not send.

So the solution might be to add an option to the node setup page, for example, is on USB power, which is a hard indicator to never set the sleep flag. Even when a timeout occurs. In my case a resend would not be neccesary ... but that's just my system. Maybe that might be a second option for node setup page ?

I would help you if I understood the way the code works, but for now i haven't fully figured it out.
I'll keep working on it

Hope you can help me.

TIA

Louis

[Gene]

Hi Louis,

did you flag the node with the new option? After flagging it just wake it up once to clear the sleeping flag and it won't be flagged anymore.

[louis]

Hi Gene,

I did, the only difference i have is the "Send to sleep after given delay" on 0 seconds.

Btw i had to turn on program 91, which i previously did not use. Which i guess causes the problem to be bigger ... i now lost both my sensors after just one minute in my last test ....

Might it be that messages are mixed up (wrongly interpreted) due to the auto sending of status reports.

Aswell the fact that now program 91 is active he will send more request to a specific node  .. and more responses might get mixed up ?

I asume there's a kind of serializer for sending/receiving messages to a (one) node.

I also often see a large reponse time of up to 3 seconds in the log ....

Just some thoughts

Hope this helps.

If you need more info I'm always available ... (in the evening).

Thanks again !!!

Louis

[Gene]

This works for me, so perhaps logs can help.
Try also disabling the prog 91 after the first wake up. This should also work around the issue. If I well understood we might add a flag "query node on wake up" to prog 91 to let the user decide if the node has to be queried. This is easy to do, you can try yourself modifying the 91 app. If this works please share it

[louis]

Hi Gene,

Due to your changes i figured out a bit more about the code.

I was able to make some changes to the code, I hope you don't mind.

This is the way i ment it

I'm not sure if this is what you want in your code but i hope you get my idea ...

I just cloned your last revision and did some updates on it .... one thing i haven't found yet is to save it to the modules.xml.
If you could include these changes in an upcoming version that would be great

I will  attach the files being changed.

TIA

kind regards

Louis

PS that would also mean that prog 91 changes can be undone 
But ofcourse not the changes in the MIG modules.
Somewhere the property (which was added in prog 91) still needs to be added somewhere else, at least I think, but as you're the expert i hope you can help me on that one.