Honeywell CH/DHW via RF - evohome, sundial, hometronics, chronotherm

Share your Projects!
1439

@TheMystery Please post/PM me a copy of the evohome_cc section of your configuration.yaml.

Please start HA with no evohome_cc (or: restore_state: false) and send/PM me a copy of it after 15 mins.

1440

Can people report any other bugs - all I have so far is:

  • @cinnamon: AssertionError: invalid device type
  • @TheMystery: AttributeError: 'NoneType' object has no attribute 'encode'
  • @iMiMx: 2-hourly gaps in line graph of DHW setpoint

These have all been fixed and will be ā€˜releasedā€™ soon.

These are being looked at:

Before I push another release - are there any more?

1441

Iā€™ve send a log where the state/temperature was gone after a few hours.

1442

Restarting to capture some logs.

1443

@TheMystery All my testing tells me that the is_faked hint is working as expected.

It is working in my system, and seems to be working with the stuff you PMā€™d me.

Could you kindly test it again?

  • have the is_faked hint in your configuration.yaml
  • delete your .storage/evohome_cc file and restart HA
  • confirm the faking is working, and the hint is in the .storage/evohome_cc file
  • restart HA, ensuring that restore_state: true
  • confirm the faking is still working, and the hint remains in the .storage/evohome_cc file

When I say hint, I mean:

"04": {
	"heating_type": "radiator_valve",
	"sensor": {
		"device_id": "03:256005",
		"is_faked": true
	},
	"devices": [
		"03:256005",
		"04:008512"
	]
},

instead of:

"04": {
	"heating_type": "radiator_valve",
	"sensor": "03:256005",
	"devices": [
		"03:256005",
		"04:008512"
	]
},
1444

I removed the evohome_cc file, set restore State to false and i have the is fake hint in the configuration and rebooted ha, after this everything is Good in the evohome_cc file.

Then i set the restore State to true and rebooted, after this the 4 hr92 of the main zone are going to the orphand section and the hr92 from the zone with the fake sensor.
The fake hint is still in the zone.

So it Goes wrong with restore State true.

1445

Although I am verry happy with the latest version that is working stable and I am not sure if it is a bug but I am still missing the items below that I did have in Domoticz:

self.boiler_water_temp
self.ch_water_pressure
self.dhw_flow_rate
self.dhw_temp
self.return_cv_temp

1446

Hi, Iā€™m trying to figure out how to configure fake sensors, and where I can find the evohome_cc file on a Hass OS installation (do I need ssh access port 22222?).
I imagine these fake sensors can be used as a zone sensor instead of the TRV sensors, so I can use values of my Hue or Xiaomi sensor for these? Can it also be used as an outside sensor, and will that do any good for the climate management during summer or winter?
Did a search in this topic and googled it of course, but canā€™t seem to find a clear explanation of the purpose and how to install/use them.
Thanks!

1447

You can find the evohome_cc file under the .storage/ directory under the config/ directory. Which is is the root when you login via the SSH / Webterminal add-on.

If you can add an external sensor to a zone with a TRV, you will be able to use the fake sensors (although highly experimental).

Using it as an outside sensor is not yet possible to my knowledge, but would be a cool feature :slight_smile:

Iā€™ve set it up with two fake sensors, the second one gave me some issues, but I guess that was mainly due to my impatience. After you have added a zone and connected the fake sensor with evohome_cc.create_sensor call, it is good to just wait some time before you restart HA or else as I guess that was the issue that setting zone temperatures worked for the ā€˜intermediateā€™-sensor, but the zone temp did not change. I couldnā€™t reproduce the behaviour to make a bug report and patience is a virtue anyways ;).

1448

Leonard, thanks!
how could I miss the .storage folder in the root of /config, I feel really stupid :laughing:
Thanks to your explanation I was able to find more info in post #1158 in this topic.

I think it would be, afaik outside temp is used for the Smart Weather controls, but itā€™s unclear to me how the system measures outside weather (I do have an outdoor sensor wired to my Remeha boiler, maybe Evohome can read this over OT, or is it location based?).
I updated a couple of days ago, Iā€™ll look into the faked sensors later this week, thanks again.

1449

Just pushed release 0.10.4.

The following is still being investigated - they are non-trivial bugs:

1450

AFAIK, you should be seeing all these and more.

Did you see them at some stage, and now theyā€™re gone?

1451

@All Sensor faking is WIP, bordering on experimental. I am not happy with the way it is implemented.

Beware.

1452

@TheMystery What youā€™re saying is that:
a) the sensor faking is working OK, but
b) some TRVs are orphans when they shouldnā€™t be

Is that right?

Please Note: these are two different problems, and I wasnā€™t going to attack b) until I understood that a) was resolved.

Can people using sensor faking confirm that doing something like the following works for them:

evohome_cc:
  schema:
    controller: 01:145038
    zones:
      "07": {"sensor": {"device_id": "03:256029", "is_faked": true}}

If your saved state is invalid, you may have to restore_state: false (to replace it with a new one), but after that things should be OK with restore_state: true.

1453

If added to my config:

  zones:
      "07": {"sensor": {"device_id": "03:256021", "is_faked": true}}
      "08": {"sensor": {"device_id": "03:256004", "is_faked": true}}

And added restore_state: true to the config. Did a restart and everything appears fine. Will monitor if something strange happens in the near future. As long as you do not hear anything it is running fine in my setup.

1454

No, I lost them after the transision from Domoticz to HA, but still using the same hardware (HGI80).

1455

Yes, sensor faking is ok, and with the config in configuration.yaml the is faked is comming back good in the evohome_cc file.

The Only problem is with cache on that tvrā€™s are orphans that shouled be.
If I am not using cache so that the evohome_cc file is rebuild after every restart everything is ok.

1456

So, those with HR80s (only - not HR90s, HR92s), will benefit from release 0.10.5, just pushed today.

@TheMystery this should solve your problem - please let me know if I am wrong.

1457

@hsluis Please raise this as an issue on zxdavb/evohome_cc and I will address it for you.

All these data - and much more - should be exposable via HA.

1458

Great, thank you, I will do that.