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. Announcements
  3. 💬 Relay

💬 Relay

Scheduled Pinned Locked Moved Announcements
139 Posts 47 Posters 63.4k Views 45 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.
  • mfalkviddM mfalkvidd

    @slt1 sending current status won't generate an ack/echo message. So there should not be a need to handle the ack/echo flag. Hardware acks (which are enabled by default) do not trigger the receive function.

    The only case when an ack/echo message will be sent is if the sketch developer explicitly requests an ack/echo by setting the ack parameter in send() to true. If the sketch developer does that, they need to handle the ack/echo message inside the receive function, according to however they plan to handle the ack/echo message.

    My guess is that people set the ack flag to true without understanding what they are doing. I hope to make the documentation slightly less confusing by doing https://github.com/mysensors/MySensors/issues/1103

    S Offline
    S Offline
    slt1
    wrote on last edited by slt1
    #127

    @mfalkvidd Thanks - and yes - I did make the assumption that send with ack = true means do a hardware ack. I was unaware that a "software ack" also exists. I read your comment here : https://forum.mysensors.org/topic/3346/discussion-reliable-delivery/17 and what you mention there needs to be made loud and clear in the docs - perhaps some mention in both the message send function and message receive function,

    mfalkviddM 1 Reply Last reply
    0
    • S slt1

      @mfalkvidd Thanks - and yes - I did make the assumption that send with ack = true means do a hardware ack. I was unaware that a "software ack" also exists. I read your comment here : https://forum.mysensors.org/topic/3346/discussion-reliable-delivery/17 and what you mention there needs to be made loud and clear in the docs - perhaps some mention in both the message send function and message receive function,

      mfalkviddM Offline
      mfalkviddM Offline
      mfalkvidd
      Mod
      wrote on last edited by
      #128

      @slt1 I agree. Made the same mistake and it took me 40 hours of reading documentation and troubleshooting before I realized there was a difference between the two acks.

      1 Reply Last reply
      0
      • B Offline
        B Offline
        b0wi
        wrote on last edited by
        #129

        The script for 'Example with button' works perfectly! Thanks for that.
        Has someone a script for multiple Relays with buttons ready to use for me?
        I want to use it in my garden to switch the lights with physical buttons and also control them with Domoticz.

        1 Reply Last reply
        0
        • J Offline
          J Offline
          jimmy loyens
          wrote on last edited by jimmy loyens
          #130
          This post is deleted!
          1 Reply Last reply
          0
          • B Offline
            B Offline
            badmannen
            wrote on last edited by badmannen
            #131

            I am having this particular switch to be recognized in "Mozilla WEBTHINGS".

            IS there some issue with having a repeater node and sensors/switches etc attaches to it? .. it sends in the data as it should when I check with MYSController and I can switch it from there with sending "V_STATUS" messages. but no luck so far of getting the sensors appear in WEBTHINGS , every other sensor works fine.

            rPi 3 - UNO R3 - Mini - Nano - custom

            1 Reply Last reply
            0
            • S Offline
              S Offline
              Seawolf
              wrote on last edited by
              #132

              // Enable debug prints to serial monitor
              #define MY_DEBUG

              // Enables and select radio type (if attached)
              #define MY_RADIO_RF24
              //#define MY_RADIO_RFM69
              //#define MY_RADIO_RFM95

              #define MY_GATEWAY_ESP8266

              #define MY_WIFI_SSID "SSID"
              #define MY_WIFI_PASSWORD "PSW"

              // Enable UDP communication
              //#define MY_USE_UDP // If using UDP you need to set MY_CONTROLLER_IP_ADDRESS or MY_CONTROLLER_URL_ADDRESS below

              // Set the hostname for the WiFi Client. This is the hostname
              // it will pass to the DHCP server if not static.
              #define MY_HOSTNAME "ESP8266_GW"

              // Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
              //#define MY_IP_ADDRESS 192,168,0,0

              // If using static ip you can define Gateway and Subnet address as well
              //#define MY_IP_GATEWAY_ADDRESS 192,168,178,1
              //#define MY_IP_SUBNET_ADDRESS 255,255,255,0

              // The port to keep open on node server mode
              #define MY_PORT 5003

              // How many clients should be able to connect to this gateway (default 1)
              #define MY_GATEWAY_MAX_CLIENTS 2

              // Controller ip address. Enables client mode (default is "server" mode).
              // Also enable this if MY_USE_UDP is used and you want sensor data sent somewhere.
              //#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 68
              //#define MY_CONTROLLER_URL_ADDRESS "my.controller.org"

              // Enable inclusion mode
              //#define MY_INCLUSION_MODE_FEATURE

              // Enable Inclusion mode button on gateway
              //#define MY_INCLUSION_BUTTON_FEATURE
              // Set inclusion mode duration (in seconds)
              //#define MY_INCLUSION_MODE_DURATION 60
              // Digital pin used for inclusion mode button
              //#define MY_INCLUSION_MODE_BUTTON_PIN D1

              // Set blinking period
              //#define MY_DEFAULT_LED_BLINK_PERIOD 300

              // Flash leds on rx/tx/err
              // Led pins used if blinking feature is enabled above
              //#define MY_DEFAULT_ERR_LED_PIN 16 // Error led pin
              //#define MY_DEFAULT_RX_LED_PIN 16 // Receive led pin
              //#define MY_DEFAULT_TX_LED_PIN 16 // the PCB, on board LED
              #define LWIP_OPEN_SRC whatever
              #define TCP_MSS whatever
              #define LWIP_IPV6 whatever
              #define LWIP_FEATURES whatever

              #include <MySensors.h>
              #include <SPI.h>
              //DHT with autodetection

              #include <dhtnew.h>

              DHTNEW mySensor(5); // ESP 16 UNO 6

              uint32_t count = 0;
              uint32_t start, stop;

              uint32_t errors[10] = { 0,0, 0,0, 0,0, 0,0, 0,0 };

              //Domoticz
              #define CHILD_ID_HUM 2
              #define CHILD_ID_TEMP 3
              MyMessage msgHum(CHILD_ID_HUM, V_HUM);
              MyMessage msgTemp(CHILD_ID_TEMP, V_TEMP);

              void presentation()
              {
              // Send the sketch version information to the gateway
              sendSketchInfo("TemperatureAndHumidity", "1.1");

              // Register all sensors to gw (they will be created as child devices)
              present(CHILD_ID_HUM, S_HUM);
              present(CHILD_ID_TEMP, S_TEMP);

              }

              void setup()
              {
              Serial.begin(115200);
              Serial.println("DHT_endless.ino");
              Serial.print("LIBRARY VERSION: ");
              Serial.println(DHTNEW_LIB_VERSION);
              Serial.println();
              }

              void loop()
              {
              count++;
              // show counters for OK and errors.
              if (count % 50 == 0)
              {
              Serial.println();
              Serial.println("OK \tCRC \tTOA \tTOB \tTOC \tTOD \tSNR \tBS \tUNK");
              for (uint8_t i = 0; i < 9; i++)
              {
              Serial.print(errors[i]);
              Serial.print('\t');
              }
              Serial.println();
              Serial.println();
              }

              if (count % 10 == 0)
              {
              Serial.println();
              Serial.println("TIM\tCNT\tSTAT\tHUMI\tTEMP\tTIME\tTYPE");
              }
              Serial.print(millis());
              Serial.print("\t");
              Serial.print(count);
              Serial.print("\t");

              start = micros();
              int chk = mySensor.read();
              stop = micros();

              switch (chk)
              {
              case DHTLIB_OK:
              Serial.print("OK,\t");
              errors[0]++;
              break;
              case DHTLIB_ERROR_CHECKSUM:
              Serial.print("CRC,\t");
              errors[1]++;
              break;
              case DHTLIB_ERROR_TIMEOUT_A:
              Serial.print("TOA,\t");
              errors[2]++;
              break;
              case DHTLIB_ERROR_TIMEOUT_B:
              Serial.print("TOB,\t");
              errors[3]++;
              break;
              case DHTLIB_ERROR_TIMEOUT_C:
              Serial.print("TOC,\t");
              errors[4]++;
              break;
              case DHTLIB_ERROR_TIMEOUT_D:
              Serial.print("TOD,\t");
              errors[5]++;
              break;
              case DHTLIB_ERROR_SENSOR_NOT_READY:
              Serial.print("SNR,\t");
              errors[6]++;
              break;
              case DHTLIB_ERROR_BIT_SHIFT:
              Serial.print("BS,\t");
              errors[7]++;
              break;
              default:
              Serial.print("U");
              Serial.print(chk);
              Serial.print(",\t");
              errors[8]++;
              break;
              }
              // DISPLAY DATA
              #ifdef MY_DEBUG
              Serial.print(mySensor.getHumidity(), 1);
              Serial.print(",\t");
              Serial.print(mySensor.getTemperature(), 1);
              Serial.print(",\t");
              Serial.print(stop - start);
              Serial.print(",\t");
              Serial.println(mySensor.getType());
              #endif

              //send to gateway
              float humidity = mySensor.getHumidity();
              send(msgHum.set(humidity, 1));
              float temperature = mySensor.getTemperature();
              send(msgTemp.set(temperature, 1));

              delay(3000);
              }

              // -- END OF FILE --

              1 Reply Last reply
              0
              • S Offline
                S Offline
                Seawolf
                wrote on last edited by
                #133

                I was so happy to have finaly a fonctionnal sketch for my esp8266 gateway whith the DHT22 that i post directly my code.
                I hope that it will help some people.
                based on: https://github.com/RobTillaart/DHTNew/blob/master/examples/dhtnew_endless/dhtnew_endless.ino

                1 Reply Last reply
                0
                • joaoabsJ Offline
                  joaoabsJ Offline
                  joaoabs
                  wrote on last edited by
                  #134

                  Hi,
                  Trying to go deep on the API and come this this doubt: The second example (with button) the child seems to be declared as "S_LIGHT" and the receiving messages are "V_LIGHT", while the first example seems better suitable for a relay (child as "S_BINNARY" and requests as "V_STATUS").
                  I haven't found any "S_LIGHT" or "V_LIGHT" in the API, only "S_LIGHT_LEVEL" and "V_LIGHT_LEVEL". What is the most suitable type for a relay node with a local button?

                  skywatchS 1 Reply Last reply
                  0
                  • joaoabsJ joaoabs

                    Hi,
                    Trying to go deep on the API and come this this doubt: The second example (with button) the child seems to be declared as "S_LIGHT" and the receiving messages are "V_LIGHT", while the first example seems better suitable for a relay (child as "S_BINNARY" and requests as "V_STATUS").
                    I haven't found any "S_LIGHT" or "V_LIGHT" in the API, only "S_LIGHT_LEVEL" and "V_LIGHT_LEVEL". What is the most suitable type for a relay node with a local button?

                    skywatchS Offline
                    skywatchS Offline
                    skywatch
                    wrote on last edited by skywatch
                    #135

                    @joaoabs A realy usually has only 2 states, on and off. So I would use S-BINARY and V_STATUS every time.

                    A changeover realy also has 2 states so again I would go for binary and status.

                    Light_Level is more suited to getting light levels from a sensor or sending a light level to a dimmable light.

                    1 Reply Last reply
                    0
                    • T Offline
                      T Offline
                      TheoL
                      Contest Winner
                      wrote on last edited by
                      #136

                      Not sure if it ever has mentioned before, but the first example contains

                      // Enable and select radio type attached
                      #define MY_RADIO_RF24
                      

                      Which results in a compile error

                      MySensors.h:287:4: error: #error No forward link or gateway feature activated. This means nowhere to send messages! Pretty pointless.
                         #error No forward link or gateway feature activated. This means nowhere to send messages! Pretty pointless.
                      

                      It should be:

                      // Enable and select radio type attached
                      #define MY_RADIO_NRF24
                      

                      And then it compiles and works :)

                      mfalkviddM 1 Reply Last reply
                      0
                      • T TheoL

                        Not sure if it ever has mentioned before, but the first example contains

                        // Enable and select radio type attached
                        #define MY_RADIO_RF24
                        

                        Which results in a compile error

                        MySensors.h:287:4: error: #error No forward link or gateway feature activated. This means nowhere to send messages! Pretty pointless.
                           #error No forward link or gateway feature activated. This means nowhere to send messages! Pretty pointless.
                        

                        It should be:

                        // Enable and select radio type attached
                        #define MY_RADIO_NRF24
                        

                        And then it compiles and works :)

                        mfalkviddM Offline
                        mfalkviddM Offline
                        mfalkvidd
                        Mod
                        wrote on last edited by mfalkvidd
                        #137

                        @TheoL which version of MySensors are you using when compiling?

                        The change from NRF24 to RF24 was intentional.

                        https://github.com/mysensors/MySensorsArduinoExamples/commit/36bee0b7426cc3955d23b3f4918da64fd2cc49ad#diff-1252bb46b9b35d77138b7fd96c37e4d3efa629af89ac0d1c2302cde6cf755ea4

                        Documentation: https://www.mysensors.org/apidocs/group__RF24SettingGrpPub.html#gad9d7b3f6173e32fa96468e05b901acba

                        T 1 Reply Last reply
                        0
                        • mfalkviddM mfalkvidd

                          @TheoL which version of MySensors are you using when compiling?

                          The change from NRF24 to RF24 was intentional.

                          https://github.com/mysensors/MySensorsArduinoExamples/commit/36bee0b7426cc3955d23b3f4918da64fd2cc49ad#diff-1252bb46b9b35d77138b7fd96c37e4d3efa629af89ac0d1c2302cde6cf755ea4

                          Documentation: https://www.mysensors.org/apidocs/group__RF24SettingGrpPub.html#gad9d7b3f6173e32fa96468e05b901acba

                          T Offline
                          T Offline
                          TheoL
                          Contest Winner
                          wrote on last edited by
                          #138

                          @mfalkvidd I'm in an older version I discovered. Ran across more small differences.

                          skywatchS 1 Reply Last reply
                          1
                          • T TheoL

                            @mfalkvidd I'm in an older version I discovered. Ran across more small differences.

                            skywatchS Offline
                            skywatchS Offline
                            skywatch
                            wrote on last edited by
                            #139

                            @TheoL Sound like a good time to update to the latest version. it is the best yet and very stable.

                            1 Reply Last reply
                            0

                            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                            With your input, this post could be even better 💗

                            Register Login
                            Reply
                            • Reply as topic
                            Log in to reply
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes


                            70

                            Online

                            12.0k

                            Users

                            11.2k

                            Topics

                            113.4k

                            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