-
Notifications
You must be signed in to change notification settings - Fork 71
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
HomematicIP #299
Comments
No. The whole HmIP stack is closed source.
I've never seen a HmIP device with a CC1101 rf module |
I bought an HMIP-RFUSB device with this chip:
…On Tue, 10 May 2022 at 13:51 Jérôme ***@***.***> wrote:
Does this library support HomematicIP?
No. The whole HmIP stack is closed source.
It also uses a CC1101 rf frontend
I've never seen a HmIP device with a CC1101 rf module
—
Reply to this email directly, view it on GitHub
<#299 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABM4WB3ZKSZF4LFUJ5MERKDVJJEUZANCNFSM5VQ32GJA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
just to add: HomeMatic Classic communication stack is also closed source AFAIK. But some details on the protocol were published over the years and the rest was reversed by a couple of smart people. |
Cool. All HmIP devices I've seen so far are using a CC1310.
just to add add... It wouldn't be possible to publish custom devices to the HmIP Server stack, because this is closed source. |
Does this library support HomematicIP? It also uses a CC1101 rf frontend and AES encryption...
The text was updated successfully, but these errors were encountered: