Looks amazing! adding boiler/heat would be nice addition, love to try it out.
Hi, since Iâve upgraded my hot water automation stopped working because of the condition being off which has changed to auto so it always failed.
Below is a new automation if anyone is interested.
id: '1642243052302'
alias: Hot Water
description: ''
trigger:
- platform: numeric_state
below: '46'
entity_id: sensor.07_053048_temperature
condition:
- condition: template
value_template: '{{ state_attr("water_heater.stored_hw", "mode").active == false }}'
action:
- service: water_heater.set_operation_mode
data:
operation_mode: boost
target:
entity_id: water_heater.stored_hw
mode: single
Everyone - please donât PM me unless I ask you to. Ask others for help first, in this forumâŚ
Please create/use a known_list, and enforce it.
Please use the smallest schema you can get away with - see the 18:xxxxxx status state attrs for a suggested minimal schema.
Please use the schema/state cache.
If anyone is able to help with the development of the HA integration, I would be grateful.
Iam sorry but you asked me to mail you personal last Monday to mail but I can confirm that itâs all working fine now I did the minimal scheme as you suggested thanks I told you I was not at home until friday
@wim001 The above doesnât apply to you in this instance - I asked you to PM me.
The request is because I do not have capacity to provide support to all - if they post here, others will be able to chip in with an answer, hopefully.
IN your case, I would still like you to PM me your configuration.yaml - I am seeking why ramses_rf produced the log files of your system with the specific nuances that I have seen.
I have just released 0.20.22f, it addresses all known bugs.
I have had to make more changes to the codebase that I would like, and hope I have not introduced any new issues. Please report any new bugs here.
I have been unable to reproduce some reported bugs, as below, so feedback that these persist / have been resolved would be appreciated:
22/09/12_1: The binary sensor for the gateway (e.g. 18:140805 status) appears unavailable for some.
22/08/00_1: (maybe fixed by 0.20.22a) I am not sure why this is happening - the code was written to handle this issue:
File "/config/custom_components/ramses_cc/climate_heat.py", line 138, in hvac_mode
if self._device.tcs.system_mode[CONF_SYSTEM_MODE] == SystemMode.AWAY:
TypeError: 'NoneType' object is not subscriptable
22/08/00_2: This is under investigation - appears only on startup? The system appears to behave normally otherwise.
File "/usr/local/lib/python3.10/site-packages/ramses_rf/gateway.py", line 545, in check_filter_lists
and dev_id != self.pkt_protocol._hgi80[SZ_DEVICE_ID]
AttributeError: 'NoneType' object has no attribute '_hgi80'
I saw that I configured the configuration.yaml file wrong I changed it yesterday evening and now all is working fine I see the water pressure now
Updated to 0.20.22f:
- 18_ gateway device doesnât seem to have appeared
- I see the below in the logs:
Logger: ramses_rf.protocol.schemas
Source: custom_components/ramses_cc/coordinator.py:119
Integration: RAMSES RF ([documentation](https://github.com/zxdavb/ramses_cc), [issues](https://github.com/zxdavb/ramses_cc/issues))
First occurred: 09:46:09 (1 occurrences)
Last logged: 09:46:09
`There should be only one HGI in the known_list: ['01:050858', '04:055594', '04:055514', '03:055594', '04:055596', '03:055596', '04:055510', '03:055510', '04:055480', '03:055480', '04:055506', '03:055506', '04:055486', '03:055486', '04:055482', '03:055482', '04:055600', '07:014869', '18:141846', '13:215029', '13:246213']`
Could this be the reason? I only see 1x 18:xxxxx device in the known_list?
- 01, controller
- 04, TRVs
- 03, faked Xiaomi BLE sensors
- 07, hot water sensor
- 13, boiler relays
- 18, 1x nanocul
Config below, for completeness:
ramses_cc:
restore_cache: true
scan_interval: 180
serial_port:
port_name: /dev/serial/by-id/usb-SHK_NANO_CUL_868-if00-port0
baudrate: 57600
packet_log:
file_name: /config/packet.log
rotate_backups: 3
ramses_rf:
enforce_known_list: true
max_zones: 8
01:050858:
zones:
"07": {sensor: 01:050858} # The Controller is the sensor for Hallway
known_list:
01:050858: # Controller
04:055594: # Living Room Rad 1
04:055514: # Living Room Rad 2
03:055594: {faked: true} # Living Room Xiaomi Faked Sensor
04:055596: # Front Room
03:055596: {faked: true} # Front Room Xiaomi Faked Sensor
04:055510: # Utility
03:055510: {faked: true} # Utility Xiaomi Faked Sensor
04:055480: # Guest Room
03:055480: {faked: true} # Guest Room Xiaomi Faked Sensor
04:055506: # Master Bedroom
03:055506: {faked: true} # Master Bedroom Xiaomi Faked Sensor
04:055486: # E Office
03:055486: {faked: true} # E Office Xiaomi Faked Sensor
04:055482: # Y Office
03:055482: {faked: true} # Y Office Xiaomi Faked Sensor
04:055600: # Hallway
07:014869: # Stored Hot Water
18:141846: # nanoCUL
13:215029: # Stored Hot Water Relay
13:246213: # Central Heating Relay
It is not clear to me why this warning is being issued, but try setting the device class of the nanoCUL:
known_list:
...
18:141846: {class: HGI} # nanoCUL
Let me know.
Bingo, I now have a status entity - much obliged:
binary_sensor.18_141846_status
But I still had/have this warning on restart:
Logger: ramses_rf.protocol.schemas
Source: custom_components/ramses_cc/coordinator.py:119
Integration: RAMSES RF ([documentation](https://github.com/zxdavb/ramses_cc), [issues](https://github.com/zxdavb/ramses_cc/issues))
First occurred: 13:10:11 (1 occurrences)
Last logged: 13:10:11
There should be only one HGI in the known_list: ['01:050858', '04:055594', '04:055514', '03:055594', '04:055596', '03:055596', '04:055510', '03:055510', '04:055480', '03:055480', '04:055506', '03:055506', '04:055486', '03:055486', '04:055482', '03:055482', '04:055600', '07:014869', '18:141846', '13:215029', '13:246213']
I have identified the cause of this bug - it is only a warning - it does not change the behaviour of the integration.
I will push a fix shortly enough.
Hi,
Can you tell me if you managed to sort this out? I have exactly the same problem and have not managed to solve it yet
Just to be sure I understand correctly your problem:
After adding the custom repo in HACS when you search in HACS using the term ramses you do not see the integration ?
Iâve just tested on my side on a different system on which this integration is not installed yet and I can find the custom repo in HACS. The integration will not appear as a tile in the integration panel of home assistant. You see it only in the integration of HACS (I say this just in case you are searching in the wrong integration page). If this does not work I have no clue whatâs wrong, sorry âŚ
Thanks for the reply. To be honest I am a really new user of HA so I am just learning the ropes.
When I go to HACS integrations I see the Ramses CC tile. I know it is installed as I got an update message for it today. According to the installation wiki the next steps are:
Add ramses_cc as an Integration via HACS
- select HACS (side panel), Integrations
- click the Explore & Add Repositories button
- search for ramses
- click on Honeywell RFâŚ
- click on Install this Repository in HACS, then Install
- restart the HA Core
Configure ramses_cc
It is this section that I cannot seem to find, when I search for âRamsesâ nothing is found and therefore I cannot click on Honeywell RF. Sorry if this is a stupid question!
If you have the tile with Ramses CC in HACS and it said to update today, it means you have already successfully installed the integration. You should not need to install anything else.
Now you can configure your integration by adding the required configuration in your configuration.yaml file (as described on the wiki here )
Coming soon (next beta):
service: ramses_cc.get_zone_schedule
data:
entity_id: climate.main_room
âŚand:
{{ state_attr('climate.main_room', 'schedule_version') }}
{{ state_attr('climate.main_room', 'schedule') }}
âŚthere is also: ramses_cc.set_zone_schedule.
Of course, all the above is also available for DHW.
All sorted now - thanks for your help.
I have 2 controllers⌠If I comment any one of them, it works. If I have both uncommented, only the first one works.
Is it not possible to add multiple controllers into this with one HA?
The integration only supports one controller. I also have 2, and run the 2nd one off the online integration. I recall that it used to be possible to copy/duplicate the custom_component and name it differently, e.g. ramses_dd, also guessing you would need a 2nd radio.