Comments (4)
Hey, this is very interesting! Oddly, I have a ventilation system at home, so I already have the following in https://github.com/zxdavb/evohome_rf/tree/add_state (see below).
In my case, the devices are 30:
(the mechanical vent) and 32:
(Humidity sensor, Switch).
First thing I'm going to do is parse the payloads!
@parser_decorator
def parser_31d9(payload, msg) -> Optional[dict]:
assert len(payload) / 2 == 17 # usu: I 30:-->30:, with a seq#!
assert payload[:2] == "21" # domain
assert payload[2:] == "00FF0000000000000000000000000000"
return {
"zone_idx" if int(payload[:2], 16) < 12 else "domain_id": _id(payload[:2]),
"unknown_0": payload[2:],
}
@parser_decorator
def parser_31da(payload, msg) -> Optional[dict]: # UFH HCE80 (Nuaire humidity)
assert len(payload) / 2 == 29 # usu: I CTL-->CTL
assert payload[:2] == "21" # domain
return {
"zone_idx" if int(payload[:2], 16) < 12 else "domain_id": _id(payload[:2]),
"relative_humidity": _cent(payload[10:12]),
"unknown_0": payload[2:10],
"unknown_1": payload[12:],
}
from ramses_protocol.
And decoded, they are:
20:001414 | 20:001414 | I | message_31da | 00EF0... || {'zone_idx': '00', 'relative_humidity': 2.39, 'unknown_0': 'EF007FFF', 'unknown_1': 'EF7FFF7FFF7FFF7FFFF000EF0251000000EFEF7FFF7FFF'}
20:001414 | 20:001414 | I | message_31d9 | 00065... || {'zone_idx': '00', 'unknown_0': '06510020202020202020202020202000'}
20:001414 | 20:001414 | I | device_info | 00000... || {'description': 'CVE-RF', 'firmware': None, 'manufactured': '2015-05-12', 'unknown': '000001001B221201FEFF'}
from ramses_protocol.
@gitkomodo Just to clarify something said above - some packets are 'known', just not documented in this wiki, yet. In addition, packets may be 'known', but not yet fully understood - the authorative reference might be here (this is missing only .0404
and 0006
parsers
I have been too busy on other projects to finish updating the wiki...
What code are you running to collect your packets? Is there any chance you could send me 24h of a packet log using https://github.com/zxdavb/evohome_rf? Especially of the packets to/from 20:
devices? There is another related packet, 31E0
(and possibly others).
If so, then I can suggest the bleeding_edge branch. If you're collecting them via another tool, I would still like to see them - maybe you could reformat them into the 'standard' format:
2020-05-13T01:16:45.808427 095 RQ --- 18:013393 01:145038 --:------ 1F09 001 00
... or as near as you can get?
from ramses_protocol.
Closing - these packets (31D9
, 31DA
) are better understood, but still a WIP.
from ramses_protocol.
Related Issues (6)
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_protocol.