Announcement

Collapse
No announcement yet.

Lifx Plug-in Error

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

  • #16
    Just an update to my previous issue. Now I have unplugged the orbi satellite so I just have my ISP provided router then the orbi router (set as AP as before). No error messages now so I can only assume the lifx bulb(s) were changing which orbi access point they connected to, maybe only momentarily, but the plugin would then be unable to find the bulb.

    Occasionally all lifx bulbs will show as offline in homeseer and I lose my automation but I believe this is a lifx wifi dropout issue, only happened once in last few weeks. The random delays are back but as soon as I can route an ethernet cable to the loft and move the rpi away from the tv I predict they will disappear as before.

    Comment


    • #17
      Got massive cpu usage on the RPI since latest update, crashing the whole system daily

      Comment


      • #18
        I'm also getting these messages in my log file.
        HS3 ZEE S2 Edition 3.0.0.531 (Linux)
        UltraLighting3 version 3.0.7027.33300
        All LIFX bulbs are latest firmware

        All lights seems to work though I had to disable/enable UL3 after a reboot for the plugin to start up.
        5/1/2019 21:26 Warning The UltraLighting3 plug-in is no longer properly initialized. Flushing 1 commands from the command queue.
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException: The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) <0x71ce7170 + 0x00070> in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () <0x71ce76b8 + 0x0004b> in :0
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException: The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) <0x71ce7170 + 0x00070> in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () <0x71ce76b8 + 0x0004b> in :0
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException: The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) <0x71ce7170 + 0x00070> in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () <0x71ce76b8 + 0x0004b> in :0
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException: The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) <0x71ce7170 + 0x00070> in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () <0x71ce76b8 + 0x0004b> in :0
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException: The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) <0x71ce7170 + 0x00070> in :0 at HSPI_ULTRALIGHTING3.hspi_plugin.CloseUDPClient () <0x71ce7020 + 0x0003b> in :0
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException: The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) <0x71ce7170 + 0x00070> in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () <0x71ce76b8 + 0x0004b> in :0
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException: The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) <0x71ce7170 + 0x00070> in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () <0x71ce76b8 + 0x0004b> in :0
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException: The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) <0x71ce7170 + 0x00070> in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () <0x71ce76b8 + 0x0004b> in :0
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException: The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) <0x71ce7170 + 0x00070> in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () <0x71ce76b8 + 0x0004b> in :0
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException: The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) <0x71ce7170 + 0x00070> in :0 at HSPI_ULTRALIGHTING3.hspi_plugin.CloseUDPClient () <0x71ce7020 + 0x0003b> in :0
        5/1/2019 21:26 1 Error System.Net.Sockets.SocketException

        Comment


        • #19
          I am getting the same error over and over again
          Aug-03 12:19:01 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
          Aug-03 12:19:01 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
          Aug-03 12:19:01 PM 1 Error System.Net.Sockets.SocketException
          Aug-03 12:19:01 PM 1 Error System.Net.Sockets.SocketException

          Comment


          • #20
            Got those errors too, with 100% CPU utilization. Turning off the UltraLighting3 plugin removes the utilization, and removes these errors, but also disables my lighting (obviously). UltraJones?? Help please??
            Aug-06 8:32:39 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x00018] in <048f685b456c4326be453e3cc3faae14>:0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
            Aug-06 8:32:39 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x00018] in <048f685b456c4326be453e3cc3faae14>:0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
            Aug-06 8:32:39 PM 1 Error System.Net.Sockets.SocketException
            Aug-06 8:32:39 PM 1 Error System.Net.Sockets.SocketException
            Aug-06 8:32:09 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x00018] in <048f685b456c4326be453e3cc3faae14>:0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
            Aug-06 8:32:09 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x00018] in <048f685b456c4326be453e3cc3faae14>:0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
            Aug-06 8:32:09 PM 1 Error System.Net.Sockets.SocketException
            Aug-06 8:32:09 PM 1 Error System.Net.Sockets.SocketException
            Aug-06 8:31:39 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x00018] in <048f685b456c4326be453e3cc3faae14>:0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
            Aug-06 8:31:39 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x00018] in <048f685b456c4326be453e3cc3faae14>:0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
            Aug-06 8:31:39 PM 1 Error System.Net.Sockets.SocketException
            Aug-06 8:31:39 PM 1 Error System.Net.Sockets.SocketException
            Aug-06 8:31:09 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x00018] in <048f685b456c4326be453e3cc3faae14>:0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
            Aug-06 8:31:09 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x00018] in <048f685b456c4326be453e3cc3faae14>:0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
            Aug-06 8:31:09 PM 1 Error System.Net.Sockets.SocketException
            Aug-06 8:31:09 PM 1 Error System.Net.Sockets.SocketException
            Aug-06 8:30:39 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x00018] in <048f685b456c4326be453e3cc3faae14>:0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
            Aug-06 8:30:39 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x00018] in <048f685b456c4326be453e3cc3faae14>:0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
            Aug-06 8:30:39 PM 1 Error System.Net.Sockets.SocketException
            Aug-06 8:30:39 PM 1 Error System.Net.Sockets.SocketException
            Aug-06 8:30:11 PM Warning File does not exist: /opt/HomeSeer/html/hspi_ultramon3/css/jquery.dataTables.min.css
            Aug-06 8:30:09 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x00018] in <048f685b456c4326be453e3cc3faae14>:0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient ()

            Comment


            • #21
              Completely reset my system starting from scratch. Getting the same errors with fresh setup.
              Aug-13 6:41:28 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
              Aug-13 6:41:28 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
              Aug-13 6:41:28 PM 1 Error System.Net.Sockets.SocketException
              Aug-13 6:41:28 PM 1 Error System.Net.Sockets.SocketException
              Aug-13 6:40:58 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
              Aug-13 6:40:58 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
              Aug-13 6:40:58 PM 1 Error System.Net.Sockets.SocketException
              Aug-13 6:40:58 PM 1 Error System.Net.Sockets.SocketException
              Aug-13 6:40:28 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
              Aug-13 6:40:28 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0

              Comment


              • #22
                Originally posted by Steaktastic87 View Post
                Got massive cpu usage on the RPI since latest update, crashing the whole system daily
                Wow, you have over 10 versions of the plug-in running... can you please restart your system, then report back to see if that's solved the issue?
                Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

                Comment


                • #23
                  Originally posted by JakeStallman View Post
                  Completely reset my system starting from scratch. Getting the same errors with fresh setup.
                  Aug-13 6:41:28 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
                  Aug-13 6:41:28 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
                  Aug-13 6:41:28 PM 1 Error System.Net.Sockets.SocketException
                  Aug-13 6:41:28 PM 1 Error System.Net.Sockets.SocketException
                  Aug-13 6:40:58 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
                  Aug-13 6:40:58 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
                  Aug-13 6:40:58 PM 1 Error System.Net.Sockets.SocketException
                  Aug-13 6:40:58 PM 1 Error System.Net.Sockets.SocketException
                  Aug-13 6:40:28 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
                  Aug-13 6:40:28 PM 1 Error System.Net.Sockets.SocketException (0x80004005): The socket is not connected at System.Net.Sockets.Socket.Shutdown (System.Net.Sockets.SocketShutdown how) [0x0001b] in :0 at HSPI_ULTRALIGHTING3.hspi_lifx_light.CloseUDPClient () [0x00013] in :0
                  Are you running a HomeSeer HomeTroller Zee S2?
                  Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

                  Comment


                  • #24
                    Originally posted by Ultrajones View Post

                    Are you running a HomeSeer HomeTroller Zee S2?
                    Yes sir I am

                    Comment


                    • #25
                      Hello UltraJones!!! Care to help us someday?

                      Comment


                      • #26
                        Originally posted by tinnov View Post
                        Hello UltraJones!!! Care to help us someday?
                        Yes, I have been working on this every day this week. The most recent update is now available in the HomeSeer updater. Please download, install, then *reboot* your HomeSeer system. Please post any issues you notice using the new build.

                        Regards,
                        Ultrajones
                        Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

                        Comment


                        • #27
                          Hey Ultrajones, everything seems to be working very well. Thanks for the update.. really appreciate it!

                          Comment


                          • #28
                            Hey Jake, is this still working for you? I gave up trying after no response from ultra so haven't used homeseer for nearly a year

                            Comment


                            • #29
                              I'm still having the issue where my bulbs show offline. However, I am still able to turn them on/off/dim with events and within the HomeSeer interface.

                              Comment


                              • #30
                                Ok thanks, i had the same problem with them showing offline, i just disabled/enabled the plugin and they would work for a while. I was having the same issue as tinnov with high cpu usage and eventually crashing my raspberry pi.

                                Comment

                                Working...
                                X