philips-hue
Here are 264 public repositories matching this topic...
-
Updated
Jun 21, 2020 - JavaScript
Should show a pop-up when the user's hardware isn't Entertainment-compatible and why / what they can do to solve it (if anything).
Reasons might be:
- Out-of-date firmware
- Gen 1 bridge
- Non-Philips, non-streamable ZigBee hardware
-
Updated
Jul 6, 2020 - JavaScript
Hello Everybody,
I am trying to run HomeGenie but my ports: 80 and port 8080 is already being used.
I found systemconfig.xml where I change the port: 80 to 85 but I could not find the hard-coded port:8080 to change. I went through the documents but could not find any related information hence my being asked for help. Now while HomeGenie is no longer using port:80 but is now locke
-
Updated
Jun 26, 2020 - C#
-
Updated
Jun 8, 2018 - Python
-
Updated
Jul 2, 2020 - Python
-
Updated
May 1, 2018 - Haskell
-
Updated
Jul 2, 2020 - Go
-
Updated
Jul 7, 2020 - TypeScript
-
Updated
May 4, 2020 - Go
-
Updated
May 6, 2020 - Python
-
Updated
Jun 22, 2020 - HTML
-
Updated
Jul 13, 2017 - JavaScript
-
Updated
Jan 20, 2018 - Ruby
-
Updated
May 27, 2020 - Go
-
Updated
May 17, 2020 - PHP
-
Updated
Jun 22, 2020 - Python
-
Updated
Jul 7, 2020 - Python
commit 681dc92d5c3baea2302f069e8cdae00ce822f8e8
OS: OS X 10.14.6
Actual Behaviour
After connecting the app to my Bridge (a hue Gen2) successfully, none of the lights/accessories/rooms/zones appeared. All values stayed at "0".
I had to quit Huebert and re-start it. Once I did, everything appeared and worked as expected.
Expected Behaviour
Once the app is connected to th
-
Updated
Jun 28, 2020 - Rust
-
Updated
Jan 19, 2020 - C#
-
Updated
Jan 9, 2019 - Ruby
-
Updated
Jun 29, 2020 - C#
-
Updated
May 13, 2020 - CoffeeScript
Improve this page
Add a description, image, and links to the philips-hue topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the philips-hue topic, visit your repo's landing page and select "manage topics."
Version of pytradfri
6.0.1
In #189 we started catching OSError because it could be raised from aiocoap. Aiocoap is starting to catch these errors themselves and wrapping them in
aiocoap.error.NetworkError. So we need to update our implementation to catch NetworkError besides OSError (not instead off just yet, as not all places have been wrapped yet in aiocoap).More info https://githu