rkkoszewski
commented
4 years ago Here is in contrast how it looks when I use the "Hue Stream" app for mobile.
192.168.250.210 - - [31/Dec/2019 02:55:12] "PUT /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups/2 HTTP/1.1" 200 -
. Seeding the random number generator... ok
. Loading the CA root certificate ... ok (0 skipped)
. Loading the server cert. and key... ok
. Bind on udp://*:2100/ ... ok
. Setting up the SSL/TLS structure... ok
. Waiting for a remote connection ...192.168.250.210 - - [31/Dec/2019 02:55:12] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:12] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:13] "PUT /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups/2 HTTP/1.1" 200 -
interrupted by SIGTERM (in net_accept())
. Cleaning up... done.
127.0.0.1 - - [31/Dec/2019 02:55:13] "PUT /api/0681c8642b7511eaac2dd6bfcb9e0f40/groups/2/action HTTP/1.1" 200 -
127.0.0.1 - - [31/Dec/2019 02:55:13] "PUT /api/0681c8642b7511eaac2dd6bfcb9e0f40/groups/2/action HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:14] "PUT /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups/2 HTTP/1.1" 200 -
. Seeding the random number generator... ok
. Loading the CA root certificate ... ok (0 skipped)
. Loading the server cert. and key... ok
. Bind on udp://*:2100/ ... ok
. Setting up the SSL/TLS structure... ok
. Waiting for a remote connection ...127.0.0.1 - - [31/Dec/2019 02:55:14] "PUT /api/0681c8642b7511eaac2dd6bfcb9e0f40/groups/2/action HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:14] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:14] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups HTTP/1.1" 200 -
ok
. Performing the SSL/TLS handshake... hello verification requested
. Waiting for a remote connection ... ok
. Performing the SSL/TLS handshake... ok
[ Protocol is DTLSv1.2 ]
[ Ciphersuite is TLS-PSK-WITH-AES-128-GCM-SHA256 ]
[ Record expansion is 37 ]
[ Maximum fragment length is 16384 ]
. Verifying peer X.509 certificate... ok
192.168.250.252 - - [31/Dec/2019 02:55:26] "GET /description.xml HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:28] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/config HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:29] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40 HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:29] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:29] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups HTTP/1.1" 200 -
{"ok"}
192.168.250.210 - - [31/Dec/2019 02:55:34] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:34] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:40] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/config HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:40] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40 HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:40] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:40] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/groups HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:40] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/sensors HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:41] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/config HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:41] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:41] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/groups HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:41] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/sensors HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:41] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/config HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:43] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/config HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:43] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40 HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:43] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:43] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:48] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/config HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:48] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40 HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:49] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:49] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/groups HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:49] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/sensors HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:49] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/config HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:51] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:51] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/groups HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:52] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:52] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/groups HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:52] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/sensors HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:52] "GET /api/56abf1382b7611eaac2dd6bfcb9e0f40/config HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:53] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/config HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:53] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40 HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:53] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:53] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups HTTP/1.1" 200 -
connection was closed gracefully
. Closing the connection... done
. Waiting for a remote connection ... interrupted by SIGTERM (in net_accept())
. Cleaning up... done.
192.168.250.210 - - [31/Dec/2019 02:55:59] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 02:55:59] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups HTTP/1.1" 200 -
{"ok"}
192.168.250.252 - - [31/Dec/2019 02:56:25] "GET /description.xml HTTP/1.1" 200 -
{"ok"}
{"ok"}
192.168.250.252 - - [31/Dec/2019 02:57:25] "GET /description.xml HTTP/1.1" 200 -
{"ok"}And the debug log:
root@huebridge:/opt/hue-emulator# python3 HueEmulator3.py --debug
2019-12-31 03:03:09,794 - root - INFO - Using Host 192.168.250.230:80
2019-12-31 03:03:09,809 - root - INFO - d6bfcb9e0f40
2019-12-31 03:03:09,810 - root - INFO - IP range for light discovery: 0-255
2019-12-31 03:03:09,810 - root - INFO - 127.0.0.1
2019-12-31 03:03:09,811 - root - INFO - Online Discovery/Remote API Enabled!
2019-12-31 03:03:09,813 - root - INFO - Config loaded
2019-12-31 03:03:09,816 - root - DEBUG - start ssdp broadcast
2019-12-31 03:03:09,819 - root - INFO - sync with lights
2019-12-31 03:03:09,822 - root - DEBUG - starting ssdp...
2019-12-31 03:03:09,830 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.250.231:80
2019-12-31 03:03:09,833 - root - INFO - Starting httpd...
2019-12-31 03:03:09,836 - root - INFO - Starting ssl httpd...
2019-12-31 03:03:09,841 - urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): discovery.diyhue.org:443
2019-12-31 03:03:09,843 - urllib3.connectionpool - DEBUG - http://192.168.250.231:80 "GET /state HTTP/1.1" 200 91
2019-12-31 03:03:10,097 - urllib3.connectionpool - DEBUG - https://discovery.diyhue.org:443 "POST / HTTP/1.1" 200 6
{"ok"}
2019-12-31 03:03:14,737 - root - DEBUG - Sending M-Search response to 192.168.250.252
192.168.250.252 - - [31/Dec/2019 03:03:14] "GET /description.xml HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 03:03:15] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/config HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 03:03:15] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40 HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 03:03:16] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 03:03:16] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups HTTP/1.1" 200 -
2019-12-31 03:03:16,231 - root - DEBUG - Sending M-Search response to 192.168.250.252
2019-12-31 03:03:17,734 - root - DEBUG - Sending M-Search response to 192.168.250.252
192.168.250.210 - - [31/Dec/2019 03:03:18] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups/2 HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 03:03:18] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups/3 HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 03:03:18] "PUT /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups/2 HTTP/1.1" 200 -
2019-12-31 03:03:18,540 - root - INFO - in PUT method
2019-12-31 03:03:18,541 - root - INFO - /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups/2
2019-12-31 03:03:18,541 - root - INFO - b'{"stream":{"active":true}}'
2019-12-31 03:03:18,543 - root - INFO - start hue entertainment
. Seeding the random number generator... ok
. Loading the CA root certificate ... ok (0 skipped)
. Loading the server cert. and key... ok
. Bind on udp://*:2100/ ... ok
. Setting up the SSL/TLS structure... ok
. Waiting for a remote connection ...192.168.250.210 - - [31/Dec/2019 03:03:18] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 03:03:18] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups HTTP/1.1" 200 -
2019-12-31 03:03:19,051 - root - INFO - [
{
"success": {
"/groups/2/stream": {
"active": true
}
}
}
]
192.168.250.210 - - [31/Dec/2019 03:03:19] "PUT /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups/2 HTTP/1.1" 200 -
2019-12-31 03:03:19,082 - root - INFO - in PUT method
2019-12-31 03:03:19,082 - root - INFO - /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups/2
2019-12-31 03:03:19,083 - root - INFO - b'{"stream":{"active":false}}'
2019-12-31 03:03:19,084 - root - INFO - stop hue entertainent
interrupted by SIGTERM (in net_accept())
. Cleaning up... done.
2019-12-31 03:03:19,393 - root - INFO - [
{
"success": {
"/groups/2/stream": {
"active": false
}
}
}
]
2019-12-31 03:03:19,395 - root - INFO - rule 1 is triggered
2019-12-31 03:03:19,405 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 127.0.0.1:80
127.0.0.1 - - [31/Dec/2019 03:03:19] "PUT /api/0681c8642b7511eaac2dd6bfcb9e0f40/groups/2/action HTTP/1.1" 200 -
2019-12-31 03:03:19,409 - root - INFO - in PUT method
2019-12-31 03:03:19,410 - root - INFO - /api/0681c8642b7511eaac2dd6bfcb9e0f40/groups/2/action
2019-12-31 03:03:19,410 - root - INFO - b'{"scene": "13"}'
2019-12-31 03:03:19,414 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.250.231:80
2019-12-31 03:03:19,429 - urllib3.connectionpool - DEBUG - http://192.168.250.231:80 "PUT /state HTTP/1.1" 200 12
2019-12-31 03:03:19,717 - root - INFO - [
{
"success": {
"/groups/2/action/scene": "13"
}
}
]
2019-12-31 03:03:19,718 - root - INFO - rule 1 is triggered
2019-12-31 03:03:19,725 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 127.0.0.1:80
2019-12-31 03:03:19,727 - urllib3.connectionpool - DEBUG - http://127.0.0.1:80 "PUT /api/0681c8642b7511eaac2dd6bfcb9e0f40/groups/2/action HTTP/1.1" 200 45
127.0.0.1 - - [31/Dec/2019 03:03:19] "PUT /api/0681c8642b7511eaac2dd6bfcb9e0f40/groups/2/action HTTP/1.1" 200 -
2019-12-31 03:03:19,734 - root - INFO - in PUT method
2019-12-31 03:03:19,734 - root - INFO - /api/0681c8642b7511eaac2dd6bfcb9e0f40/groups/2/action
2019-12-31 03:03:19,735 - root - INFO - b'{"scene": "13"}'
2019-12-31 03:03:19,739 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.250.231:80
2019-12-31 03:03:19,756 - urllib3.connectionpool - DEBUG - http://192.168.250.231:80 "PUT /state HTTP/1.1" 200 12
192.168.250.210 - - [31/Dec/2019 03:03:19] "PUT /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups/2 HTTP/1.1" 200 -
2019-12-31 03:03:19,945 - root - INFO - in PUT method
2019-12-31 03:03:19,946 - root - INFO - /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups/2
2019-12-31 03:03:19,947 - root - INFO - b'{"stream":{"active":true}}'
2019-12-31 03:03:19,948 - root - INFO - start hue entertainment
. Seeding the random number generator... ok
. Loading the CA root certificate ... ok (0 skipped)
. Loading the server cert. and key... ok
. Bind on udp://*:2100/ ... ok
. Setting up the SSL/TLS structure... ok
. Waiting for a remote connection ...2019-12-31 03:03:20,042 - root - INFO - [
{
"success": {
"/groups/2/action/scene": "13"
}
}
]
2019-12-31 03:03:20,046 - urllib3.connectionpool - DEBUG - http://127.0.0.1:80 "PUT /api/0681c8642b7511eaac2dd6bfcb9e0f40/groups/2/action HTTP/1.1" 200 45
2019-12-31 03:03:20,047 - root - INFO - rule 1 is triggered
2019-12-31 03:03:20,056 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 127.0.0.1:80
127.0.0.1 - - [31/Dec/2019 03:03:20] "PUT /api/0681c8642b7511eaac2dd6bfcb9e0f40/groups/2/action HTTP/1.1" 200 -
2019-12-31 03:03:20,060 - root - INFO - in PUT method
2019-12-31 03:03:20,061 - root - INFO - /api/0681c8642b7511eaac2dd6bfcb9e0f40/groups/2/action
2019-12-31 03:03:20,061 - root - INFO - b'{"scene": "13"}'
2019-12-31 03:03:20,067 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.250.231:80
2019-12-31 03:03:20,081 - urllib3.connectionpool - DEBUG - http://192.168.250.231:80 "PUT /state HTTP/1.1" 200 12
2019-12-31 03:03:20,371 - urllib3.connectionpool - DEBUG - http://127.0.0.1:80 "PUT /api/0681c8642b7511eaac2dd6bfcb9e0f40/groups/2/action HTTP/1.1" 200 45
2019-12-31 03:03:20,375 - root - INFO - [
{
"success": {
"/groups/2/action/scene": "13"
}
}
]
2019-12-31 03:03:20,457 - root - INFO - [
{
"success": {
"/groups/2/stream": {
"active": true
}
}
}
]
192.168.250.210 - - [31/Dec/2019 03:03:20] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 03:03:20] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups HTTP/1.1" 200 -
ok
. Performing the SSL/TLS handshake... hello verification requested
. Waiting for a remote connection ... ok
. Performing the SSL/TLS handshake... ok
[ Protocol is DTLSv1.2 ]
[ Ciphersuite is TLS-PSK-WITH-AES-128-GCM-SHA256 ]
[ Record expansion is 37 ]
[ Maximum fragment length is 16384 ]
. Verifying peer X.509 certificate... ok
connection was closed gracefully
. Closing the connection... done
. Waiting for a remote connection ...2019-12-31 03:03:21,378 - root - DEBUG - Sending M-Search response to 192.168.250.252
2019-12-31 03:03:21,857 - root - INFO - sync with lights
2019-12-31 03:03:21,864 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.250.231:80
2019-12-31 03:03:21,880 - urllib3.connectionpool - DEBUG - http://192.168.250.231:80 "GET /state HTTP/1.1" 200 91
192.168.250.210 - - [31/Dec/2019 03:03:22] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 03:03:22] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups HTTP/1.1" 200 -
2019-12-31 03:03:24,233 - root - INFO - Entertainment Service was syncing and has timed out, stopping server and clearing state
interrupted by SIGTERM (in net_accept())
. Cleaning up... done.
192.168.250.210 - - [31/Dec/2019 03:03:24] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 03:03:25] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 03:03:27] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/lights HTTP/1.1" 200 -
192.168.250.210 - - [31/Dec/2019 03:03:27] "GET /api/f4cc87182b7811eab6cbd6bfcb9e0f40/groups HTTP/1.1" 200 -
2019-12-31 03:03:31,079 - root - DEBUG - Sending M-Search response to 192.168.250.252
2019-12-31 03:03:40,141 - urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): discovery.diyhue.org:443
2019-12-31 03:03:40,395 - urllib3.connectionpool - DEBUG - https://discovery.diyhue.org:443 "POST / HTTP/1.1" 200 6
{"ok"}
2019-12-31 03:03:41,480 - root - DEBUG - Sending M-Search response to 192.168.250.252
mariusmotea
stale[bot]
So far I was running previous builds from diyHue, and I previously opened a bug because my Philips TV would not recognize diyHue as Entertainment API capable, and would default to HTTP/PUT light updates which are very laggy.
But with the latest build something seems to have changed. Now when I enable Ambilight+Hue on my TV and I setup the lights, it seems that it tries to start the "Entertainment API", but something is failing, and DiyHue goes into an infinite loop of some kind. Turning off the TV doesn't helps, and DiyHue keeps spawning more and more Python threads till the whole server slows down to a crawl. An interesting line in the log is "killall: entertain-srv: no process killed" that is shown right before the infinite loop.
Using the mobile app "Hue Stream" works perfectly. So it must be some incompatibility with what the Philips TV is sending that causes the infinite loop. It seems like it cannot stop sending PUT requests to 127.0.0.1. I have some debug logs that could shed some more light.
Here are some logs:
To put into context what is happening here: I previously paired my Philips TV with DiyHue and added the emulated bulb [ESP] to DiyHue and is setup on the TV correctly. So what happens during the log is that I start DiyHue, and then I start my TV. After some seconds the TV starts sending the screen colors and the whole thing explodes (The ESP emulated light completely freezes during the infinite loop).
Here is the same as before but running with --debug:
What I find suspicious here is that the TV starts by sending "Group Stream active: FALSE" while the Hue Stream app starts with "Group Stream active: TRUE"..