Originally posted by philchillbill
View Post
EvoControl - custom Alexa skill for Evohome
Collapse
X
-
They do nowOriginally posted by Midland45;Do the flame icons modulate their opacity on the main dashboard relative to the zones % heat demand or just on the verbally called up heat demand screen? As when running the heating I can only see this on the heat demand screen.
I had inadvertently squashed the opacity factor in my attempt to prevent the '--' when demand is unavailable/unknown from the HGI. Thanks for uncovering.
Comment
-
-

The website now has a suggestion in the Usage Tips section on how to create a custom Alexa routine that will automatically revert to baseline at a certain time every day. If e.g. you schedule your activities a lot or request frequent schedule shifts, here's a way to ensure you cannot accidentally leave a morphed schedule to inadvertently run a week later.
Comment
-
-
I just tried to activate and activaty and am told “According to honeywell permission to connect to tcc was never autorized or has been revoked”
was working earlier for sure… anything change? Could it be related to the charging model? Do i now need to pay?
Jon
Comment
-
-
@jweaver I can see in the logs this morning that your 401 is the special case of 'You are not allowed to perform this action' instead of 'Unauthorized'. That happens when Honeywell resets your account and all your IDs change. The authorization is for the old IDs and therefore fails. Did you reset something in your TCC account or did you call Honeywell support? Anyway, you need to login to your smartskills dashboard and re-auth TCC.
Do *not* unlink the skill.
EDIT: Regarding your saying "it's still the same this morning" you should realise that with oauth, once it misaligns it will never automatically realign, no matter how long you wait. You will always have to re-auth when a misalignment happens, for whatever reason.Last edited by philchillbill; 21 October 2023, 09:04 AM.
Comment
-
-
You might be onto something. I have opened a ticket to tell them about my problem with Smart Weather when using Vodafone as the ISP. Just on the off chance they have any thoughts.Originally posted by philchillbill View Post@jweaver I can see in the logs this morning that your 401 is the special case of 'You are not allowed to perform this action' instead of 'Unauthorized'. That happens when Honeywell resets your account and all your IDs change. The authorization is for the old IDs and therefore fails. Did you reset something in your TCC account or did you call Honeywell support?
They replied in the afternoon saying they would pass the ticket to the developers so i wonder if they did something first.
Thinking about it, a similar thing happened earlier in the year when i installed my hot water module and contacted them for help. It seems that even when their support is “non-intrusive” they still do things on your account which deauth apps.
I will reauth this morning and let you know if i have any problems.
Thanks.
Jon
Comment
-
-
I had already created a special error message for when that happens but due to a typo it was not triggering (now corrected). Difficult to debug when this doesn't happen to people often.Originally posted by jweaver View PostYou might be onto something. I have opened a ticket to tell them about my problem with Smart Weather when using Vodafone as the ISP. Just on the off chance they have any thoughts.
They replied in the afternoon saying they would pass the ticket to the developers so i wonder if they did something first.
Thinking about it, a similar thing happened earlier in the year when i installed my hot water module and contacted them for help. It seems that even when their support is “non-intrusive” they still do things on your account which deauth apps.
I will reauth this morning and let you know if i have any problems.
Thanks.
Jon
Comment
-
-
Just reauthed and now i am getting a new error (probably the one you talk about above) which ultimately tells me to reauth.Originally posted by philchillbill View PostI had already created a special error message for when that happens but due to a typo it was not triggering (now corrected). Difficult to debug when this doesn't happen to people often.
So i am a bit stuck.
Comment
-
-
Nope.. same error.. says my config doesnt match and i need to reauth.Originally posted by philchillbill View PostAfter re-authing, you need to refresh your configuration in the skill itself. If you're being thrown out of the skill after launching, try a one-shot: "Alexa, ask smart heat to refresh my configuration".
Comment
-
-
I can see that Honeywell is still issuing oauth for the older IDs so apparently their system is unaware that they changed your IDs.Originally posted by jweaver View PostNope.. same error.. says my config doesnt match and i need to reauth.
In retrospect, the skill gets the updated oauth the moment you re-do it on my account dashboard so it's actually unnecessary to ask the skill to update the config (I forgot I already implemented that over the Summer).
What may help is if you go to your TCC login page and delete/re-add your location to your TCC account. This is also the way to get rid of ghost zones so it's done regularly by people and is not that scary a thing to do. Then re-auth on my dashboard and open the skill.
Pity that Honeywell doesn't re-align the oauth when they mess with people's IDs. You have a userId, systemId, locationId, dhwId and zoneIds and they seem to change some of them when you call tech support...
Comment
-


Comment