Image file for Domoticz running on a Pi with HGI80 drivers installed

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • bruce_miranda
    Automated Home Legend
    • Jul 2014
    • 2309

    #16
    both my windows and mac laptops won't download the file via Chrome and Wifi. MTU has been set manually on both to 1488 which is the value set on my BT HH5. Download works fine on the Synology NAS, which is hardwired into the network. So I really don't know what is going on. All the laptops stop downloading at 0.3GB for some reason.

    Comment

    • paulockenden
      Automated Home Legend
      • Apr 2015
      • 1719

      #17
      But like I said, the clients might need an MTU that's less than set on the router.

      The ping test is the only way to set it, reliably.

      P.

      Comment

      • bruce_miranda
        Automated Home Legend
        • Jul 2014
        • 2309

        #18
        It seems like the MTU settings on the client take a while to take effect. Setting my MTU manually on my mac allowed a download via Chrome and Safari. Previously both were failing when they got to 318MB. I also confirmed by going back to the default MTU of 1500 that the downloads stopped at exactly 318MB with the default setting.
        Now to working out why my windows PC still isn't taking the manual MTU setting. Maybe like everything windows, it needs a reboot for the values to take effect.

        Comment

        • bruce_miranda
          Automated Home Legend
          • Jul 2014
          • 2309

          #19
          i realise that I am at risk of turning this into a Networking forum. But I don't seem to have any joy downloading this image directly on to my windows PC.

          Code:
          Microsoft Windows [Version 10.0.14393]
          (c) 2016 Microsoft Corporation. All rights reserved.
          
          C:\WINDOWS\system32>netsh interface ipv4 show subinterfaces
          
             MTU  MediaSenseState   Bytes In  Bytes Out  Interface
          ------  ---------------  ---------  ---------  -------------
            1488                1    2585852     591111  Wireless Network Connection
            1500                5          0          0  Local Area Connection* 6
          4294967295                1          0      28196  Loopback Pseudo-Interface 1
            1500                5          0          0  Local Area Connection* 7
            1500                5          0          0  Bluetooth Network Connection
            1488                5          0          0  Local Area Connection
          
          
          C:\WINDOWS\system32>ping google.com -f -l 1488
          
          Pinging google.com [172.217.23.46] with 1488 bytes of data:
          Packet needs to be fragmented but DF set.
          Packet needs to be fragmented but DF set.
          Packet needs to be fragmented but DF set.
          Packet needs to be fragmented but DF set.
          
          Ping statistics for 172.217.23.46:
              Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
          
          C:\WINDOWS\system32>ping google.com -f -l 1460
          
          Pinging google.com [172.217.23.46] with 1460 bytes of data:
          Reply from 172.217.23.46: bytes=64 (sent 1460) time=11ms TTL=54
          Reply from 172.217.23.46: bytes=64 (sent 1460) time=11ms TTL=54
          Reply from 172.217.23.46: bytes=64 (sent 1460) time=12ms TTL=54
          Reply from 172.217.23.46: bytes=64 (sent 1460) time=11ms TTL=54
          
          Ping statistics for 172.217.23.46:
              Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
          Approximate round trip times in milli-seconds:
              Minimum = 11ms, Maximum = 12ms, Average = 11ms
          
          C:\WINDOWS\system32>ping google.com -f -l 1460
          
          Pinging google.com [216.58.208.174] with 1460 bytes of data:
          Reply from 216.58.208.174: bytes=64 (sent 1460) time=60ms TTL=54
          Reply from 216.58.208.174: bytes=64 (sent 1460) time=63ms TTL=54
          Reply from 216.58.208.174: bytes=64 (sent 1460) time=534ms TTL=54
          Reply from 216.58.208.174: bytes=64 (sent 1460) time=887ms TTL=54
          
          Ping statistics for 216.58.208.174:
              Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
          Approximate round trip times in milli-seconds:
              Minimum = 60ms, Maximum = 887ms, Average = 386ms
          
          C:\WINDOWS\system32>ping google.com -f -l 1461
          
          Pinging google.com [216.58.208.174] with 1461 bytes of data:
          Packet needs to be fragmented but DF set.
          Packet needs to be fragmented but DF set.
          Packet needs to be fragmented but DF set.
          Packet needs to be fragmented but DF set.
          
          Ping statistics for 216.58.208.174:
              Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
          This is why I set my MTU to 1488 which seems to work fine on the MBP.

          Comment

          • bruce_miranda
            Automated Home Legend
            • Jul 2014
            • 2309

            #20
            Did you expect this error on your build?

            Code:
            2017-01-12 21:20:15.112 Domoticz V3.6136 (c)2012-2016 GizMoCuz
            2017-01-12 21:20:15.112 Build Hash: 7affb87, Date: 2016-12-13 07:44:57
            2017-01-12 21:20:15.113 System: Raspberry Pi
            2017-01-12 21:20:15.113 Startup Path: /home/pi/dev-domoticz/
            2017-01-12 21:20:15.687 Error: PluginSystem: Failed load 'libpython3.5.so', Python probably not installed on system.
            2017-01-12 21:20:15.726 Active notification subsystems: http (1/12)
            2017-01-12 21:20:15.750 WebServer(HTTP) started on address: :: with port 8080
            2017-01-12 21:20:15.787 WebServer(SSL) started on address: :: with port 443
            2017-01-12 21:20:15.793 Proxymanager started.
            2017-01-12 21:20:15.798 Starting shared server on: :::6144
            2017-01-12 21:20:15.804 TCPServer: shared server started...
            2017-01-12 21:20:15.805 RxQueue: queue worker started...
            2017-01-12 21:20:17.806 EventSystem: reset all events...
            2017-01-12 21:20:17.811 EventSystem: reset all device statuses...
            2017-01-12 21:20:17.814 EventSystem: Started
            P.S. : Later found that it is a "feature" of the beta! https://www.domoticz.com/forum/viewtopic.php?t=14784
            Last edited by bruce_miranda; 12 January 2017, 10:37 PM.

            Comment

            • bruce_miranda
              Automated Home Legend
              • Jul 2014
              • 2309

              #21
              OK, so the latest beta seems to have solve that error too. Thanks to Paul I now have a version of Domoticz on a Raspberry pi that I can compile myself. Lets start having some fun. I need to figure out why two of my zones are show oscillating temperatures and I have a few unexplained temperature sensors and zone relays. Thanks again Paul.

              Code:
              2017-01-13 07:05:21.969 Domoticz V3.6334 (c)2012-2017 GizMoCuz
              2017-01-13 07:05:21.974 Build Hash: 2fd8bdc, Date: 2017-01-12 08:08:14
              2017-01-13 07:05:21.975 System: Raspberry Pi
              2017-01-13 07:05:21.975 Startup Path: /home/pi/dev-domoticz/
              2017-01-13 07:05:22.989 PluginSystem: Started, Python version '3.4.2'.
              2017-01-13 07:05:23.024 Active notification Subsystems: http (1/12)
              2017-01-13 07:05:23.033 WebServer(HTTP) started on address: :: with port 8080
              2017-01-13 07:05:23.060 WebServer(SSL) started on address: :: with port 443
              2017-01-13 07:05:23.065 Proxymanager started.
              2017-01-13 07:05:23.075 Starting shared server on: :::6144
              2017-01-13 07:05:23.077 RxQueue: queue worker started...
              2017-01-13 07:05:23.077 TCPServer: shared server started...
              2017-01-13 07:05:25.080 EventSystem: reset all events...
              2017-01-13 07:05:25.084 EventSystem: reset all device statuses...
              2017-01-13 07:05:25.087 EventSystem: Started
              2017-01-13 07:05:25.278 PluginSystem: Entering work loop.

              Comment

              • bruce_miranda
                Automated Home Legend
                • Jul 2014
                • 2309

                #22
                This image proved invaluable in debugging the problems I was seeing on my Evohome Domoticz set-up. Thanks again. Not there yet but pretty close. I have OpenTherm as well, which seems to be a largely unknown set-up to the Domoticz community. So that could well be causing the issues I am still experiencing.

                Comment

                • DanD
                  Automated Home Ninja
                  • Feb 2016
                  • 250

                  #23
                  I'm working on adding the Opentherm Gateway to the Domoticz Evohome code at the moment. Hopefully will have this sorted and added into the main Domoticz code in the next 3-4 weeks along with the fixes for a couple of bugs which Bruce's set-up also highlighted. The underfloor heating controller is another device that Domoticz doesn't currently handle correctly and I'll turn my attention to this once I've fixed the OT gateway.

                  It's a great idea having this Pi image available to make the installation pretty painless enabling the quick re-compilation of new fixes.

                  Thanks,
                  Dan

                  Comment

                  • bruce_miranda
                    Automated Home Legend
                    • Jul 2014
                    • 2309

                    #24
                    Oh cool so you have been able to see some OT commands within my setup. Excellent, let me know if you need to try something. I still have my HGI80 connected to my test system, so able to try anything you need, you know how to find me.

                    Comment

                    • paulockenden
                      Automated Home Legend
                      • Apr 2015
                      • 1719

                      #25
                      Probably won't be maintaining this now, as I've moved my Domoticz install from the Pi onto my NAS.

                      The compiles are soooooooo much faster!

                      P.

                      Comment

                      • bruce_miranda
                        Automated Home Legend
                        • Jul 2014
                        • 2309

                        #26
                        Which NAS Paul, I run this on a Synology myself but haven't built this from source on the NAS.

                        Comment

                        • paulockenden
                          Automated Home Legend
                          • Apr 2015
                          • 1719

                          #27
                          I'm using a Qnap.

                          I'm actually running it in a Ubuntu VM hosted on the NAS, rather than natively.

                          P.

                          Comment

                          • bruce_miranda
                            Automated Home Legend
                            • Jul 2014
                            • 2309

                            #28
                            I've got my Synology NAS chrooted running Debian. I too am planning to run my Domoticz from within the Debian environment. But the Synology package was so easy, I've not bothered.

                            Comment

                            • orange
                              Automated Home Guru
                              • Dec 2014
                              • 149

                              #29
                              Hi Paul

                              was thinking of moving it to my qnap - did you get the HGI80 drivers working ok too ?

                              Comment

                              • paulockenden
                                Automated Home Legend
                                • Apr 2015
                                • 1719

                                #30
                                That's one of the reasons I went for Ubuntu running under Virtualization Station, rather than using a native build on the NAS. The drivers are already there, I didn't have to do anything special.

                                P.

                                Comment

                                Working...
                                X