Domoticz Evohome HGI80 multi-controller update released

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • paulockenden
    Automated Home Legend
    • Apr 2015
    • 1719

    #16
    Update: Left it running overnight. It's found Hot Water, but no zones.

    Comment

    • bruce_miranda
      Automated Home Legend
      • Jul 2014
      • 2307

      #17
      Did you enable the Debug in the EvohomeBase.cpp before you compiled?

      Comment

      • paulockenden
        Automated Home Legend
        • Apr 2015
        • 1719

        #18
        I didn't - just wanted to leave everything vanilla at first.

        But I guess it makes sense to do so now.

        Based on my tests last time I'm sure it'll work if I switch to release and then switch back to beta afterwards.

        Comment

        • paulockenden
          Automated Home Legend
          • Apr 2015
          • 1719

          #19
          OK, evoraw.log looks like this:

          Code:
          2017-06-07 08:31:45 evohome: Controller ID specified (0x68736172)
          2017-06-07 08:31:48 095 RQ --- 18:002859 28:221554 --:------ 2E04 001 FF (.)
          2017-06-07 08:31:49 095 RQ --- 18:002859 28:221554 --:------ 1260 001 00 (.)
          2017-06-07 08:31:50 095 RQ --- 18:002859 28:221554 --:------ 1F41 001 00 (.)
          2017-06-07 08:31:51 095 RQ --- 18:002859 28:221554 --:------ 30C9 001 00 (.)
          2017-06-07 08:31:52 095 RQ --- 18:002859 28:221554 --:------ 2349 001 00 (.)
          2017-06-07 08:31:53 095 RQ --- 18:002859 28:221554 --:------ 000A 001 00 (.)
          2017-06-07 08:31:54 095 RQ --- 18:002859 28:221554 --:------ 0004 002 0000 (..)
          2017-06-07 08:31:55 095 RQ --- 18:002859 28:221554 --:------ 0418 003 000000 (...)
          2017-06-07 08:32:23 047  I --- 07:016581 --:------ 07:016581 1260 003 0015F9 (...)
          2017-06-07 08:33:23 047  I --- 07:016581 --:------ 07:016581 1260 003 0015F9 (...)
          2017-06-07 08:33:36 045  I --- 01:076916 --:------ 01:076916 1F09 003 FF063B (..;)
          2017-06-07 08:33:36 evohome: unknown command 1f09
          2017-06-07 08:33:36 045  I --- 01:076916 --:------ 01:076916 2309 030 0005780105780205780305780405780505780604EB0705780805780904B0 (..x..x..x..x..x..x.....x..x...)
          2017-06-07 08:33:36 045  I --- 01:076916 --:------ 01:076916 30C9 030 0007B801087902079A03078A0407F10507D006081607076F08079F0907BD (.....y.................o......)
          2017-06-07 08:33:44 080  I --- 04:197187 --:------ 04:197187 30C9 003 00072B (..+)
          2017-06-07 08:34:08 075  I --- 34:050968 --:------ 34:050968 30C9 003 0007BA (...)
          2017-06-07 08:34:23 048  I --- 07:016581 --:------ 07:016581 1260 003 0015E6 (...)
          2017-06-07 08:34:32 086  I --- 04:197183 --:------ 01:076916 3150 002 0000 (..)
          2017-06-07 08:34:33 061  I --- 04:117152 --:------ 01:076916 3150 002 0000 (..)
          2017-06-07 08:35:23 046  I --- 07:016581 --:------ 07:016581 1260 003 0015F9 (...)
          2017-06-07 08:35:57 095  I --- 03:248043 --:------ 03:248043 1060 003 00FF01 (...)
          2017-06-07 08:35:59 095  I --- 03:248043 --:------ 03:248043 0009 003 0000FF (...)
          2017-06-07 08:35:59 evohome: unknown command 0009
          2017-06-07 08:36:00 095  I --- 03:248043 --:------ 03:248043 1100 008 00180404007FFF01 (........)
          2017-06-07 08:36:00 evohome: unknown command 1100
          2017-06-07 08:36:16 045  I --- 01:076916 --:------ 01:076916 1F09 003 FF063B (..;)
          2017-06-07 08:36:16 evohome: unknown command 1f09
          2017-06-07 08:36:16 045  I --- 01:076916 --:------ 01:076916 2309 030 0005780105780205780305780405780505780604EB0705780805780904B0 (..x..x..x..x..x..x.....x..x...)
          2017-06-07 08:36:16 045  I --- 01:076916 --:------ 01:076916 30C9 030 0007BA01087902079A03078A0407F10507D006081607076F08079F0907BD (.....y.................o......)
          2017-06-07 08:36:23 047  I --- 07:016581 --:------ 07:016581 1260 003 0015F9 (...)
          2017-06-07 08:37:20 045  I --- 01:076916 --:------ 01:076916 0008 002 FA00 (..)
          2017-06-07 08:37:23 047  I --- 07:016581 --:------ 07:016581 1260 003 0015E6 (...)
          2017-06-07 08:37:30 045  I --- 13:095360 --:------ 13:095360 3EF0 003 0000FF (...)
          2017-06-07 08:37:30 evohome: ACTUATOR_STATE: ID:0x357480 (13:95360) DevNo 0x00: 0
          2017-06-07 08:37:30 052  I --- 13:079313 --:------ 13:079313 3EF0 003 0000FF (...)
          2017-06-07 08:37:30 evohome: ACTUATOR_STATE: ID:0x3535d1 (13:79313) DevNo 0x00: 0
          2017-06-07 08:37:35 045  I --- 01:076916 --:------ 01:076916 3B00 002 FCC8 (..)
          2017-06-07 08:37:35 evohome: ACTUATOR_CHECK: DevNo 0xfc All: 200
          2017-06-07 08:37:36 045  I --- 13:095360 --:------ 13:095360 3EF0 003 0000FF (...)
          2017-06-07 08:37:36 evohome: ACTUATOR_STATE: ID:0x357480 (13:95360) DevNo 0x00: 0
          2017-06-07 08:37:36 053  I --- 13:079313 --:------ 13:079313 3EF0 003 0000FF (...)
          2017-06-07 08:37:36 evohome: ACTUATOR_STATE: ID:0x3535d1 (13:79313) DevNo 0x00: 0
          2017-06-07 08:38:12 095  I --- --:------ --:------ 12:169545 0008 002 0000 (..)
          2017-06-07 08:38:12 evohome: invalid message structure - possible corrupt message
          2017-06-07 08:38:13 095  I --- --:------ --:------ 12:169545 0008 002 0000 (..)
          2017-06-07 08:38:13 evohome: invalid message structure - possible corrupt message
          2017-06-07 08:38:14 095  I --- --:------ --:------ 12:169545 0008 002 0000 (..)
          2017-06-07 08:38:14 evohome: invalid message structure - possible corrupt message
          2017-06-07 08:38:18 045  I --- 04:117422 --:------ 01:076916 2309 003 050578 (..x)
          2017-06-07 08:38:20 053  I --- 04:117424 --:------ 01:076916 3150 002 0400 (..)
          2017-06-07 08:38:23 048  I --- 07:016581 --:------ 07:016581 1260 003 0015E6 (...)
          2017-06-07 08:38:49 081  I --- 34:050968 --:------ 34:050968 30C9 003 0007BA (...)
          2017-06-07 08:38:55 045  I --- 01:076916 --:------ 01:076916 1F09 003 FF063B (..;)
          2017-06-07 08:38:55 evohome: unknown command 1f09
          2017-06-07 08:38:55 045  I --- 01:076916 --:------ 01:076916 2309 030 0005780105780205780305780405780505780604EB0705780805780904B0 (..x..x..x..x..x..x.....x..x...)
          2017-06-07 08:38:55 045  I --- 01:076916 --:------ 01:076916 30C9 030 0007BA01087902079A03078A0407F10507D006081607076F08079F0907BD (.....y.................o......)
          2017-06-07 08:38:59 045  I --- 04:195661 --:------ 01:076916 12B0 003 030000 (...)
          2017-06-07 08:39:02 045  I --- 04:195661 --:------ 01:076916 12B0 003 030000 (...)
          2017-06-07 08:39:23 049  I --- 07:016581 --:------ 07:016581 1260 003 0015E6 (...)
          2017-06-07 08:39:27 061  I --- 04:195657 --:------ 01:076916 3150 002 0800 (..)
          2017-06-07 08:39:42 086  I --- 13:080021 --:------ 13:080021 3EF0 003 0000FF (...)
          2017-06-07 08:39:42 evohome: ACTUATOR_STATE: ID:0x353895 (13:80021) DevNo 0x00: 0
          No devices seen.

          P.

          Comment

          • bruce_miranda
            Automated Home Legend
            • Jul 2014
            • 2307

            #20
            Any chance of a screen shot of your controller screen showing the Device ID?

            Comment

            • paulockenden
              Automated Home Legend
              • Apr 2015
              • 1719

              #21
              On the hardware screen the Controller ID field is blank (if that's what you mean?)

              Or if you mean the ID shown on the controller itself, that's 052C74 (01:076916)

              Like I said above, with the Stable build I'm sure everything is fine. This only happens with a brand new install of Beta.

              P.
              Last edited by paulockenden; 7 June 2017, 09:36 AM.

              Comment

              • bruce_miranda
                Automated Home Legend
                • Jul 2014
                • 2307

                #22
                For some reason your installation seems to be using a controller ID of 68736172 even though you said you haven't specified one. Hence there are no devices showing up. Try something and add your Controllers Device ID and see if the first message changes to show the code using that. I think the devices will start appearing the moment that ID is specified. There appears to be a bug when none is supplied.

                Comment

                • paulockenden
                  Automated Home Legend
                  • Apr 2015
                  • 1719

                  #23
                  Interesting - when I entered / saved the ID I got "Serial Worker stopped..." and Domoticz locked up.

                  But you're right - on re-launch that seemed to fix it.

                  But strange how it still managed to pick up my DHW, even when it had assumed the wrong ID.
                  Last edited by paulockenden; 7 June 2017, 10:14 AM.

                  Comment

                  • bruce_miranda
                    Automated Home Legend
                    • Jul 2014
                    • 2307

                    #24
                    I find that Domoticz doesn't respond well to in-flight changes to the Hardware parameters. What I tend to do is Disable the Hardware device, make the changes, Update Hardware and then reenable the hardware.

                    Comment

                    • paulockenden
                      Automated Home Legend
                      • Apr 2015
                      • 1719

                      #25
                      Just looked at Domoticz for the first time in ages. Either my HGI80 has died or a soon-to-be-released firmware version that I've been testing has changed things enough that HGI80 snooping longer works (which, I suppose, would be sensible given the security implications).

                      But I suspect it's my HGI80 that's gone west.

                      P.

                      Comment

                      • DanD
                        Automated Home Ninja
                        • Feb 2016
                        • 250

                        #26
                        Hi Paul,

                        Thanks for the info. Is there any sign of life in the HGI80, is it still recognised as a USB device by Linux/Windows?

                        It is also possible that the Evohome wifi controller might have its compatibility with the RFG100 gateway removed via a firmware update which would break a lot of the Domoticz functionality.

                        Comment

                        • paulockenden
                          Automated Home Legend
                          • Apr 2015
                          • 1719

                          #27
                          Originally posted by DanD View Post
                          Is there any sign of life in the HGI80, is it still recognised as a USB device by Linux/Windows?
                          Yup. It just doesn't see any traffic.

                          But the reason I suspect the HGI80 might be broken is that initially it was just seeing lots of corrupt packets, so I did a complete reinstall of (release) Domoticz and now it doesn't see anything.

                          I'm going for a full power-cycle of the NAS now....

                          P.

                          Comment

                          • DBMandrake
                            Automated Home Legend
                            • Sep 2014
                            • 2361

                            #28
                            Is it worth plugging it into a PC and assuming it appears as a serial uart, running a serial comms program with hex display mode ? Or does it need commands first before it starts relaying incoming messages...

                            Comment

                            • paulockenden
                              Automated Home Legend
                              • Apr 2015
                              • 1719

                              #29
                              Sussed it - it won't work UNLESS you type the device ID into the hardware screen.

                              Without it, I was seeing nothing. This is on a completely fresh build of Domoticz. But as soon as I type the device ID in and do an update it then starts to see traffic.

                              So nothing to do with firmware. I think.

                              Comment

                              • DanD
                                Automated Home Ninja
                                • Feb 2016
                                • 250

                                #30
                                Phew! I'm glad you've got it working OK. In theory, Domoticz should have either auto-detected your controller within 5min and then messages should have started flowing or an error should have been reported in the log if it detected multiple Honeywell systems. I've just resumed working on the Evohome Domoticz code so I'll add this to my bug list to investigate.

                                Comment

                                Working...
                                X