[Major Announcement] ConnectedRoom Hub for Windows, macOS and Linux
Philips Hue integration is not working anymore due to API limits having been reached. The growing volume of ConnectedRoom makes us hit every limit possible, and companies like Philips are limiting us on their API.
Decentralization of ConnectedRoom
Volume of users is growing very fast and caught us by surprise. Many limits of many third party tools we use have been reached too quickly. As a business, these are growing expenses that need to be taken care of quickly. Lights need to be running locally on the user’s network, or it will be an endless fight against API usage.
Physical Hub vs Software Hub
Because we do not feel good about requiring a purchase to all of our existing customers, we decided 5 weeks ago to start the development of a software version of the ConnectedRoom Hub that will be able to be running on existing computers, or servers.
A new product line will be announced this week concerning this, one that will be physical and require a purchase, and a DIY version that will be able to run on existing Windows, macOS and Linux installs. Stay tuned in the app, on social media to learn about our new solution to run lights locally and the decentralization of ConnectedRoom.
If you have ConnectedRoom OS, simply pair the ConnectedRoom Hub and Philips Hue lights will start working again, bypassing existing limits.
DIY openness
ConnectedRoom’s vision is to simplify the access to automation to everybody, while also keeping it advanced enough for power users to push further. This is why a headless version of the ConnectedRoom Hub will be available to run on Linux servers as well, including Virtual Machine images for tech-savvy users that wants to run their lights locally on their existing infrastructure.
Log in to comment and vote
Comments12
Robert
Sep 20
My ConnectedRoom OS can’t be connected after this update. I added screenshots to the Change log post.
Guillaume
Sep 20
Hi Robert, I found the issue
The new update is building.
I will let you know when it is available. Sorry about that
Robert
Sep 20
All good. Everything still working good today.
Robert
Sep 20
Did the update and restarted a few times. Still unable to connect to ConnectedRoom OS hub. Phone still doesn’t even give the option, web just shows “Scanning…”
Michael
Sep 21
This is really great! Question: If we’re running ConnectedRoom OS on a Raspberry PI should we be installing the Linux version of Hub onto that device or should we be using the Pair ConnectedRoom OS hub feature?
Michael
Oct 14
@Guillaume Forgive me; I’m very much a novice with this stuff. Is ConnectedRoom Hub a standalone app or does it need to be installed on a machine running ConnectedRoom OS?
Guillaume
Oct 14
@Michael both. It comes bundled with ConnectedRoom OS, but is also available to be downloaded on macOS, Window and Linux as standalone app. It is available in the app in the Hub tab. A landing page will be created for the Hub and everything will be explained in details. There are simply so many new features coming and quickly too. The updates will keep chaining up every week for the next 2 years.
Michael
Oct 21
@Guillaume Update: was able to get my WLED theatre lights working this weekend using a Raspberry Pi 5 running ConnectedRoom OS functioning as the Hub. Thank you!
Bradley
Sep 21
I am able to work with the new hub and my Philips light system, however in the recent email announcement, it shows the ability to connect to “Entertainment Areas” created in the Philips Hue app. I have tried to sort this out and have been unable to figure out how to do this. Any clarification would be helpful. Thanks.
Guillaume
Sep 21
Hi Bradley, thank you for your feedback.
This is currently a bug, but you can achieve this by disconnecting the Hue integration in the app.
Then on the Hub App, you can connect it again using the Setup On Local Network button.
You have 30 seconds to press the bridge button, but this will be increased in next update when the bridge is in a completely different room.
After that, the Entertainment Area will appear in your Actions when you click Add Devices+
Bradley
Sep 21
Thank you
Richard
Sep 26
2026-09-26T21:17:09.981Z [hub] Pusher: connecting -> connected
2026-09-26T21:17:09.982Z [hub] Socket set up
2026-09-26T21:17:10.173Z Hub started...
2026-09-26T21:17:10.302Z [hue] integration loaded — discovery order: configured IP, last known address, mDNS, discovery service, subnet scan
2026-09-26T21:17:10.505Z [hue] using the configured bridge address 192.168.0.191
2026-09-26T21:17:10.633Z [hue] local control ready via bridge ? at 192.168.0.191
2026-09-26T21:17:10.633Z [hue] entertainment streaming available
2026-09-26T21:17:10.709Z Setting up heartbeat...
2026-09-26T21:17:10.788Z [govee] INFO sniffer listening on UDP port 4003
2026-09-26T21:17:10.789Z [govee] INFO LAN binding to network interface 192.168.0.111
2026-09-26T21:17:10.789Z [govee] DEBUG LAN listening on port 4002
2026-09-26T21:17:10.828Z [govee] DEBUG LAN: Found H619E (0C:D7:D0:05:C0:46:1F:1C) at 192.168.0.195
2026-09-26T21:17:10.840Z [govee] DEBUG LAN: Found H610A (17:1F:EF:2F:44:C6:35:37) at 192.168.0.240
2026-09-26T21:17:10.840Z [govee] DEBUG LAN: Found H610A (09:EC:EF:2F:45:46:46:0E) at 192.168.0.203
2026-09-26T21:17:10.852Z [govee] DEBUG LAN: Found H6022 (3F:06:D0:03:C1:86:2C:4F) at 192.168.0.67
but the hub says no govee lights were found. Is this a bug?