Windows GUI/Controller for MySensors
-
Hi @tekka,
Thanks for the reply, I created a "clear eeprom" hex and after uploading it is working as expected, the ID resets.
Using the function in Mycontroller however, does not work. Not sure if this is a bug, or perhaps an error caused by an Arduino clone, but the "reassign ID" function is not working as intended here.
Anyone here that got it working as intended?
-
@Tekka Same "bug" here" with MYSBootloader 1.1 (hex from github) on arduino nano. Try to change ID of node N°1, Log :
[2015-09-21 21:52:57.053 Info] INFO *** Logging START *** [2015-09-21 21:52:57.053 Info] VERSION MYSController 0.1.2.282 [2015-09-21 21:52:57.053 Info] STARTUP INI file loaded [2015-09-21 21:52:57.053 Info] STARTUP Loading FW repository... [2015-09-21 21:52:57.054 Info] REPO FW "Blink" loaded. t=10, v=1, blocks=72, crc=0xD098 [2015-09-21 21:52:57.064 Info] REPO FW "TimeReporter" loaded. t=20, v=1, blocks=840, crc=0x4AC5 [2015-09-21 21:52:57.076 Info] REPO FW "Motion" loaded. t=30, v=1, blocks=1024, crc=0xD1BF [2015-09-21 21:52:57.092 Info] REPO FW "Sensebender Micro" loaded. t=100, v=1, blocks=1344, crc=0x3482 [2015-09-21 21:52:57.108 Info] REPO FW "Sensebender Blink" loaded. t=110, v=1, blocks=768, crc=0x1314 [2015-09-21 21:52:57.108 Info] REPO FW repository loaded. Items=5 [2015-09-21 21:52:57.111 Info] STARTUP Initialize message types [2015-09-21 21:52:57.111 Info] NODE New node discovered, node id=0 [2015-09-21 21:52:57.111 Info] NODE New node discovered, node id=255 [2015-09-21 21:52:59.606 Info] INFO Connected to 192.168.1.90:5003 [2015-09-21 21:53:04.373 Info] NODE New node discovered, node id=1 [2015-09-21 21:53:04.376 Info] CHILD New child discovered, node id=1, child id=internal [2015-09-21 21:53:04.379 Info] INFO BL version=257 [2015-09-21 21:53:04.380 Info] INFO No FW assigned [2015-09-21 21:53:04.383 Info] RX 1;255;4;0;0;1E0001000004BFD10101 [2015-09-21 21:53:04.681 Info] NODE New node discovered, node id=4 [2015-09-21 21:53:04.685 Info] CHILD New child discovered, node id=4, child id=1 [2015-09-21 21:53:04.688 Info] RX 4;1;1;0;0;21.6 [2015-09-21 21:53:04.691 Info] CHILD New child discovered, node id=4, child id=2 [2015-09-21 21:53:04.694 Info] RX 4;2;1;0;1;71 [2015-09-21 21:53:06.421 Info] INFO BL version=257 [2015-09-21 21:53:06.424 Info] INFO No FW assigned [2015-09-21 21:53:06.427 Info] RX 1;255;4;0;0;1E0001000004BFD10101 [2015-09-21 21:53:08.470 Info] INFO BL version=257 [2015-09-21 21:53:08.472 Info] INFO No FW assigned [2015-09-21 21:53:08.476 Info] RX 1;255;4;0;0;1E0001000004BFD10101 [2015-09-21 21:53:14.903 Info] UPDATE 4295098650 [2015-09-21 21:53:14.906 Info] INFO BL version=257 [2015-09-21 21:53:14.909 Info] INFO No FW assigned [2015-09-21 21:53:14.913 Info] RX 1;255;4;0;0;1E0001000004BFD10101 [2015-09-21 21:53:14.916 Info] INFO BL version=257 [2015-09-21 21:53:14.918 Info] INFO No FW assigned [2015-09-21 21:53:14.922 Info] RX 1;255;4;0;0;1E0001000004BFD10101 [2015-09-21 21:53:14.925 Info] DEBUG Update child id=255, type=ARDUINO_NODE [2015-09-21 21:53:14.929 Info] RX 1;255;0;0;17;1.5 [2015-09-21 21:53:14.933 Info] TX 1;255;3;0;6;M [2015-09-21 21:53:14.937 Info] RX 1;255;3;0;6;0 [2015-09-21 21:53:14.945 Info] CHILD New child discovered, node id=0, child id=0 [2015-09-21 21:53:14.950 Info] RX 0;0;3;0;14;Gateway startup complete. [2015-09-21 21:53:16.680 Info] RX 1;255;3;0;11;Motion Sensor [2015-09-21 21:53:16.691 Info] RX 1;255;3;0;12;1.0 [2015-09-21 21:53:16.695 Info] CHILD New child discovered, node id=1, child id=1 [2015-09-21 21:53:16.701 Info] DEBUG Update child id=1, type=MOTION [2015-09-21 21:53:16.714 Info] RX 1;1;0;0;1; [2015-09-21 21:53:16.718 Info] RX 1;1;1;0;16;0 [2015-09-21 21:53:38.779 Info] INFO Node trigger set, node=1, trigger=1 [2015-09-21 21:53:39.793 Info] INFO Retained message triggered for release, node=1 [2015-09-21 21:53:39.796 Info] CHILD New child discovered, node id=1, child id=1 [2015-09-21 21:53:39.800 Info] TX 1;0;3;0;13;0 [2015-09-21 21:53:39.805 Info] RX 1;1;1;0;16;1 [2015-09-21 21:53:39.808 Info] CHILD New child discovered, node id=1, child id=internal [2015-09-21 21:53:39.811 Info] DEBUG Update child id=255, type=ARDUINO_NODE [2015-09-21 21:53:39.815 Info] RX 1;255;0;0;17;1.5 [2015-09-21 21:53:56.729 Info] INFO Disconnected [2015-09-21 21:53:58.924 Info] INFO *** Logging STOP ***``` -
@Tekka Same "bug" here" with MYSBootloader 1.1 (hex from github) on arduino nano. Try to change ID of node N°1, Log :
[2015-09-21 21:52:57.053 Info] INFO *** Logging START *** [2015-09-21 21:52:57.053 Info] VERSION MYSController 0.1.2.282 [2015-09-21 21:52:57.053 Info] STARTUP INI file loaded [2015-09-21 21:52:57.053 Info] STARTUP Loading FW repository... [2015-09-21 21:52:57.054 Info] REPO FW "Blink" loaded. t=10, v=1, blocks=72, crc=0xD098 [2015-09-21 21:52:57.064 Info] REPO FW "TimeReporter" loaded. t=20, v=1, blocks=840, crc=0x4AC5 [2015-09-21 21:52:57.076 Info] REPO FW "Motion" loaded. t=30, v=1, blocks=1024, crc=0xD1BF [2015-09-21 21:52:57.092 Info] REPO FW "Sensebender Micro" loaded. t=100, v=1, blocks=1344, crc=0x3482 [2015-09-21 21:52:57.108 Info] REPO FW "Sensebender Blink" loaded. t=110, v=1, blocks=768, crc=0x1314 [2015-09-21 21:52:57.108 Info] REPO FW repository loaded. Items=5 [2015-09-21 21:52:57.111 Info] STARTUP Initialize message types [2015-09-21 21:52:57.111 Info] NODE New node discovered, node id=0 [2015-09-21 21:52:57.111 Info] NODE New node discovered, node id=255 [2015-09-21 21:52:59.606 Info] INFO Connected to 192.168.1.90:5003 [2015-09-21 21:53:04.373 Info] NODE New node discovered, node id=1 [2015-09-21 21:53:04.376 Info] CHILD New child discovered, node id=1, child id=internal [2015-09-21 21:53:04.379 Info] INFO BL version=257 [2015-09-21 21:53:04.380 Info] INFO No FW assigned [2015-09-21 21:53:04.383 Info] RX 1;255;4;0;0;1E0001000004BFD10101 [2015-09-21 21:53:04.681 Info] NODE New node discovered, node id=4 [2015-09-21 21:53:04.685 Info] CHILD New child discovered, node id=4, child id=1 [2015-09-21 21:53:04.688 Info] RX 4;1;1;0;0;21.6 [2015-09-21 21:53:04.691 Info] CHILD New child discovered, node id=4, child id=2 [2015-09-21 21:53:04.694 Info] RX 4;2;1;0;1;71 [2015-09-21 21:53:06.421 Info] INFO BL version=257 [2015-09-21 21:53:06.424 Info] INFO No FW assigned [2015-09-21 21:53:06.427 Info] RX 1;255;4;0;0;1E0001000004BFD10101 [2015-09-21 21:53:08.470 Info] INFO BL version=257 [2015-09-21 21:53:08.472 Info] INFO No FW assigned [2015-09-21 21:53:08.476 Info] RX 1;255;4;0;0;1E0001000004BFD10101 [2015-09-21 21:53:14.903 Info] UPDATE 4295098650 [2015-09-21 21:53:14.906 Info] INFO BL version=257 [2015-09-21 21:53:14.909 Info] INFO No FW assigned [2015-09-21 21:53:14.913 Info] RX 1;255;4;0;0;1E0001000004BFD10101 [2015-09-21 21:53:14.916 Info] INFO BL version=257 [2015-09-21 21:53:14.918 Info] INFO No FW assigned [2015-09-21 21:53:14.922 Info] RX 1;255;4;0;0;1E0001000004BFD10101 [2015-09-21 21:53:14.925 Info] DEBUG Update child id=255, type=ARDUINO_NODE [2015-09-21 21:53:14.929 Info] RX 1;255;0;0;17;1.5 [2015-09-21 21:53:14.933 Info] TX 1;255;3;0;6;M [2015-09-21 21:53:14.937 Info] RX 1;255;3;0;6;0 [2015-09-21 21:53:14.945 Info] CHILD New child discovered, node id=0, child id=0 [2015-09-21 21:53:14.950 Info] RX 0;0;3;0;14;Gateway startup complete. [2015-09-21 21:53:16.680 Info] RX 1;255;3;0;11;Motion Sensor [2015-09-21 21:53:16.691 Info] RX 1;255;3;0;12;1.0 [2015-09-21 21:53:16.695 Info] CHILD New child discovered, node id=1, child id=1 [2015-09-21 21:53:16.701 Info] DEBUG Update child id=1, type=MOTION [2015-09-21 21:53:16.714 Info] RX 1;1;0;0;1; [2015-09-21 21:53:16.718 Info] RX 1;1;1;0;16;0 [2015-09-21 21:53:38.779 Info] INFO Node trigger set, node=1, trigger=1 [2015-09-21 21:53:39.793 Info] INFO Retained message triggered for release, node=1 [2015-09-21 21:53:39.796 Info] CHILD New child discovered, node id=1, child id=1 [2015-09-21 21:53:39.800 Info] TX 1;0;3;0;13;0 [2015-09-21 21:53:39.805 Info] RX 1;1;1;0;16;1 [2015-09-21 21:53:39.808 Info] CHILD New child discovered, node id=1, child id=internal [2015-09-21 21:53:39.811 Info] DEBUG Update child id=255, type=ARDUINO_NODE [2015-09-21 21:53:39.815 Info] RX 1;255;0;0;17;1.5 [2015-09-21 21:53:56.729 Info] INFO Disconnected [2015-09-21 21:53:58.924 Info] INFO *** Logging STOP ***``` -
@tekka Could you please explain the steps. Otherwise on next upgrade I have open all the boxes and play with soldering iron :(
-
I have decided it is time for me to finally learn how to do OTA uploading so I read though all the posts to learn how to do it. As I was reading through the posts I was thinking how this tool would be also be useful for troubleshooting. I'm not at home so I can't do any testing right now but I was wondering if it's possible to have the MYSController accessing my Ethernet gateway at the same time my controller (Vera) is? It seems like there could be problems with ACK messages but maybe I'm not fully understanding something? What I'd like to do is have this controller running to watch messagew but not have it interfere with normal communications with Vera. Is that possible? Thanks in advance!
-
I have decided it is time for me to finally learn how to do OTA uploading so I read though all the posts to learn how to do it. As I was reading through the posts I was thinking how this tool would be also be useful for troubleshooting. I'm not at home so I can't do any testing right now but I was wondering if it's possible to have the MYSController accessing my Ethernet gateway at the same time my controller (Vera) is? It seems like there could be problems with ACK messages but maybe I'm not fully understanding something? What I'd like to do is have this controller running to watch messagew but not have it interfere with normal communications with Vera. Is that possible? Thanks in advance!
-
I have decided it is time for me to finally learn how to do OTA uploading so I read though all the posts to learn how to do it. As I was reading through the posts I was thinking how this tool would be also be useful for troubleshooting. I'm not at home so I can't do any testing right now but I was wondering if it's possible to have the MYSController accessing my Ethernet gateway at the same time my controller (Vera) is? It seems like there could be problems with ACK messages but maybe I'm not fully understanding something? What I'd like to do is have this controller running to watch messagew but not have it interfere with normal communications with Vera. Is that possible? Thanks in advance!
-
@petewill yeah i 2nd that.
i keep it up to make sure the sensors are sending and then watch the change in vera.
so no problems running both at the same time for however long you want. -
@tekka Do you have any plan of supporting DualOptiboot in the MYSController (not a request, just an inquiry). I believe (at least for myself) that your excellent tool is the best option to instrument OTA and since I have included external flash in my boards I would like to use DualOptiboot for OTA since it provides some "safety" in case RF transmission is shaky.
I am not saying MYSBootloader is bad in any way, but since it does not need an external flash (which is a good thing), it is more sensitive to RF interference and sometimes I suppose boards will be "soft bricked" in that case. -
@rvendrame & @mvader Great, thanks!
@petewill I can also confirm that MYSController can coexist with Vera.
I use node-red to abstract things. In my case, I want the Vera (and MYSController) to be left in the dark on how my controller is actually implemented and node-red is the ideal tool to do this.This is my "flow"
Using it, I can have either a serial or an ethernet gw without the controllers knowing.
Instead, I create network serial pipes using socat that the controllers connect to.
I can also filter out the debug prints from the gw if I want to examine something and also prevent them from "disturbing" the controllers (if they do not explicitly support the debug messages or gets bogged down by them).I still need to see if the node-red nodes support OTA since they key packets on '\n' currently which is not really "binary friendly" though, but for normal MySensors operation not involving binary streams, it works just fine :)
-
@tekka Do you have any plan of supporting DualOptiboot in the MYSController (not a request, just an inquiry). I believe (at least for myself) that your excellent tool is the best option to instrument OTA and since I have included external flash in my boards I would like to use DualOptiboot for OTA since it provides some "safety" in case RF transmission is shaky.
I am not saying MYSBootloader is bad in any way, but since it does not need an external flash (which is a good thing), it is more sensitive to RF interference and sometimes I suppose boards will be "soft bricked" in that case.@Anticimex The latest MYSController release supports DualOptiboot, simply check the sensebender board option (node tree, right click). Besides that, MYSBootloader will not leave you with a "soft-bricked" node but rather with a slower OTA update time in the case of RF interferences. If the OTA update fails for whatever reasons (loss of connection, power issues, etc.) MYSBootloader will re-request the FW during the next power-up. Since many community members do not have an external flash option, a slightly longer down-time for the direct update should not cause any problems. Importantly, a faulty sketch with the DualOptiboot update (e.g. no regular gw.process() calls) will result in a real "soft-bricked" node. In the end, both OTA update options have their (dis)advantages, a hardware configuration w/o external flash will only work with offline OTA updates.
-
@petewill I can also confirm that MYSController can coexist with Vera.
I use node-red to abstract things. In my case, I want the Vera (and MYSController) to be left in the dark on how my controller is actually implemented and node-red is the ideal tool to do this.This is my "flow"
Using it, I can have either a serial or an ethernet gw without the controllers knowing.
Instead, I create network serial pipes using socat that the controllers connect to.
I can also filter out the debug prints from the gw if I want to examine something and also prevent them from "disturbing" the controllers (if they do not explicitly support the debug messages or gets bogged down by them).I still need to see if the node-red nodes support OTA since they key packets on '\n' currently which is not really "binary friendly" though, but for normal MySensors operation not involving binary streams, it works just fine :)
-
quite a few post. so apologies if this has been asked before.
I'm trying to upload a sketch(hex) to one of my nano's
it's going but froze at 70%
i had to reboot the gateway.
this time it got to 87% and seems froze again.
any thoughts/suggestions on why the gateway is freezing up?edit: i can't seem to get a sketch to upload. it gets to some random % and then the gateway freezes.
a push of the gateway reset button seems to start it over. but then freezes at random.edit 2: must have been a distance thing.. i put the bridge right next to the gateway and the code uploaded quickly without freezing.
however, i still am curious as to why the gateway fails to respond/freezes if the firmware is not able to be uploaded.@mvader said:
quite a few post. so apologies if this has been asked before.
I'm trying to upload a sketch(hex) to one of my nano's
it's going but froze at 70%
i had to reboot the gateway.
this time it got to 87% and seems froze again.
any thoughts/suggestions on why the gateway is freezing up?edit: i can't seem to get a sketch to upload. it gets to some random % and then the gateway freezes.
a push of the gateway reset button seems to start it over. but then freezes at random.edit 2: must have been a distance thing.. i put the bridge right next to the gateway and the code uploaded quickly without freezing.
however, i still am curious as to why the gateway fails to respond/freezes if the firmware is not able to be uploaded.I thought this may have been a fluke or something. but tonight i tried to OTA a mysensors sensebender board and ran into the same issue basically.
i get to some random point 60 or 70 % and then it just stops.
i moved my sensor right next to the gateway and reset it.
took off again.. but then stopped at a certain point.
and i see "firmware 130" a few times but nothing else about firmware.
the board and gateway continue to function, the sensor sends back temp and humidity etc. but nothing else about firmware. on the left in the gui, it says FW updating. but that never changes.
i won't post the entire debug log, but just the last part of it so you can see what i'm talking about9/29/2015 21:34:44 RX 3;255;4;0;2;82000100DA04 9/29/2015 21:34:44 TX 3;255;4;0;3;82000100D90421503109410951095695479537952795 9/29/2015 21:34:44 RX 3;255;4;0;2;82000100D904 9/29/2015 21:34:44 TX 3;255;4;0;3;82000100D80460E874E88EE190E0A70196010E945F2C 9/29/2015 21:34:44 RX 3;255;4;0;2;82000100D804 9/29/2015 21:34:44 TX 3;255;4;0;3;82000100D704EF92FF92CF93DF93EC016A017B01B22E 9/29/2015 21:34:44 RX 3;255;4;0;2;82000100D704 9/29/2015 21:34:44 TX 3;255;4;0;3;82000100D6040F91FF90DF90CF900895BF92CF92DF92 9/29/2015 21:34:44 RX 3;255;4;0;2;82000100D604 9/29/2015 21:34:45 TX 3;255;4;0;3;82000100D5048064808381E090E00F90DF91CF911F91 9/29/2015 21:34:45 RX 3;255;4;0;2;82000100D504 9/29/2015 21:34:45 TX 3;255;4;0;3;82000100D404FC91579760835096ED91FC9151978081 9/29/2015 21:34:45 RX 3;255;4;0;2;82000100D404 9/29/2015 21:34:45 TX 3;255;4;0;3;82000100D304FC915397808180620CC0D6015696ED91 9/29/2015 21:34:45 RX 3;255;4;0;2;82000100D304 9/29/2015 21:34:45 RX 3;1;1;0;0;75.5 9/29/2015 21:34:45 RX 3;2;1;0;1;56 9/29/2015 21:34:45 TX 3;255;4;0;3;82000100D204FF4F6083D6015B960C935B975296ED91 9/29/2015 21:34:45 RX 3;255;4;0;2;82000100D204 9/29/2015 21:34:45 TX 3;255;4;0;3;82000100D1040E940D266981EBCF838DE80FF11DE35A 9/29/2015 21:34:45 RX 3;255;4;0;2;82000100D104 9/29/2015 21:34:45 TX 3;255;4;0;3;82000100D004ED91FC915197808185FFF1CFC6016983 9/29/2015 21:34:45 RX 3;255;4;0;2;82000100D004 9/29/2015 21:34:45 TX 3;255;4;0;3;82000100CF04848DF81211C00FB607FCF9CFD6015096 9/29/2015 21:34:45 RX 3;255;4;0;2;82000100CF04 9/29/2015 21:34:45 TX 3;255;4;0;3;82000100CE04038D10E00F5F1F4F0F731127F02EF601 9/29/2015 21:34:45 RX 3;255;4;0;2;82000100CE04 9/29/2015 21:34:45 TX 3;255;4;0;3;82000100CD045096ED91FC915197808185FD2EC0F601 9/29/2015 21:34:45 RX 3;255;4;0;2;82000100CD04 9/29/2015 21:34:46 TX 3;255;4;0;3;82000100CC045B969C915B975C968C915C97981307C0 9/29/2015 21:34:46 RX 3;255;4;0;2;82000100CC04 9/29/2015 21:34:46 TX 3;255;4;0;3;82000100CB04CDB7DEB76C0181E0D60158968C935897 9/29/2015 21:34:46 RX 3;255;4;0;2;82000100CB04 9/29/2015 21:34:46 TX 3;255;4;0;3;82000100CA04CF92DF92FF920F931F93CF93DF931F92 9/29/2015 21:34:46 RX 3;255;4;0;2;82000100CA04 9/29/2015 21:34:46 RX 3;255;3;0;0;59 9/29/2015 21:34:46 TX 3;255;4;0;3;82000100C904EDCFCE010E940D26E7CFDF91CF910895 9/29/2015 21:34:46 RX 3;255;4;0;2;82000100C904 9/29/2015 21:34:46 TX 3;255;4;0;3;82000100C804F5CF808185FFF2CFA889B9898C9185FF 9/29/2015 21:34:46 RX 3;255;4;0;2;82000100C804 9/29/2015 21:34:46 TX 3;255;4;0;3;82000100C70405C0A889B9898C9186FD0FC00FB607FC 9/29/2015 21:34:46 RX 3;255;4;0;2;82000100C704 9/29/2015 21:34:47 TX 3;255;4;0;3;82000100C604EC01888D8823C9F0EA89FB89808185FD 9/29/2015 21:34:47 RX 3;255;4;0;2;82000100C604 9/29/2015 21:34:47 TX 3;255;4;0;3;82000100C504F389E02D80818F7D80830895CF93DF93 9/29/2015 21:34:47 RX 3;255;4;0;2;82000100C504 9/29/2015 21:34:47 TX 3;255;4;0;3;82000100C4048C9180648C93938D848D981306C00288 9/29/2015 21:34:47 RX 3;255;4;0;2;82000100C404 9/29/2015 21:34:47 RX 3;1;1;0;0;75.5 9/29/2015 21:34:47 RX 3;2;1;0;1;56 9/29/2015 21:34:47 TX 3;255;4;0;3;82000100C3048F739927848FA689B7892C93A089B189 9/29/2015 21:34:48 RX 3;255;4;0;2;82000100C304 9/29/2015 21:34:48 TX 3;255;4;0;3;82000100C204A80FB11DA35ABF4F2C91848D90E00196 9/29/2015 21:34:48 RX 3;255;4;0;2;82000100C204 9/29/2015 21:34:48 TX 3;255;4;0;3;82000100C104692781110C9400000895FC01848DDF01 9/29/2015 21:34:48 RX 3;255;4;0;2;82000100C104 9/29/2015 21:34:48 RX 3;1;1;0;0;75.5 9/29/2015 21:34:48 RX 3;2;1;0;1;56 9/29/2015 21:34:48 TX 3;255;4;0;3;82000100C00497E2892B49F080E090E0892B29F00E94 9/29/2015 21:34:48 RX 3;255;4;0;2;82000100C004 9/29/2015 21:34:48 TX 3;255;4;0;3;82000100BF049F73928F90E008958FEF9FEF089589E6 9/29/2015 21:34:48 RX 3;255;4;0;2;82000100BF04 9/29/2015 21:34:48 TX 3;255;4;0;3;82000100BE04828DDF01A80FB11D5D968C91928D9F5F 9/29/2015 21:34:48 RX 3;255;4;0;2;82000100BE04 9/29/2015 21:34:48 TX 3;255;4;0;3;82000100BD048FEF9FEF0895FC01918D828D981761F0 9/29/2015 21:34:48 RX 3;255;4;0;2;82000100BD04 9/29/2015 21:34:49 RX 3;255;3;0;0;60 9/29/2015 21:34:49 RX 3;255;4;0;2;130 9/29/2015 21:34:49 RX 3;1;1;0;0;75.6 9/29/2015 21:34:49 RX 3;2;1;0;1;56 9/29/2015 21:34:49 RX 3;255;4;0;2;130 9/29/2015 21:34:49 RX 3;1;1;0;0;75.5 9/29/2015 21:34:49 RX 3;2;1;0;1;56 9/29/2015 21:34:50 RX 3;255;4;0;2;130 9/29/2015 21:34:50 RX 3;255;4;0;2;130 9/29/2015 21:34:50 RX 3;1;1;0;0;75.6 9/29/2015 21:34:50 RX 3;2;1;0;1;56 9/29/2015 21:34:51 RX 3;1;1;0;0;75.5 9/29/2015 21:34:51 RX 3;2;1;0;1;56 9/29/2015 21:34:51 RX 3;255;4;0;2;130 9/29/2015 21:34:51 RX 3;1;1;0;0;75.5 9/29/2015 21:34:51 RX 3;2;1;0;1;56 9/29/2015 21:34:58 RX 1;1;1;0;0;72.8 9/29/2015 21:34:58 RX 1;2;1;0;1;58 9/29/2015 21:35:55 RX 3;1;1;0;0;75.3 9/29/2015 21:35:55 RX 3;2;1;0;1;56 9/29/2015 21:36:02 RX 1;1;1;0;0;72.8 9/29/2015 21:36:02 RX 1;2;1;0;1;58 9/29/2015 21:37:06 RX 1;1;1;0;0;72.9 9/29/2015 21:37:06 RX 1;2;1;0;1;58 9/29/2015 21:38:03 RX 3;1;1;0;0;75.0 9/29/2015 21:38:03 RX 3;2;1;0;1;57 9/29/2015 21:38:10 RX 1;1;1;0;0;72.9 9/29/2015 21:38:10 RX 1;2;1;0;1;58 9/29/2015 21:38:58 RX 2;1;1;0;0;72.1 9/29/2015 21:39:07 RX 3;1;1;0;0;74.9 9/29/2015 21:39:07 RX 3;2;1;0;1;57 9/29/2015 21:39:14 RX 1;1;1;0;0;72.9 9/29/2015 21:39:14 RX 1;2;1;0;1;58 9/29/2015 21:40:03 RX 2;1;1;0;0;72.2 9/29/2015 21:40:03 RX 2;2;1;0;1;55 9/29/2015 21:40:11 RX 3;1;1;0;0;74.8 9/29/2015 21:40:11 RX 3;2;1;0;1;58 9/29/2015 21:40:17 RX 1;1;1;0;0;72.9 9/29/2015 21:40:17 RX 1;2;1;0;1;58 9/29/2015 21:41:15 RX 3;1;1;0;0;74.7 9/29/2015 21:41:15 RX 3;2;1;0;1;58 9/29/2015 21:41:21 RX 1;1;1;0;0;72.8 9/29/2015 21:41:21 RX 1;2;1;0;1;58 9/29/2015 21:42:18 RX 3;1;1;0;0;74.6 9/29/2015 21:42:19 RX 3;2;1;0;1;58 9/29/2015 21:42:25 RX 1;1;1;0;0;72.9 9/29/2015 21:42:25 RX 1;2;1;0;1;58 9/29/2015 21:43:22 RX 3;1;1;0;0;74.6 9/29/2015 21:43:22 RX 3;2;1;0;1;58 9/29/2015 21:43:29 RX 1;1;1;0;0;72.9 9/29/2015 21:43:29 RX 1;2;1;0;1;58 9/29/2015 21:44:26 RX 3;1;1;0;0;74.4 9/29/2015 21:44:26 RX 3;2;1;0;1;56 9/29/2015 21:44:33 RX 1;1;1;0;0;72.9 9/29/2015 21:44:33 RX 1;2;1;0;1;58 9/29/2015 21:45:23 RX 2;1;1;0;0;72.1 9/29/2015 21:45:23 RX 2;2;1;0;1;54 9/29/2015 21:45:30 RX 3;1;1;0;0;74.2 9/29/2015 21:45:30 RX 3;2;1;0;1;54 9/29/2015 21:45:37 RX 1;1;1;0;0;72.9 9/29/2015 21:45:37 RX 1;2;1;0;1;58 9/29/2015 21:46:27 RX 2;1;1;0;0;72.2 9/29/2015 21:46:28 RX 2;2;1;0;1;54 9/29/2015 21:46:41 RX 1;1;1;0;0;72.9 9/29/2015 21:46:41 RX 1;2;1;0;1;58 9/29/2015 21:47:38 RX 3;1;1;0;0;73.9 9/29/2015 21:47:38 RX 3;2;1;0;1;53 9/29/2015 21:47:45 RX 1;1;1;0;0;72.9 9/29/2015 21:47:45 RX 1;2;1;0;1;58 -
@Anticimex The latest MYSController release supports DualOptiboot, simply check the sensebender board option (node tree, right click). Besides that, MYSBootloader will not leave you with a "soft-bricked" node but rather with a slower OTA update time in the case of RF interferences. If the OTA update fails for whatever reasons (loss of connection, power issues, etc.) MYSBootloader will re-request the FW during the next power-up. Since many community members do not have an external flash option, a slightly longer down-time for the direct update should not cause any problems. Importantly, a faulty sketch with the DualOptiboot update (e.g. no regular gw.process() calls) will result in a real "soft-bricked" node. In the end, both OTA update options have their (dis)advantages, a hardware configuration w/o external flash will only work with offline OTA updates.
@tekka ok, cool! But I installed from the link in the top post last night and I could not find DualOptiboot mentioned anywhere. Is it only by picking a Sensbender board type that option appears? Are there other settings also affected by that? My board(s) are not Sensbenders per se although they should have the same hw features.
-
@tekka ok, cool! But I installed from the link in the top post last night and I could not find DualOptiboot mentioned anywhere. Is it only by picking a Sensbender board type that option appears? Are there other settings also affected by that? My board(s) are not Sensbenders per se although they should have the same hw features.