gw to node: isalive ?

[hek]

@epierre

Yea, but it must be awake and answer replies (of your choice).

[epierre]

hello, the warersensor is always awake but sending a 2;5:2;35 ; doesn't bring back value.... that is why I'm asking for help

[marceltrapman]

I also have this with the repeater ("ARDIUNO_RELAY").
I want to make sure that this and all sensors are available by asking them for their version and sketch but they do not always reply so it seems...

[hek]

@epierre said:

hello, the warersensor is always awake but sending a 2;5:2;35 ; doesn't bring back value.... that is why I'm asking for help

What exactly are you trying to send here? 35? How does your code look like? Are you handling the incoming message in the sensor and create a reply back to controller?

[epierre]

@hek hi, I've added nothing yet but your answer make me realize there is no query logic by default in tbe sensor.

[epierre]

@marceltrapman what kind of message do you send ? I don't see in the API you can request internal values...

@hek would the ack be aplicable to all sensors ?

[marceltrapman]

@epierre I am working on my plugin for Indigo.
This is what these messages look like:

2014-07-16 21:59:18.267	MySensors Debug	Sending command 2;0;3;0;2;Get Version
2014-07-16 21:59:18.267	MySensors Debug	Sending command 2;0;3;0;11;Get Sketch Name

[epierre]

@marceltrapman it did not work for me... but tje sensor is back again to my higjer satisfaction...

@hek it is importantbfor an alarm ti ping its node to know if there is signal jamming...

[marceltrapman]

@epierre said:

@marceltrapman tje sensor is back again to my higjer satisfaction...

Nice.

Looking at Indigo and Z-wave there is the same issue. A node that is asleep can not be awoken from Indigo (or any other controller).
The reason I would like this to be different is so that I know that a sensor has fallen out (battery dead or otherwise).

The problem is that waking a sensor up means that the sensor has to listen.
When a sensor listens it has to be awake (I believe).
Vicious Circle...

[epierre]

@marceltrapman yes...in my case some are not asleep... not to say all... in z-wave the hysteresis management is good, controller ofter fairly manage device that always send something every 2h...

[hek]

A better approach is probably to send in something every time sensor wakes up.

[epierre]

@hek well if sensor sends something I know it is awoken ;-) I'll try implement something on my water sensor on this !

[marceltrapman]

@hek said:

A better approach is probably to send in something every time sensor wakes up.

@hek @epierre
While thinking about this I think I want to add a 'wake-interval' like implemented in z-wave (and exposed in Indigo).
I want to be able to set a wake interval to every 5, 10, 15, 20, 30, 45 minutes, 1, 2, 4 hours, twice per day, once per day or once per week.

Not sure if this is something for me to do or that this belongs in the libraries...

[hek]

@marceltrapman

This could very well be implemented with the current libraries.

You could for instance request VAR_1 every time the sensor wakes up which contains the sleep time used when putting Arduino to sleep..

This would make sleep time configurable from controller-side.

[marceltrapman]

@hek said:

This could very well be implemented with the current libraries.

You could for instance request VAR_1 every time the sensor wakes up which contains the sleep time used when putting Arduino to sleep..

This would make sleep time configurable from controller-side.

Hah, gonna use that!!!!!!

[epierre]

@marceltrapman @hek that would mean sketched upgrade, but I plus it !