I seem to have now lost connectivity with my HGI-80 since yesterday evening. Not sure if its connected with the recent changes, as I did also have a server issue yesterday evening, which required a restart. However after Domoticz restarted and its server's remote address updated, my Echo Show Domo Icon was showing red. I have everything verified "ticked" on my Evocontrol Dashboard, and can access Domoticz remotely via other devices ok, so not sure what the problem may be at the moment?
EvoControl - custom Alexa skill for Evohome
Collapse
X
-
Sorry, my bad. There was a typo among the parameters in the new settings screen. It's fixed now so if you slide the HGI toggle it should work for you againOriginally posted by Midland45 View PostI seem to have now lost connectivity with my HGI-80 since yesterday evening. Not sure if its connected with the recent changes, as I did also have a server issue yesterday evening, which required a restart. However after Domoticz restarted and its server's remote address updated, my Echo Show Domo Icon was showing red. I have everything verified "ticked" on my Evocontrol Dashboard, and can access Domoticz remotely via other devices ok, so not sure what the problem may be at the moment?
PS. It would not have affected you without your server issue. Amazing how coincidences always conspire to cause train crashes. You are renewing your ngrok tunnels manually after server restarts. Did you see the recent post about having that automated using easy-ngrok?Last edited by philchillbill; 27 January 2023, 11:40 AM.
Comment
-
-
Great that's all working again now, so many thanks. Yes you are right, occasionally the "holes line up in the swiss cheese slices" and an unpredicted event occurs. From an end user's point of view, the Domo Icon proved its value in fault finding hereOriginally posted by philchillbill View PostSorry, my bad. There was a typo among the parameters in the new settings screen. It's fixed now so if you slide the HGI toggle it should work for you again
PS. It would not have affected you without your server issue. Amazing how coincidences always conspire to cause train crashes. You are renewing your ngrok tunnels manually after server restarts. Did you see the recent post about having that automated using easy-ngrok?
Looking at the new settings screen I did notice that the "Enable/Use HGI-80" toggle, although enabled on my screen is greyed out, not sure if this was your intended intention?
I had spotted your automated easy-ngrok but haven't tried it out yet, but will do. I was actually considering moving away from ngrok, as my ISP supplied IP address, although dynamic hasn't changed in over a year, so maybe switch to apache etc going forward.
Comment
-
-
'Bug' in Echo Show 5" firmware
Thanks to @bruce_miranda sending me a photo of his device, I've identified that the Echo Show 5" is incorrectly reporting itself as HUB-LANDSCAPE-MEDIUM even on the device itself. I added a parameter in the bottom left corner of the Settings screen to print what the device is reporting as. Anybody else with a 5" will see the same anomaly.
This Amazon anomaly means that ALL EvoControl views on the 5" are way off the simulator view, which reports the 5" (correctly) as HUB-LANDSCAPE-SMALL. On the actual device, there are vertical black bars on the left and right to fudge a different aspect ratio than native. So EvoControl looks very different to my intention on a 5" device! Yikes!
The only way I can fix this is to tick a box in the developer portal that says 'my skill can handle a 5" device natively'. This triggers the Echo to report correctly. However, I cannot update the LIVE skill with that change without submitting for recertification, which will take a while.
FYI: Amazon did this because when the 5" originally came out, it had a different aspect ratio to the original Echo Show. By reporting itself incorrectly, existing skills would at least display correctly inside a window on the 5".
Comment
-
-

The upcoming switchpoints screen has been updated to now display as 2 columns on most devices (which will accommodate a boatload of zones better). On the small round Echo Spot it displays with a scroll indicator and is still one column.
As a memory jog, it sorts the upcoming switchpoints by their time-of-day, so it's yet another way to see schedules in effect across your zones. Note that this is schedule-only and does not take into account e.g. a constrained temporaryOverride terminating.
You get to it by voice (only) by asking e.g. "what's up next" or "show today's roster". The first item is annunciated by Alexa so also works nicely on screenless Echos. You can also ask for a particular zone by saying e.g."what's next for the bedroom".
Comment
-
-
I have little experience with AI skills but I find it strange that some commands have to be spoken exactly how the developer coded them. I thought with Natural language processing the AI engine would know what you intended to do. e.g. I would have asked for "What's today's schedule". But it seems like everything is quite specific. Or am I mistaken?
Comment
-
-
Originally posted by bruce_miranda View PostI have little experience with AI skills but I find it strange that some commands have to be spoken exactly how the developer coded them. I thought with Natural language processing the AI engine would know what you intended to do. e.g. I would have asked for "What's today's schedule". But it seems like everything is quite specific. Or am I mistaken?
Comment
-
-
The Scenes/Activities Editor, Setpoint Editor, Group Editor and Offsets Editor should now be noticeably snappier in use. I figured out a way to just update the data without having to resend the markup on each delta. Incidentally, that prevents the issue @midland45 was having before the recent tile-responsiveness change where the scroll would jump each time an increment/decrement was done on off-screen tiles.
Please advise if any issues arise.
Comment
-
-
Just occurred to me now, but you could define an activity with all zones at 5 deg and call it Off/Sleep/Dormant/Vacant/Standby as you wish. It would then be "Activate standby for 2 hours". That can even be scheduled: "Activate standby at 17:00 for 2 hours"Originally posted by bruce_miranda;Just an easier command to remember. And it's more natural to say "Turn off heating for 5 hours" especially with the cost of gas in 2023.
Comment
-
-
'Standby' activity auto-created
The more I think of it, the more I like Bruce's idea for a quasi HeatingOff mode that still allows manual overrides from a TRV dial (they are ignored when the real HeatingOff mode is active).
From now on when you first link the skill (or update your configuration if already linked), an activity called Standby- after 7PM]
- Alexa, schedule Standby to start at 7PM for 2 hours
- Alexa, schedule Standby to start at 4PM until 5:30PM
- Alexa, schedule Standby from 2PM to 3:45PM
You can rename, delete or modify this activity in the normal touchscreen activity-editor. Any mods you make will not be clobbered if you update your config. However, if you delete it then it will be recreated on each refresh.
If you have DHW and want to include it in your Standby activity you can make a manual edit to do so. It's not auto-included by default.
Comment
-
I like....
I would go further and say "Activate StandBy" should be permanent and not until the next setpoint. Maybe add another command to "Activate StandBy Until next change". My rational is, any command without any explicit time constraints, should be exactly that.
The other advantage of this StandBy is you can issue per zone instructions while in StandBy, rather than constantly being told, command not possible while Heating Mode is OFF.
Comment
-


Comment