Windows GUI/Controller for MySensors
-
@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@mvader please upload the entire log file to check a few things. Also, if the node is next to (or too close) you will get RF interferences (this has been observed for the large antenna and max tx power).
EDIT: before I forget, also upload the log from the node - this will help to elicit the problem...
-
@mvader please upload the entire log file to check a few things. Also, if the node is next to (or too close) you will get RF interferences (this has been observed for the large antenna and max tx power).
EDIT: before I forget, also upload the log from the node - this will help to elicit the problem...
-
@tekka I think I might have found a bug (or perhaps this is considered a feature request):
The GW "version" (1.5) is not shown in the node info although it has sent a response to a version request as shown here:
Also, I am not sure what the "signing" field is intended for. Showing signing request status? It says "Unknown" for both my GW and my "secure" node. The node require signing and the gw is signing messages sent to it. Perhaps reserved for future functionality?
Still a great and very useful tool!
-
@mvader please upload the entire log file to check a few things. Also, if the node is next to (or too close) you will get RF interferences (this has been observed for the large antenna and max tx power).
EDIT: before I forget, also upload the log from the node - this will help to elicit the problem...
-
@tekka MYSBootloader is a great gift for us. With zero touch we can upgrade our firmware in to target board.
In some cases I want to recompile the source code for 8 MHz or lesser frequency or different boards. As this is not a Arduino code, I do not know how to recompile this software. I hope many people facing issue with recompiling. Could you please add some document how to recompile this source code under https://github.com/mysensors/Arduino/tree/master/MYSBootloader
Also can you post source code of MYSBootloader 1.5 version?
Thank you!
-
@tekka MYSBootloader is a great gift for us. With zero touch we can upgrade our firmware in to target board.
In some cases I want to recompile the source code for 8 MHz or lesser frequency or different boards. As this is not a Arduino code, I do not know how to recompile this software. I hope many people facing issue with recompiling. Could you please add some document how to recompile this source code under https://github.com/mysensors/Arduino/tree/master/MYSBootloader
Also can you post source code of MYSBootloader 1.5 version?
Thank you!
-
@mvader said:
i'm not sure how to grab the log from the node, please advise.
here is the MYSController debug log in full.
MySensors_20150930-203313.log -
@tekka I think I might have found a bug (or perhaps this is considered a feature request):
The GW "version" (1.5) is not shown in the node info although it has sent a response to a version request as shown here:
Also, I am not sure what the "signing" field is intended for. Showing signing request status? It says "Unknown" for both my GW and my "secure" node. The node require signing and the gw is signing messages sent to it. Perhaps reserved for future functionality?
Still a great and very useful tool!
-
@Anticimex No, not a bug and in the feature request list (I_VERSION handling). The signing field is updated once the node sends its signing preferences.
@tekka Ok, but then I believe I found a bug, because I have reset my node and it did send its presentation messages, but the field did not update. I'm not at home right now so I can't get you the logs but I will see if I can replicate the steps and send you later on.
-
@tekka Thanks for this great tool! I have been using it to monitor my nodes successfully for over a day. It's great. I do have a couple of questions.
Is there a way to see Variables that are sent from my controller (Vera)? I see the request sent from the node but not the response from Vera. Here is a screenshot. I would expect to see numbers sent back from Vera but maybe I'm missing something.
Is there a way to send a message to a node that hasn't checked in with the controller yet? I tried to manually type in a Node and Sensor but was unable to. I'd like to be able to send commands to nodes that haven't checked in if possible. For example, if the controller wasn't running for a while but I want to start it up to send a reboot command to a node that is no longer communicating. Or, if I have a relay node that doesn't check in often but I need to change the state.
Thanks again!!
My "How To" home automation video channel: https://www.youtube.com/channel/UCq_Evyh5PQALx4m4CQuxqkA
-
@tekka Thanks for this great tool! I have been using it to monitor my nodes successfully for over a day. It's great. I do have a couple of questions.
Is there a way to see Variables that are sent from my controller (Vera)? I see the request sent from the node but not the response from Vera. Here is a screenshot. I would expect to see numbers sent back from Vera but maybe I'm missing something.
Is there a way to send a message to a node that hasn't checked in with the controller yet? I tried to manually type in a Node and Sensor but was unable to. I'd like to be able to send commands to nodes that haven't checked in if possible. For example, if the controller wasn't running for a while but I want to start it up to send a reboot command to a node that is no longer communicating. Or, if I have a relay node that doesn't check in often but I need to change the state.
Thanks again!!
@petewill said:
Is there a way to see Variables that are sent from my controller (Vera)?
No, not to my knowledge - anybody?
Is there a way to send a message to a node that hasn't checked in with the controller yet? I tried to manually type in a Node and Sensor but was unable to.
You can manually add a node, but not a sensor: in the node tree view: right click | Add node | enter ID.
I will add the manual sensor adding to the feature requests.
-
@tekka Ok, but then I believe I found a bug, because I have reset my node and it did send its presentation messages, but the field did not update. I'm not at home right now so I can't get you the logs but I will see if I can replicate the steps and send you later on.
@Anticimex Just had a quick look at the library code: if signing is enabled (in the GW), the I_REQUEST_SIGNING message is not published. This field is only updated if signing is disabled (in the GW). However, MYSController will reply with a "signing not supported" message.
-
@Anticimex Just had a quick look at the library code: if signing is enabled (in the GW), the I_REQUEST_SIGNING message is not published. This field is only updated if signing is disabled (in the GW). However, MYSController will reply with a "signing not supported" message.
@tekka right. Signing exchange is currently only done in the rf protocol, not to the controller. So are there currently any ways for the controller to populate that field?
A future addition of a I_CONFIG message is under discussion where node properties such as signing and other things can be published to a controller, so I suppose that field in the ui is for future use then :)Do you feel secure today? No? Start requiring some signatures and feel better tomorrow ;)
-
@tekka right. Signing exchange is currently only done in the rf protocol, not to the controller. So are there currently any ways for the controller to populate that field?
A future addition of a I_CONFIG message is under discussion where node properties such as signing and other things can be published to a controller, so I suppose that field in the ui is for future use then :) -
@petewill said:
Is there a way to see Variables that are sent from my controller (Vera)?
No, not to my knowledge - anybody?
Is there a way to send a message to a node that hasn't checked in with the controller yet? I tried to manually type in a Node and Sensor but was unable to.
You can manually add a node, but not a sensor: in the node tree view: right click | Add node | enter ID.
I will add the manual sensor adding to the feature requests.
@tekka said:
I will add the manual sensor adding to the feature requests.
Great, thanks!
As for the variables, I don't think I was clear in what I was asking. The variable is a MySensors variable. It just doesn't look like it's picked up by the MYSController. I am doing a horrible job describing this but here is that I see in the log file:
50 10/02/15 7:30:16.689 luup_log:27: Arduino: Request: 1;2;2;0;24;Front Yard <0x308de680> 50 10/02/15 7:30:16.689 luup_log:27: Arduino: Requesting status for: 1;2 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Request status for Variable1 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Sending: 1;2;1;0;24;8 <0x308de680>I'm not seeing the '8' in the MYSController though. Hopefully that makes a little more sense.
Thanks again for all the hard work!
-
@mvader please upload the entire log file to check a few things. Also, if the node is next to (or too close) you will get RF interferences (this has been observed for the large antenna and max tx power).
EDIT: before I forget, also upload the log from the node - this will help to elicit the problem...
@tekka said:
@mvader please upload the entire log file to check a few things. Also, if the node is next to (or too close) you will get RF interferences (this has been observed for the large antenna and max tx power).
EDIT: before I forget, also upload the log from the node - this will help to elicit the problem...
I have to do more testing over the weekend, but i updated my gateway to 1.5, as my nodes where 1.5 but gate was 1.4, the 1st one i tried, worked without issue.
dont know if it was a fluke/lucky or updating to 1.5 on the gateway solved my issue.. i'll post more as i test more nodes -
@tekka said:
I will add the manual sensor adding to the feature requests.
Great, thanks!
As for the variables, I don't think I was clear in what I was asking. The variable is a MySensors variable. It just doesn't look like it's picked up by the MYSController. I am doing a horrible job describing this but here is that I see in the log file:
50 10/02/15 7:30:16.689 luup_log:27: Arduino: Request: 1;2;2;0;24;Front Yard <0x308de680> 50 10/02/15 7:30:16.689 luup_log:27: Arduino: Requesting status for: 1;2 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Request status for Variable1 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Sending: 1;2;1;0;24;8 <0x308de680>I'm not seeing the '8' in the MYSController though. Hopefully that makes a little more sense.
Thanks again for all the hard work!
@petewill said:
As for the variables, I don't think I was clear in what I was asking. The variable is a MySensors variable. It just doesn't look like it's picked up by the MYSController. I am doing a horrible job describing this but here is that I see in the log file:
50 10/02/15 7:30:16.689 luup_log:27: Arduino: Request: 1;2;2;0;24;Front Yard <0x308de680> 50 10/02/15 7:30:16.689 luup_log:27: Arduino: Requesting status for: 1;2 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Request status for Variable1 <0x308de680> 50 10/02/15 7:30:16.690 luup_log:27: Arduino: Sending: 1;2;1;0;24;8 <0x308de680>I'm not seeing the '8' in the MYSController though. Hopefully that makes a little more sense.
The controller receives messages from the GW but does not intercept messages sent from other controllers (due to the architecture). Similarly, messages sent with MYSController won't appear in Vera.
But this leads me to an interesting idea...let's see :)
-
looking for some help with OTA and a sensebender board.
if i manually reset the board, then it will take the OTA and that works fine.
however, that's the only way i can get it to work.
it doesn't respond to a reboot command (I assume this is because it's sleeping)
and even if i select the battery/sleeping option, when a transmission does come in, it doesn't reset or start an OTA.
the only way so far is to physically PF the device and then the OTA works.
what am i missing?
thanks!EDIT: so this does seems to work.. i spent all morning trying to come up with hack-y ways to get this to work.
using the default sensebender sketch the OTA wait time is set to 300 milli seconds. which is like .3 seconds.
i changed that 3000 (3 seconds) set the FW and waited for the next transmission..boom off it went (the OTA).
so for anyone running into this issue. try this solution.
I cant imagine 3 seconds vs .3 seconds is going to make a huge difference in battery life. -
Looking for help to interpret log data after an OTA update. I am just learning, and successfully OTA'ed a simple DS18B temperature sketch to a node using MysController. Now I am trying to OTA an DHT22 node (the example sketch in 1.5 version, no changes to it.) The firmware OTA seems to go fine, but the Pro Mini never seems to start. Below is the log, I have bolded the log entries I don't understand. As shown, the first bold section comes right after the OTA. The second 16 minutes later is because I pushed the reset button on the pro mini. Any help understanding the log entry is appreciated.
10/5/2015 7:04:01 RX 2;255;4;0;2;820001000200
10/5/2015 7:04:01 TX 2;255;4;0;3;8200010001000C94AE010C94AE010C94ED020C94AE01
10/5/2015 7:04:01 RX 2;255;4;0;2;820001000100
10/5/2015 7:04:01 TX 2;255;4;0;3;8200010000000C9486010C94D11A0C94FE1A0C94AE01
10/5/2015 7:04:01 RX 2;255;4;0;2;820001000000
10/5/2015 7:04:01 INFO BL version=257
10/5/2015 7:04:01 INFO Send FW info to node 2: type=82, version=1, blocks=0x0570, CRC=0x9AEC
10/5/2015 7:04:01 TX 2;0;4;0;1;820001007005EC9A
10/5/2015 7:04:01 RX 2;255;4;0;0;820001007005EC9A0101
10/5/2015 7:07:23 RX 24;1;1;0;0;60.5
10/5/2015 7:07:23 RX 24;2;1;0;1;59
10/5/2015 7:11:41 RX 24;1;1;0;0;60.5
10/5/2015 7:11:41 RX 24;2;1;0;1;59
10/5/2015 7:13:24 RX 23;0;1;0;1;55.7
10/5/2015 7:15:59 RX 24;1;1;0;0;60.5
10/5/2015 7:15:59 RX 24;2;1;0;1;59
10/5/2015 7:18:27 CHILD New child discovered, node id=23, child id=1
10/5/2015 7:18:27 RX 23;1;1;0;0;63.0
10/5/2015 7:18:27 RX 23;0;1;0;1;55.9
10/5/2015 7:20:14 INFO BL version=257
10/5/2015 7:20:14 INFO Send FW info to node 2: type=82, version=1, blocks=0x0570, CRC=0x9AEC
10/5/2015 7:20:14 TX 2;0;4;0;1;820001007005EC9A
10/5/2015 7:20:14 RX 2;255;4;0;0;820001007005EC9A0101
10/5/2015 7:21:50 TX 2;0;3;0;13;0
10/5/2015 7:23:32 RX 23;0;1;0;1;56.0
10/5/2015 7:24:26 RX 24;3;1;0;24;78
