Hi im feeling really stupid but i have only installed home assistant today as im trying to move away from Domoticz
But i cant for the life of me figure out what im needing to do!
as far as im aware i have
installed hacs
added ramses_cc as a repository
and ive added ramses_cc
i can see my hgi80 using dmesg
usb 1-1.3: TI USB 3410 1 port adapter converter now attached to ttyUSB0
now what do i do ?
Welcome - I think you’ll see that HA is much better than Domoticz!
I have tweaked the wiki: [ramses_cc Wiki: 1. Installation
TL DR; follow the instructions in: ramses_cc Wiki: 2. configuration.yaml
Your language isn’t precise enough for me to understand exactly what you mean. Have you added it to your configuration.yaml? If so, please post a copy of the ramses_cc: section here.
Let me know if that is not enough.
hi many thanks for the reply.
i haven’t done anything with configuration.yaml as i have no idea where to locate the file
this is all i have in my HACS integrations list
i just have no idea what i do next
right edited that and
now im getting this in the logs
but i haven’t had it saying anything is detected
i have read in the latest HASS OS 9.0 USBIP is supported.on kernel level. perhaps soon it will be made available in the UI.
i have upgraded to 0.20.22g. all went fine. but i noticed i have a lot of sensors of the boiler unavailable. how can i see if my EMS-OT converter relays this information? if my gateway doesn’t send the sensor data, it would be pointless to have the sensors in HA.
Well, the log snippet looks good!
It looks like it has found stuff…
Try adding this to configuration.yaml:
logger:
default: warning
logs:
custom_components.ramses_cc.binary_sensor: info
custom_components.ramses_cc.climate: info
custom_components.ramses_cc.climate_heat: info
custom_components.ramses_cc.sensor: info
custom_components.ramses_cc.water_heater: info
ramses_rf.processor: info
The custom_component...: info will cause a bunch of Found a... messages.
The ramses_rf.processor: info will show the packets received.
Look at the packet log (what boiler do you have?)
Thank you again for this help!
I’m sorry for not understanding more of this
@zxdavb I have a new installation, it works to some extent but I get a few weird errors in the log that I am yet to fully resolve, one of them is this.
Logger: ramses_rf.protocol.parsers
I — 08:133345 63:262142 --:------ 10E0 038 000002FF0803FFFFFFFEFFFFFFFF1D0307E64A61737065722045494D00000000000000000000 < Support the development of ramses_rf by reporting this packet, with the make/model of device: 08:133345 (device type 08 not known to have signature: 0002FF0803FFFFFFFE)
evofw3 gateway attributes list this device (08) as a “jasper interface” but I am unsure what that is, I wonder whether that is my Honeywell Y87RF wireless thermostat which is used to control an electrical heat zone / underfloor heating. I suspect this because this “jasper” device is not automatically discovered in the ramses_cc schema attributes
- ‘34:144349’:
class: thermostat- ‘13:129954’:
class: electrical_relay- ‘63:262143’:
class: hvac_device- ‘18:068640’:
class: gateway_interface- ‘31:025463’:
class: jasper_thermostat- ‘13:076108’:
class: electrical_relay- ‘08:133345’:
class: jasper_interface- ‘08:080414’:
class: jasper_interface- ‘31:050330’:
class: jasper_thermostat
Note: I am only using Honeywell Evohome devices, no faking, HVAC/ventilation.
I’am trying to update from 0.18.8 to 0.20.22g
changed my config from:
evohome_cc:
# scan_interval: 300
restore_cache: true
serial_port:
port_name: /dev/serial/by-id/usb-SHK_NANO_CUL_868-if00-port0
ramses_rf:
enforce_known_list: true
max_zones: 6
packet_log:
file_name: packet.log
rotate_bytes: null
rotate_backups: 7
# advanced_override: true
schema:
controller: 01:155341
known_list:
- 01:155341
- 04:008512
- 04:070150
- 04:070154
- 04:070160
- 04:073460
- 04:108167
- 04:108169
- 04:108171
- 04:108173
- 13:189740
- 18:203293
- 03:256005: {faked: true}
to:
ramses_cc:
scan_interval: 60
restore_cache: true
serial_port: /dev/serial/by-id/usb-SHK_NANO_CUL_868-if00-port0
packet_log:
file_name: packet.log
rotate_backups: 7
ramses_rf:
enforce_known_list: true
max_zones: 6
01:155341: {}
known_list:
01:155341
04:008512
04:070150
04:070154
04:070160
04:073460
04:108167
04:108169
04:108171
04:108173
13:189740
18:203293
03:256005: {faked: true}
But the last line gives me an error in studio code: bad indentadion of a mapping entry, but i can’t see whats wrong with it.
Does someone spot the error?
known_list needs ‘:’ on the end of each line, i.e.
01:155341:
thx that was it.
I was reading the wiki and this is unclear for me if i have to do something with it:
Unfortunately, ramses_rf cannot discover:
when the appliance_control: is an OTB (OpenTherm bridge)
when the zone sensor: is the controller
ramses_cc:
ramses_cc: 01:111111: system: appliance_control: 10:123446 # an OTB zones: "07": {sensor: 01:111111} # controller is the sensor
Does this mean if you use the controller as a temperature sonsor i the main zone that you need to set it in the configuration?
The temp for my main zone is available after the migration so i think i don’t have to do anything?
Migrated succesfully, i had to add my bdr91 to appliance control and class HGI to my nanocul otherwise i didn’t get an status sensor.
full config:
ramses_cc:
scan_interval: 60
restore_cache: true
serial_port: /dev/serial/by-id/usb-SHK_NANO_CUL_868-if00-port0
packet_log:
file_name: packet.log
rotate_backups: 7
ramses_rf:
enforce_known_list: true
01:155341:
system:
appliance_control: 13:189740
known_list:
01:155341: # Controller
04:008512:
04:070150:
04:070154:
04:070160:
04:073460:
04:108167:
04:108169:
04:108171:
04:108173:
13:189740: # BDR91 Ketel
18:203293: {class: HGI} # nanoCUL
03:256005: {faked: true} # BME680 Kantoor
I have a Nefit/Bosch boiler. this boiler does not support opentherm, but uses the EMS bus. to connect my OTB to the boiler i have to use a EMS-OT gateway. i am not sure if this gateway transmits all the sensor data an original OT boiler would transmit.
and how do i make mine look like that?
many thanks
If either of you had the time to make a Wiki article, that would be amazing!
Sure I’ll work on that but I only have the cloud integration fully functioning, the rames_cc integration remains a WIP. I am actually running both integrations concurrently on the same system.