Closed daanroeterink closed 3 months ago
I’ve got the same problem.
Same issue here.
if I remove the fake remote from the configuration there is no problem (but then I do not have a remote).
I reverted back to 2024.07.4. Then the fake remotes works again.
I am experiencing the same issue as well.
I can look at this mid next week.
I have the same issue. When I remove the "commands" section from the configuration, it works. Maybe that helps in the investigation.
I am having the same issue The HVAC Orcon part stopt working after update. Evo home still works fine. the service: ramses_cc.send_command is missing in the developer tools ?
service: ramses_cc.send_command data: entity_id: remote.29_149235 command: high1h num_repeats: 3 delay_secs: 0.05
Yup same here, at the exact timestamp after an 'auto update' to the latest HASS "stable"-tag docker image on 07-08-2024 (which was 2024.8.0) the packet.log also stopped updating (likely related to the plugin not initializing). The docker image has been updated since then on 10-08 but error remains the same. Nothing really noteworthy in the releasenotes, and based on my inspection of the docker image layers between the current verstion and 2024.07 they both use python 3.12.4.
Additionally, after rolling back to 2024.7.4 this morning as reported by Daan it works again. Also I noticed the following log line when starting: The 'ramses_cc' option near /config/configuration.yaml:3 is deprecated, please remove it from your configuration
.
FYI my (messy, but exactly as-is) config
ramses_cc:
serial_port: /dev/ttyACM0
# serial_port: /share/Logs_SSD/homeassistant_symlinks/ttyEvoFw3
# restore_cache:
# restore_schema: false
# restore_state: true
packet_log:
file_name: evohome_rameses_logs/packet.log
rotate_backups: 7
ramses_rf:
enforce_known_list: true
disable_discovery: false
enable_eavesdrop: false
# enable_eavesdrop: true
01:176155:
system:
appliance_control: 10:133877
known_list:
18:071181: # gateway
01:176155: # controller
10:133877: # ketel?
03:123456: {class: THM, faked: true} # device type must be 03 (recommended), 12, 22 or 34
37:123456:
class: REM
faked: true
commands:
normal: ' I 073 --:------ --:------ 31:086097 22F1 003 000204'
boost: ' I 069 --:------ --:------ 31:086097 22F1 003 000404'
I have issued a fix to the library that I believe is responsible for this bug: https://github.com/alecthomas/voluptuous/pull/524
Works for me, thank you!
Hi, would you be OK with actually releasing this (instead of "pre-release" which it is now)? The HACS "store" still shows 0.41.23 as the latest version, so I can't auto-Update to this version which I would prefer over a manual update.
With the colder weathered here in the Netherlands I might actually need to run my heating system any day now, so having my "faked" temperature sensors up and running would be great :-)
Thanks!
Op za 17 aug 2024 om 23:47 schreef acseven @.***>
Works for me, thank you!
— Reply to this email directly, view it on GitHub https://github.com/zxdavb/ramses_cc/issues/198#issuecomment-2294994366, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA6CPHNIBMPJECBVMSGQKFTZR7AIVAVCNFSM6AAAAABMICAOXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHE4TIMZWGY . You are receiving this because you commented.Message ID: @.***>
Describe the bug Configuration error after updating to: Home assisstant 2024.8.0
To Reproduce Steps to reproduce the behaviour (for example):
Configuration
Exception
I already tried to add quotes to the value of class in the known_list entries but that didn't seem to do the trick.