philips hue modul

Markus M. · 24 September 2016, 12:34:03

Super, danke!

Kannst du die "percent" bitte noch auf "pct" ändern?

ernst1024 · 27 September 2016, 15:39:49

Der neue HUE Bewegungsmelder hört sich ja gut an. Hat den schon jemand in den Händen gehabt?

Markus M. · 27 September 2016, 15:47:11

Zitat von: ernst1024 am 27 September 2016, 15:39:49
Der neue HUE Bewegungsmelder hört sich ja gut an. Hat den schon jemand in den Händen gehabt?

Unwahrscheinlich dass sich den hier jemand zulegt. Ein Bewegungsmelder den man pollen muss ist relativ sinnfrei.

Fredi69 · 29 September 2016, 14:46:24

Um das

Code Auswählen

2016.09.15 07:26:50 2: myHUEBridge01: empty answer received for http://192.168.0.49/api/asaksjdasdjsaopdjsaodjasopodsif/lights
2016.09.15 07:26:50 3: HUEBridge_Call: failed, retrying
2016.09.15 07:36:50 2: myHUEBridge01: empty answer received for http://192.168.0.49/api/asaksjdasdjsaopdjsaodjasopodsif
2016.09.15 07:36:50 3: HUEBridge_Call: failed, retrying
2016.09.15 07:44:50 2: myHUEBridge01: empty answer received for http://192.168.0.49/api/asaksjdasdjsaopdjsaodjasopodsif/lights
2016.09.15 07:44:50 3: HUEBridge_Call: failed, retrying
2016.09.15 08:44:50 2: myHUEBridge01: empty answer received for http://192.168.0.49/api/asaksjdasdjsaopdjsaodjasopodsif/lights
2016.09.15 08:44:50 3: HUEBridge_Call: failed, retrying
2016.09.15 08:48:50 2: myHUEBridge01: empty answer received for http://192.168.0.49/api/asaksjdasdjsaopdjsaodjasopodsif
2016.09.15 08:48:50 3: HUEBridge_Call: failed, retrying
2016.09.15 08:51:50 2: myHUEBridge01: empty answer received for http://192.168.0.49/api/asaksjdasdjsaopdjsaodjasopodsif/lights
2016.09.15 08:51:50 3: HUEBridge_Call: failed, retrying
2016.09.15 08:55:50 2: myHUEBridge01: empty answer received for http://192.168.0.49/api/asaksjdasdjsaopdjsaodjasopodsif/lights
2016.09.15 08:55:50 3: HUEBridge_Call: failed, retrying
2016.09.15 09:00:50 2: myHUEBridge01: empty answer received for http://192.168.0.49/api/asaksjdasdjsaopdjsaodjasopodsif
2016.09.15 09:00:50 3: HUEBridge_Call: failed, retrying

Problem weiter einzugrenzen, habe ich jetzt mal Apptime bemüht.

Code Auswählen

name             function    max  count    total  average maxDly
tmr-HUEBridge_GetUpdate      HASH(0x3be1c58)  13804    183    91778   501.52    110 HASH(HUEBridge01)

Gibt es dazu eine Erklärung warum das so lange (13804ms) dauert?

justme1968 · 29 September 2016, 15:12:54

das modul hat einen timeout auf 3 sekunden. wenn die bridge dann nicht geantwortet hat wird abgebrochen. die 13000ms kommen also nicht direkt aus dem modul.

hast du irgendwelche notifys an irgendeinem hue device hängen?

ansonsten: ich bin immer noch der meinung das die vielen meldungen auf ein netzwerk problem hindeuten. oder eventuell
das die intervalle der devices und der bridge zu klein sind und sich auch noch in die quere kommen. verwendest du pollDevices ?

gruss
andre

Fredi69 · 29 September 2016, 16:08:15

Zitat von: justme1968 am 29 September 2016, 15:12:54
ansonsten: ich bin immer noch der meinung das die vielen meldungen auf ein netzwerk problem hindeuten. oder eventuell
das die intervalle der devices und der bridge zu klein sind und sich auch noch in die quere kommen. verwendest du pollDevices ?

Was meinst Du konkret mit "Intervalle der Devices und der Bridge"?
Was sollte ich prüfen bzw. verändern?
"pollDevices" steht auf "1"

EDIT 1:

Zitat von: justme1968 am 29 September 2016, 15:12:54hast du irgendwelche notifys an irgendeinem hue device hängen?

Es hängen RandomTimer an den HUE Devices

justme1968 · 29 September 2016, 16:37:20

das intervall steht im define. bzw. in den internals. es sollte bei den devices 0 sein und bei der bridge etwas anderes.

die zeit die im notify verbraucht wird wird mit gezählt. d.h. du musst genauer hin schauen.

Fredi69 · 29 September 2016, 16:45:58

Zitat von: justme1968 am 29 September 2016, 16:37:20
das intervall steht im define. bzw. in den internals. es sollte bei den devices 0 sein und bei der bridge etwas anderes.

die zeit die im notify verbraucht wird wird mit gezählt. d.h. du musst genauer hin schauen.

Das hatten wir bereits Anfang Juli geklärt, 60 und 0:

https://forum.fhem.de/index.php/topic,11020.msg470031.html#msg470031
https://forum.fhem.de/index.php/topic,11020.msg470122.html#msg470122

Fredi69 · 30 September 2016, 15:32:58

Und jetzt?
Kann ich noch irgendetwas prüfen, irgendwelche Ideen?

Vielen Dank
Fredi

Fredi69 · 30 September 2016, 21:16:15

Hier nochmal ein aktueller Log Auszug:

Code Auswählen

2016.09.30 15:17:16 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 15:17:16 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 15:17:16 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 15:17:16 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 15:17:16 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 15:17:16 1: HMLAN_Parse: HMLAN1 new condition ok
2016.09.30 15:18:09 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS/lights
2016.09.30 15:18:09 3: HUEBridge_Call: failed, retrying
2016.09.30 15:18:09 1: Perfmon: possible freeze starting at 15:18:05, delay is 4.343
2016.09.30 15:28:06 1: Perfmon: possible freeze starting at 15:28:05, delay is 1.396
2016.09.30 15:29:24 3: FRITZBOX: set FB7490 update 
2016.09.30 15:29:24 1: FRITZBOX FB7490: Readout_Start.658 Old readout process still running. Killing old process HASH(0x8e6ba08)
2016.09.30 15:32:09 1: Perfmon: possible freeze starting at 15:32:05, delay is 4.346
2016.09.30 15:32:24 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 15:32:24 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 15:32:24 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 15:32:24 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 15:32:24 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 15:32:24 1: HMLAN_Parse: HMLAN1 new condition ok
2016.09.30 15:34:52 1: Perfmon: possible freeze starting at 15:34:50, delay is 2.372
2016.09.30 15:35:07 1: Perfmon: possible freeze starting at 15:35:05, delay is 2.91
2016.09.30 15:41:19 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 15:41:19 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 15:41:19 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 15:41:21 1: Perfmon: possible freeze starting at 15:41:20, delay is 1.012
2016.09.30 15:42:07 1: Perfmon: possible freeze starting at 15:42:06, delay is 1.412
2016.09.30 15:42:21 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 15:42:21 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 15:42:25 1: HMLAN_Parse: HMLAN1 new condition ok
2016.09.30 15:43:09 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS/lights
2016.09.30 15:43:09 3: HUEBridge_Call: failed, retrying
2016.09.30 15:43:09 1: Perfmon: possible freeze starting at 15:43:06, delay is 3.429
2016.09.30 15:44:07 1: Perfmon: possible freeze starting at 15:44:05, delay is 2.232
, or ] expected while parsing array, at character offset 15726 (before "(end of string)") at ./FHEM/72_FRITZBOX.pm line 4508.
2016.09.30 15:51:09 1: Perfmon: possible freeze starting at 15:51:08, delay is 1.892
2016.09.30 15:51:15 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 15:51:15 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 15:51:15 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 15:52:11 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS/lights
2016.09.30 15:52:11 3: HUEBridge_Call: failed, retrying
2016.09.30 15:52:11 1: Perfmon: possible freeze starting at 15:52:08, delay is 3.85
2016.09.30 15:52:15 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 15:52:15 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 16:00:19 1: HMLAN_Parse: HMLAN1 new condition ok
2016.09.30 16:09:10 1: Perfmon: possible freeze starting at 16:09:08, delay is 2.614
2016.09.30 16:10:11 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS/lights
2016.09.30 16:10:11 3: HUEBridge_Call: failed, retrying
2016.09.30 16:10:12 1: Perfmon: possible freeze starting at 16:10:08, delay is 4.54
2016.09.30 16:11:35 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 16:11:35 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 16:11:35 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 16:11:35 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 16:11:35 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 16:11:35 1: HMLAN_Parse: HMLAN1 new condition ok
2016.09.30 16:13:19 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 16:13:19 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 16:13:19 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 16:13:23 1: Perfmon: possible freeze starting at 16:13:21, delay is 2.84
2016.09.30 16:14:10 1: Perfmon: possible freeze starting at 16:14:08, delay is 2.276
2016.09.30 16:14:26 1: Perfmon: possible freeze starting at 16:14:23, delay is 3.013
2016.09.30 16:15:11 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS
2016.09.30 16:15:11 3: HUEBridge_Call: failed, retrying
2016.09.30 16:15:12 1: Perfmon: possible freeze starting at 16:15:08, delay is 4.607
2016.09.30 16:15:26 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 16:15:26 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 16:15:26 1: HMLAN_Parse: HMLAN1 new condition ok
2016.09.30 16:17:09 1: Perfmon: possible freeze starting at 16:17:08, delay is 1.61
2016.09.30 16:18:11 1: Perfmon: possible freeze starting at 16:18:08, delay is 3.358
2016.09.30 16:22:09 1: Perfmon: possible freeze starting at 16:22:08, delay is 1.936
2016.09.30 16:23:11 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS/lights
2016.09.30 16:23:11 3: HUEBridge_Call: failed, retrying
2016.09.30 16:23:11 1: Perfmon: possible freeze starting at 16:23:08, delay is 3.834
2016.09.30 16:25:09 1: Perfmon: possible freeze starting at 16:25:08, delay is 1.519
2016.09.30 16:26:12 1: Perfmon: possible freeze starting at 16:26:08, delay is 4.371
2016.09.30 16:26:35 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 16:26:35 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 16:26:35 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 16:26:35 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 16:26:35 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 16:26:35 1: HMLAN_Parse: HMLAN1 new condition ok
2016.09.30 16:33:09 1: Perfmon: possible freeze starting at 16:33:08, delay is 1.535
2016.09.30 16:35:10 1: Perfmon: possible freeze starting at 16:35:08, delay is 2.421
2016.09.30 16:35:27 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 16:35:27 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 16:35:27 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 16:36:11 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS/lights
2016.09.30 16:36:11 3: HUEBridge_Call: failed, retrying
2016.09.30 16:36:12 1: Perfmon: possible freeze starting at 16:36:08, delay is 4.632
2016.09.30 16:36:29 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 16:36:29 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 16:36:29 1: HMLAN_Parse: HMLAN1 new condition ok
2016.09.30 16:40:10 1: Perfmon: possible freeze starting at 16:40:08, delay is 2.173
2016.09.30 16:57:10 1: Perfmon: possible freeze starting at 16:57:08, delay is 2.207
2016.09.30 16:58:11 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS/lights
2016.09.30 16:58:11 3: HUEBridge_Call: failed, retrying
2016.09.30 16:58:12 1: Perfmon: possible freeze starting at 16:58:08, delay is 4.154
2016.09.30 17:15:11 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS
2016.09.30 17:15:11 3: HUEBridge_Call: failed, retrying
2016.09.30 17:15:12 1: Perfmon: possible freeze starting at 17:15:08, delay is 4.322
2016.09.30 18:32:11 1: Perfmon: possible freeze starting at 18:32:09, delay is 2.615
2016.09.30 18:34:26 3: Watchdog watchdogHALarsFRITZBox triggered
2016.09.30 18:45:11 1: Perfmon: possible freeze starting at 18:45:09, delay is 2.265
2016.09.30 18:46:12 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS/lights
2016.09.30 18:46:12 3: HUEBridge_Call: failed, retrying
2016.09.30 18:46:13 1: Perfmon: possible freeze starting at 18:46:09, delay is 4.144
2016.09.30 18:50:12 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS
2016.09.30 18:50:12 3: HUEBridge_Call: failed, retrying
2016.09.30 18:50:12 1: Perfmon: possible freeze starting at 18:50:09, delay is 3.498
2016.09.30 18:50:27 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 18:50:27 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 18:50:27 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 18:51:28 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 18:51:28 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 18:51:57 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 18:51:57 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 18:51:57 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 18:52:58 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 18:52:58 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 18:53:02 1: HMLAN_Parse: HMLAN1 new condition ok
2016.09.30 18:54:45 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 18:54:45 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 18:54:45 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 18:55:48 1: Perfmon: possible freeze starting at 18:55:45, delay is 3.01
2016.09.30 18:56:11 1: Perfmon: possible freeze starting at 18:56:09, delay is 2.786
2016.09.30 18:56:48 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 18:56:48 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 18:56:52 1: HMLAN_Parse: HMLAN1 new condition ok
2016.09.30 18:58:10 1: Perfmon: possible freeze starting at 18:58:09, delay is 1.621
2016.09.30 18:59:12 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS/lights
2016.09.30 18:59:12 3: HUEBridge_Call: failed, retrying
2016.09.30 18:59:12 1: Perfmon: possible freeze starting at 18:59:09, delay is 3.539
2016.09.30 19:07:11 1: Perfmon: possible freeze starting at 19:07:09, delay is 2.168
2016.09.30 19:08:12 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS
2016.09.30 19:08:12 3: HUEBridge_Call: failed, retrying
2016.09.30 19:08:13 1: Perfmon: possible freeze starting at 19:08:09, delay is 4.309
2016.09.30 19:12:12 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS/lights
2016.09.30 19:12:12 3: HUEBridge_Call: failed, retrying
2016.09.30 19:12:12 1: Perfmon: possible freeze starting at 19:12:09, delay is 3.413
2016.09.30 19:28:12 1: Perfmon: possible freeze starting at 19:28:09, delay is 3.232
2016.09.30 19:30:25 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 19:30:25 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 19:30:25 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 19:30:27 1: Perfmon: possible freeze starting at 19:30:26, delay is 1.103
2016.09.30 19:31:12 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS/lights
2016.09.30 19:31:12 3: HUEBridge_Call: failed, retrying
2016.09.30 19:31:13 1: Perfmon: possible freeze starting at 19:31:09, delay is 4.223
2016.09.30 19:31:27 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 19:31:27 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 19:36:31 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 19:36:31 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 19:36:31 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 19:36:31 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 19:36:31 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 19:36:31 1: HMLAN_Parse: HMLAN1 new condition ok
2016.09.30 19:36:47 3: CUL_HM set Aussen_Garten_Lampe_Haustuer on-for-timer 60
2016.09.30 19:37:11 1: Perfmon: possible freeze starting at 19:37:09, delay is 2.768
2016.09.30 19:38:12 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS
2016.09.30 19:38:12 3: HUEBridge_Call: failed, retrying
2016.09.30 19:38:13 1: Perfmon: possible freeze starting at 19:38:09, delay is 4.99
2016.09.30 19:45:11 1: Perfmon: possible freeze starting at 19:45:09, delay is 2.375
2016.09.30 19:45:26 1: HMLAN_Parse: HMLAN1 new condition timeout
2016.09.30 19:45:26 1: 192.168.0.39:1000 disconnected, waiting to reappear (HMLAN1)
2016.09.30 19:45:26 1: HMLAN_Parse: HMLAN1 new condition disconnected
2016.09.30 19:46:12 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS/lights
2016.09.30 19:46:12 3: HUEBridge_Call: failed, retrying
2016.09.30 19:46:13 1: Perfmon: possible freeze starting at 19:46:09, delay is 4.235
2016.09.30 19:46:26 1: HMLAN_Parse: HMLAN1 new condition init
2016.09.30 19:46:26 1: 192.168.0.39:1000 reappeared (HMLAN1)
2016.09.30 20:02:11 1: Perfmon: possible freeze starting at 20:02:09, delay is 2.111
2016.09.30 20:03:12 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS/lights
2016.09.30 20:03:12 3: HUEBridge_Call: failed, retrying
2016.09.30 20:03:13 1: Perfmon: possible freeze starting at 20:03:09, delay is 4.543
2016.09.30 20:26:12 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS
2016.09.30 20:26:12 3: HUEBridge_Call: failed, retrying
2016.09.30 20:26:12 1: Perfmon: possible freeze starting at 20:26:09, delay is 3.965
2016.09.30 20:48:29 1: Perfmon: possible freeze starting at 20:48:26, delay is 3.092
2016.09.30 20:56:12 2: MyHUEBridge01: empty answer received for http://192.168.0.49/api/ASJDLjkasjdkasJDasd98s9adJASKDjkasjdakjAS
2016.09.30 20:56:12 3: HUEBridge_Call: failed, retrying
2016.09.30 20:56:13 1: Perfmon: possible freeze starting at 20:56:09, delay is 4.705
2016.09.30 21:08:31 1: Perfmon: possible freeze starting at 21:08:29, delay is 2.573

Code Auswählen

  name             function    max  count    total  average maxDly
tmr-HUEBridge_GetUpdate      HASH(0x3af5bb8)   5963   1741   331086   190.17   2229 HASH(MyHUEBridge01)

grappa24 · 01 Oktober 2016, 23:04:55

Hallo,

ich steuere eine Q-LED Leuchte jetzt mit ...
- der dazugehörigen FB
- der HUE-Bridge/App
- einem Busch-Jaeger Zigbee Wandtaster

Was kann denn der Grund dafür sein, dass die Leuchte von der HUE/App nicht mehr erreichbar ist (dabei spielt es wohl keine Rolle, ob die Leuchte an oder aus ist ...)

VG Dieter

justme1968 · 01 Oktober 2016, 23:45:44

@Fredi69: es tut mir leid, aber ich habe keine idee. ich kann es weder nachstellen noch scheinen andere das problem zu haben.

sets mal httpUtils für die bridge auf 1.

ansonsten: deine bridge scheint einfach nicht zu antworten und der timeout läuft ab.

greift sonst noch etwas auf die bridge zu?

@grappa24: kann es sein das du aus versehen die lampe am schalter an und an der bridge abgelernt hast?
siehst du den schalter wenn du ein get <bridge> sensors machst?

gruss
andre

grappa24 · 02 Oktober 2016, 00:01:00

Zitat von: justme1968 am 01 Oktober 2016, 23:45:44
@grappa24: kann es sein das du aus versehen die lampe am schalter an und an der bridge abgelernt hast?
siehst du den schalter wenn du ein get <bridge> sensors machst?

interessant

. Der Befehlt liefert

Code Auswählen

ID:1, Name: Daylight, TYPE: Daylight Ist das der Zigbee-Schalter? Gerade gehts wieder, muss es mal beobachten. Ganz schöne Sensibelchen diese ZigBee Komponenten ...

justme1968 · 02 Oktober 2016, 00:03:57

nein. das ist nicht der zigbee schalter. das ist ein virtueller dämmerungssensor. den kann man in regeln in der bridge verwenden um lampen morgens und abends automatisch zu schalten.

wenn da nicht mehr kommt scheint der schalter nicht an der bridge angelernt zu sein oder die bridge kann nur die phillips schalter.

aber wenn es mal geht und mal nicht dann ist zumindest immer noch alles im richtigen netz.

Nopax · 02 Oktober 2016, 15:57:49

Hallo zusammen,

ich versuche gerade aus manchen Hue-Lampen Structuren Hue-Groups zu bilden.
Das hat soweit auch funktioniert, allerdings bekomme ich es nicht hin eine Hue-Group für z.B 120 Sekunden einzuschalten auf z.B 10 Prozent oder bri 50.

So funktioniert es leider nicht:

Code Auswählen

set DL_Licht_Decke on-for-timer 120 : pct 10

Kann mir jemand dabei weiter helfen?

philips hue modul

Nopax