NEWS
HMIP-Adapter: Cannot read property 'home' of undefined
-
Darf der Fehler kommen, wenn die Cloud mal wieder down ist, oder sollte das nicht passieren?
2022-01-20 12:05:36.578 - [33mwarn[39m: hmip.0 (256) ws connection closed (0) - code: 1006 - reason: 2022-01-20 12:05:46.925 - [33mwarn[39m: hmip.0 (256) ws connection error (0): Error: connect ECONNREFUSED 81.14.202.238:8888 2022-01-20 12:05:46.926 - [33mwarn[39m: hmip.0 (256) ws connection closed (1) - code: 1006 - reason: 2022-01-20 12:05:58.688 - [32minfo[39m: hmip.0 (256) ws connection opened 2022-01-20 12:05:58.705 - [33mwarn[39m: hmip.0 (256) ws connection closed (2) - code: 1000 - reason: 2022-01-20 12:06:10.395 - [32minfo[39m: hmip.0 (256) ws connection opened 2022-01-20 12:06:10.401 - [33mwarn[39m: hmip.0 (256) ws connection closed (3) - code: 1000 - reason: 2022-01-20 12:06:22.026 - [32minfo[39m: hmip.0 (256) ws connection opened 2022-01-20 12:06:22.033 - [33mwarn[39m: hmip.0 (256) ws connection closed (4) - code: 1000 - reason: 2022-01-20 12:06:33.891 - [32minfo[39m: hmip.0 (256) ws connection opened 2022-01-20 12:06:33.936 - [33mwarn[39m: hmip.0 (256) ws connection closed (5) - code: 1000 - reason: 2022-01-20 12:06:45.717 - [32minfo[39m: hmip.0 (256) ws connection opened 2022-01-20 12:06:45.762 - [33mwarn[39m: hmip.0 (256) ws connection closed (6) - code: 1000 - reason: 2022-01-20 12:06:57.369 - [32minfo[39m: hmip.0 (256) ws connection opened 2022-01-20 12:06:57.386 - [33mwarn[39m: hmip.0 (256) ws connection closed (7) - code: 1000 - reason: 2022-01-20 12:07:09.068 - [32minfo[39m: hmip.0 (256) ws connection opened 2022-01-20 12:07:09.078 - [33mwarn[39m: hmip.0 (256) ws connection closed (8) - code: 1000 - reason: 2022-01-20 12:07:20.752 - [32minfo[39m: hmip.0 (256) ws connection opened 2022-01-20 12:07:20.758 - [33mwarn[39m: hmip.0 (256) ws connection closed (9) - code: 1000 - reason: 2022-01-20 12:07:32.467 - [32minfo[39m: hmip.0 (256) ws connection opened 2022-01-20 12:07:32.487 - [33mwarn[39m: hmip.0 (256) ws connection closed (10) - code: 1000 - reason: 2022-01-20 12:07:43.933 - [32minfo[39m: hmip.0 (256) ws connection opened 2022-01-20 12:07:43.943 - [33mwarn[39m: hmip.0 (256) ws connection closed (11) - code: 1000 - reason: 2022-01-20 12:07:44.233 - [33mwarn[39m: hmip.0 (256) Request error: StatusCodeError: 418 - {"errorCode":"INVALID_REQUEST"} 2022-01-20 12:07:45.439 - [33mwarn[39m: hmip.0 (256) Request error: StatusCodeError: 403 - {"errorCode":"INVALID_AUTHORIZATION"} 2022-01-20 12:07:45.510 - [31merror[39m: hmip.0 (256) error starting homematic: TypeError: Cannot read property 'home' of undefined 2022-01-20 12:07:45.510 - [31merror[39m: hmip.0 (256) Try reconnect in 30s 2022-01-20 12:07:45.512 - [32minfo[39m: hmip.0 (256) hmip adapter connected and ready 2022-01-20 12:08:29.186 - [32minfo[39m: hmip.0 (256) ws connection opened 2022-01-20 12:08:39.297 - [32minfo[39m: hmip.0 (256) hmip adapter connected and ready
v1.15.2
-
@ofbeqnpolkkl6mby5e13 Jupp hatte ich auch heute. Wird mit nächster Version gefixt sein
-
Soll ich trotzdem ein issue aufmachen?
-
@ofbeqnpolkkl6mby5e13 Ne in dem Fall mal ausnahmsweise nicht
-
Du scheinst ja zumindest auch einen Access Point laufen zu haben. Hattest du auch Reconnects gestern gegen 13:50 Uhr?
2022-04-07 13:38:19.983 - [32minfo[39m: hmip.0 (363) ws connection opened 2022-04-07 13:38:20.017 - [33mwarn[39m: hmip.0 (363) ws connection closed (2) - code: 1000 - reason: 2022-04-07 13:38:32.498 - [32minfo[39m: hmip.0 (363) ws connection opened 2022-04-07 13:38:32.502 - [33mwarn[39m: hmip.0 (363) ws connection closed (3) - code: 1000 - reason: 2022-04-07 13:38:46.340 - [32minfo[39m: hmip.0 (363) ws connection opened 2022-04-07 13:38:46.345 - [33mwarn[39m: hmip.0 (363) ws connection closed (4) - code: 1000 - reason: 2022-04-07 13:38:59.756 - [32minfo[39m: hmip.0 (363) ws connection opened 2022-04-07 13:38:59.766 - [33mwarn[39m: hmip.0 (363) ws connection closed (5) - code: 1000 - reason: 2022-04-07 13:39:11.669 - [32minfo[39m: hmip.0 (363) ws connection opened 2022-04-07 13:39:11.676 - [33mwarn[39m: hmip.0 (363) ws connection closed (6) - code: 1000 - reason: 2022-04-07 13:39:23.598 - [32minfo[39m: hmip.0 (363) ws connection opened 2022-04-07 13:39:23.604 - [33mwarn[39m: hmip.0 (363) ws connection closed (7) - code: 1000 - reason: 2022-04-07 13:39:24.343 - [33mwarn[39m: hmip.0 (363) Request error: StatusCodeError: 418 - {"errorCode":"INVALID_REQUEST"} 2022-04-07 13:39:24.724 - [33mwarn[39m: hmip.0 (363) Request error: StatusCodeError: 403 - {"errorCode":"INVALID_AUTHORIZATION"} 2022-04-07 13:39:24.725 - [31merror[39m: hmip.0 (363) error starting homematic: Error: No current State received 2022-04-07 13:39:24.725 - [31merror[39m: hmip.0 (363) Try reconnect in 30s 2022-04-07 13:39:24.747 - [32minfo[39m: hmip.0 (363) hmip adapter connected and ready 2022-04-07 13:40:03.740 - [32minfo[39m: hmip.0 (363) ws connection opened 2022-04-07 13:40:07.108 - [32minfo[39m: hmip.0 (363) hmip adapter connected and ready 2022-04-07 13:42:03.592 - [33mwarn[39m: hmip.0 (363) State "hmip.0.devices.3014F711****.channels.3.functionalChannelType" has no existing object, this might lead to an error in future versions 2022-04-07 13:42:03.593 - [33mwarn[39m: hmip.0 (363) State "hmip.0.devices.3014F711****.channels.4.functionalChannelType" has no existing object, this might lead to an error in future versions 2022-04-07 13:42:03.593 - [33mwarn[39m: hmip.0 (363) State "hmip.0.devices.3014F711****.channels.5.functionalChannelType" has no existing object, this might lead to an error in future versions 2022-04-07 13:42:03.627 - [32minfo[39m: hmip.0 (363) New devices or channels detected ... reinitialize in 5s... 3014F711**** 2022-04-07 13:42:03.704 - [33mwarn[39m: hmip.0 (363) ws connection closed (7) - code: 1005 - reason: 2022-04-07 13:42:14.601 - [32minfo[39m: hmip.0 (363) ws connection opened 2022-04-07 13:42:17.830 - [32minfo[39m: hmip.0 (363) ws connection opened 2022-04-07 13:42:17.837 - [33mwarn[39m: hmip.0 (363) ws connection closed (8) - code: 1000 - reason: 2022-04-07 13:42:17.954 - [33mwarn[39m: hmip.0 (363) ws connection closed (9) - code: 1005 - reason: 2022-04-07 13:42:29.299 - [32minfo[39m: hmip.0 (363) hmip adapter connected and ready . . . 2022-04-07 14:13:05.206 - [33mwarn[39m: hmip.0 (363) Request error: StatusCodeError: 429 - undefined 2022-04-07 14:13:05.207 - [31merror[39m: hmip.0 (363) error starting homematic: Error: No current State received 2022-04-07 14:13:05.207 - [31merror[39m: hmip.0 (363) Try reconnect in 30s 2022-04-07 14:13:05.209 - [32minfo[39m: hmip.0 (363) hmip adapter connected and ready 2022-04-07 14:13:15.043 - [32minfo[39m: hmip.0 (363) hmip adapter connected and ready 2022-04-07 14:13:15.064 - [32minfo[39m: hmip.0 (363) hmip adapter connected and ready 2022-04-07 14:13:15.514 - [32minfo[39m: hmip.0 (363) ws connection opened 2022-04-07 14:13:18.693 - [32minfo[39m: hmip.0 (363) hmip adapter connected and ready 2022-04-07 14:13:35.513 - [33mwarn[39m: hmip.0 (363) Request error: StatusCodeError: 429 - undefined 2022-04-07 14:13:35.514 - [31merror[39m: hmip.0 (363) error starting homematic: Error: No current State received
Das ging so, bis ich das gegen 14:50 Uhr bemerkte. Ich habe dann die Instanz etwa 10 Minuten gestoppt. Danach war die Verbindung wieder möglich. EQ-3 hatte mich wegen dieser Geschichte gedrosselt. Die haben übrigens dazugelernt. Statt komplett zu blocken wird man gedrosselt und in der App wird dies sogar angezeigt. Sogar, dass es um REST geht.
Anzumerken ist hier auch, dass der Adapter meint, dass ein bestehender Fußbodenheizungsaktor als neu zu erkennen ist.
-
Also ja, ich hatte auch einen Reconnect, aber - weiss ja nicht welche Version Du einsetzt, die aktuellsten Versionen des Adapter haben das sehr optimiert.
-
v1.15.5
-
@ofbeqnpolkkl6mby5e13 Bist Du dir da gaaaanz sicher???
Bitte github issue mit vollständigem Log
-