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

dariusz · December 22, 2019, 1:38pm

Interesting… Never heard about that.
So in my case what could be the hassi.io USB-port settings?

root@proxmox:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 018: ID 10ac:0102 Honeywell, Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@proxmox:~# ls -l /dev/ttyUSB0
crw-rw-rw- 1 root dialout 188, 0 Dec 22 02:22 /dev/ttyUSB0
root@proxmox:~#

zxdavb · December 22, 2019, 2:35pm

@dariusz try: screen /dev/ttyUSB0 115200 - after a few seconds you should see packets.

you may need to apt -y install screen

scstraus · December 22, 2019, 2:39pm

So roughly 15 hours later, parent_zones still haven’t shown up, but the graphs are a heck of a lot more detailed than before:

as compared to (graph starts about 10 hours earlier but still has fewer steps than the one above which is half the duration… Also increments of .2 rather than .5 with official component.

scstraus · December 22, 2019, 2:42pm

Is it possible to get a sensor on the whole zone rather than the individual TRV’s?

dariusz · December 22, 2019, 3:18pm

The problem is that I see /dev/ttyUSB0 on ‘proxmox’ host console.
But I do not see /dev/ttyUSB0 on Debian LXC.

I only see:

crw-rw-rw- 1 root root   5, 0 Dec 22 13:36 tty
crw------- 1 root tty  136, 0 Dec 22  2019 tty1
crw--w---- 1 root tty  136, 1 Dec 22 13:36 tty2

SO the USB ‘ttyUSB0’ is not extended to the environment where evohome is installed…

dariusz · December 23, 2019, 10:00am

Some small progress…
I see on ‘/tty/hgi80’ some output (screen /dev/hgi80 115200):

045  I --- 04:041701 --:------ 04:041701 30C9 003 000732
093  I --- 04:029184 --:------ 01:023389 3150 002 0A00
045  I --- 04:042926 --:------ 01:023389 1060 003 04FF01
045  I --- 04:042926 --:------ 04:042926 1060 003 00FF01
057  I --- 04:029113 --:------ 01:023389 1060 003 09FF01
057  I --- 04:029113 --:------ 04:029113 1060 003 00FF01
065  I --- 04:029297 --:------ 01:023389 3150 002 0000
080  I --- 04:032446 --:------ 04:032446 30C9 003 0008B8
066  I --- 04:044027 --:------ 01:023389 3150 002 0600
076  I --- 04:032446 --:------ 01:023389 3150 002 0780
077  I --- 04:032446 --:------ 01:023389 2309 003 0708CA
045  I --- 04:042926 --:------ 04:042926 30C9 003 00077C
067  I --- 04:044027 --:------ 04:044027 30C9 003 000732

Maybe some remark to someone who will have similar issue:
On ‘proxmox’ (ls -l /dev) I see:

.
.
.
lrwxrwxrwx  1 root root             7 Dec 23 10:43 hgi80 -> ttyUSB0
.
.
.
crw-rw-rw-  1 root dialout 188,     0 Dec 23 10:43 ttyUSB0
.
.
.

Note 2 lines; for ‘hgi80’ and ‘ttyUSB0’

The ‘.conf’ file is with following settings (/etc/pve/lxc/CTID.conf):

arch: amd64
cores: 1
hostname: Debian10
memory: 1024
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.1.1,hwaddr=A2:36:D0:73:1F:CA,ip=192.168.1.45/24,type=veth
ostype: debian
rootfs: local-zfs:subvol-110-disk-0,size=16G
swap: 512
unprivileged: 1
lxc.cgroup.devices.allow: c 188:* rwm
lxc.mount.entry: /dev/hgi80 dev/hgi80 none bind,optional,create=file

Plus ‘.rules’ file was created (/etc/udev/rules.d/99-hgi80.rules):

SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{idVendor}=="10ac", ATTRS{idProduct}=="0102", SYMLINK+="hgi80" , MODE="0666", GROUP="dialout"

Note: all above on ‘Debian’ container (CT) installed on ‘Proxmox’.

But - what next?

zxdavb · December 23, 2019, 10:12am

Yes, and no - The controller has this value, but I can’t recall if I implemented it yet.

I am in the middle of a big refactor of the client library, presently…

dariusz · December 23, 2019, 11:55am

I’m not sure of one thing…How ‘hass.io’ will “see” the ‘/dev/ttyUSB0’ (or in my case /dev/hgi80) USB port…???
As I see in ‘hass.io’ under ‘hardware’ button following ports - screen.
In ‘.yaml’ I have defined ‘/dev/hgi80’.

usb ports

scstraus · December 23, 2019, 7:45pm

It does somehow automagically. I didn’t have to do anything to get hass.io to work. Unless you have special problems related to proxmox.

dariusz · December 23, 2019, 10:10pm

Well… There is option on ‘proxmox’ to “see” attached USB device in ‘hass.io’,
but then the all ‘evohome’ code should be also on ‘hass.io’.
It would be nice to have some ‘add-on’ in ‘hass.io’ for the HGI80 or ‘evohome’ integration…

scstraus · December 23, 2019, 11:17pm

Add on isn’t needed, it works straight out of the box on hass.io. I just plugged in my HGI80, told it /dev/USB0 in the config and it came right up on my hass.io instance. I think your problem is with proxmox.

dariusz · December 24, 2019, 3:02pm

‘hass.io’ and ‘debian’ are installed on ‘proxmox’, and both are completely isolated systems…
And I’m not sure how to get communicated each other… Pass USB from one to another.

scstraus · December 24, 2019, 3:13pm

Proxmox should have a way to map the /dev/USB0 from outside the VM to /dev/USB0 inside the VM, then just use the default config he gives, hass.io will do the rest. If that doesn’t work, it’s likely a problem with proxmox. Some USB devices don’t play nicely with VM’s, we are having the same problem with the Coral TPU which no one can get working in a VM.

dariusz · December 24, 2019, 3:23pm

Yes, I’ve read hundred posts and forums about this… And this is problematic.
In my case ‘hass.io’ is installed as ‘VM’.
But ‘Debian’ as ‘CT’.

There are some instructions, but the result is poor… Not working in proper way…

scstraus · December 24, 2019, 3:28pm

So wait, you have hass.io installed inside the debian container or on it’s own vm which has nothing to do with the debian container? What is the debian container doing?

dariusz · December 24, 2019, 4:14pm

First I have ‘proxmox’ installed on NUC.
Then I have VM ‘hass.io’ as a VM.
And ‘Debian’ as a ‘CT’.

‘Hass.io’ has nothing to do with container…

scstraus · December 24, 2019, 10:43pm

Why are you talking about debian if it doesn’t have anything to do with your hass.io install? If you have hass.io running in a VM, then you just need to map the USB device to that VM so that it can be accessed. Then hass.io should be able to find it with the /dev/ name you map your hgi-80 to.

dariusz · December 25, 2019, 12:09am

Yes, but from 1st post I understood that I must install “client library” ‘evohome_rf’ on the machine where HGI80 is connected. I’m wrong…?

scstraus · December 25, 2019, 1:38am

That also confused me. You can ignore that. Don’t overthink it, just go into your custom_components folder and do

git clone https://github.com/zxdavb/evohome_cc evohome_rf

That’s all you need to do to install in hass.io besides add the config lines they said, and if you are in a VM, map your hgi-80 into the VM.

dariusz · December 25, 2019, 3:24pm

Well, even if I follow that - I still can not see the USB port in ‘hass.io’.
In ‘proxmox’ the USB port is seen as ‘usb0’. NO way to change that name to something else…

When I scan ‘hass.io’ /dev - I do not see any usefull port for purpose we are talking about…