-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Orcon ventilation: 31D9 payload not recognized, wrong fan modes #45
Comments
Here's a more complete trace, trying all the buttons on my remote:
The replies are now different (000001FE instead of 00000100, etc). |
The issue is that none of this protocol is documented. I have updated the code, so that it can parse your packet log without error/warning. I will be dropping a refactored build soon. The client.py is for ad-hoc, you can:
I will reach out to you shortly, when I have capacity |
Thanks, confirmed that current master parses the
|
BTW, the fan modes may be wrong for your orcon-compatible HRU (or the 15RF), but they were OK for the system I had access to before (a Nuaire PIV)... I think the way forward is to get it working with your system, then use the |
@maleadt The time has come to get remotes working... Please tell me the make/model of your remote The latest version of the client.py has a new switch, |
@llevering could you tell me the exact make/model of your remote and your vent unit? Or is it a fancy CO2 sensor? |
An Orcon 15RF (the device also mentions VMN-15LF01, 21800000, 2002, H6S9). The plain model, without CO2 sensor. |
@llevering Can you confirm your remote does not have a CO2 sensor - it looks like it has one to me:
It also has a movement/presence sensor? Or maybe that device isn't yours? |
I can confirm it does not have a co2 sensor. There are versions that have one but it ours doesn't.
…________________________________
From: David Bonnes ***@***.***>
Sent: Tuesday, July 5, 2022 6:41:34 PM
To: zxdavb/ramses_rf ***@***.***>
Cc: llevering ***@***.***>; Mention ***@***.***>
Subject: Re: [zxdavb/ramses_rf] Orcon ventilation: 31D9 payload not recognized, wrong fan modes (Issue #45)
@llevering<https://github.com/llevering> Can you confirm your remote does not have a CO2 sensor - it looks like it has one to me:
2021-11-28T09:46:51.619824 083 I --- 37:258565 37:261128 --:------ 22F1 003 000404
2021-11-28T09:48:40.337879 082 I --- 37:258565 --:------ 37:258565 1298 003 0002F7
2021-11-28T09:49:33.668304 085 I --- 37:258565 37:261128 --:------ 31E0 004 00000100
2021-11-28T09:49:41.282669 082 I --- 37:258565 --:------ 37:258565 1298 003 00030B
2021-11-28T09:49:48.897074 081 I --- 37:258565 37:261128 --:------ 2E10 003 000100
—
Reply to this email directly, view it on GitHub<#45 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAVUDMVGGMC6HHHKUGCYDBDVSRQT5ANCNFSM5VPRAXJA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
May I have a copy of your |
No response - closing. |
I'm looking into using this (awesome!) software with my Orcon HRC-350 (sold to me under the brand Ventiline) through an Arduino running evofw3, and am encountering a couple of issues.
The first is a payload that isn't recognized. When I set the ventilation fan speed to respectively away, 1, 2, 3, or auto, encoded as fan modes 0 to 4, my unit responds with a 31D9 message where the payload is simply either 00000000, 00000100, 00000200, 00000300 or 00000400. That doesn't match the regex in
ramses.py
, which seems to expect much more data:This also shows that the fan modes are not mapped correctly: 0 is away, 1-3 match fan speed 1 to 3, and 4 should be auto (fan speed determined by air humidity).
The much more complicated 31DA packets are fully recognized though 🙂 The rendering in the CLI is cut off though (maybe it could drop fields that are known to be bogus for this model?):
Finally, I also encountered the following packet with a prompt to file an issue:
Let me know if you need additional information.
The text was updated successfully, but these errors were encountered: