Add support for port parameter #98
Open
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
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.
Hello guys,
thanks a lot for this great and useful project!
With this simple pull request, I'd like to add support for specifying a port parameter in the initializer of the Bridge.
Background: I have ZigBee hardware addon for the Raspberry Pi which is called RaspBee (https://www.dresden-elektronik.de/raspbee). The vendor provide a REST service that is compatible with Philips hue and that can run on an different port then the default 80. With the changes in this PR and some other changes in the "hue" component within the "Home Assistant" project (https://home-assistant.io), I am able to connect to that device and control the lights.