@tekka: it was probably a mix of power/distance. when change these two parameters, OTA went fine. thank you
What is the best way to handle OTA for sleeping nodes? is there something else todo besides setting the property under settings in MYSController? Do I need to powercycle the node or will MYSController kicks in when the node sleeps/smartSleeps?
thank you for your time
@tekka : fair enough, i should read better next time 
i'll try the way you suggest. thank you.
Hello,
I am trying to use MYSController with MYSBootloader 1.3pre2 to reassign a node's ID, and I cannot make it work.
I've tried to check/uncheck the Auto ID toggle/tried to use the MYSBootloader CMDs/Assign ID and setting a new one to no avail.
After that, when it reboots, the node reask for it's firmware, and MYSController re-uploads it, but the node keeps the old ID from the EEProm. (note that the sketch don't hardcode the node's ID).
I'd like to keep the ID management free (i.e. do not hardcode all my node's IDs of course)
How can I do that?
[2016-10-21 13:41:33.318 Info] CLICK Reassign ID from 1 to 20
[2016-10-21 13:41:33.319 Info] TX 1;0;3;0;13;0
[2016-10-21 13:41:33.364 Info] RX 0;255;3;0;9;!TSP:MSG:SEND 0-0-1-1 s=0,c=3,t=13,pt=0,l=1,sg=0,ft=0,st=fail:0
[2016-10-21 13:41:37.886 Info] RX 0;255;3;0;9;TSP:MSG:READ 4-4-0 s=255,c=3,t=22,pt=5,l=4,sg=0:155561124
[2016-10-21 13:41:37.886 Info] RX 4;255;3;0;22;155561124
[2016-10-21 13:41:42.855 Info] RX 0;255;3;0;9;TSP:MSG:READ 2-2-0 s=1,c=1,t=16,pt=0,l=1,sg=0:0
[2016-10-21 13:41:42.857 Info] RX 2;1;1;0;16;0
[2016-10-21 13:41:46.623 Info] RX 0;255;3;0;9;TSP:MSG:READ 8-5-0 s=2,c=1,t=16,pt=0,l=1,sg=0:0
[2016-10-21 13:41:46.625 Info] RX 8;2;1;0;16;0
[2016-10-21 13:41:47.899 Info] RX 0;255;3;0;9;TSP:MSG:READ 8-5-0 s=3,c=1,t=23,pt=2,l=2,sg=0:80
[2016-10-21 13:41:47.901 Info] RX 8;3;1;0;23;80
[2016-10-21 13:41:50.491 Info] RX 0;255;3;0;9;TSP:MSG:READ 4-4-0 s=1,c=1,t=0,pt=7,l=5,sg=0:22.0
[2016-10-21 13:41:50.494 Info] RX 0;255;3;0;9;TSP:MSG:ACK msg
[2016-10-21 13:41:50.540 Info] RX 0;255;3;0;9;!TSP:MSG:SEND 0-0-4-4 s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=fail:22.0
[2016-10-21 13:41:50.540 Info] RX 4;1;1;0;0;22.0
[2016-10-21 13:41:50.570 Info] RX 0;255;3;0;9;TSP:MSG:READ 4-4-0 s=255,c=3,t=22,pt=5,l=4,sg=0:155562401
[2016-10-21 13:41:50.570 Info] RX 4;255;3;0;22;155562401
[2016-10-21 13:41:57.014 Info] RX 0;255;3;0;9;TSP:SANCHK:OK
[2016-10-21 13:42:02.832 Info] RX 0;255;3;0;9;TSP:MSG:READ 4-4-0 s=255,c=3,t=22,pt=5,l=4,sg=0:155563404
[2016-10-21 13:42:02.832 Info] RX 4;255;3;0;22;155563404
[2016-10-21 13:42:20.453 Info] RX 0;255;3;0;9;TSP:MSG:READ 1-1-0 s=255,c=3,t=22,pt=5,l=4,sg=0:4712
[2016-10-21 13:42:20.453 Info] RX 1;255;3;0;22;4712
[2016-10-21 13:42:20.453 Info] CHILD New child discovered, node id=1, child id=internal
[2016-10-21 13:42:20.951 Info] RX 0;255;3;0;9;TSP:MSG:READ 1-1-0 s=2,c=1,t=16,pt=0,l=1,sg=0:0
[2016-10-21 13:42:20.953 Info] RX 1;2;1;0;16;0
[2016-10-21 13:42:20.953 Info] CHILD New child discovered, node id=1, child id=2
[2016-10-21 13:42:21.954 Info] RX 0;255;3;0;9;TSP:MSG:READ 1-1-0 s=3,c=1,t=23,pt=2,l=2,sg=0:42
[2016-10-21 13:42:21.956 Info] RX 1;3;1;0;23;42
[2016-10-21 13:42:21.956 Info] CHILD New child discovered, node id=1, child id=3
[2016-10-21 13:42:27.773 Info] RX 0;255;3;0;9;TSP:MSG:READ 4-4-0 s=255,c=3,t=22,pt=5,l=4,sg=0:155565680
[2016-10-21 13:42:27.774 Info] RX 4;255;3;0;22;155565680
[2016-10-21 13:42:40.382 Info] RX 0;255;3;0;9;TSP:MSG:READ 4-4-0 s=255,c=3,t=22,pt=5,l=4,sg=0:155566954
[2016-10-21 13:42:40.382 Info] RX 4;255;3;0;22;155566954
Starting sensor (RNNNA-, 2.0.0)
TSM:INIT
TSM:RADIO:OK
TSP:ASSIGNID:OK (ID=1)
TSM:FPAR
TSP:MSG:SEND 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSP:MSG:READ 5-5-1 s=255,c=3,t=8,pt=1,l=1,sg=0:1
TSP:MSG:FPAR RES (ID=5, dist=1)
TSP:MSG:PAR OK (ID=5, dist=2)
TSP:MSG:READ 0-0-1 s=255,c=3,t=8,pt=1,l=1,sg=0:0
TSP:MSG:FPAR RES (ID=0, dist=0)
TSP:MSG:PAR OK (ID=0, dist=1)
TSM:FPAR:OK
TSM:ID
TSM:CHKID:OK (ID=1)
TSM:UPL
TSP:PING:SEND (dest=0)
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=ok:1
TSP:MSG:READ 0-0-1 s=255,c=3,t=25,pt=1,l=1,sg=0:1
TSP:MSG:PONG RECV (hops=1)
TSP:CHKUPL:OK
TSM:UPL:OK
TSM:READY
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=ok:0100
TSP:MSG:SEND 1-1-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,ft=0,st=ok:2.0.0
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=ok:0
TSP:MSG:READ 0-0-1 s=255,c=3,t=15,pt=6,l=2,sg=0:0100
TSP:MSG:READ 0-0-1 s=255,c=3,t=15,pt=6,l=2,sg=0:0100
TSP:MSG:READ 0-0-1 s=255,c=3,t=6,pt=0,l=1,sg=0:M
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=11,pt=0,l=12,sg=0,ft=0,st=ok:Multi Sensor
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,ft=0,st=ok:1.0
TSP:MSG:SEND 1-1-0-0 s=2,c=0,t=1,pt=0,l=0,sg=0,ft=0,st=ok:
TSP:MSG:SEND 1-1-0-0 s=0,c=0,t=7,pt=0,l=0,sg=0,ft=0,st=ok:
TSP:MSG:SEND 1-1-0-0 s=1,c=0,t=6,pt=0,l=0,sg=0,ft=0,st=ok:
TSP:MSG:SEND 1-1-0-0 s=3,c=0,t=16,pt=0,l=0,sg=0,ft=0,st=ok:
Request registration...
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=ok:2
TSP:MSG:READ 0-0-1 s=255,c=3,t=27,pt=1,l=1,sg=0:1
Node registration=1
Init complete, id=1, parent=0, distance=1, registration=1
TSP:MSG:SEND 1-1-0-0 s=2,c=1,t=16,pt=0,l=1,sg=0,ft=0,st=ok:0
TSP:MSG:SEND 1-1-0-0 s=3,c=1,t=23,pt=2,l=2,sg=0,ft=0,st=ok:54
@tekka my node wakes up every two minutes (or on pir movement) sends some messages (temperature, light level...) and sleeps right away. will MYSController be able to do that in this small time window? is there something i can code to help it? (heartBeat, wait, smartSomething?)
(as i saw during my few tests, i had to powercycle my node, maybe i wasn't patient enough :))
@tekka: it was probably a mix of power/distance. when change these two parameters, OTA went fine. thank you
What is the best way to handle OTA for sleeping nodes? is there something else todo besides setting the property under settings in MYSController? Do I need to powercycle the node or will MYSController kicks in when the node sleeps/smartSleeps?
thank you for your time
@mannkind : thanks for the clarifications. My problem is that the node seems to hang at the booting phase in MYSController sa per the screenshot.
@tekka that should be it (gw in the 50 cm range). I'll try more tests and get back here in any case.
@mannkind, @tekka: How do we interpret the OTA logs?
@mannkind : thank you for your message. I'll give that a go later on.
@tekka , @anyone
I am trying to make this work using MYSController (from MYSBootloader_V13pre2/). I've followed the instructions above from @tekka, but it feels like the OTA process kicks around quite quick, then it seems to block in a loop
[2016-10-17 23:09:29.821 Info] RX 1;255;4;0;0;0A0001005000D4460102
[2016-10-17 23:09:29.821 Info] INFO BL version=258
[2016-10-17 23:09:29.821 Info] INFO Send FW info to node 1: type=A, version=1, blocks=0x0050, CRC=0x46D4
[2016-10-17 23:09:29.822 Info] TX 1;0;4;0;1;0A0001005000D446
I'll try to keep it going all night, but here are my full log till now.
Any idea what is going wrong?
0_1476738954886_MySensors_20161017-230018.log
@mannkind thank you for your reply. I don't want to get you in trouble regarding the rules. i don't feel it is against the rules to promote open source or contribution around mysensors if it makes the journey more enjoyable. maybe a mod or admin can pitch in and clarify in any case.
I understand that the gateway role is to open up integration with other controllers (and we have quite many thanks to that)
The problem i am trying to wrap my head around is to have mysensors network attached to my current controller, and ideally be able to update over the air the sketches. how can i begin doing that? i am ready to use 2 or more controller (mycontroller or myscontroller or...), 2 ore more gateways and even maybe have the nodes on two different rf channels.
Basically, what is the recommended way to achieve that, while having for the time being at least, another controller attached.?
@mannkind what other software do you use for ota firmware update?
thanks
@tekka great work! thank you for sharing this.
Your controller and great contribution had me quickly started with mysensors. I am interested in a way to do OTA updates using MYSController via api or a script call or even rewriting the logic in an outside code. I'll try to explain the need based on my setup below.
Given that I am using jeedom right now as a controller, but sadly it doesn't seem to support yet OTA updates. I'd like to be able to reuse or even contribute to this feature and I'd appreciate pointers to start doing that.
My setup has it that jeedom runs off a raspi and has a mysensors serial gateway attached. (1 to 2 Watts draw for this setup). MYSController can work as an ethernet relay gateway, but if I understand correctly I have to run it on windows (more moving parts), or a much hungrier box than my raspi.
Is there a way I can make that work somehow? I am ready and appreciate any type of suggestions with the current setup I have or an evolution which goes into that direction.