Windows GUI/Controller for MySensors
-
Ok, thanks for that.
I finally found my problem.
The Node was sleeping most of the time. In spite of waking up twice per second, it was not enough to enter the uploading mode in the mysbootloader, so the node wasn't answering back to the gateway, nor MYSController.Now I have a questions
How can I OTA update/upload the firmware of a sleeping node? Should the gateway, or a relay node, send the upload message to the sleeping node as soon as it wakes up for transmiting its data?
I guess that in order to do that, the sleeping node should always wait for an aknowledge or some kind of message after waking up. I mean:Sleeping node wakes up
Then, it send its data to controller or to relay node
Afterwards, it wait for the controller to acknoledge the data just send, and to tell him (sleeping node) if there is a firmware upgrade for it.
If there's not, go back to sleep. If there is, go to OTA upgrade routine.Thanks, regards.
@gonzalonal
OTA updates for sleeping nodes with MYSBootloader:- add gw.wait(200) after the gw.send() (=node processes incoming messages for 200ms after sending a message)
- In MYSController, right-click on the node, select "Battery-powered / sleeping", then assign FW, confirm to reboot node (reboot request is now queued)
MYSController will now wait until it receives a message from that node, send the reboot command and hence, initiate OTA update.
-
@gonzalonal
OTA updates for sleeping nodes with MYSBootloader:- add gw.wait(200) after the gw.send() (=node processes incoming messages for 200ms after sending a message)
- In MYSController, right-click on the node, select "Battery-powered / sleeping", then assign FW, confirm to reboot node (reboot request is now queued)
MYSController will now wait until it receives a message from that node, send the reboot command and hence, initiate OTA update.
@tekka Great Tekka, thanks again. I will try that.
Regards. -
Hi,
I am trying to debug a mysensors temp. sensor using this tool (it is not detected by Domoticz). I connected the serial gateway to your program and when I turn the temperature sensor, I see that there is traffic back and forth between the gateway and the sensor. But my knowledge stops there.... any pointers? I can upload a screenshot of the log if it helps.
Thanks
Z. -
Hi,
I am trying to debug a mysensors temp. sensor using this tool (it is not detected by Domoticz). I connected the serial gateway to your program and when I turn the temperature sensor, I see that there is traffic back and forth between the gateway and the sensor. But my knowledge stops there.... any pointers? I can upload a screenshot of the log if it helps.
Thanks
Z. -
Hey guys,
maybe anyone can help. I tried to debug my sensors, but didn't got MYSController to talk with my gateway.
I have the NRF24L01+ directly connected to my rPi and can use the Gateway with Pimatic plugin. Then I tried different ways to give MYSController access:- redirecting the serial gateway to tcp port (tried ser2net and socat) to use ethernet option, but didn't got this to work.
- creating a new gateway using a spare nano with NRF24L01+ at my PC. This one worked, but the gateway didn't noticed my nodes. Are they somehow coded to only talk with the gateway they know? I waited serveral minuters (sensors reporting each minute), but didn't got any readings. I assume this programm has an auto update to show now nodes, right?
Hope someone can help, I would realy love the option to debug using my windows PC and in future upload new sketches OTA (with new bootloader).
Regards,
Anduril -
I have followed the procedure listed and that mentioned in post 77. Pro Mini 3.3v 8mhz Arduino.
I keep getting the following message in the debug window every few minutes. Have repeated the process in post 77 several times however get the same results.
[2015-09-01 18:09:17.276 Info] DEBUG Undefined firmware/type for node=2
[2015-09-01 18:09:17.323 Info] INFO BL version=257
[2015-09-01 18:09:17.354 Info] INFO Send FW info to node 2: type=A, version=1, blocks=0x0048, CRC=0xD098
[2015-09-01 18:09:17.386 Info] TX 2;0;4;0;1;0A000100480098D0
[2015-09-01 18:09:17.417 Info] RX 2;255;4;0;0;FFFFFFFFFFFFFFFF0101Any pointers??
-
I have followed the procedure listed and that mentioned in post 77. Pro Mini 3.3v 8mhz Arduino.
I keep getting the following message in the debug window every few minutes. Have repeated the process in post 77 several times however get the same results.
[2015-09-01 18:09:17.276 Info] DEBUG Undefined firmware/type for node=2
[2015-09-01 18:09:17.323 Info] INFO BL version=257
[2015-09-01 18:09:17.354 Info] INFO Send FW info to node 2: type=A, version=1, blocks=0x0048, CRC=0xD098
[2015-09-01 18:09:17.386 Info] TX 2;0;4;0;1;0A000100480098D0
[2015-09-01 18:09:17.417 Info] RX 2;255;4;0;0;FFFFFFFFFFFFFFFF0101Any pointers??
-
@allysmith please provide more information about the setup and upload the MYSController log for further troubleshooting
@tekka Thanks for getting back to me. This is my my first go at this bootloader. Hope I am not doing something daft!
I have Arduino IDE 1.6.5, MySensors 1.5, MYSBootloader 1.1, MYSController_0_1_2_282 running on Windows 8, USBasp to urn bootloader.
Arduino Pro Mini 3.3v 8mhz board. I am using the standard settings in your write up for the boards.txt
Log file hopefully attached.
-
@tekka Thanks for getting back to me. This is my my first go at this bootloader. Hope I am not doing something daft!
I have Arduino IDE 1.6.5, MySensors 1.5, MYSBootloader 1.1, MYSController_0_1_2_282 running on Windows 8, USBasp to urn bootloader.
Arduino Pro Mini 3.3v 8mhz board. I am using the standard settings in your write up for the boards.txt
Log file hopefully attached.
-
@allysmith Try clearing EEPROM via MYSBootloader command, assign blink FW and upload the entire log again....
-
@tekka As requested, cleared EEPROM via MYSBootloader, assigned blink FW.
Attached is the log.
Device shows up in the nodes window as Booting: 65535:65535 (BL1.1)@tekka Have made a change to how I was powering the NRF and now straight from battery.
Looks like it was a power issue. Sufficient for transmit from the node ut not for receiving the updates.
See attached log.
Now got a different issue when I tried to reassign the FW from link to Timereporter.
I think I am moving in the right direction now.
Thanks for your help so far.
Keep up this great work.Deug.txt
-
WOOOHOOO, i got OTA working :dancers:
This is awesome guysBTW, I guess OTA will not work if there's a repeater in the middle?
-
@tekka i guess OTA is not available when using a MQTT gateway?
I would like to switch my whole setup to MQTT, but don't wanna loose the super fantastic OTA feature.