Monitor boiler parameters when using an OT Bridge, a HGI80 and Evohome

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

    Monitor boiler parameters when using an OT Bridge, a HGI80 and Evohome

    If you have an OT Bridge, an HGI80 (or similar) and Evohome, you can now monitor the boiler parameters on Domoticz. My code changes will create new additional devices to track various boiler parameter e.g. Control Setpoint, Flow and Return Temperatures, Relative Modulation Level etc. The devices are called the same names as they would have if you were using an OTGW directly attached to Domoticz.

    Have a play and let me know how you get on. Until my PR gets merged with the main Domoticz code base, you'll get to grab the code from my branch at https://github.com/brucemiranda/domoticz
  • bruce_miranda
    Automated Home Legend
    • Jul 2014
    • 2307

    #2
    My code changes are now also able to track if the boiler flame is ON or OFF and that is reported on Domoticz too.

    Comment

    • oxygen
      Automated Home Jr Member
      • Sep 2018
      • 40

      #3
      Originally posted by bruce_miranda View Post
      If you have an OT Bridge, an HGI80 (or similar) and Evohome, you can now monitor the boiler parameters on Domoticz. My code changes will create new additional devices to track various boiler parameter e.g. Control Setpoint, Flow and Return Temperatures, Relative Modulation Level etc. The devices are called the same names as they would have if you were using an OTGW directly attached to Domoticz.

      Have a play and let me know how you get on. Until my PR gets merged with the main Domoticz code base, you'll get to grab the code from my branch at https://github.com/brucemiranda/domoticz
      I confirm that the new code you pushed late 2019 in the main dev branch of Domoticz is working fine.
      It shows proper values on my system (based on a Perfinox 4100 + HGI80 + OT Bridge).
      I'll need to wait until your code is streamlined into the dev branch of Domoticz, I would like to avoid wrecking up my current Domoticz config by switching to your dev branch.

      If I may comment, having a unit displayed for the values with a unit would be great. I'm not sure the official OpenTherm specs units that are supposed to be used.

      Code:
      2020-01-19 15:22:08.551 Status: evohome: OPENTHERM_BRIDGE: Fault Code = 0000
      2020-01-19 15:22:09.146 Status: evohome: OPENTHERM_BRIDGE: Relative Modulation Level = 2400
      2020-01-19 15:22:09.604 Status: evohome: OPENTHERM_BRIDGE: CH water pressure = 0169
      2020-01-19 15:22:10.134 Status: evohome: OPENTHERM_BRIDGE: DHW flow rate = 0000
      2020-01-19 15:22:10.727 Status: evohome: OPENTHERM_BRIDGE: Flow water temperature = 65.00C
      2020-01-19 15:22:11.318 Status: evohome: OPENTHERM_BRIDGE: DHW Temperature = 64.00C
      2020-01-19 15:22:12.307 Status: evohome: OPENTHERM_BRIDGE: Return water temperature = 53.00C
      2020-01-19 15:22:12.901 Status: evohome: OPENTHERM_BRIDGE: OEM diagnostic code = 0000

      Comment

      • bruce_miranda
        Automated Home Legend
        • Jul 2014
        • 2307

        #4
        Thanks for that. My latest code changes now no longer simply display these messages on the Status Log, but actually make these into devices that are updated as the messages come in. That then allows you to treat them like other Domoticz devices.

        Comment

        • oxygen
          Automated Home Jr Member
          • Sep 2018
          • 40

          #5
          That was my undertanding. And it looks promissing !
          But i will wait until you push the code into the dev/beta branch to update my install. I'm chickening out

          Comment

          • bruce_miranda
            Automated Home Legend
            • Jul 2014
            • 2307

            #6
            Completely understand. However you have just shown me that on some boilers the OTB is able to read and display the DHW Temperatures too.

            Comment

            • bruce_miranda
              Automated Home Legend
              • Jul 2014
              • 2307

              #7
              My changes are now in the main development branch of Domoticz, so if you update your code and recompile it, you will get them.

              Comment

              • oxygen
                Automated Home Jr Member
                • Sep 2018
                • 40

                #8
                Yes, all seems good.
                But I've the feeling I've lost the error codes reporting.
                It's a good thing to keep them somehow, as in my config, the boiler sometimes is getting trouble following the orders and falls in error mode. It eventually gets our of error, but I'm missing the ability to follow this up.
                Unless I'm mistaken, only the data that goes into the devices are now fetch.

                To monitor my error codes, I could put the otgw that I've idle (and that I have built for that), but lazyness got the better of it, so far :-)
                (Or even better, evohome firmware should have the ability to report back those data instead of throwing them away)

                Comment

                • bruce_miranda
                  Automated Home Legend
                  • Jul 2014
                  • 2307

                  #9
                  Dont worry, the error code is tracked into a device. If you dont see a device that means you have no Error code. I create devices only for messages that have a non zero value. This way the database isnt tracking a value forever.

                  Comment

                  • oxygen
                    Automated Home Jr Member
                    • Sep 2018
                    • 40

                    #10
                    It makes sense, even if it means that I cannot activate the device until it generates it first error code.

                    My boiler generated a new OEM Error code, so I've been able to add it, but I'm still missing the general fault code to track it.
                    (OEM Error beeing 61, or for my boiler "Ambiant Sensor in Fault", I consider this is a false positive of my LMU64<>OT Gateway).

                    Btw, since it was generated, I've the feeling the value is "kept", even if the error is now gone. I don't know how to go around that to "acknowledge" the error and clear the counter/device.
                    Last edited by oxygen; 20 January 2020, 10:35 AM.

                    Comment

                    • bruce_miranda
                      Automated Home Legend
                      • Jul 2014
                      • 2307

                      #11
                      Ah yes, I can see why, its an issue with the way Domoticz works. To get around that, I think it might be better to just log everything, so that way you know for a fact that a 0 error code has been received and then you can also see when errors are cleared.

                      Comment

                      • paulockenden
                        Automated Home Legend
                        • Apr 2015
                        • 1719

                        #12
                        Just updated to the latest dev build and I can see the new 'devices'. I confirm that the values match what I see through the Intergas InComfort interface (which I also feed to Domoticz).

                        Thanks Bruce!

                        Comment

                        • bruce_miranda
                          Automated Home Legend
                          • Jul 2014
                          • 2307

                          #13
                          Originally posted by oxygen View Post
                          Btw, since it was generated, I've the feeling the value is "kept", even if the error is now gone. I don't know how to go around that to "acknowledge" the error and clear the counter/device.
                          What do people feel is a better solution for devices that track an error code? Keep it at the last error code until the next one or reset the error code, if the error gets reset. With the first solution if an error happens overnight, you will still know in the morning, however it will stay that way until you know how to reset it on Domoticz. Or if I just make the device track whatever the boiler sends then you could potentially use the Notify feature in Domoticz to inform you of a momentary error condition. However then, Domoticz will potentially be logging a lot of 0s.

                          Comment

                          • oxygen
                            Automated Home Jr Member
                            • Sep 2018
                            • 40

                            #14
                            Originally posted by bruce_miranda View Post
                            What do people feel is a better solution for devices that track an error code? Keep it at the last error code until the next one or reset the error code, if the error gets reset. With the first solution if an error happens overnight, you will still know in the morning, however it will stay that way until you know how to reset it on Domoticz. Or if I just make the device track whatever the boiler sends then you could potentially use the Notify feature in Domoticz to inform you of a momentary error condition. However then, Domoticz will potentially be logging a lot of 0s.
                            It's a tricky question.
                            The thing is my config generates a lot of errors. This is not your code, this is really my setup (My Perfinox 4100 is not officially OT compatible, yet beeing controlled by an LMU64, it reacts perfectly well to OT. That beeing said, it sometimes has trouble following the requested load sent by the OT Gateway // this is my understanding based on now ~2years of running it)

                            last-7-days.jpg

                            The issue in your code is that the error code is changed just when a NEW code is collected.
                            In between, I've no way to know for sure if the error went away or not.

                            This is true for the error code 61 that you can see, as it is actually a "ghost" error (it happens only once and then disapears, quite opposed to the error 151)

                            61 is "Faulty Ambiant Sensor"
                            151 is LMU issue, usually coming with a "ionisation current limitation".

                            From my understanding, the OT Gateway may request a too low modulation and the boiler fails to keep it so flameout/ionisation current limit occurs.

                            With the current code behavior, I cannot know for sure if the error was "ghostly" (as in occured just once, or it was there for a "long time").
                            => My feeling is reset the code if the OT Gateway reset the code.
                            The logging is still there to followup if there was an error.

                            If you want to be "better" you could still use a on/off device that you "enable" if you trap a non-zero value, and leave it to the "user" to reset this on/off device.
                            This way we would have "an error was detected" in a specific device, and leave it to the user to acknoledge.

                            Comment

                            • bruce_miranda
                              Automated Home Legend
                              • Jul 2014
                              • 2307

                              #15
                              If you pull down the new Beta you will get a change that keeps the devices updated with whatever value is received from the boiler. Unfortunately Domoticz has very few inbuilt devices that I can choose now. You can still get the device to trigger a notification on an error condition that you are interested in.
                              My latest changes also displays the controller's Fault Logbook on the Status Log and generate a Domoticz error message if the Controller detects an error.

                              Comment

                              Working...
                              X