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. General Discussion
  3. Is there any complete "how to guide"?

Is there any complete "how to guide"?

Scheduled Pinned Locked Moved General Discussion
16 Posts 5 Posters 5.1k Views 2 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.
  • DwaltD Dwalt

    @Magnus-Pernemark You do not need a special bootloader to run MYSController. The MYSBootlader is to provide over-the-air programming for the nodes, you do not need to worry about that at this point. You do, however, need to hardcode a node ID into your arduino sketch as MYSController does not assign them (as Vera and other controllers generally do this when the sensor node is included into your network). After that, MYSController should see your node and you can read sensor data and send commands to the node. It isn't a permanent substitute for a controller but it is a useful diagnostic tool for troubleshooting your setup. Read through the thread on MYSController.

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

    @Dwalt said:

    You do, however, need to hardcode a node ID into your arduino sketch as MYSController does not assign them (as Vera and other controllers generally do this when the sensor node is included into your network).

    Nope, not true. MYSController does assign IDs - make sure to select "Auto ID" in the tool bar.

    1 Reply Last reply
    0
    • A Offline
      A Offline
      alfredocdmiranda
      wrote on last edited by
      #6

      Now, I am confuse, who does assign IDs? Controller or Gateway?

      1 Reply Last reply
      0
      • sundberg84S Offline
        sundberg84S Offline
        sundberg84
        Hardware Contributor
        wrote on last edited by sundberg84
        #7

        Never the gateway - this just pass along the msg to the controller.
        If you do not set a static node id, the controller assign.

        Controller: Proxmox VM - Home Assistant
        MySensors GW: Arduino Uno - W5100 Ethernet, Gw Shield Nrf24l01+ 2,4Ghz
        MySensors GW: Arduino Uno - Gw Shield RFM69, 433mhz
        RFLink GW - Arduino Mega + RFLink Shield, 433mhz

        1 Reply Last reply
        1
        • magpernM Offline
          magpernM Offline
          magpern
          wrote on last edited by
          #8

          Yet again thanks @Dwalt.
          I guess I'll have to wait for the Vera Edge to arrive. Can't make head or tail out of this.

          I don't get anything useful out of MYSController. I have tried to read about it, but I can't find anything but the forum thread about it. Everybody seams to already have it running and have other problems (and talk about MYSBootloader alot)

          MYSController connects to my gateway at 192.168.0.250:5003. It says
          0;0;3;0;14;Gateway startup completed

          when I power up my sensor, MYSController does some TX and RX (I also see thing happen in telnet client).
          2015-10-14 22:05:23 TX 255;255;3;0;4;1
          2015-10-14 22:05:23 RX 255;255;3;0;3;
          But that's about it. Nothing more. Nodes does not update, routing table is the same
          it just say this in the nodes list

          0 - Gateway
          Broadcast

          tekkaT 1 Reply Last reply
          0
          • magpernM magpern

            Yet again thanks @Dwalt.
            I guess I'll have to wait for the Vera Edge to arrive. Can't make head or tail out of this.

            I don't get anything useful out of MYSController. I have tried to read about it, but I can't find anything but the forum thread about it. Everybody seams to already have it running and have other problems (and talk about MYSBootloader alot)

            MYSController connects to my gateway at 192.168.0.250:5003. It says
            0;0;3;0;14;Gateway startup completed

            when I power up my sensor, MYSController does some TX and RX (I also see thing happen in telnet client).
            2015-10-14 22:05:23 TX 255;255;3;0;4;1
            2015-10-14 22:05:23 RX 255;255;3;0;3;
            But that's about it. Nothing more. Nodes does not update, routing table is the same
            it just say this in the nodes list

            0 - Gateway
            Broadcast

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

            @Magnus-Pernemark said:

            2015-10-14 22:05:23 TX 255;255;3;0;4;1
            2015-10-14 22:05:23 RX 255;255;3;0;3;

            That looks already good. The node is asking for an ID, and the controller assigns ID 1 (not chronological in the log). What sketch are you running?

            For further troubleshooting, please make sure "Logging" is enabled and upload the generated log file - that helps to understand what is going on.

            1 Reply Last reply
            0
            • sundberg84S Offline
              sundberg84S Offline
              sundberg84
              Hardware Contributor
              wrote on last edited by sundberg84
              #10

              @Magnus-Pernemark You can read about the serial api here: http://www.mysensors.org/download/serial_api_15
              255 = Node does not have an id
              3 = Internal
              0 = No ack
              ...

              damn... tecka was first :)

              Controller: Proxmox VM - Home Assistant
              MySensors GW: Arduino Uno - W5100 Ethernet, Gw Shield Nrf24l01+ 2,4Ghz
              MySensors GW: Arduino Uno - Gw Shield RFM69, 433mhz
              RFLink GW - Arduino Mega + RFLink Shield, 433mhz

              tekkaT 1 Reply Last reply
              0
              • sundberg84S sundberg84

                @Magnus-Pernemark You can read about the serial api here: http://www.mysensors.org/download/serial_api_15
                255 = Node does not have an id
                3 = Internal
                0 = No ack
                ...

                damn... tecka was first :)

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

                @sundberg84 sorry...lol :)

                1 Reply Last reply
                0
                • magpernM Offline
                  magpernM Offline
                  magpern
                  wrote on last edited by
                  #12

                  Hi @tekka. I just took a ESP8266 NodeMcu V0.9 and connected a NRF24L01+ radio to it. Uploaded sketch according to instructions found about this gateway.
                  Then I did the same thing with a Mini Pro, hooked up a NRF and uploaded the RelayActuator.
                  I didn't change any code, more then the LED pin on the gateway, SSID and password for WIFI.

                  Applyed power to gateway, started MYSController, applyed power to sensor.

                  And this is what I get

                  2015-10-14 22:30:13	STARTUP	Initialize message logging
                  2015-10-14 22:30:13	STARTUP	MYSController 0.1.2.282
                  2015-10-14 22:30:13	STARTUP	FPC 2.6.4 / Lazarus 1.4.2
                  2015-10-14 22:30:13	STARTUP	still under development :) tekka 2015
                  2015-10-14 22:30:13	STARTUP	Load INI file...
                  2015-10-14 22:30:13	STARTUP	INI version 0.1.2.282
                  2015-10-14 22:30:13	INFO	*** Logging START ***
                  2015-10-14 22:30:13	VERSION	MYSController 0.1.2.282
                  2015-10-14 22:30:13	STARTUP	INI file loaded
                  2015-10-14 22:30:13	STARTUP	Loading FW repository...
                  2015-10-14 22:30:13	REPO	FW "Blink" loaded. t=10, v=1, blocks=72, crc=0xD098
                  2015-10-14 22:30:13	REPO	FW "TimeReporter" loaded. t=20, v=1, blocks=840, crc=0x4AC5
                  2015-10-14 22:30:13	REPO	FW "Sensebender Micro" loaded. t=100, v=1, blocks=1344, crc=0x3482
                  2015-10-14 22:30:13	REPO	FW "Sensebender Blink" loaded. t=110, v=1, blocks=768, crc=0x1314
                  2015-10-14 22:30:13	REPO	FW repository loaded. Items=4
                  2015-10-14 22:30:13	STARTUP	Initialize message types
                  2015-10-14 22:30:13	NODE	New node discovered, node id=0
                  2015-10-14 22:30:13	NODE	New node discovered, node id=255
                  2015-10-14 22:30:17	INFO	Connected to 192.168.0.250:5003
                  2015-10-14 22:30:17	CHILD	New child discovered, node id=0, child id=0
                  2015-10-14 22:30:17	RX	0;0;3;0;14;Gateway startup complete.
                  2015-10-14 22:30:25	UPDATE	4295098650
                  2015-10-14 22:30:38	CHILD	New child discovered, node id=255, child id=internal
                  2015-10-14 22:30:38	TX	255;255;3;0;4;1
                  2015-10-14 22:30:38	RX	255;255;3;0;3;
                  2015-10-14 22:30:39	TX	255;255;3;0;4;1
                  2015-10-14 22:30:39	RX	255;255;3;0;3;
                  2015-10-14 22:30:41	TX	255;255;3;0;4;1
                  2015-10-14 22:30:42	RX	255;255;3;0;3;
                  2015-10-14 22:30:43	TX	255;255;3;0;4;1
                  2015-10-14 22:30:43	RX	255;255;3;0;3;
                  
                  
                  tekkaT 1 Reply Last reply
                  0
                  • magpernM magpern

                    Hi @tekka. I just took a ESP8266 NodeMcu V0.9 and connected a NRF24L01+ radio to it. Uploaded sketch according to instructions found about this gateway.
                    Then I did the same thing with a Mini Pro, hooked up a NRF and uploaded the RelayActuator.
                    I didn't change any code, more then the LED pin on the gateway, SSID and password for WIFI.

                    Applyed power to gateway, started MYSController, applyed power to sensor.

                    And this is what I get

                    2015-10-14 22:30:13	STARTUP	Initialize message logging
                    2015-10-14 22:30:13	STARTUP	MYSController 0.1.2.282
                    2015-10-14 22:30:13	STARTUP	FPC 2.6.4 / Lazarus 1.4.2
                    2015-10-14 22:30:13	STARTUP	still under development :) tekka 2015
                    2015-10-14 22:30:13	STARTUP	Load INI file...
                    2015-10-14 22:30:13	STARTUP	INI version 0.1.2.282
                    2015-10-14 22:30:13	INFO	*** Logging START ***
                    2015-10-14 22:30:13	VERSION	MYSController 0.1.2.282
                    2015-10-14 22:30:13	STARTUP	INI file loaded
                    2015-10-14 22:30:13	STARTUP	Loading FW repository...
                    2015-10-14 22:30:13	REPO	FW "Blink" loaded. t=10, v=1, blocks=72, crc=0xD098
                    2015-10-14 22:30:13	REPO	FW "TimeReporter" loaded. t=20, v=1, blocks=840, crc=0x4AC5
                    2015-10-14 22:30:13	REPO	FW "Sensebender Micro" loaded. t=100, v=1, blocks=1344, crc=0x3482
                    2015-10-14 22:30:13	REPO	FW "Sensebender Blink" loaded. t=110, v=1, blocks=768, crc=0x1314
                    2015-10-14 22:30:13	REPO	FW repository loaded. Items=4
                    2015-10-14 22:30:13	STARTUP	Initialize message types
                    2015-10-14 22:30:13	NODE	New node discovered, node id=0
                    2015-10-14 22:30:13	NODE	New node discovered, node id=255
                    2015-10-14 22:30:17	INFO	Connected to 192.168.0.250:5003
                    2015-10-14 22:30:17	CHILD	New child discovered, node id=0, child id=0
                    2015-10-14 22:30:17	RX	0;0;3;0;14;Gateway startup complete.
                    2015-10-14 22:30:25	UPDATE	4295098650
                    2015-10-14 22:30:38	CHILD	New child discovered, node id=255, child id=internal
                    2015-10-14 22:30:38	TX	255;255;3;0;4;1
                    2015-10-14 22:30:38	RX	255;255;3;0;3;
                    2015-10-14 22:30:39	TX	255;255;3;0;4;1
                    2015-10-14 22:30:39	RX	255;255;3;0;3;
                    2015-10-14 22:30:41	TX	255;255;3;0;4;1
                    2015-10-14 22:30:42	RX	255;255;3;0;3;
                    2015-10-14 22:30:43	TX	255;255;3;0;4;1
                    2015-10-14 22:30:43	RX	255;255;3;0;3;
                    
                    
                    tekkaT Offline
                    tekkaT Offline
                    tekka
                    Admin
                    wrote on last edited by tekka
                    #13

                    @Magnus-Pernemark looks like the node does not receive the ID reply - this has previously been observed: adding a larger capacitor or replacing the nRF often solved the issue.

                    1 Reply Last reply
                    0
                    • magpernM Offline
                      magpernM Offline
                      magpern
                      wrote on last edited by
                      #14

                      Thanks @tekka that did it. I didn't have a capacitor on the gateway. I added a 4.7uF and now the sensor pops up in MYSController. (The capacitor recommendation was not in the ESP8266 setup, hense lack of one)

                      Thank you so much. One less thing to loose sleep over.

                      tekkaT 1 Reply Last reply
                      0
                      • magpernM magpern

                        Thanks @tekka that did it. I didn't have a capacitor on the gateway. I added a 4.7uF and now the sensor pops up in MYSController. (The capacitor recommendation was not in the ESP8266 setup, hense lack of one)

                        Thank you so much. One less thing to loose sleep over.

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

                        @Magnus-Pernemark :) have fun

                        1 Reply Last reply
                        0
                        • A Offline
                          A Offline
                          alfredocdmiranda
                          wrote on last edited by
                          #16

                          @sundberg84 Thanks for your answer! Now makes a lot of sense and it works I am able to assign ids :)

                          1 Reply Last reply
                          0
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          21

                          Online

                          11.7k

                          Users

                          11.2k

                          Topics

                          113.1k

                          Posts


                          Copyright 2025 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