Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Controllers
  3. Windows GUI/Controller for MySensors

Windows GUI/Controller for MySensors

Scheduled Pinned Locked Moved Controllers
myscontrollermysbootloader
486 Posts 101 Posters 348.2k Views 73 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G gonzalonal

    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.

    tekkaT Offline
    tekkaT Offline
    tekka
    Admin
    wrote on last edited by
    #214

    @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.

    G 1 Reply Last reply
    0
    • tekkaT tekka

      @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.

      G Offline
      G Offline
      gonzalonal
      wrote on last edited by
      #215

      @tekka Great Tekka, thanks again. I will try that.
      Regards.

      1 Reply Last reply
      0
      • Z Offline
        Z Offline
        zuru
        wrote on last edited by
        #216

        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.

        tekkaT 1 Reply Last reply
        0
        • Z zuru

          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.

          tekkaT Offline
          tekkaT Offline
          tekka
          Admin
          wrote on last edited by
          #217

          @zuru screenshots and/or log files are always good starting points ;)

          1 Reply Last reply
          0
          • Z Offline
            Z Offline
            zuru
            wrote on last edited by
            #218

            I found my problem.... so everything is fine now.
            Thanks
            Z.

            1 Reply Last reply
            0
            • AndurilA Offline
              AndurilA Offline
              Anduril
              wrote on last edited by
              #219

              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:

              1. redirecting the serial gateway to tcp port (tried ser2net and socat) to use ethernet option, but didn't got this to work.
              2. 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

              1 Reply Last reply
              0
              • A Offline
                A Offline
                allysmith
                wrote on last edited by
                #220

                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;FFFFFFFFFFFFFFFF0101

                Any pointers??

                tekkaT 1 Reply Last reply
                0
                • A allysmith

                  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;FFFFFFFFFFFFFFFF0101

                  Any pointers??

                  tekkaT Offline
                  tekkaT Offline
                  tekka
                  Admin
                  wrote on last edited by
                  #221

                  @allysmith please provide more information about the setup and upload the MYSController log for further troubleshooting

                  A 1 Reply Last reply
                  0
                  • E Offline
                    E Offline
                    ericvdb
                    wrote on last edited by
                    #222

                    @tekka What kind of SPI flash is needed for this OTA stuff? Can you provide part numbers?

                    tekkaT 1 Reply Last reply
                    0
                    • E ericvdb

                      @tekka What kind of SPI flash is needed for this OTA stuff? Can you provide part numbers?

                      tekkaT Offline
                      tekkaT Offline
                      tekka
                      Admin
                      wrote on last edited by
                      #223

                      @ericvdb MYSBootloader works without external flash, in contrary to the sensebender board and dualoptiboot bootloader

                      1 Reply Last reply
                      0
                      • tekkaT tekka

                        @allysmith please provide more information about the setup and upload the MYSController log for further troubleshooting

                        A Offline
                        A Offline
                        allysmith
                        wrote on last edited by
                        #224

                        @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.

                        MySensors_20150901-185920.log

                        tekkaT 1 Reply Last reply
                        0
                        • A allysmith

                          @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.

                          MySensors_20150901-185920.log

                          tekkaT Offline
                          tekkaT Offline
                          tekka
                          Admin
                          wrote on last edited by tekka
                          #225

                          @allysmith Try clearing EEPROM via MYSBootloader command, assign blink FW and upload the entire log again....

                          A 1 Reply Last reply
                          0
                          • tekkaT tekka

                            @allysmith Try clearing EEPROM via MYSBootloader command, assign blink FW and upload the entire log again....

                            A Offline
                            A Offline
                            allysmith
                            wrote on last edited by
                            #226

                            @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)

                            MySensors_20150902-055736.log

                            A 1 Reply Last reply
                            0
                            • A allysmith

                              @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)

                              MySensors_20150902-055736.log

                              A Offline
                              A Offline
                              allysmith
                              wrote on last edited by
                              #227

                              @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

                              1 Reply Last reply
                              0
                              • E Offline
                                E Offline
                                ericvdb
                                wrote on last edited by ericvdb
                                #228

                                WOOOHOOO, i got OTA working :dancers:
                                This is awesome guys

                                BTW, I guess OTA will not work if there's a repeater in the middle?

                                tekkaT 1 Reply Last reply
                                0
                                • E ericvdb

                                  WOOOHOOO, i got OTA working :dancers:
                                  This is awesome guys

                                  BTW, I guess OTA will not work if there's a repeater in the middle?

                                  tekkaT Offline
                                  tekkaT Offline
                                  tekka
                                  Admin
                                  wrote on last edited by
                                  #229

                                  @ericvdb said:

                                  WOOOHOOO, i got OTA working :dancers:
                                  This is awesome guys

                                  BTW, I guess OTA will not work if there's a repeater in the middle?

                                  congrats! :)
                                  OTA updates will also work with repeating nodes in between...

                                  1 Reply Last reply
                                  0
                                  • E Offline
                                    E Offline
                                    ericvdb
                                    wrote on last edited by
                                    #230

                                    @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.

                                    tekkaT 1 Reply Last reply
                                    0
                                    • E ericvdb

                                      @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.

                                      tekkaT Offline
                                      tekkaT Offline
                                      tekka
                                      Admin
                                      wrote on last edited by
                                      #231

                                      @ericvdb in theory possible, but AFAIK not supported by any controller...at the moment :)

                                      1 Reply Last reply
                                      0
                                      • E Offline
                                        E Offline
                                        ericvdb
                                        wrote on last edited by
                                        #232

                                        @tekka would you mind describing in detail the process (on the controller side) how the OTA works?

                                        1 Reply Last reply
                                        0
                                        • C Offline
                                          C Offline
                                          cdr
                                          wrote on last edited by
                                          #233

                                          Can somebody explain to me how the "Reassing ID" function works in MYScontroller? I haven't been able to change a ID remotely.

                                          ID's keep the same after reboots or power cycles, with or without the AutoID option on.

                                          SparkmanS tekkaT 2 Replies Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          11

                                          Online

                                          11.7k

                                          Users

                                          11.2k

                                          Topics

                                          113.0k

                                          Posts


                                          Copyright 2019 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • MySensors
                                          • OpenHardware.io
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular