@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”
Too soon.
HA’s official evohome integration does a pretty good job on this (I wrote it) - you can use that pro-tem.
In the meantime, I think I’ll concentrate on adding to evohome_cc that functionality which the official integration cannot do…
I asked it because i want to replace the module on the wall with a tablet. So i want to make a schedule in HA and control the preset modus with evohome_cc. But the nice future tot add another temp sensor is very interesting!!
No, “homeassistant”
may need unhiding to become visible.
More recent instructions may be simpler though
Anyone is welcome to edit the evohome_cc wiki to provide instructions for the benefit of others!
@ stuiow
I have ‘proxmox’ and ‘hassio’ installed on it as ‘VM’.
Then on the same ‘proxmox’ I installed ‘Debian’ as ‘CT’. With ‘evohome-rf’ module…
The problem I have: not always whole the staff is working and communicating each-other. And I have no idea why… Still trying to get some stable solution. But I’m afraid this is wrong way…
I think we should find the way to install ‘evohome-rf’ module on ‘hassio’ directly…
Apparently you have restricted the wiki pages to collaborators only. i have to study how to use Github, because i don’t think my first attempt (correction of link) has worked.
I get the below… Does this mean it found the controllers but not the TRV’s? I’m guessing it just needs some time to search?
Logger: custom_components.evohome_cc.sensor
Source: custom_components/evohome_cc/sensor.py:43
Integration: evohome_cc
First occurred: 2:23:26 AM (1 occurrences)
Last logged: 2:23:26 AM
Found a Sensor (heat demand), id=01:158182, zone=None
Logger: custom_components.evohome_cc
Source: custom_components/evohome_cc/__init__.py:161
Integration: evohome_cc
First occurred: 2:23:26 AM (2 occurrences)
Last logged: 2:24:26 AM
Schema = {'controller': '01:158182', 'system': {'heating_control': None, 'orphans': []}, 'stored_hotwater': None, 'ufh_controllers': {}, 'zones': {}, 'device_info': {}}
Logger: custom_components.evohome_cc
Source: custom_components/evohome_cc/__init__.py:189
Integration: evohome_cc
First occurred: 2:23:26 AM (2 occurrences)
Last logged: 2:24:26 AM
Params = {'system': {'mode': None, 'language': None, 'heating_control': {}}, 'stored_hotwater': None, 'zones': {}}
Logger: custom_components.evohome_cc
Source: custom_components/evohome_cc/__init__.py:190
Integration: evohome_cc
First occurred: 2:23:26 AM (2 occurrences)
Last logged: 2:24:26 AM
Status = {'system': {'datetime': None}, 'stored_hotwater': None, 'zones': {}, 'devices': {}}
@scstraus I am afraid I need better logs. Are these troubleshooting instructions of any use:
My apologies - it is that way by default - I’d forgotten - should be fixed now?
Does anyone have multiroom zones? What issues are you experiencing?
I am interested in hearing from those who have multiroom zones with more than two HR92s, or two HR92s and a temperature sensor.
I have these, will try to get back to you with better logs.