Skip to content
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

Open
unaiur opened this issue May 10, 2022 · 4 comments
Open

HomematicIP #299

unaiur opened this issue May 10, 2022 · 4 comments

Comments

@unaiur
Copy link

unaiur commented May 10, 2022

Does this library support HomematicIP? It also uses a CC1101 rf frontend and AES encryption...

@jp112sdl
Copy link
Collaborator

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

@unaiur
Copy link
Author

unaiur commented May 10, 2022 via email

@TomMajor
Copy link
Contributor

TomMajor commented May 10, 2022

No. The whole HmIP stack is closed source.

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.
In theory, the same would be possible for HmIP, but due to encryption and other "enhancements" this task will be far more difficult than for the Classic version.

@jp112sdl
Copy link
Collaborator

I bought an HMIP-RFUSB device with this chip

Cool. All HmIP devices I've seen so far are using a CC1310.

HomeMatic Classic communication stack is also closed source AFAIK
just to add

just to add add... It wouldn't be possible to publish custom devices to the HmIP Server stack, because this is closed source.
Wasn't clear in my first answer ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants