Telldus link #1107
Closed
Telldus link #1107
Conversation
This file contains hidden or 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
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.
The link to the compatiblity list on https://home-assistant.io/components/tellstick/ leads to a 404 page, since telldus started to move away from 433MHz radio technology towards zwave technology.
The best resource to get hardware compatibility is the protocol example list in the telldus developer wiki, so i changed the dead link to this list.
Please note the 2 commits from Sep 19, which are basically handled in #959. Somehow i got a merge conflict between my origin and upstream and fixed it - and they ended up appearing in this branch as well. I'm sorry for that.
You will notice that there is no difference between these commits in this pull request and the ones already merged in #959, so git should just ignore these commits when merging.