Anna v1.8.20 not working

[sanderdw]

As requested by @bouwew (https://github.com/home-assistant/core/issues/28947#issuecomment-607419232) i installed the new plugwise-beta component in my clean home assistant test setup.

Plugwise Anna version: v1.8.20 (so the old version)

Installing: Adding this Repo to HACS went fine and also adding the integration was easy. Maybe you could document it somewhat clearer that you have to add this git repo to HACS, but i figured it out anyway.

After adding the integration it's also added to Lovelace:

But it is a water_heater instead of a climate component?

This are the entity's that were added by this component:

Also the reported temperature (33) is not correct. Currently it's 20.1 and climate is set to 20. So it's seems it's reporting the boiler temperature in the first screenshot. direct_objects.zip

Let me know what to check next?

Thanks for developing this nice component!

[CoMPaTech]

@sanderdw Those values should be from your water-heater/boiler indeed. Looks like something doesn't match up in our code to add the 'climate' part. (Or better stated, to detect which one is your climate).

We are patching up to 0.0.51 but I don't think that will ensure your climate will be detected (there are minor fixes in there for Anna 1.8, but I don't suppose it will fix this).

[bouwew]

@sanderdw can you show us the errors related to plugwise-beta in Developer Tools --> Logs?

[bouwew]

The temperature reported by the water_heater is the temperature of the water inside your CV-ketel. The water_heater represents the CV-ketel and shows it operating state: idle, heating or hot_water. Each state also has it's own appropriate icon.

[sanderdw]

Here is a sceenshot of the log:

Not much info...

[bouwew]

Ok, no error, thanks.

[bouwew]

The next release should fix the missing climate-entity. Coming soon...

[bouwew]

Please update via HACS to version 0.0.52, restart HA and try again.

[sanderdw]

Updated and did a fresh intergration again:

anna_temperature = 20.09 and anna_thermostat = 20.0 are correct. Not seeing a climate component yet though...

[bouwew]

Can you please enable the logger in configuration.yaml?

logger:
  default: warn
  logs:
    custom_components.plugwise-beta: debug

And then restart HA once more?

After the restart go to Developer Tools --> Logs and press the large refresh HA Log below the separation-line.There should be many lines related to plugwise-beta, please show us these.

[sanderdw]

[bouwew]

Great, thanks, this helps.

[CoMPaTech]

Just pushed out 0.0.54 #13 that should fix this

[sanderdw]

Error log is looking better:

Also the climate component is here now:

Although it says heating but currently it isn't?

[bouwew]

That is progress! Yes, I noticed that too, the Anna says heating and the water_heater says hot_water. What kind of device do you control with the Anna? And is it creating hot water?

[sanderdw]

It's a vaillaint boiler. The 'native' integration is reporting it correctly.

I turned on the heating to see what it shows but it makes no difference.

[bouwew]

Can you please capture the /core/appliances XML-data with heating on and heating off?

[bouwew]

Also, do you see a difference on the Anna when the heating is on versus when hot water is being tapped?

[sanderdw]

Ok so i got the xml files when not heating, using the central heating and also tapping hot water: anna_status.zip

[bouwew]

Thanks!

Looks like domestic_hot_water_state is always on, central_heating_state is always off, and boiler_state is on when heating or tapping hot water, otherwise off. So only boiler_state to look at in your system.

[bouwew]

Ah yes, in haanna it reads:

    def get_domestic_hot_water_status(self, root):
        """Get the domestic hot water status."""
        if self.legacy_anna:
            return None

And we do not do that (yet) in Plugwise-Smile.

[bouwew]

Please try release 0.0.55. Now the heating-result should be the same as the native component.

[sanderdw]

Updated: it still says heating as icon and color indicator when it's not: In the text it looks correct, inactief when not heating and verwarmen when it's heating

[bouwew]

Ok, good, issue solved :)

About the picture, the flame icon actually means there is no schedule active, it is in standard heating-mode following the setpoint that can be changed manually, from within HA, the Pw App or from the Anna. If you create a week-schedule in the Plugwise App and activate it there, in HA the schedule-icon would turn green together with the circle, indicating it is in auto-mode, with an "AI" regulating the setpoint. Also, please know that the status shown with the circle is not the function of the CV-ketel, it is simply showing: no heating required == inactief, or heating required = verwarmen. The algo is very simpel: if current_temp < heating_setpoint then need heating, etc. The true status of your CV-ketel is shown by the water-heater-entity. The reason to do it like this is coming from the Adam to which many thermostats can be connected. In the old situation they would all show the same status while the heating-demand would only come from one thermostat. With the new algo it is clear which thermostat has a heating-demand.

Our last request: can you please create a weekschedule and test if you can activate it and deactivate it from within HA?

[sanderdw]

I'm not sure if I understand you correctly. According to me the active flame should only be there when either the central heating is active or when you are tapping hot water, right?

Wil check the schedule stuff tomorrow, thanks for helping!

[bouwew]

Incorrect, the orange flame- or the green schedule-icon are always there/on, when selected, because they show the active climate MODE. What you are looking for is the active climate ACTION which is shown via the text (Inactief, etc.). See here for details: https://developers.home-assistant.io/docs/entity_climate/ There can also be a cooling-icon or an off-icon, representing other HVAC-MODES.

Many people think like you but you are thinking wrong. Ask the top-HA guys, they will tell you the same, they have come up with the present, maybe illogical, implementation.

[bouwew]

Closing this topic as the issue is solved.

[bouwew]

@sanderdw Do you see an icon of a tap on the screen of your Anna when you are tapping hot water?

[sanderdw]

Like on the physical device screen? Yes that's correct.

[bouwew]

Yes, on the screen of the Anna itself.

Ok, good to know, thanks! Then our assumption that the legacy Anna did not support showing this state/icon is wrong. Now we need to find out why on one user's legacy Anna the key "domestic_hot_water_state" is always "on", whether he is tapping hot water or not...

[bouwew]

@sanderdw, please update to version 0.2.4rc0 and let me know if on climate.anna(?) hvac_mode is showing the heating and idle states correctly and if binary_sensor.auxiliary_dhw_state is showing the state of tapping hot water correctly.

[sanderdw]

How can i install this version with HACS? 0.2.3 is reported as the last version.

[CoMPaTech]

You can make this version visible in HACS, when you are in the selected Plugwise-beta integration, by clicking the 3 dots on the right and selecting "Show beta". borrowed from bouwew in another update :)

[sanderdw]

0.2.4rc0.xlsx

Here you go. I included everything, also the core 'legacy' implemantion.

[bouwew]

@sanderdw, I see two test-cases: everything off and heating tap-water. Can you also please test the case of heating the radiators/floor? What I am seeing for the two test-case, all looks OK.

About the difference between the present and legacy implementation, "hvac_mode" is not a representation of the heater-state, this state is provided by "hvac_action". "Hvac_mode" shows the operation-mode of the system: either auto-mode or heat-mode. Auto-mode means controlled by an automation like a weekly schedule, heat-mode means, set to heating based on a fixed setpoint (which can only be changed "manually"). I think they should give this mode another name :) Please note, the legacy-implementation was not according to the HA-climate-guidelines.

[sanderdw]

0.2.4rc0_v2.xlsx

I updated the sheet with the heating turned on.

Yes, about these guidelines, iagree to follow them even it's a little weird :). Thanks anyway.

[bouwew]

@sanderdw version 0.2.4rc1 is available on HACS, please test.

[sanderdw]

0.2.4rc1.xlsx

Will add heating the water later...

[bouwew]

Thanks. Another user told me too that it doesn't work. He is checking a possible solution for me. And I have asked for help from Plugwise. More to follow...

[sanderdw]

Hi @bouwew just wanted to let you know that i installed 0.2.9rc0 and now the integration is broken. I also tried to re-add the integration but none if the devices and entity's are showing anymore.

[bouwew]

@sanderdw Sorry to hear that. What is shown in Developer Tools --> Logs? Any errors related to Plugwise-beta?

[sanderdw]

[bouwew]

Timeout fetching data means there is a not-so-great connection between the Smile and your Home Assistant server. For the rest it looks OK to me. Is it working now for you?

[sanderdw]

No it's not working. The legacy (which i'm still using) is working fine though?

[bouwew]

Strange! Can you please also look at the sensors? Are these also not working?

Also, are you using legacy (meaning the official HA Plugwise component?) and plugwise-beta at the same time?

[sanderdw]

Also not working:

I'm testing on a seperate Pi3 with only the this new developed HACS version of the component.

My main HA instance is working correctly and there i still use the 'included Anna component'.

[bouwew]

Ok, so you are running 2 Home Assistant instances in parallel? And your Smile is connected via Wifi? It might be that your Smile is being overloaded due to maybe a not-so-good WiFi-connection.

@CoMPaTech anything to add?

[sanderdw]

Yes correct. Smile is connected with LAN.

I will try to go back some versions to see if it's a programming error.

[sanderdw]

Ok so looks like 0.2.4rc1 is running fine and from 0.2.7rc0 it's not working anymore.

[bouwew]

Thanks, good feedback :) I'll have a detailed look later today.

[bouwew]

Can you please test plugwise-beta version 0.2.7rc0 with Smile versions 0.2.4, v0.2.5, v0.2.6 and v0.2.7? Edit/modify the version number in plugwise-beta/manifest.json and then restart HA.