Comments (11)
zxdavb
commented on September 23, 2024
MsgTransport.write(RQ --- 18:000730 01:072888 --:------ 002 0004): no dispatcher
These messages can be ignored - they were debug code, and have since been removed. The issue they were highlighting for me won't be affecting you.
from ramses_cc.
zxdavb
commented on September 23, 2024
You can stop obscuring your device_ids - there is no value in doing so (but do continue to do so if you wish).
from ramses_cc.
zxdavb
commented on September 23, 2024
Generally: please cut-and-paste text instead of providing screen captures.
from ramses_cc.
zxdavb
commented on September 23, 2024
Inconsistent schema: 04:056057 (02): None cant change parent (01:145038_02 (RAD)_02 to 01:145038_00 (RAD)_00) (try restarting the client library)
It really depends if this is a one-off, or it happens a often. If a one-off, then it likely to be a corrupt packet.
Otherwise: I cannot be 100% certain, unless I see a packet log form your system (please feel free to PM me one), but:
- this usually indicated that your system is configured incorrectly
An example would be where a TRV was - in the past - moved from one zone to another, but not removed form the old zone. The only way to remove a TRV from a zone (via the evohome UI) is to delete/recreate that zone.
from ramses_cc.
zxdavb
commented on September 23, 2024
If you want, PM me a packet log - or simply close this issue. Please tell me if you have eavesdropping on (generally: don't).
from ramses_cc.
jasperb-iot
commented on September 23, 2024
Hi, thank you for your replies and comments.
I indeed replaced one failing TRV once. It was never removed from the zone and the zone was never deleted. Do you suggest to delete the zone and add the current TVR's back?
I created this post because the restore cache doesn't work. If I disable restore from cache, everything is working fine. When cache is enabled everything is and stays unavailable. Is this caused by the removed TRV?
Eavesdropping is disabled. I enabled it during installation.
How can I create a packet log and PM it to you?
from ramses_cc.
zxdavb
commented on September 23, 2024
I indeed replaced one failing TRV once
It is a misconfigured TRV (child of two zones), not a missing TRV, that would cause this issue.
Send me a packet log, and/or the config/.storage/ramses_cc file - you can ask on the community forum for the details of this... or you try to simply re-create zone 0, zone 2 - I'd probably want to look at the schema first.
I created this post because the restore cache doesn't work.
Not sure - packet log please. It won't be cause by a missing TRV - there is no such concept.
How can I create a packet log and PM it to you?
Post a message on the community forum & I'll ping you
from ramses_cc.
jasperb-iot
commented on September 23, 2024
Hi,
After removing the affected zone and recreating it, the errors disappeared. I can now use the cache function.
2022-07-04 15:28:27 WARNING (MainThread) [custom_components.evohome_cc.schema] Using a Schema restored from cache: {'main_controller': '01:072888', '01:072888': {'system': {'heating_control': '13:090460'}, 'orphans': [], 'stored_hotwater': {}, 'underfloor_heating': {}, 'zones': {'00': {'_name': 'Woonkamer', 'zone_type': 'radiator_valve', 'zone_sensor': None, 'sensor_alt': None, 'devices': ['04:023497', '04:023501', '04:147405'], 'actuators': ['04:023497', '04:023501', '04:147405']}, '01': {'_name': 'Entree', 'zone_type': 'radiator_valve', 'zone_sensor': '04:023285', 'sensor_alt': '04:023285', 'devices': ['04:023285'], 'actuators': ['04:023285']}, '02': {'_name': 'Keuken', 'zone_type': 'radiator_valve', 'zone_sensor': '04:023503', 'sensor_alt': '04:023503', 'devices': ['04:023503'], 'actuators': []}, '03': {'_name': 'Zolder', 'zone_type': 'radiator_valve', 'zone_sensor': '04:147415', 'sensor_alt': '04:147415', 'devices': ['04:147415'], 'actuators': ['04:147415']}, '04': {'_name': 'Bijkeuken', 'zone_type': 'radiator_valve', 'zone_sensor': '04:023293', 'sensor_alt': '04:023293', 'devices': ['04:023293'], 'actuators': ['04:023293']}, '05': {'_name': 'Slaapkamer', 'zone_type': 'radiator_valve', 'zone_sensor': '04:023295', 'sensor_alt': '04:023295', 'devices': ['04:023295'], 'actuators': ['04:023295']}, '06': {'_name': 'Garderobe', 'zone_type': 'radiator_valve', 'zone_sensor': '04:023297', 'sensor_alt': '04:023297', 'devices': ['04:023297'], 'actuators': ['04:023297']}}}, 'orphans': [], 'device_hints': {}}
I do see invalid addresses in the packet log. I don't have devices which start with "37"
How can I avoid this? I have an allow list in configuration.yaml
configuration.yaml part:
#Honeywell HGI80
evohome_cc:
serial_port:
port_name: /dev/serial/by-id/usb-Texas_Instruments_TUSB3410_Boot_Device_TUSB3410-if00-port0
packet_log: evohome_cc.log
schema:
controller: 01:072888
restore_cache: true
ramses_rf:
restore_state: true
enable_eavesdrop: false
enforce_allowlist: true
enforce_known_list: true
allow_list:
- "04:023497": {"alias": "--Woonkamer raam--"}
- "04:023501": {"alias": "--Woonkamer convectie--"}
- "04:147405": {"alias": "--Woonkamer aquarium--"}
- "01:072888": {"alias": "--EVO Touch--"}
- "04:023285": {"alias": "Entree"}
- "04:147415": {"alias": "Zolder"}
- "04:023293": {"alias": "Bijkeuken"}
- "04:023295": {"alias": "Slaapkamer"}
- "04:023297": {"alias": "Garderobe"}
- "04:023503": {"alias": "Keuken"}
- "13:090460": {"alias": "heating_control"}
- "18:013466": {"alias": "HGI80"}
known_list:
- "04:023497": {"alias": "--Woonkamer raam--"}
- "04:023501": {"alias": "--Woonkamer convectie--"}
- "04:147405": {"alias": "--Woonkamer aquarium--"}
- "01:072888": {"alias": "--EVO Touch--"}
- "04:023285": {"alias": "Entree"}
- "04:147415": {"alias": "Zolder"}
- "04:023293": {"alias": "Bijkeuken"}
- "04:023295": {"alias": "Slaapkamer"}
- "04:023297": {"alias": "Garderobe"}
- "04:023503": {"alias": "Keuken"}
- "13:090460": {"alias": "heating_control"}
- "18:013466": {"alias": "HGI80"}
trace log attached.
from ramses_cc.
zxdavb
commented on September 23, 2024
Your config is a mix of the old scheme (<= 0.19.x) and the new (>= 0.20.x). For example, you only use one of known_list (newer) or allow_list (older), depending upon which version of the code you are using.
Below is the version for version 0.20.x.
You use enforce_known_list to exclude the orphan/alien devices from HA - note: they will still be still logged in the packet log - just ignore them.
FWIW - I have never seen so many 37:xxx devices (heat recovery/ventilation units) - you must be living in a block of apartments? DO you have a ventilation unit in your house?
evohome_cc:
serial_port:
port_name: /dev/serial/by-id/usb-Texas_Instruments_TUSB3410_Boot_Device_TUSB3410-if00-port0
packet_log: evohome_cc.log
restore_cache: true
ramses_rf:
enable_eavesdrop: false
enforce_known_list: true
schema:
controller: 01:072888
known_list:
- "01:072888": {"alias": "--EVO Touch--"}
- "04:023497": {"alias": "--Woonkamer raam--"}
- "04:023285": {"alias": "Entree"}
- "04:023293": {"alias": "Bijkeuken"}
- "04:023295": {"alias": "Slaapkamer"}
- "04:023297": {"alias": "Garderobe"}
- "04:023501": {"alias": "--Woonkamer convectie--"}
- "04:023503": {"alias": "Keuken"}
- "04:147405": {"alias": "--Woonkamer aquarium--"}
- "04:147415": {"alias": "Zolder"}
- "13:090460": {"alias": "heating_control"}
- "18:013466": {"alias": "HGI80"}
```
from ramses_cc.
jasperb-iot
commented on September 23, 2024
Hi,
thanks again.
There are three story apartments on the other side of the road, but not that many.
I have a ITHO ventilator unit in house which I control via MQTT. I have pulled the plug, 37:xxx messages are still coming in, so it's not this unit.
I guess I can just ignore it, right?
from ramses_cc.
zxdavb
commented on September 23, 2024
Yes: the known_list limits what is passed up to HA - you can ignore the packet log (which will have all packets seen by the USB dongle).
There must be at least two-dozen 37: devices...
One (some, if you have a remote, and/or a sensor) of them is yours - if you can work out which, then add it too... The ventilator's sensors will show up in HA as well (and soon, you will be able to control it via ramses_cc).
I suggest you run version 0.20.x (a beta/pre-release).
from ramses_cc.
Related Issues (20)
- Cant bind to my MVS-15R from orcon
- Entity climate.01:215596 (<class 'custom_components.ramses_cc.climate.RamsesController'>) implements HVACMode(s): heat, off, auto and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. HOT 1
- ramses_rf transmits too many packets per unit time HOT 4
- The integration is not tolerant of temporary issues with the packet source. HOT 8
- 0.31.16 Problem with the serial port: Transport did not initialise HOT 12
- 0.31.16 ramses_cc.get_zone_schedule service failing HOT 3
- Startup hangs with pyserial-asyncio-fast HOT 32
- 0.31.7 known_list does not filter out my next door neighbour's Evohome HOT 11
- [Question] What class to use for dual purpose device? HOT 2
- Packet log not rotating in config_flow HOT 3
- Warning: Detected that custom integration 'ramses_cc' accesses hass.helpers.storage HOT 1
- Missing sensor for bypass_mode Orchon 22f7
- Detected blocking call to open inside the event loop by custom integration 'ramses_cc' HOT 6
- All entities Unknown with Gateway status stuck on Problem HOT 13
- How to fake a Nuaire CO2 Sensor
- voluptuous.error.MultipleInvalid: not a valid value for dictionary value @ data['class'] after updating to 2024.8.0 HOT 12
- Ramses_CC stopped working after HA update 2024.8.2 HOT 3
- Entity supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature
- `Accept packets from known devices IDs only` causes exception HOT 4
- Detected blocking call ... inside the event loop
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ramses_cc.