Skip to content
  • 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. Repeater when available
  • Getting Started
  • Controller
  • Build
  • Hardware
  • Download/API
  • Forum
  • Store

Repeater when available

Scheduled Pinned Locked Moved General Discussion
9 Posts 4 Posters 1.3k Views 3 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.
  • ร Offline
    ร Offline
    รอเรือ
    wrote on last edited by
    #1

    Hi there.

    I've got a coffee brewer that currently acts as a repeater. If I go for a vacation, I'll probably unplug my coffee brewer. Would that impact my MySensors network badly (more bad than if there were never a repeater defined), that is, should I better remove the repeater function if I have the need to turn it off 2 weeks per year?

    Thanks!

    mfalkviddM 1 Reply Last reply
    0
    • ร รอเรือ

      Hi there.

      I've got a coffee brewer that currently acts as a repeater. If I go for a vacation, I'll probably unplug my coffee brewer. Would that impact my MySensors network badly (more bad than if there were never a repeater defined), that is, should I better remove the repeater function if I have the need to turn it off 2 weeks per year?

      Thanks!

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

      If your other nodes can communicate without the repeater, I don't see any benefit from defining it as a repeater
      => do not use the coffee brewer as repeater.

      If your other nodes can't communicate without the repeater, unplugging it will cause the nodes to fail
      => you'll need another repeater anyway so do not use the coffee brewer as repeater.

      ร 1 Reply Last reply
      0
      • CrankyCoderC Offline
        CrankyCoderC Offline
        CrankyCoder
        wrote on last edited by
        #3

        mfalkvidd im sure you can confirm if i have my understanding correct here. If you have a repeater and it's gone, the nodes will eventually try to do a find par(ent) again right? at that point they may or may not be able to rejoin the network?

        Home Automation Tinkerer
        www.CrankyCoder.net

        Controller: HomeAssistant in Kubernetes
        Gateway: MQTTClientGateway
        MySensors: 2.3

        mfalkviddM 1 Reply Last reply
        0
        • mfalkviddM mfalkvidd

          If your other nodes can communicate without the repeater, I don't see any benefit from defining it as a repeater
          => do not use the coffee brewer as repeater.

          If your other nodes can't communicate without the repeater, unplugging it will cause the nodes to fail
          => you'll need another repeater anyway so do not use the coffee brewer as repeater.

          ร Offline
          ร Offline
          รอเรือ
          wrote on last edited by
          #4

          @mfalkvidd

          Thanks!

          1 Reply Last reply
          0
          • CrankyCoderC CrankyCoder

            mfalkvidd im sure you can confirm if i have my understanding correct here. If you have a repeater and it's gone, the nodes will eventually try to do a find par(ent) again right? at that point they may or may not be able to rejoin the network?

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

            @crankycoder said in Repeater when available:

            mfalkvidd im sure you can confirm if i have my understanding correct here. If you have a repeater and it's gone, the nodes will eventually try to do a find par(ent) again right? at that point they may or may not be able to rejoin the network?

            Correct. If they are able to join the network, the repeater was not needed. If they are not able to join the network, another repeater is needed.

            1 Reply Last reply
            0
            • alowhumA Offline
              alowhumA Offline
              alowhum
              Plugin Developer
              wrote on last edited by
              #6

              From my understanding: if your device does not run on batteries, always set it to work as a repeater. There are no downsides, and it will make your network more robust. If any device goes down for a bit, the sensors will route around it. Just like on the internet.

              ร 1 Reply Last reply
              0
              • alowhumA alowhum

                From my understanding: if your device does not run on batteries, always set it to work as a repeater. There are no downsides, and it will make your network more robust. If any device goes down for a bit, the sensors will route around it. Just like on the internet.

                ร Offline
                ร Offline
                รอเรือ
                wrote on last edited by
                #7

                @alowhum

                I believe it's very important that a repeater has a good communication with the gateway. I can imagine that a repeater with less than optimal communication with the gateway could make things worse.

                1 Reply Last reply
                0
                • alowhumA Offline
                  alowhumA Offline
                  alowhum
                  Plugin Developer
                  wrote on last edited by
                  #8

                  Of course. But if more devices are repeaters, chances are that they might bridge that bad connection with an extra hop in between. In a mesh network, the more help form that mesh, the better.

                  1 Reply Last reply
                  0
                  • CrankyCoderC Offline
                    CrankyCoderC Offline
                    CrankyCoder
                    wrote on last edited by
                    #9

                    Does adding ack to messages help trigger any failures if something can't deliver? ... well that didn't make much sense.

                    So lets say i have 2 repeaters on my network. i have a sensor that wakes up to report info. it normally goes to repeater1 -> gateway but repeater1 is acting up. Could you tell it to wait for an ack? after X amount of time with no ack would it trigger to find a new parent?

                    Home Automation Tinkerer
                    www.CrankyCoder.net

                    Controller: HomeAssistant in Kubernetes
                    Gateway: MQTTClientGateway
                    MySensors: 2.3

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


                    18

                    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
                    • OpenHardware.io
                    • Categories
                    • Recent
                    • Tags
                    • Popular