These are chat archives for mycontroller-org/mycontroller

29th
Nov 2015
Jeeva Kandasamy
@jkandasa
Nov 29 2015 16:36
<br># - used to specify "the nth" XXX day of the month, ex: "6#3" - the third Friday of the month</p> "the nth" XXX day<-----what does that mean???
symbol # - used to specify "the nth" XXX day of the month. For example, the value of "6#3" in the day-of-week field means "the third Friday of the month" (day 6 = Friday and "#3" = the 3rd one in the month). Other examples: "2#1" = the first Monday of the month and "4#5" = the fifth Wednesday of the month. Note that if you specify "#5" and there is not 5 of the given day-of-week in the month, then no firing will occur that month.
@Dietmar-Franken it's easy only to translate, I will do it
Didi
@Dietmar-Franken
Nov 29 2015 17:04
@jkandasa thank you
mycontroller-org/mycontroller@45cc65b added
mycontroller-org/mycontroller@4044a5b added
Didi
@Dietmar-Franken
Nov 29 2015 18:14
:+1:
Артур
@arturmon
Nov 29 2015 18:24
upgrade ru
Jeeva Kandasamy
@jkandasa
Nov 29 2015 18:38
@arturmon done :+1: mycontroller-org/mycontroller@6272a72
Артур
@arturmon
Nov 29 2015 18:51
senks
Артур
@arturmon
Nov 29 2015 19:13
as well as the working node status? I wrote "no status".
Jeeva Kandasamy
@jkandasa
Nov 29 2015 19:14
@arturmon I'm sorry I didn't get you
Артур
@arturmon
Nov 29 2015 21:27
How does it work
Jeeva Kandasamy
@jkandasa
Nov 29 2015 21:39
this feature supports where node is running on 1.6 MySensors
Артур
@arturmon
Nov 29 2015 21:40
hm
Jeeva Kandasamy
@jkandasa
Nov 29 2015 21:40
sends I_HEARTBEAT every 30 minutes once, if there is no I_HEARTBEAT response from node for more than 30 minutes will make it as "Not Reachable"
interval of 30 minutes can changeable, supports from 1 minute to any minutes
this will explain more, mycontroller-org/mycontroller#27
Артур
@arturmon
Nov 29 2015 21:42
not suitable for stand-alone sensors.
you mean for battery operated sensor will be in sleep always right?
Артур
@arturmon
Nov 29 2015 21:43
yes
1.6 is still unstable.
Jeeva Kandasamy
@jkandasa
Nov 29 2015 21:44
yes, but for other sensors we can track
Yes, there is huge change b/w 1.5 and 1.6, hence not interested to develop features with 1.5, directly jumped to 1.6..
even current MQTT also supports only for 1.6
@Dietmar-Franken I will test your pull request(mycontroller-org/mycontroller#122) locally and update merge it. Thank you.
Артур
@arturmon
Nov 29 2015 21:47
look, but still very wet 1.6
when I wanted to install mqtt broker, then a fiction, even it is integrated into mysensors.org
at that time, even most of the sample was not going to.
I will wait for a stable release.
Jeeva Kandasamy
@jkandasa
Nov 29 2015 21:48
Yes, we will wait for stable release, I asked Hek, time line, he is waiting someones response
Артур
@arturmon
Nov 29 2015 21:49
therefore not yet stable branch will soon be ready?
Jeeva Kandasamy
@jkandasa
Nov 29 2015 21:50
But, better we can create another branch in MyController from 1.7 mysensors version
no time line,
Артур
@arturmon
Nov 29 2015 21:50
On what is planned in 1.7?
Jeeva Kandasamy
@jkandasa
Nov 29 2015 21:50
the response i got is, "Can't give any est. on 1.6 yet. Waiting for commits from Patrick and Thomas.. Then I'd like to split the repo to have a more Arduino-library layout so we need to make some chnanges on the build system I guess."
no, right now we have only master branch in MyController, in future, we can create new branch as "development"
Артур
@arturmon
Nov 29 2015 21:51
understandably. will wait ))
Артур
@arturmon
Nov 29 2015 21:52
great idea. especially if it will follow the development of mysensors or something new will be introduced to the project.
Jeeva Kandasamy
@jkandasa
Nov 29 2015 21:53
yes, we can release all the support in MyController on the same time when new release happens in MySensors
@arturmon I go to sleep now. Good night.. (I hope it's night for you now)
Артур
@arturmon
Nov 29 2015 22:10
ok