Announcement

Collapse
No announcement yet.

Sonoff Basic Wifi Garage MQTT configuration

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Sonoff Basic Wifi Garage MQTT configuration

    Currently testing running installed mcsTasmota.bin Program Version 5.9.11 and downgrade mcsMQTT to version 3.4.1.0. (also tried current release 3.4.2.0).


    The SonOff basic is not connecting to HS3 Mosquitto (running mcsMQTT).


    SonOff basic Console logs are showing:

    IP 171 is the Homeseer 3 server.

    00:00:00 Project sonoff Garage Door (Topic GarageDoor, Fallback GarageDoor, GroupTopic sonoffs) Version 5.9.11
    00:00:00 WIF: Connecting to AP1 xyz in mode 11N as GarageDoor-7596...
    00:00:04 WIF: Connected
    00:00:04 DNS: Initialized
    00:00:04 HTP: Web server active on GarageDoor-7596.local with IP address 192.168.244.220
    00:00:04 UPP: Multicast (re)joined
    00:00:06 MQT: Attempting connection...
    00:00:06 MQT: Connect failed to 192.168.244.171:1883, rc -2. Retry in 10 sec
    00:00:06 UPP: Multicast (re)joined
    05:55:24 MQT: Attempting connection...
    05:55:24 MQT: Connect failed to 192.168.244.171:1883, rc -2. Retry in 10 sec
    05:55:24 UPP: Multicast (re)joined

    Pointed the SonOff to the Node Red RPi box and see it working fine.

    00:00:04 HTP: Web server active on GarageDoor-7596.local with IP address 192.168.244.220
    00:00:04 UPP: Multicast (re)joined
    00:00:06 MQT: Attempting connection...
    00:00:06 MQT: Connected
    00:00:06 MQT: GarageDoor/LWT = Online (retained)
    00:00:06 MQT: GarageDoor/cmnd/POWER =
    00:00:06 MQT: GarageDoor/INFO1 = {"Module":"Sonoff Basic", "Version":"5.9.11", "FallbackTopic":"GarageDoor", "GroupTopic":"sonoffs"}
    00:00:06 MQT: GarageDoor/INFO2 = {"WebServerMode":"Admin", "Hostname":"GarageDoor-7596", "IPAddress":"192.168.244.220"}
    00:00:06 MQT: GarageDoor/INFO3 = {"RestartReason":"Software/System restart"}
    00:00:06 UPP: Multicast (re)joined
    05:53:15 MQT: GarageDoor/POWER = Off
    05:53:22 MQT: GarageDoor/STATE = {"Time":"2018-06-14T05:53:22", "Uptime":0 0, "Vcc":3.496, "Wifi":{"AP":1, "SSId":"xyz", "RSSI":100, "IPAddress":"192.168.244.220", "APMac":"00:00:00:00:00:00"}}
    05:53:22 MQT: GarageDoor/Door = INDETERMINATE

    I have read about the "Multicast (re)joined" error relating to maybe the WAP channel. But also see "RSSI":100.

    Tried this morning with SonOff Tasmota current build / Mosquitto stuff...

    [ATTACH]69341[/ATTACH]

    Same results as above. Talks to Node Red running Mosquitto and not to HS3 running mcsMQTT. Will post shortly.

    Have I misconfigured the SonOff Wifi basic module?
    Last edited by Pete; June 14th, 2018, 07:52 AM.
    - Pete

    Auto mator
    Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
    Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

  • #2
    Same problem here with 4 Ch Pro. Also my device went off line after changing config and had to reboot it.


    Originally posted by Pete View Post
    Currently testing running installed mcsTasmota.bin Program Version 5.9.11 and downgrade mcsMQTT to version 3.4.1.0. (also tried current release 3.4.2.0).


    The SonOff basic is not connecting to HS3 Mosquitto (running mcsMQTT).


    SonOff basic Console logs are showing:

    IP 171 is the Homeseer 3 server.

    00:00:00 Project sonoff Garage Door (Topic GarageDoor, Fallback GarageDoor, GroupTopic sonoffs) Version 5.9.11
    00:00:00 WIF: Connecting to AP1 xyz in mode 11N as GarageDoor-7596...
    00:00:04 WIF: Connected
    00:00:04 DNS: Initialized
    00:00:04 HTP: Web server active on GarageDoor-7596.local with IP address 192.168.244.220
    00:00:04 UPP: Multicast (re)joined
    00:00:06 MQT: Attempting connection...
    00:00:06 MQT: Connect failed to 192.168.244.171:1883, rc -2. Retry in 10 sec
    00:00:06 UPP: Multicast (re)joined
    05:55:24 MQT: Attempting connection...
    05:55:24 MQT: Connect failed to 192.168.244.171:1883, rc -2. Retry in 10 sec
    05:55:24 UPP: Multicast (re)joined

    Pointed the SonOff to the Node Red RPi box and see it working fine.

    00:00:04 HTP: Web server active on GarageDoor-7596.local with IP address 192.168.244.220
    00:00:04 UPP: Multicast (re)joined
    00:00:06 MQT: Attempting connection...
    00:00:06 MQT: Connected
    00:00:06 MQT: GarageDoor/LWT = Online (retained)
    00:00:06 MQT: GarageDoor/cmnd/POWER =
    00:00:06 MQT: GarageDoor/INFO1 = {"Module":"Sonoff Basic", "Version":"5.9.11", "FallbackTopic":"GarageDoor", "GroupTopic":"sonoffs"}
    00:00:06 MQT: GarageDoor/INFO2 = {"WebServerMode":"Admin", "Hostname":"GarageDoor-7596", "IPAddress":"192.168.244.220"}
    00:00:06 MQT: GarageDoor/INFO3 = {"RestartReason":"Software/System restart"}
    00:00:06 UPP: Multicast (re)joined
    05:53:15 MQT: GarageDoor/POWER = Off
    05:53:22 MQT: GarageDoor/STATE = {"Time":"2018-06-14T05:53:22", "Uptime":0 0, "Vcc":3.496, "Wifi":{"AP":1, "SSId":"xyz", "RSSI":100, "IPAddress":"192.168.244.220", "APMac":"00:00:00:00:00:00"}}
    05:53:22 MQT: GarageDoor/Door = INDETERMINATE

    I have read about the "Multicast (re)joined" error relating to maybe the WAP channel. But also see "RSSI":100.

    Tried this morning with SonOff Tasmota current build / Mosquitto stuff...

    [ATTACH]69341[/ATTACH]

    Same results as above. Talks to Node Red running Mosquitto and not to HS3 running mcsMQTT. Will post shortly.

    Have I misconfigured the SonOff Wifi basic module?
    Don

    Comment


    • #3
      OK so installing SonOff TasMota 5.14 on my SonOff #1 device worked and I can see it now in the mcsMQTT plugin. Left the SonOff #2 with the mcs.bin V.11 on it and it is not seen by the plugin.

      Issues with the build that I see is that the navigation of the GUI is slow and a couple of times now the SonOff goes off line (blinking light) where I have to unplug it wait a bit then plug it back in.
      Very slow ping times from HS3...using same WAP.

      HS3Pro:~# ping 192.168.244.220
      PING 192.168.244.220 (192.168.244.220) 56(84) bytes of data.
      64 bytes from 192.168.244.220: icmp_seq=1 ttl=128 time=449 ms

      compared to the mcsTasmota Sonoff #2

      HS3Pro:~# ping 192.168.244.221
      PING 192.168.244.221 (192.168.244.221) 56(84) bytes of data.
      64 bytes from 192.168.244.221: icmp_seq=1 ttl=128 time=58.3 ms



      [ATTACH]69343[/ATTACH]

      Quick Recap:

      1 - SonOff #1 with TasMota 5.14 works and mcsMQTT sees it fine and I see it working in the gui sonoff console.
      2 - SonOff #2 with V.11 of the mcsTasmota.bin file does not connect to Homeseer mcsMQTT plugin and it shows errors connecting in the gui sonoff console.
      Last edited by Pete; June 14th, 2018, 10:54 AM.
      - Pete

      Auto mator
      Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
      Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

      X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

      Comment


      • #4
        Note the signal strength of the SonOff to the AP when I tested it connected to the Node Red box.

        "AP":1, "SSId":"xyz", "RSSI":100, "IPAddress":"192.168.244.220"

        and on Sonoff #2 ...

        AP1 SSId (RSSI) xyz (100%)
        Hostname sonoff-3523
        IP Address 192.168.244.221
        Gateway 192.168.244.129
        Subnet Mask 255.255.255.128
        DNS Server 192.168.244.129

        such that this is not an issue relating to the WAP access.

        Been doing continous pings in my laptop terminal window when navigating the GUI and I see the pings slow way down and just disconnect.
        - Pete

        Auto mator
        Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
        Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

        X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

        Comment


        • #5
          What I can do is start with 5.14 Tasmota and add the irrigation logic and see if that improves anything.

          Comment


          • #6
            Thank you Michael.

            Check out the build first as it seems to run really slow on the SonOff Wifi Basic and it does drop off the wireless AP after running a few minutes which your current build does not do.

            Is your Sonoff to HS3 MQTT working fine on your SonOff boxes?
            - Pete

            Auto mator
            Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
            Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

            X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

            Comment


            • #7
              My four units that I have in production are all very stable and inter-operate with mcsMQTT. These were all with mcsTasmota versions prior to .11.

              I have .11 installed on a pair or 4Ch and a Basic. There was not too many hours on them after the development testing. When I do power them up they have no problem connecting to AP and browser access seems reasonable to me with response similar to what I see with HS server.

              I have the irrigation logic implemented on top of 5.14. It is going through testing now.

              but have struggled with load/startup at times. I am using an original revision for 4CH Pro for this testing. 5.14 has blown through the 512K limit for straight OTA loading. Now a minimal image needs to be first loaded and then the desired one.

              I have the serial monitor connected. I can see that often after the minimal image load that the Wifi is trying to connect to null SSID rather than my normal one. I need to use serial to reflash. After that it has the SSID retained from before. It is a bad situation where the minimal loaded successfully, but then it was not able to connect via WiFi.

              I do not know why the minimal image is giving me problems or perhaps it is the install of the image OTA that leaves it in a bad state. I will try some combinations to try to isolate. I notice that I have minimal from May and a slightly smaller one is available now.

              I am using one original and one R2 4CH Pro. Located next to each other about 30' from AP and a couple wall. RSSI for both are in the 80's.

              Comment


              • #8
                So now testing here with SonOff #2 basic Wifi Module with mcsTasmota.bin v11.

                It is configured as documented in the documentation except it is GarageDoor2.

                Console is showing:

                01:52:17 MQT: Connect failed to 192.168.244.171:1883, rc -2. Retry in 10 sec
                01:52:17 UPP: Multicast (re)joined
                01:52:28 MQT: Attempting connection...
                01:52:28 MQT: Connect failed to 192.168.244.171:1883, rc -2. Retry in 10 sec
                01:52:28 UPP: Multicast (re)joined
                01:52:39 MQT: Attempting connection...
                01:52:39 MQT: Connect failed to 192.168.244.171:1883, rc -2. Retry in 10 sec
                01:52:39 UPP: Multicast (re)joined
                01:52:50 MQT: Attempting connection...
                01:52:50 MQT: Connect failed to 192.168.244.171:1883, rc -2. Retry in 10 sec
                01:52:50 UPP: Multicast (re)joined

                IP 171 is Homeseer server.

                So if I point it to my Node Red with OWFS / MQTT IP 175 I see the MQTT connection working fine.

                00:00:00 Project sonoff Sonoff-2 (Topic GarageDoor2, Fallback GarageDoor2, GroupTopic sonoffs) Version 5.9.11
                00:00:00 WIF: Connecting to AP1 ICS-0 in mode 11N as GarageDoor2-3523...
                00:00:04 WIF: Connected
                00:00:04 DNS: Initialized
                00:00:04 HTP: Web server active on GarageDoor2-3523.local with IP address 192.168.244.221
                00:00:04 UPP: Multicast (re)joined
                00:00:06 MQT: Attempting connection...
                00:00:06 MQT: Connected
                00:00:06 MQT: GarageDoor2/LWT = Online (retained)
                00:00:06 MQT: GarageDoor2/cmnd/POWER =
                00:00:06 MQT: GarageDoor2/INFO1 = {"Module":"Sonoff Basic", "Version":"5.9.11", "FallbackTopic":"GarageDoor2", "GroupTopic":"sonoffs"}
                00:00:06 MQT: GarageDoor2/INFO2 = {"WebServerMode":"Admin", "Hostname":"GarageDoor2-3523", "IPAddress":"192.168.244.221"}
                00:00:06 MQT: GarageDoor2/INFO3 = {"RestartReason":"Software/System restart"}
                00:00:06 UPP: Multicast (re)joined
                00:00:07 MQT: GarageDoor2/POWER = Off
                01:57:34 MQT: GarageDoor2/STATE = {"Time":"2018-06-15T01:57:34", "Uptime":0 0, "Vcc":3.519, "Wifi":{"AP":1, "SSId":"ICS-0", "RSSI":100, "IPAddress":"192.168.244.221", "APMac":"00:00:00:4D:E1:B7"}}
                01:57:34 MQT: GarageDoor2/Door = INDETERMINATE

                Now if I go to Homeseer Associations I see the SonOff #2 fine.

                [ATTACH]69345[/ATTACH]

                Reading also about the deep sleep the SonOff can go to if not chit chatting MQTT all of the time.

                I am confused about this.

                Why is it that when I point the MQTT set up on the SonOff2 to HS3 it goes off line (console) and when I point it to an RPi running Mosquitto it goes back on line and is seen by Homeseer?
                Last edited by Pete; June 14th, 2018, 08:37 PM.
                - Pete

                Auto mator
                Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
                Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

                X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                Comment


                • #9
                  Redid Sonos Basic Wifi #1.

                  Using serial JTAG uploaded mcsTasmota.bin version .12.

                  Boots up to blinking light and never connects to AP. Tried powering off and on a few times and couldn't get it to connect to AP - always a blinking light.

                  Using serial JTAG uploaded mcsTasmota.bin version .11

                  Configured MQTT in SonOff #1 as SonOff #2 connected to Node Red IP 175. Seeing SonOff 1 devices now in the Association tab.

                  00:00:00 Project sonoff Sonoff-1 (Topic GarageDoor1, Fallback GarageDoor1, GroupTopic sonoffs) Version 5.9.11
                  00:00:00 WIF: Connecting to AP1 ICS-0 in mode 11N as GarageDoor1-7596...
                  00:00:04 WIF: Connected
                  00:00:04 DNS: Initialized
                  00:00:04 HTP: Web server active on GarageDoor1-7596.local with IP address 192.168.244.220
                  00:00:04 UPP: Multicast (re)joined
                  00:00:06 MQT: Attempting connection...
                  00:00:06 MQT: Connected
                  00:00:06 MQT: GarageDoor1/LWT = Online (retained)
                  00:00:06 MQT: GarageDoor1/cmnd/POWER =
                  00:00:06 MQT: GarageDoor1/INFO1 = {"Module":"Sonoff Basic", "Version":"5.9.11", "FallbackTopic":"GarageDoor1", "GroupTopic":"sonoffs"}
                  00:00:06 MQT: GarageDoor1/INFO2 = {"WebServerMode":"Admin", "Hostname":"GarageDoor1-7596", "IPAddress":"192.168.244.220"}
                  00:00:06 MQT: GarageDoor1/INFO3 = {"RestartReason":"Power on"}
                  00:00:06 UPP: Multicast (re)joined
                  00:00:07 MQT: GarageDoor1/POWER = Off
                  04:06:24 MQT: GarageDoor1/STATE = {"Time":"2018-06-15T04:06:24", "Uptime":0 0, "Vcc":3.505, "Wifi":{"AP":1, "SSId":"ICS-0", "RSSI":100, "IPAddress":"192.168.244.220", "APMac":"00:00:00:4D:E1:B7"}}
                  04:06:24 MQT: GarageDoor1/Door = INDETERMINATE
                  04:11:24 MQT: GarageDoor1/STATE = {"Time":"2018-06-15T04:11:24", "Uptime":0 0, "Vcc":3.499, "Wifi":{"AP":1, "SSId":"ICS-0", "RSSI":100, "IPAddress":"192.168.244.220", "APMac":"00:00:00:4D:E1:B7"}}
                  04:11:24 MQT: GarageDoor1/Door = INDETERMINATE

                  Still do not understand if I point the MQTT to Homeseer 3 with IP 171 it will not connect.

                  04:15:15 MQT: Connect failed to 192.168.244.171:1883, rc -2. Retry in 10 sec
                  04:15:15 UPP: Multicast (re)joined

                  Also noticed now that both are talking Mosquitto response times of the GUI are fast.
                  - Pete

                  Auto mator
                  Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
                  Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

                  X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                  Comment


                  • #10
                    Been mulling a garage door opener for years - never had the guts to do it. Always afraid of a power bump or some glitch popping a door open.

                    In the past I have wired an open switch in series so the button to open/close is only actuated when the door is fully open.

                    So security aside you all feel confident there wont be an issue that pops the door open without you know?

                    Thanks


                    ~Bill

                    Comment


                    • #11
                      Yeah here use Sentrol switches which have NC / NO connections. Kind of overdoing it for a garage door with two on a door (top and bottom).

                      [ATTACH]69348[/ATTACH]

                      Back in the 1990's while automating did have a glitch which closed the garage door while my wife was on a conference call in her car while running. I also wired pieces of the switch in series that prevented the GDO from opening the door at the time.

                      That said today it is wired to the OmniPro 2 system and recently upgraded GDO to a myQ series door and would never connect this to the cloud or internet or wireless although might tinker with it.

                      I did have issues with the upgrade relating to my HomeLink buttons in the automobiles.

                      The SonOff stuff is hardware tinkering and most likely will not be utilized for opening or closing the door and related to getting familiar with Michael's endeavors.
                      Last edited by Pete; June 15th, 2018, 08:22 AM.
                      - Pete

                      Auto mator
                      Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
                      Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

                      X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                      Comment


                      • #12
                        Relating to testing I do see some sort of glitch with mcsTasmota version .12. It starts fine then just tries to connect to the AP over and over again. I see this in the serial connection.

                        So at this time settled on mcsTasmota version .11

                        The other issue is relating to not connecting to mcsMQTT. The error is very common with the SonOff devices.

                        01:52:17 MQT: Connect failed to 192.168.244.171:1883, rc -2. Retry in 10 sec
                        01:52:17 UPP: Multicast (re)joined
                        01:52:28 MQT: Attempting connection...
                        01:52:28 MQT: Connect failed to 192.168.244.171:1883, rc -2. Retry in 10 sec
                        01:52:28 UPP: Multicast (re)joined


                        Running Homeseer 3 here on a Pine64 2Gb computer with Ubuntu 16.04 64 bit server and on an Intel iSeries 3 with Ubuntu 16.04 64 bit server.

                        I can get it to work by pointing the two SonOff devices to my Node Red running on an RPi2 for the OWFS / 1-wire stuff.

                        Stuff I have read about so far is:

                        1 - weak AP signal - here getting 100%
                        2 - sleepy SonOff - MQTT out keeps it alive and falling to a deep state sleep.
                        3 - firewall issues - this is all internal
                        4 - telemetry issues - * thinking maybe this is my issue?
                        5 - tested most current Tasmota.bin file and seeing the same disconnecting issue with it as the mcsTasmota.bin version .12.

                        All written I am fixing my issue mickey mouse wise at this time.

                        I am currently only testing using the JTAG port to upload the bin files and not doing OTA at this time.

                        I have both of the SonOff devices configured with DHCP reservation on the PFSense firewall. I have them configured with ARP off at this time.

                        This also might have to do with concurrently having the two Node Red boxes talking to the plugin.

                        These two boxes messages are not published as they are only 1-Wire OWFS sensors.

                        On the network doing Mosquitto at this time are:

                        1 - RPi Node Red doing OWFS / MQTT number 1 with multiple temperature / humidity sensors in the basement
                        2 - RPi Node Red doing OWFS / MQTT number 2 with multiple temperature / humidity sensors and a HB Lightning counter in the attic
                        3 - SonOff Wifi Basic - two of these in test mode MQTT working but not pointed to the plugin.

                        Plan to add SonOff Pro 4's and Mosquitto running on my test micro router providing mostly status using probably python.

                        I have read that Mosquitto runs great in OpenWRT. (have a few test objects for this stuff).
                        Last edited by Pete; June 15th, 2018, 10:03 AM.
                        - Pete

                        Auto mator
                        Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
                        Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

                        X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                        Comment


                        • #13
                          @Michael...

                          ...posting again as same console messages are there for the two SonOff Pro Wifi devices (using mcsTasmota bin version 11) that I configured for Don except that he is running Homeseer 3 in windows and using low voltage to power the devices.

                          - plugin version 3.4.2.0
                          - mcsTasmota.bin version 11

                          After MQTT configuration SonOff console is showing:

                          01:52:17 MQT: Connect failed to 192.168.244.171:1883, rc -2. Retry in 10 sec
                          01:52:17 UPP: Multicast (re)joined
                          01:52:28 MQT: Attempting connection...
                          01:52:28 MQT: Connect failed to 192.168.244.171:1883, rc -2. Retry in 10 sec
                          01:52:28 UPP: Multicast (re)joined

                          and upgrading to mcsTasmota version 12 the SonOff never connects to the WAP.

                          Here downgraded to an earlier version of the mcsMQTT plugin from last month and really didn't get much of a chance to test as it upgraded itself with out any interaction by me.

                          I have seen this twice now with V.435 and updated updater.
                          - Pete

                          Auto mator
                          Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
                          Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

                          X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                          Comment


                          • #14
                            As Pete said...

                            PHP Code:
                            20:45:29 UPPMulticast (re)joined
                            20
                            :45:39 MQTAttempting connection...
                            20:45:44 MQTConnect failed to 192.168.42.7:1883rc -2. Retry in 10 sec
                            20
                            :45:45 UPPMulticast (re)joined
                            20
                            :45:55 MQTAttempting connection...
                            20:46:00 MQTConnect failed to 192.168.42.7:1883rc -2. Retry in 10 sec
                            20
                            :46:01 UPPMulticast (re)joined
                            20
                            :46:11 MQTAttempting connection...
                            20:46:16 MQTConnect failed to 192.168.42.7:1883rc -2. Retry in 10 sec
                            20
                            :46:17 UPPMulticast (re)joined
                            20
                            :46:27 MQTAttempting connection...
                            20:46:32 MQTConnect failed to 192.168.42.7:1883rc -2. Retry in 10 sec
                            20
                            :46:33 UPPMulticast (re)joined
                            20
                            :46:39 RSLtele/sonoff5/STATE = {"Time":"2018-06-15T20:46:39""Uptime":0 0"Vcc":3.523"POWER1":"OFF""POWER2":"OFF""POWER3":"OFF""POWER4":"OFF""Wifi":{"AP":2"SSId":"hug2g549874""RSSI":100"IPAddress":"192.168.42.147""APMac":"00:80:AE:D2:40:95"}}
                            20:46:43 MQTAttempting connection...
                            20:46:48 MQTConnect failed to 192.168.42.7:1883rc -2. Retry in 10 sec
                            20
                            :46:49 UPPMulticast (re)joined
                            20
                            :46:59 MQTAttempting connection...
                            20:47:04 MQTConnect failed to 192.168.42.7:1883rc -2. Retry in 10 sec
                            20
                            :47:05 UPPMulticast (re)joined 
                            Don

                            Comment


                            • #15
                              I can see you did connect once to HS3...

                              20:46:39 RSL: tele/sonoff5/STATE = {"Time":"2018-06-15T20:46:39", "Uptime":0 0, "Vcc":3.523, "POWER1":"OFF", "POWER2":"OFF", "POWER3":"OFF", "POWER4":"OFF", "Wifi"......


                              to get rid of the tele/sonoff5 thing configure your MQTT like this:

                              [ATTACH]69355[/ATTACH]

                              Once connecting your associations will look like this:

                              [ATTACH]69356[/ATTACH]
                              - Pete

                              Auto mator
                              Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
                              Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

                              X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                              Comment

                              Working...
                              X