<![CDATA[Mihome Vaccum adapter bleibt rot]]>Ich habe mir heute Den S/ Max Ultra geholt und wollte diesen einbinden.
Das mit dem Token hat alles geklappt aber leider will der Adapter nicht grün werden, aus dem Log werde ich auch nicht schlau hat hier jemand tips und hilfe.

Danke Michael

Inkedsauger.jpg

Sauger 2.JPG

]]>https://forum.iobroker.net/topic/57053/mihome-vaccum-adapter-bleibt-rotRSS for NodeTue, 19 May 2026 14:35:54 GMTThu, 11 Aug 2022 14:42:02 GMT60<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Mon, 15 Aug 2022 11:57:53 GMT]]>@lessthanmore also ich verstehe es zwar nicht aber gerade nochmals probiert und jetzt geht es warum auch immer.

Danke an alle die geholfen haben

]]>https://forum.iobroker.net/post/842226https://forum.iobroker.net/post/842226Mon, 15 Aug 2022 11:57:53 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Mon, 15 Aug 2022 10:26:25 GMT]]>@michael-1975 Was steht denn im Log (Debug) sobald du ihn versuchst zu starten?

]]>https://forum.iobroker.net/post/842146https://forum.iobroker.net/post/842146Mon, 15 Aug 2022 10:26:25 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 20:26:42 GMT]]>@lessthanmore @lessthanmore Also nach dem ich jetzt nochmal alles neu gemacht habe incl. App und Ihn nur im 2.4 Netz angelernt habe ist der Adapter jetzt grün und bringt daten,allerdings kann ich Ihn nicht Über den Iobroker steuern er macht nicht.
sauger.JPG

Bei diesen datenpunkte steht einfach nur "null" und wenn ich true eingeben macht er nichts. Hat Hier auch noch jemand einen Tip.

Gruß Michael

]]>https://forum.iobroker.net/post/841987https://forum.iobroker.net/post/841987Sun, 14 Aug 2022 20:26:42 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:53:27 GMT]]>@lessthanmore werde ich nachher schauen muß jetzt weg danke schon mal

]]>https://forum.iobroker.net/post/841754https://forum.iobroker.net/post/841754Sun, 14 Aug 2022 10:53:27 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:52:02 GMT]]>@michael-1975 Mach mal noch ein Update von nodejs.
Also sudo apt update
und sudo apt upgrade -y

Hast du die Map Erstellung im Adapter aktiv? Hast du die notwendigen Dinge manuell gemäß Anleitung installiert?

Bedenke auch dass du noch buster nutzt und evtl. mal auf bullseye upgraden solltest (EOL).

]]>https://forum.iobroker.net/post/841753https://forum.iobroker.net/post/841753Sun, 14 Aug 2022 10:52:02 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:45:30 GMT]]>@lessthanmore sagte in Mihome Vaccum adapter bleibt rot:

uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs

sauger.JPG

das kommt

]]>https://forum.iobroker.net/post/841748https://forum.iobroker.net/post/841748Sun, 14 Aug 2022 10:45:30 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:38:33 GMT]]>@michael-1975 Node 16.15.1?
Was kommt denn bei

sudo ln -s /usr/bin/node /usr/bin/nodejs
uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs

in der Konsole? Das stammt aus Thomas Braun zweitem Link (Signatur).

]]>https://forum.iobroker.net/post/841745https://forum.iobroker.net/post/841745Sun, 14 Aug 2022 10:38:33 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:34:52 GMT]]>@michael-1975 kannst du den von deiner firewall den robot anpingen? Siehst du den robot denn in deiner firewall?

]]>https://forum.iobroker.net/post/841744https://forum.iobroker.net/post/841744Sun, 14 Aug 2022 10:34:52 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:33:20 GMT]]>@dirkhe Sind beide im Selben Netz, das war auch meine Vermutung

]]>https://forum.iobroker.net/post/841742https://forum.iobroker.net/post/841742Sun, 14 Aug 2022 10:33:20 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:33:15 GMT]]>@michael-1975 unterschiedlche netze ist auch ein guter hinweis, geht bei dren aktuellen saugern nicht, ist en bekanntes problem

]]>https://forum.iobroker.net/post/841741https://forum.iobroker.net/post/841741Sun, 14 Aug 2022 10:33:15 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:30:55 GMT]]>@lessthanmore Pihole habe ich nicht im einsatz Adressbereich sind die selben.

]]>https://forum.iobroker.net/post/841737https://forum.iobroker.net/post/841737Sun, 14 Aug 2022 10:30:55 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:29:50 GMT]]>@dirkhe habe die Firewall gerade mal ausgeschaltet geht aber trotdem nicht

]]>https://forum.iobroker.net/post/841735https://forum.iobroker.net/post/841735Sun, 14 Aug 2022 10:29:50 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:26:41 GMT]]>@michael-1975 PiHole im Einsatz oder sind der iob und der Sauger in unterschiedlichen Adressbereichen?

]]>https://forum.iobroker.net/post/841733https://forum.iobroker.net/post/841733Sun, 14 Aug 2022 10:26:41 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:25:05 GMT]]>@michael-1975 ich würde vermuten firewall?

]]>https://forum.iobroker.net/post/841730https://forum.iobroker.net/post/841730Sun, 14 Aug 2022 10:25:05 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:23:28 GMT]]>@dirkhe sowie es aussieht klappt das nicht aber warum?

]]>https://forum.iobroker.net/post/841729https://forum.iobroker.net/post/841729Sun, 14 Aug 2022 10:23:28 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:25:44 GMT]]>@michael-1975 nein, am port musst du normalerweise nichts ändern, sondern nur, wenn du mehr wie einem im netz hast. kannst du den roboter von dem iobroker rechner anpingen?
Lösch mal deinen token aus dem log...

Werde das mal bei gelegenheit im adapter anpassen

]]>https://forum.iobroker.net/post/841727https://forum.iobroker.net/post/841727Sun, 14 Aug 2022 10:25:44 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:07:45 GMT]]>@darkdevil naja meiner ist jetzt schon 3 Tage gelb und war noch nie grün, hast du was am Port eingestellt?

]]>https://forum.iobroker.net/post/841720https://forum.iobroker.net/post/841720Sun, 14 Aug 2022 10:07:45 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 10:07:02 GMT]]>@dirkhe Ip adresse stimmt
beim Port habe ich nichts geändert den habe ich so übernommen oder muß ich da was ändern?

Firewall sollte eigentlich auch passen.

]]>https://forum.iobroker.net/post/841719https://forum.iobroker.net/post/841719Sun, 14 Aug 2022 10:07:02 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 09:27:55 GMT]]>Ich hatte gestern genau das gleiche Thema mit beiden Instanzen.
Nachdem ich auf debug gestellt habe (und die gleichen Einträge wie du hattest) wurde der Adapter irgendwann grün und funktionierte

]]>https://forum.iobroker.net/post/841708https://forum.iobroker.net/post/841708Sun, 14 Aug 2022 09:27:55 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sun, 14 Aug 2022 09:17:52 GMT]]>@michael-1975 iobroker kann mit deinem sauger nicht quatschen. Stimmen die ip und port? Firewall richtig konfiguriert?

]]>https://forum.iobroker.net/post/841704https://forum.iobroker.net/post/841704Sun, 14 Aug 2022 09:17:52 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sat, 13 Aug 2022 07:19:56 GMT]]>@dirkhe so

]]>https://forum.iobroker.net/post/841286https://forum.iobroker.net/post/841286Sat, 13 Aug 2022 07:19:56 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sat, 13 Aug 2022 07:19:25 GMT]]> mihome-vacuum.0 2022-08-13 09:18:37.913 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:18:25.912 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:18:23.910 debug server started on 0.0.0.0:53422 mihome-vacuum.0 2022-08-13 09:18:23.907 info IOT enabled, create state mihome-vacuum.0 2022-08-13 09:18:23.906 debug MIIO: Config: ip:192.168.178.217 token: 55337144574946746d4f304178544c34 mihome-vacuum.0 2022-08-13 09:18:23.905 debug Create State for deviceInfowifi_signal mihome-vacuum.0 2022-08-13 09:18:23.905 debug Create State for deviceInfofw_ver mihome-vacuum.0 2022-08-13 09:18:23.905 debug Create State for deviceInfomodel mihome-vacuum.0 2022-08-13 09:18:23.905 debug Create State for deviceInfomac mihome-vacuum.0 2022-08-13 09:18:23.904 debug Create State for deviceInfo mihome-vacuum.0 2022-08-13 09:18:23.846 debug load Map creator... true mihome-vacuum.0 2022-08-13 09:18:23.815 info starting. Version 3.6.0 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v16.15.1, js-controller: 4.0.23 mihome-vacuum.0 2022-08-13 09:18:23.596 debug Plugin sentry Initialize Plugin (enabled=true) mihome-vacuum.0 2022-08-13 09:18:22.553 debug States connected to redis: 127.0.0.1:9000 mihome-vacuum.0 2022-08-13 09:18:22.295 debug States create User PubSub Client mihome-vacuum.0 2022-08-13 09:18:22.292 debug States create System PubSub Client mihome-vacuum.0 2022-08-13 09:18:22.090 debug Redis States: Use Redis connection: 127.0.0.1:9000 mihome-vacuum.0 2022-08-13 09:18:21.904 debug Objects connected to redis: 127.0.0.1:9001 mihome-vacuum.0 2022-08-13 09:18:21.881 debug Objects client initialize lua scripts mihome-vacuum.0 2022-08-13 09:18:21.577 debug Objects create User PubSub Client mihome-vacuum.0 2022-08-13 09:18:21.576 debug Objects create System PubSub Client mihome-vacuum.0 2022-08-13 09:18:21.496 debug Objects client ready ... initialize now mihome-vacuum.0 2022-08-13 09:18:21.128 debug Redis Objects: Use Redis connection: 127.0.0.1:9001 mihome-vacuum.0 2022-08-13 09:18:16.683 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2022-08-13 09:18:16.683 debug Plugin sentry destroyed mihome-vacuum.0 2022-08-13 09:18:16.683 info terminating mihome-vacuum.0 2022-08-13 09:18:16.683 error Socket Close mihome-vacuum.0 2022-08-13 09:18:16.682 info Got terminate signal TERMINATE_YOURSELF mihome-vacuum.0 2022-08-13 09:18:08.209 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:17:56.207 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:17:44.204 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:17:32.203 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:17:20.201 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:17:08.199 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:16:56.196 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:16:44.195 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:16:32.193 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:16:20.192 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:16:08.190 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:15:56.188 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:15:44.186 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:15:32.184 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:15:20.182 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:15:08.180 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:14:56.178 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:14:44.176 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:14:32.174 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:14:20.172 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:14:08.170 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:13:56.168 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:13:44.167 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:13:32.165 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:13:20.164 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:13:08.162 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:12:56.160 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:12:44.160 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:12:32.158 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:12:20.156 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:12:08.154 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:11:56.152 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:11:44.149 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:11:32.147 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:11:20.145 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:11:08.142 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:10:56.139 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:10:44.137 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:10:32.135 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:10:20.132 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:10:08.129 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:09:56.127 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:09:44.124 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:09:32.122 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:09:20.119 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:09:08.117 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:08:56.114 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:08:44.113 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:08:32.113 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:08:20.113 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:08:08.112 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:07:56.112 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:07:44.112 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:07:32.111 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:07:20.111 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:07:08.111 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:06:56.110 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:06:44.110 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:06:32.109 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:06:20.107 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:06:08.106 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:05:56.105 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:05:44.103 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:05:32.099 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:05:20.098 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:05:08.097 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:04:56.096 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:04:44.096 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:04:32.095 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:04:20.094 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:04:08.093 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:03:56.092 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:03:44.090 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:03:32.090 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:03:20.090 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:03:08.089 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:02:56.088 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:02:44.087 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:02:32.086 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:02:20.085 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:02:08.083 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:01:56.082 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:01:44.081 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:01:32.080 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:01:20.079 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:01:08.077 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:00:56.076 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:00:44.075 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:00:32.073 debug Helo message Timeout mihome-vacuum.0 2022-08-13 09:00:20.073 debug Helo message Timeout ]]>https://forum.iobroker.net/post/841285https://forum.iobroker.net/post/841285Sat, 13 Aug 2022 07:19:25 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Sat, 13 Aug 2022 06:48:56 GMT]]>@michael-1975 stell den adapter mal auf debug und poste das log. Es reicht dann auch, nur die mihome einträge zu posten

]]>https://forum.iobroker.net/post/841277https://forum.iobroker.net/post/841277Sat, 13 Aug 2022 06:48:56 GMT<![CDATA[Reply to Mihome Vaccum adapter bleibt rot on Fri, 12 Aug 2022 08:11:39 GMT]]>@Thomas-Braun Okay meinst du so




2022-08-12 10:03:14.458 - info: hue-extended.0 (2873) State value to set for "hue-extended.0.sensors.012-bwm_wohnzimmer.state.presence" has to be type "string" but received type "boolean"
2022-08-12 10:03:17.536 - info: admin.0 (752) ==> Connected system.user.admin from ::ffff:192.168.178.109
2022-08-12 10:03:32.348 - info: hue-extended.0 (2873) State value to set for "hue-extended.0.sensors.012-bwm_wohnzimmer.state.presence" has to be type "string" but received type "boolean"
2022-08-12 10:03:49.286 - info: host.iobroker stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
2022-08-12 10:03:49.291 - info: mihome-vacuum.0 (5001) Got terminate signal TERMINATE_YOURSELF
2022-08-12 10:03:49.293 - error: mihome-vacuum.0 (5001) Socket Close
2022-08-12 10:03:49.294 - info: mihome-vacuum.0 (5001) terminating
2022-08-12 10:03:49.294 - info: mihome-vacuum.0 (5001) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-08-12 10:03:49.332 - info: host.iobroker stopInstance system.adapter.mihome-vacuum.0 send kill signal
2022-08-12 10:03:49.975 - info: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-08-12 10:03:52.569 - info: host.iobroker instance system.adapter.mihome-vacuum.0 started with pid 7642
2022-08-12 10:03:53.164 - debug: mihome-vacuum.0 (7642) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-08-12 10:03:53.261 - debug: mihome-vacuum.0 (7642) Objects client ready ... initialize now
2022-08-12 10:03:53.312 - debug: mihome-vacuum.0 (7642) Objects create System PubSub Client
2022-08-12 10:03:53.313 - debug: mihome-vacuum.0 (7642) Objects create User PubSub Client
2022-08-12 10:03:53.607 - debug: mihome-vacuum.0 (7642) Objects client initialize lua scripts
2022-08-12 10:03:53.628 - debug: mihome-vacuum.0 (7642) Objects connected to redis: 127.0.0.1:9001
2022-08-12 10:03:53.764 - debug: mihome-vacuum.0 (7642) Redis States: Use Redis connection: 127.0.0.1:9000
2022-08-12 10:03:53.888 - debug: mihome-vacuum.0 (7642) States create System PubSub Client
2022-08-12 10:03:53.889 - debug: mihome-vacuum.0 (7642) States create User PubSub Client
2022-08-12 10:03:54.208 - debug: mihome-vacuum.0 (7642) States connected to redis: 127.0.0.1:9000
2022-08-12 10:03:54.876 - debug: mihome-vacuum.0 (7642) Plugin sentry Initialize Plugin (enabled=true)
2022-08-12 10:03:55.197 - info: mihome-vacuum.0 (7642) starting. Version 3.6.0 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v16.15.1, js-controller: 4.0.23
2022-08-12 10:03:55.229 - debug: mihome-vacuum.0 (7642) load Map creator... true
2022-08-12 10:03:55.292 - debug: mihome-vacuum.0 (7642) Create State for deviceInfo
2022-08-12 10:03:55.292 - debug: mihome-vacuum.0 (7642) Create State for deviceInfomac
2022-08-12 10:03:55.292 - debug: mihome-vacuum.0 (7642) Create State for deviceInfomodel
2022-08-12 10:03:55.293 - debug: mihome-vacuum.0 (7642) Create State for deviceInfofw_ver
2022-08-12 10:03:55.293 - debug: mihome-vacuum.0 (7642) Create State for deviceInfowifi_signal
2022-08-12 10:03:55.293 - debug: mihome-vacuum.0 (7642) MIIO: Config: ip:192.168.178.217 token: 55337144574946746d4f304178544c34
2022-08-12 10:03:55.295 - info: mihome-vacuum.0 (7642) IOT enabled, create state
2022-08-12 10:03:55.296 - debug: mihome-vacuum.0 (7642) server started on 0.0.0.0:53422
2022-08-12 10:03:57.298 - debug: mihome-vacuum.0 (7642) Helo message Timeout
2022-08-12 10:03:57.816 - info: hue-extended.0 (2873) State value to set for "hue-extended.0.sensors.012-bwm_wohnzimmer.state.presence" has to be type "string" but received type "boolean"
2022-08-12 10:04:01.117 - info: hue-extended.0 (2873) State value to set for "hue-extended.0.sensors.015-bwm_1.state.presence" has to be type "string" but received type "boolean"
2022-08-12 10:04:09.299 - debug: mihome-vacuum.0 (7642) Helo message Timeout
2022-08-12 10:04:10.488 - info: meross.0 (1503) Can not get Data for Device 20121538045776290d2348e1e940edbb: Error: Device has no data connection available
2022-08-12 10:04:10.488 - warn: meross.0 (1503) Can not get Data for Device 20121538045776290d2348e1e940edbb: undefined
2022-08-12 10:04:20.431 - error: eusec.0 (3119) P2PClientProtocol.lookup(): station: T8410P202124034C - All address lookup tentatives failed.
2022-08-12 10:04:20.431 - info: eusec.0 (3119) Timeout connecting to station T8410P202124034C
2022-08-12 10:04:21.301 - debug: mihome-vacuum.0 (7642) Helo message Timeout
]]>https://forum.iobroker.net/post/840828https://forum.iobroker.net/post/840828Fri, 12 Aug 2022 08:11:39 GMT