The best thing you can say about the Evohome apps are that they work, just!
So many opportunities to improve usability
I can't say I use the App very much. The only time I use it is when returning from holidays, or when we've been out late and want to boost the Living Room rad. It's pretty much set and forget with me....Originally Posted by dmsims
But yeah, the Apps aren't great and so much could have been done with it. Maybe that's why I never use it!
I purchased an evohome system about 4 months ago and finally got to installing it around a month ago. Checking the software version I get:
Application Software Version: 02.00.11.21
WiFi Software Version: 02.00.17.00
So the wifi software is upto date with the version in this thread but I seem to be on an old application version. I had assumed that it would auto update itself at some point but after a number of weeks I am starting to suspect that won't happen. Was version 02.00.17.03 fully released and if so can anyone tell me how I go about getting the update?
Email Resideo (Honeywell) at consumersupportuk@honeywellhome.com
They can push the software update manually if you provide your MAC and CRC numbers.
Wow, so it's now been 2 years since the last firmware and no new Evohome replacement products too. What's up Honeywell.
Sorry to re-open such an old conversation but I'd be really interested to know the answer!
That is, whether or not the HCE80 UFH demand percentages are avaialble through the public web API or the raw local radio signals via HGI80?
Having trawled some more on this great site, and through watchForStock's equally wonderful evohomeClient2, I can see that valve demand signals are certainly not in the web API.
But are they in the radio signals? I saw the TRV demand but haven't been able to get UFH demands?
Yes, I am getting demand signals for each UFH zone (from an HCC80R).
Thanks, that's good to hear.
Are you by chance the author of evohome-Listener? It's quite something!
I have that running with a nanoCUL FTDI 868MHz. Can see lots of evohome signals including a variety of ZONE_HEAT_DEMAND messages but these report as the HCC80 ID not as a zone.
Our system is 1 controller, 1 BDR91 driving the boiler, 2 HCC80 sharing an antenna supplying 9 UFH zones, the first using evhome controller temperatuer and the other 8 each with HCW82. And 3 zones each with a single TRV.
Yesterday I did a factory reset and bound just 3 UFH zones so that I could figure out how to configure the Listener. Zone 1 uses evohome temperate and the other two use HCW82. All 3 zones are on the same HCC80.
Here's the corresponding devices.json
2020-01-15 23:29:36 | | | Devices loaded from 'devices.json' file:
2020-01-15 23:29:36 | | | 01:062953 - evoHomePanel - Zone 1 [Master]
2020-01-15 23:29:37 | | | 02:023727 - UFH2? - Zone 0
2020-01-15 23:29:37 | | | 02:025324 - UFH1? - Zone 0
2020-01-15 23:29:37 | | | 03:125829 - Garden room - Zone 3 [Master]
2020-01-15 23:29:37 | | | 03:255727 - Living room - Zone 2 [Master]
2020-01-15 23:29:37 | | | 13:233522 - evoHeatDemand - Zone 0
2020-01-15 23:29:37 | | | 30:071715 - EvoGateway - Zone 240 [Master]
And the different ZONE_HEAT_DEMAND messages I get back are:
2020-01-16 00:11:45 |1| ZONE_HEAT_DEMAND | I | CONTROLLER -> BROADCAST MESSAGE | 0.0% [Zone 252]
2020-01-16 00:26:57 |1| ZONE_HEAT_DEMAND | I | UFH UFH2? -> CONTROLLER | 92.0%
2020-01-16 02:08:55 |1| ZONE_HEAT_DEMAND | I | UFH UFH2? -> CONTROLLER | 50.0% [Zone 4 ]
It looks close but I' hoped to see Zone1/2/3 heat demand messages. What have I got wrong?
THanks
The heat demand radio messages for the UFH controller is definitely decoded. So this could easily be a bug with the data parser that you are using. What does Domoticz show for your UFH device?
Posting Permissions
Reply With Quote