EvoControl - custom Alexa skill for Evohome

[philchillbill]

I'm not familiar enough yet with HA to know how to purge the entities & then have Ramses_cc rediscover. I see there is an eavesdrop input for ramses_rf, but I'm not sure how to clear out old entities yet.

Sorry, neither am I proficient in HA. I know just enough to work with it via the API

Now that I added handling of the 2nd form via conditional-chaining, does the data show correctly and can you now plot graphs for all zones?

[s.w.webb1]

[philchillbill]

Set points are showing correctly, however the trend graph not working for any zones. It’s just pops back to the skill home page

OK, that's progress. I just found and corrected an anomaly on the graphs so please retry.

[s.w.webb1]

Graphs working for those entities that have the new structure. For entities based on the original it crashes the skill and goes back to echo home page.

Btw - rapid response on this! Much appreciated. Evocontrol is awesome!

[philchillbill]

Graphs working for those entities that have the new structure. For entities based on the original it crashes the skill and goes back to echo home page.

Btw - rapid response on this! Much appreciated. Evocontrol is awesome!

Glad to assist. Sorry for the ping-pong but without access to HA I cannot debug before I (almost) fix stuff.

Found a NaN issue with the older schema which is now fixed so you should finally be good to go.

[s.w.webb1]

[philchillbill]

Cooking on gas now!

Readouts for all zones work and everything reporting as expected. Top work!

This process has led me learn why a radiator in the living room kept coming on randomly. Transpires it’s assigned to the wrong zone for who knows how long ��

I see that the UNTIL values reported by the newer scheme are of the format "2023-07-27T14:00:00+01:00" while the old format is "2023-07-27T14:00:00". This is giving you the red-screen error. I'll take a look at it tomorrow.


EDIT: The skill now handles both situations

[bruce_miranda]

I would need to see the Schema for this installation that is causing the issue. Also the latest version of ramses_cc is 0.22.40

[bruce_miranda]

HA can be installed in several flavours, Docker, OS etc. I bet ramses_cc is using several inbuilt HA functions which might be platform dependent. All fine while the entities and data stay and are managed within HA. But when you extract the data out to a 3rd party system things start to look weird.

[philchillbill]

HA can be installed in several flavours, Docker, OS etc. I bet ramses_cc is using several inbuilt HA functions which might be platform dependent. All fine while the entities and data stay and are managed within HA. But when you extract the data out to a 3rd party system things start to look weird.

That may explain the different formatting of the until time, but it would not explain the difference between TemporaryOverride and temporary_override and the nesting of the data-structure in general.

[bruce_miranda]

That may explain the different formatting of the until time, but it would not explain the difference between TemporaryOverride and temporary_override and the nesting of the data-structure in general.

Now I am intrigued. But that could be down to the version or ramses_cc used. I'm on the latest version

[s.w.webb1]

[philchillbill]

Now I am intrigued. But that could be down to the version or ramses_cc used. I'm on the latest version

In that case, David must have made a conscious choice to completely change the data-structure at some stage. When I asked him about the ramses_cc schema on the HA forums, he never mentioned that there were different versions to potentially take into account.

One way or another it doesn't matter to me as the skill now handles both data schemes and it wasn't much work to do it (once I saw the DS). It's just the element of surprise that I wasn't prepared for it and the HA integration initially failed for @s.w.webb1.

[philchillbill]

Domoticz 2023.2 was recently released and it includes the new API format introduced in a June beta, so the version-check code in the skill will now approve stable 2023-2 (and upwards). This means you no longer have to be on a beta to use the Domoticz connector.

[bruce_miranda]

ramses_cc has not had an update for a long time. But previously it was changing quite rapidly and often quite significantly. I have another theory about why there appear to be two different structures. It could be that this install had 2 different versions of ramses_cc installed over time. So some climate objects were created in an older version. I'd be tempted to delete all the climate objects atleast from HA and start again with the latest ramses_cc installed