Open pocketware opened 11 months ago
Update: No packages received after 2023-09-26T20:36:31.636218. Current time is: 2023-09-26T20:57:35
Log:
2023-09-26 20:36:31.637 INFO (MainThread) [ramses_rf.dispatcher] RQ --- 18:070670 32:161205 --:------ 22F4 001 00 < Invalid code for 32:161205 (FAN) to Rx/Tx: 22F4
2023-09-26 20:37:16.493 INFO (MainThread) [custom_components.ramses_cc.coordinator] Saving the client state cache (packets, schema)...
2023-09-26 20:42:16.493 INFO (MainThread) [custom_components.ramses_cc.coordinator] Saving the client state cache (packets, schema)...
2023-09-26 20:47:16.494 INFO (MainThread) [custom_components.ramses_cc.coordinator] Saving the client state cache (packets, schema)...
2023-09-26 20:52:16.495 INFO (MainThread) [custom_components.ramses_cc.coordinator] Saving the client state cache (packets, schema)...
2023-09-26 20:57:16.495 INFO (MainThread) [custom_components.ramses_cc.coordinator] Saving the client state cache (packets, schema)...
I see nothing wrong with the configuration / packet logs you have provided.
I would suggest you utilize the cache (rather than disabling it):
restore_cache: true # recommended
No matter which option you choose, keep:
ramses_cc:
serial_port: /dev/serial/by-id/usb-SparkFun_evofw3_atmega32u4-if00
packet_log: packet.log
ramses_rf:
enforce_known_list: true
orphans_hvac: [18:070670, 32:161205, 29:179059]
known_list:
32:161205: {class: FAN}
18:070670: {class: HGI}
29:179059: {class: REM}
I believe the codes you want are 22F1
and 22F3
(rather than says 22F2
, 22F4
), no?
Adding configuration like commands:, faked: etc. or enabling send_package is causing issues.
You don't make clear what issues you're having. What are you seeing, and what do you expect to see, instead?
For example:
Invalid code for 32:161205 (FAN) to Rx/Tx: 22F4
I assume you've created an automation, or some such? AFAIK, almost all FANs don't deal with 22F2/22F4 commands, so this message (which is not an error) is correct.
Hello David,
Using a config without the orphans_hvac and known_list items the SSM-D2 is generation log records in de package.log file. No issues with this config, except I don't get any sensors in HomeAssistant; which is correct, because there is no configuration.
When I add the orphans_hvac and known_list items the capturing is working for a few minutes. After I get the RQ messages in the log with the invalid code the device stops working.
I don't have any automation configured. Just want to see the sensors from my Orcon HRC-300-EcoMax. That's why I have the
send_packet: false
in the config.
I really dont know where the invalid code requests are coming from; I suppose the ramses_rf or ramses_cc code.
Please send me a packet log, minimum 24h, but longer is better.
You can post (say) file hosting links here if you're willing, or PM me that stuff via community.home-assistant.io: I am zxdavb
In the home-assistant.log:
I have a lot of issues with the SSM-D2 from Peter Price. Maybe this is the cause of it...
Retrieving data with a a almost empty configuration:
is working without any issues. Getting all kind of logs in de packet.log file.
After adding configuration to retrieve (and send) command my system hangs after a while. No log captured anymore and also my other 868MHz devices aren't working anymore. Seems that the SSM-D2 keeps sending packages.
Current config is:
With this configuration I'm getting data (after resetting HomeAssistant and the SSM serveral times).
Adding configuration like commands:, faked: etc. or enabling send_package is causing issues.
Also enabled extra logging with:
Log after last reboot (only Ramses lines):