I am gonna try it! i keep you posted! Thx for your work.
Update:
@zxdavb it works like a charm for now!! i can control the temperature, but only when i select from off to heat.
But when i change the temp with the arrows, i jumps back to the old temperature at the screen. but after a period i see that he changed the temperature.
Hello,
someone has tried to use ESP8266 + nRF905 to make a Evohome to MQTT gateway?
thanks
What you describe is partly a issue with convergence. The change happens immediately, but HA only checks for changes every few minutes or so by default.
I am cheating: my system checks every few seconds, so I forgot to to make accommodation for this.
I’ll implement a fix presently.
What are you changing from off to heat, the zone or the controller?
Hello,
I currently have a HGI80 connected to domoticz which I use to simulate evohome thermostats in some rooms (using Xiaomi temperature sensors). On the Home Assistant side I use the integration via the API of evohome website. I would be very interested to remove domoticz (it’s less stable than HA in my setup) and put everything in HA. I’ve tried to read this feed to see what is possible with the evohome_cc integration, but I cannot see if it enables also to simulate thermostats using a temperature sensor in the same way that the domoticz integration do. Could you please confirm if this is possible or not ?
I cant also select preset modus like eco or away
@bishop I am aware of this functionality.
I am very keen to enable people to migrate from Domoticz to HA and my plan is to do everything Domoticz can do and more. Already, evohome_cc can do many things Domoticz cannot, but this particular feature is not yet one of them - Domoticz had a big head start on me!
For others: this is one of the best things you can do for evohome - to use a temperature sensor other than a TRV. The Honeywell/resideo 'stats are expensive, however.
This feature will allow you to use a wifi/bluetooth room temperature sensor with evohome (in fact, any sensor that can talk to HA) - it will appear in the controller UI as a ‘normal’ temperature sensor.
3 Likes
known issue - will be addressed in time
I’ve made some re-configuration, installed newest components, etc…
Now I do not see all entities (like battery for example).
I did something wrong?
@dariusz I presume you got the secret max zones feature working OK?
Can I ask you to double check you’ve the latest version of everything, especially 0.4.0 in manifest.json?
There is no reason why devices should be missing - odd that it’s just the batteries - could you send me log files please - both HA and packet.log, just for 1st 5 mins of startup will do - I don’t think I’ve seen your system with the new discovery code.
dariusz
What did you find was the issue preventing you from getting evohome_rf on your hassio?
My issues are mirroring yours.
you have to install manually evohome_rf 0.40.0. When it is only in the manifest, nothing will hapened.
(In my case)
How do i do that with HASSIO?
I have installed portainer, gone to the only container running (hassio_observer), started a command and tried PIP, PIP3 etc… all are unsuccessful. Same errors as above.
Looking through this thread, i think i need to unhide a container (rather than use the only one i can see) - can anyone shed any more light on this part of the process?
This is a bit painful. The client libraries for custom components used to install automatically, but it appears HA hardened up on this sometime recently.
I have a better solution coming… Give me a few minutes to test it.
you can unhide containers in portainer.
in settings you can select Hidden containers then remove the label 
OK, latest install instructions (bear with me if this doesn’t work first go) - it doesn’t need pip.
Note: if you are happy with pip, then you can continue to do it that way as well.
For version 0.4.1, something like:
To reset everything:
cd custom_components
rm -rf evohome_cc
To install from scratch:
cd custom_components
# rm -rf evohome_cc
git clone https://github.com/zxdavb/evohome_cc
cd evohome_cc
git clone https://github.com/zxdavb/evohome_rf
mv evohome_rf/evohome_rf/* evohome_rf
To update:
cd custom_components
cd evohome_cc
git pull
rm -rf evohome_rf
git clone https://github.com/zxdavb/evohome_rf
mv evohome_rf/evohome_rf/* evohome_rf
Note there is no bleeding_edge branch anymore.
.
Nice work!
Did you also fix the preset modes? Or is it too soon? 
what container do i need to work on?
Am i right to assume “core”?
yes! then you can enter the consolepart of “core”