These are chat archives for mycontroller-org/mycontroller

1st
Dec 2015
Артур
@arturmon
Dec 01 2015 07:01
maybe it's worth to make a manual selection of nodes polling time?
and knowing the estimated time of response node adjusted to them
Jeeva Kandasamy
@jkandasa
Dec 01 2015 10:27
@arturmon for now only one thread is running to handle heartbeat polling for all the nodes, if we make it for each node, it will become costly operation. We will try to figure out is there any alternative solutions for this.
Артур
@arturmon
Dec 01 2015 11:23
as it is illogical. we have in fact two types of sensors, autonomous and constantly working. can make two streams? and only the second stream has already been done for each sensor.
Jeeva Kandasamy
@jkandasa
Dec 01 2015 13:56
@arturmon this is good idea. the current approach is working as like, sending HEARTBEAT request to all the nodes, after some time(based on interval) checking last seen.
For example HEARTBEAT interval is 30 minutes. If battery operated node sends (HEARTBEAT response) themselves within 30 minutes, will be considered as alive
if a node last received HEARTBEAT goes more than 30 minutes then it will be marked as NOT REACHABLE, so we can adjust this interval from 1 MINUTE to ANY MINUTES and we can achieve both battery operated and normal nodes.
What do you think on this?
Артур
@arturmon
Dec 01 2015 14:06
@jkandasa I think it will be better than it is now implemented in ьmysensors. I do not understand how going to keep track of all the autonomous nodes.
Jeeva Kandasamy
@jkandasa
Dec 01 2015 14:08
@arturmon we have to give special attention on REPEATER NODES, it will be covered.
planing to introduce alarm module for node level in MyController.org, with this we can track something like "If data not received from Node ABC for last XX minutes/hours trigger"
this will cover everything
Артур
@arturmon
Dec 01 2015 14:13
need to try.