Support for TRV10RFM and RX10RF #29
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've added support for TRV10RFM (radiator valve) and RX10RF (boiler receiver) as binary sensor devices to show when they are on/off.
Since they are categorised as sensors, the on/off value is read only, it cannot be set.
The exact models, TRV10RFM and RX10RF, are not mentioned in the response from the gateway, so it's likely that this change will add support for more than these two, but I only have these to test with. For example, there's TRV28RFM which looks like it only differs from TRV10RFM in the diameter of the attachment point. The exact models reported by the gateway are:
it600MINITRVit600ReceiverIn theory, both of them receive commands to open/close, but I haven't figured out a way to do it via the gateway API. There's also no way to control them from the mobile app, so my guess is that it's not possible at all to control them through the API.