Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Neuer Adapter für Roborock-Staubsauger

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.3k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.0k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.4k

Neuer Adapter für Roborock-Staubsauger

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
922 Beiträge 136 Kommentatoren 324.8k Aufrufe 125 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • copystringC copystring

    Ein Log brauche ich erstmal nicht. Könnt ihr bestätigen, dass der Ausfall mit der aktualisierten dev von gestern, ziemlich genau jede Stunde auftritt?

    da_WoodyD Online
    da_WoodyD Online
    da_Woody
    schrieb am zuletzt editiert von
    #432

    @copystring sagte in Neuer Adapter für Roborock-Staubsauger:

    der Ausfall mit der aktualisierten den von gestern, ziemlich genau jede Stunde Auftritt?

    meinst du kartenupdate?
    kann ich nicht genau sagen. bei mir läuft der adapter seit dem letzten test. gerade einen kurzen testlauf gemacht.
    meine buttons funktionieren, die map nicht. roborock.0.Devices.xxx.deviceStatus.state klappt auch, allerdings mit verzögerung.
    4b2dd96c-6367-4922-b383-480cbfc9af72-grafik.png
    häng dir trotzdem ein log da an...

    
    roborock.0
    2024-01-17 14:47:49.638	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8148 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:49.489	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:49.489	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:49.401	debug	Update map
    
    roborock.0
    2024-01-17 14:47:49.300	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:49.188	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:48.187	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:48.073	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:47.941	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8147 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:47.932	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:47.932	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:47.390	debug	Update map
    
    roborock.0
    2024-01-17 14:47:47.073	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:46.954	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:45.948	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:45.849	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:45.617	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8146 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:45.506	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:45.506	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:45.390	debug	Update map
    
    roborock.0
    2024-01-17 14:47:44.842	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:44.739	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:43.739	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:43.609	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:43.509	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8145 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:43.462	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:43.462	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:43.383	debug	Update map
    
    roborock.0
    2024-01-17 14:47:43.062	debug	homedata successfully updated
    
    roborock.0
    2024-01-17 14:47:43.036	debug	get_timer: "[]
    
    roborock.0
    2024-01-17 14:47:43.036	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:42.793	debug	getParameter for 5umEnoJEB0hmM5UmYlkumw: get_timer
    
    roborock.0
    2024-01-17 14:47:42.793	debug	get_server_timer: " + []
    
    roborock.0
    2024-01-17 14:47:42.793	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:42.641	debug	getParameter for 5umEnoJEB0hmM5UmYlkumw: get_server_timer
    
    roborock.0
    2024-01-17 14:47:42.641	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:42.609	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:42.495	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:42.440	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8144 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:42.201	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:42.201	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:42.170	debug	getParameter for 5umEnoJEB0hmM5UmYlkumw: get_network_info
    
    roborock.0
    2024-01-17 14:47:42.170	debug	Consumables of robot: {"main_brush_work_time":68952,"side_brush_work_time":68952,"filter_work_time":68952,"filter_element_work_time":0,"sensor_dirty_time":97966}
    
    roborock.0
    2024-01-17 14:47:42.169	debug	Length of message queue: 6
    
    roborock.0
    2024-01-17 14:47:41.712	debug	getParameter for 5umEnoJEB0hmM5UmYlkumw: get_consumable
    
    roborock.0
    2024-01-17 14:47:41.712	warn	Failed to map rooms. You need to name your rooms via the mobile app on your phone.
    
    roborock.0
    2024-01-17 14:47:41.712	debug	All mapped rooms: []
    
    roborock.0
    2024-01-17 14:47:41.712	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:41.495	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:41.480	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:41.386	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:41.383	debug	Update map
    
    roborock.0
    2024-01-17 14:47:40.995	debug	getParameter for 5umEnoJEB0hmM5UmYlkumw: get_room_mapping
    
    roborock.0
    2024-01-17 14:47:40.929	debug	get_status: {"msg_ver":2,"msg_seq":1465,"state":8,"battery":99,"clean_time":133,"clean_area":2172500,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0}
    
    roborock.0
    2024-01-17 14:47:40.928	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:40.687	debug	getParameter for 5umEnoJEB0hmM5UmYlkumw: get_status
    
    roborock.0
    2024-01-17 14:47:40.687	debug	Latest data requested
    
    roborock.0
    2024-01-17 14:47:40.669	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8143 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:40.620	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:40.620	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:40.385	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:40.236	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:39.382	debug	Update map
    
    roborock.0
    2024-01-17 14:47:39.234	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:39.090	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:38.088	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:38.011	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8142 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:37.936	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:37.808	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:37.807	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:37.366	debug	Update map
    
    roborock.0
    2024-01-17 14:47:36.935	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:36.816	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:35.816	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:35.694	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:35.546	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8141 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:35.429	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:35.428	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:35.366	debug	Update map
    
    roborock.0
    2024-01-17 14:47:34.694	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:34.577	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:33.564	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:33.459	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:33.411	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8140 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:33.377	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:33.377	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:33.366	debug	Update map
    
    roborock.0
    2024-01-17 14:47:32.443	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:32.329	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:31.546	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8139 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:31.366	debug	Update map
    
    roborock.0
    2024-01-17 14:47:31.354	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:31.354	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:31.327	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:31.211	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:30.291	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8138 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:30.209	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:30.112	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:29.524	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:29.523	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:29.358	debug	Update map
    
    roborock.0
    2024-01-17 14:47:29.111	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:29.010	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:28.010	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:27.892	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:27.547	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8137 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:27.427	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:27.427	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:27.356	debug	Update map
    
    roborock.0
    2024-01-17 14:47:26.891	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:26.774	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:25.952	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8136 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:25.924	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:25.923	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:25.773	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:25.660	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:25.356	debug	Update map
    
    roborock.0
    2024-01-17 14:47:24.659	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:24.556	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:23.969	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8135 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:23.949	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:23.948	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:23.556	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:23.447	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:23.344	debug	Update map
    
    roborock.0
    2024-01-17 14:47:22.447	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:22.324	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:22.194	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8134 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:22.118	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:22.118	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:21.344	debug	Update map
    
    roborock.0
    2024-01-17 14:47:21.316	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:21.198	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:20.215	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8133 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:20.197	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:20.130	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:20.129	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:20.033	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:19.343	debug	Update map
    
    roborock.0
    2024-01-17 14:47:19.032	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:18.875	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:17.875	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:17.813	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8132 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:17.761	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:17.726	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:17.726	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:17.334	debug	Update map
    
    roborock.0
    2024-01-17 14:47:16.761	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:16.651	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:15.842	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8131 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:15.664	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:15.664	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:15.651	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:15.506	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:15.328	debug	Update map
    
    roborock.0
    2024-01-17 14:47:14.506	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:14.405	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:13.825	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8130 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:13.405	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:13.373	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:13.373	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:13.328	debug	Update map
    
    roborock.0
    2024-01-17 14:47:13.289	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:12.289	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:12.153	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:12.050	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8129 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:11.898	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:11.898	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:11.323	debug	Update map
    
    roborock.0
    2024-01-17 14:47:11.153	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:11.016	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:10.015	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:09.883	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:09.872	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8128 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:09.483	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:09.482	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:09.320	debug	Update map
    
    roborock.0
    2024-01-17 14:47:08.879	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:08.757	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:07.757	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:07.665	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8127 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:07.646	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:07.506	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:07.506	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:07.320	debug	Update map
    
    roborock.0
    2024-01-17 14:47:06.645	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:06.494	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:05.607	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8126 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:05.494	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:05.399	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:05.398	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:47:05.352	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:05.315	debug	Update map
    
    roborock.0
    2024-01-17 14:47:04.350	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:04.236	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:03.506	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8125 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:03.502	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:03.502	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:03.300	debug	Update map
    
    roborock.0
    2024-01-17 14:47:03.235	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:03.123	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:02.122	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8124 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:47:02.122	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:02.009	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:47:01.922	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:01.922	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:47:01.294	debug	Update map
    
    roborock.0
    2024-01-17 14:47:01.007	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:47:00.907	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:59.906	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:59.784	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:59.415	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8123 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:59.366	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:59.366	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:59.294	debug	Update map
    
    roborock.0
    2024-01-17 14:46:58.783	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:58.652	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:57.652	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:57.521	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:57.416	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8122 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:57.310	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:57.310	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:57.275	debug	Update map
    
    roborock.0
    2024-01-17 14:46:56.521	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:56.394	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:55.550	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8121 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:55.502	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:55.500	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:55.386	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:55.275	debug	Update map
    
    roborock.0
    2024-01-17 14:46:55.259	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:54.257	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:54.089	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:53.593	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8120 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:53.372	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:53.372	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:53.272	debug	Update map
    
    roborock.0
    2024-01-17 14:46:53.089	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:52.980	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:51.979	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:51.813	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:51.563	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8116 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:51.398	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:51.398	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:51.272	debug	Update map
    
    roborock.0
    2024-01-17 14:46:50.809	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:50.708	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:49.708	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:49.542	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:49.365	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8111 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:49.307	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:49.306	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:49.272	debug	Update map
    
    roborock.0
    2024-01-17 14:46:48.539	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:48.411	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:47.411	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:47.305	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8110 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:47.303	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:47.303	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:47.287	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:47.272	debug	Update map
    
    roborock.0
    2024-01-17 14:46:46.284	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:46.167	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:45.447	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8109 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:45.341	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:45.340	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:45.272	debug	Update map
    
    roborock.0
    2024-01-17 14:46:45.167	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:45.049	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:44.044	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:43.925	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:43.331	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8108 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:43.315	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:43.314	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:43.271	debug	Update map
    
    roborock.0
    2024-01-17 14:46:43.015	debug	homedata successfully updated
    
    roborock.0
    2024-01-17 14:46:42.923	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:42.782	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:41.847	debug	get_timer: "[]
    
    roborock.0
    2024-01-17 14:46:41.846	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:41.782	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:41.674	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:41.605	debug	getParameter for 5umEnoJEB0hmM5UmYlkumw: get_timer
    
    roborock.0
    2024-01-17 14:46:41.605	debug	get_server_timer: " + []
    
    roborock.0
    2024-01-17 14:46:41.605	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:41.523	debug	getParameter for 5umEnoJEB0hmM5UmYlkumw: get_server_timer
    
    roborock.0
    2024-01-17 14:46:41.523	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:41.352	debug	getParameter for 5umEnoJEB0hmM5UmYlkumw: get_network_info
    
    roborock.0
    2024-01-17 14:46:41.352	debug	Consumables of robot: {"main_brush_work_time":68952,"side_brush_work_time":68952,"filter_work_time":68952,"filter_element_work_time":0,"sensor_dirty_time":97966}
    
    roborock.0
    2024-01-17 14:46:41.352	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:41.328	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8107 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:41.271	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:41.271	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:41.266	debug	Update map
    
    roborock.0
    2024-01-17 14:46:41.225	debug	getParameter for 5umEnoJEB0hmM5UmYlkumw: get_consumable
    
    roborock.0
    2024-01-17 14:46:41.225	warn	Failed to map rooms. You need to name your rooms via the mobile app on your phone.
    
    roborock.0
    2024-01-17 14:46:41.225	debug	All mapped rooms: []
    
    roborock.0
    2024-01-17 14:46:41.225	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:41.148	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:40.953	debug	getParameter for 5umEnoJEB0hmM5UmYlkumw: get_room_mapping
    
    roborock.0
    2024-01-17 14:46:40.940	debug	get_status: {"msg_ver":2,"msg_seq":1433,"state":8,"battery":99,"clean_time":133,"clean_area":2172500,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0}
    
    roborock.0
    2024-01-17 14:46:40.940	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:40.687	debug	getParameter for 5umEnoJEB0hmM5UmYlkumw: get_status
    
    roborock.0
    2024-01-17 14:46:40.686	debug	Latest data requested
    
    roborock.0
    2024-01-17 14:46:40.671	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:40.528	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:39.526	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:39.422	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:39.418	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8106 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:39.410	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:39.410	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:39.263	debug	Update map
    
    roborock.0
    2024-01-17 14:46:38.419	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:38.268	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:37.722	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8105 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:37.719	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:37.718	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:37.263	debug	Update map
    
    roborock.0
    2024-01-17 14:46:37.248	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:37.097	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:36.095	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:35.970	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:35.567	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8104 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:35.496	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:35.496	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:35.263	debug	Update map
    
    roborock.0
    2024-01-17 14:46:34.970	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:34.854	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:33.845	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:33.760	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8103 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:33.744	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:33.744	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:33.728	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:33.262	debug	Update map
    
    roborock.0
    2024-01-17 14:46:32.728	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:32.629	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:31.629	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:31.515	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:31.355	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8102 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:31.328	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:31.327	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:31.255	debug	Update map
    
    roborock.0
    2024-01-17 14:46:30.514	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:30.410	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:29.694	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8101 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:29.675	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:29.675	debug	Length of message queue: 5
    
    roborock.0
    2024-01-17 14:46:29.410	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:29.303	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:29.254	debug	Update map
    
    roborock.0
    2024-01-17 14:46:28.292	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:28.189	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:27.550	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8100 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:27.253	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:27.253	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:27.253	debug	Update map
    
    roborock.0
    2024-01-17 14:46:27.189	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:27.082	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:26.079	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:25.960	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:25.448	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8099 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:25.312	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:25.311	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:25.253	debug	Update map
    
    roborock.0
    2024-01-17 14:46:24.952	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:24.814	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:23.813	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:23.700	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:23.554	warn	Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8098 with method get_map_v1 timed out after 10 seconds for response.102
    
    roborock.0
    2024-01-17 14:46:23.381	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:23.380	debug	Length of message queue: 4
    
    roborock.0
    2024-01-17 14:46:23.252	debug	Update map
    
    roborock.0
    2024-01-17 14:46:22.700	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:22.552	warn	MQTT connection reconnect.
    
    roborock.0
    2024-01-17 14:46:21.552	warn	MQTT connection close.
    
    roborock.0
    2024-01-17 14:46:21.425	warn	MQTT connection reconnect.
    

    gruß vom Woody
    HAPPINESS is not a DESTINATION, it's a WAY of LIFE!

    1 Antwort Letzte Antwort
    0
    • copystringC copystring

      Ein Log brauche ich erstmal nicht. Könnt ihr bestätigen, dass der Ausfall mit der aktualisierten dev von gestern, ziemlich genau jede Stunde auftritt?

      T Offline
      T Offline
      tritanium
      schrieb am zuletzt editiert von
      #433

      @copystring
      Ich müsste ehrlich gesagt lügen.

      Kann nachher mal schauen, was meine Logs sagen... hast du ne vermutung ? :-)

      ...wenn du schon so gezielt fragst ...

      copystringC 1 Antwort Letzte Antwort
      0
      • T tritanium

        @copystring
        Ich müsste ehrlich gesagt lügen.

        Kann nachher mal schauen, was meine Logs sagen... hast du ne vermutung ? :-)

        ...wenn du schon so gezielt fragst ...

        copystringC Offline
        copystringC Offline
        copystring
        schrieb am zuletzt editiert von copystring
        #434

        Wenn der Fehler mit der neusten dev von GitHub genau nach einer Stunde Auftritt, hätte ich eine Idee. Könnte ihr das bestätigen? Lässt sich das wiederholt reproduzieren? Zum Beispiel: disconnect und reconnect schleife immer eine Stunde, nachdem der Adapter gestartet wurde.

        Unterstütze meine Arbeit gerne mit einer Spende über PayPal:
        https://paypal.me/copystring

        T 1 Antwort Letzte Antwort
        0
        • copystringC copystring

          Wenn der Fehler mit der neusten dev von GitHub genau nach einer Stunde Auftritt, hätte ich eine Idee. Könnte ihr das bestätigen? Lässt sich das wiederholt reproduzieren? Zum Beispiel: disconnect und reconnect schleife immer eine Stunde, nachdem der Adapter gestartet wurde.

          T Offline
          T Offline
          tritanium
          schrieb am zuletzt editiert von
          #435

          @copystring

          das ja einfach nachzustellen -> Mein Adapter ist grade aus!

          Ich schalte den ein und warte ab :-)

          -> Ich berichte, sobald sich was tut ... is später....

          T 1 Antwort Letzte Antwort
          0
          • T tritanium

            @copystring

            das ja einfach nachzustellen -> Mein Adapter ist grade aus!

            Ich schalte den ein und warte ab :-)

            -> Ich berichte, sobald sich was tut ... is später....

            T Offline
            T Offline
            tritanium
            schrieb am zuletzt editiert von
            #436

            So, Adapter läuft.

            Dann warten wir mal auf 19 Uhr :-D

            da_WoodyD 1 Antwort Letzte Antwort
            0
            • T tritanium

              So, Adapter läuft.

              Dann warten wir mal auf 19 Uhr :-D

              da_WoodyD Online
              da_WoodyD Online
              da_Woody
              schrieb am zuletzt editiert von da_Woody
              #437

              @tritanium hab auch gerade neu gestartet. mal schauen...
              schau im debuglog mit... im moment ist ruhe.

              
              roborock.0
              2024-01-17 18:10:09.214	debug	MQTT connection connected {"cmd":"connack","retain":false,"qos":0,"dup":false,"length":2,"topic":null,"payload":null,"sessionPresent":false,"returnCode":0}.
              
              roborock.0
              2024-01-17 18:10:09.123	debug	tcp client for 5umEnoJEB0hmM5UmYlkumw connected
              
              roborock.0
              2024-01-17 18:10:08.666	debug	Robot key: roborock.vacuum.a08
              
              roborock.0
              2024-01-17 18:10:08.665	debug	RoomIDs debug: {"16510226":"Studio"}
              
              roborock.0
              2024-01-17 18:10:08.665	info	MQTT initialized
              
              roborock.0
              2024-01-17 18:10:08.636	debug	localDevices: {"5umEnoJEB0hmM5UmYlkumw":"192.168.1.15"}
              
              roborock.0
              2024-01-17 18:10:02.231	info	Starting adapter. This might take a few minutes depending on your setup. Please wait.
              
              roborock.0
              2024-01-17 18:10:02.201	info	starting. Version 0.5.1 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v18.19.0, js-controller: 5.0.17
              
              roborock.0
              2024-01-17 18:10:01.203	debug	Plugin sentry Initialize Plugin (enabled=true)
              

              edith: erstes warning ist da. allerdings anderes thema.
              ich hab nur einen raum, der ist benannt. wurde auch richtig erkannt.

              
              roborock.0
              2024-01-17 18:10:08.665	debug	RoomIDs debug: {"16510226":"Studio"}
              

              2 min später

              
              roborock.0
              2024-01-17 18:12:05.443	warn	Failed to map rooms. You need to name your rooms via the mobile app on your phone.
              
              roborock.0
              2024-01-17 18:12:05.443	debug	All mapped rooms: []
              

              gruß vom Woody
              HAPPINESS is not a DESTINATION, it's a WAY of LIFE!

              T 1 Antwort Letzte Antwort
              0
              • da_WoodyD da_Woody

                @tritanium hab auch gerade neu gestartet. mal schauen...
                schau im debuglog mit... im moment ist ruhe.

                
                roborock.0
                2024-01-17 18:10:09.214	debug	MQTT connection connected {"cmd":"connack","retain":false,"qos":0,"dup":false,"length":2,"topic":null,"payload":null,"sessionPresent":false,"returnCode":0}.
                
                roborock.0
                2024-01-17 18:10:09.123	debug	tcp client for 5umEnoJEB0hmM5UmYlkumw connected
                
                roborock.0
                2024-01-17 18:10:08.666	debug	Robot key: roborock.vacuum.a08
                
                roborock.0
                2024-01-17 18:10:08.665	debug	RoomIDs debug: {"16510226":"Studio"}
                
                roborock.0
                2024-01-17 18:10:08.665	info	MQTT initialized
                
                roborock.0
                2024-01-17 18:10:08.636	debug	localDevices: {"5umEnoJEB0hmM5UmYlkumw":"192.168.1.15"}
                
                roborock.0
                2024-01-17 18:10:02.231	info	Starting adapter. This might take a few minutes depending on your setup. Please wait.
                
                roborock.0
                2024-01-17 18:10:02.201	info	starting. Version 0.5.1 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v18.19.0, js-controller: 5.0.17
                
                roborock.0
                2024-01-17 18:10:01.203	debug	Plugin sentry Initialize Plugin (enabled=true)
                

                edith: erstes warning ist da. allerdings anderes thema.
                ich hab nur einen raum, der ist benannt. wurde auch richtig erkannt.

                
                roborock.0
                2024-01-17 18:10:08.665	debug	RoomIDs debug: {"16510226":"Studio"}
                

                2 min später

                
                roborock.0
                2024-01-17 18:12:05.443	warn	Failed to map rooms. You need to name your rooms via the mobile app on your phone.
                
                roborock.0
                2024-01-17 18:12:05.443	debug	All mapped rooms: []
                
                T Offline
                T Offline
                tritanium
                schrieb am zuletzt editiert von
                #438

                @da_woody

                okay, bei mir is gähnende Leere in Sachen roborock Adapter....

                Ein Sprachkommando zu Alexa, welches ein blockly triggert um Roborock "FRIDAY" zu finden via DP "find_me" funktioniert ohne Probleme.

                Also das klappt auch :-)

                bin mal gespannt.... noch 5 Minuten ....

                1 Antwort Letzte Antwort
                0
                • copystringC copystring

                  Ein Log brauche ich erstmal nicht. Könnt ihr bestätigen, dass der Ausfall mit der aktualisierten dev von gestern, ziemlich genau jede Stunde auftritt?

                  da_WoodyD Online
                  da_WoodyD Online
                  da_Woody
                  schrieb am zuletzt editiert von
                  #439

                  @copystring ich hab 75minuten gewartet. nur debug meldungen, bis auf die komische map warning.
                  kurze testfahrt gemacht, alles ok.
                  ich lass das log noch weiterlaufen. schaun wir mal...

                  gruß vom Woody
                  HAPPINESS is not a DESTINATION, it's a WAY of LIFE!

                  T 1 Antwort Letzte Antwort
                  0
                  • da_WoodyD da_Woody

                    @copystring ich hab 75minuten gewartet. nur debug meldungen, bis auf die komische map warning.
                    kurze testfahrt gemacht, alles ok.
                    ich lass das log noch weiterlaufen. schaun wir mal...

                    T Offline
                    T Offline
                    tritanium
                    schrieb am zuletzt editiert von
                    #440

                    @da_woody
                    hier derzeit auch alles ruhig.... nach 100 Minuten....

                    Ich warte auch noch :-)

                    ....

                    1 Antwort Letzte Antwort
                    0
                    • T Offline
                      T Offline
                      tritanium
                      schrieb am zuletzt editiert von
                      #441

                      @copystring

                      So, hier gehts los.... nach 3h dauerhafte re-connects....

                      Vorher keine Logs zum Roborock Adapter....:

                      roborock.0
                         2024-01-17 21:07:21.291	warn	MQTT connection reconnect.
                      roborock.0
                         2024-01-17 21:07:20.291	warn	MQTT connection close.
                      roborock.0
                         2024-01-17 21:07:20.124	warn	MQTT connection reconnect.
                      roborock.0
                         2024-01-17 21:07:19.123	warn	MQTT connection close.
                      roborock.0
                         2024-01-17 21:07:18.974	warn	MQTT connection reconnect.
                      roborock.0
                         2024-01-17 21:07:17.974	warn	MQTT connection close.
                      roborock.0
                         2024-01-17 21:07:17.737	warn	MQTT connection reconnect.
                      roborock.0
                         2024-01-17 21:07:17.734	warn	MQTT connection close.
                      roborock.0
                         2024-01-17 21:07:17.695	warn	Reconnecting mqtt client!
                      linux-control.0
                         2024-01-17 21:05:50.014	info	successful received data from ioBroker (192.168.50.5:22)
                      linux-control.0
                         2024-01-17 21:05:36.041	info	getting data from ioBroker (192.168.50.5:22)
                      tr-064.0
                         2024-01-17 21:05:04.878	info	starting. Version 4.2.18 in /opt/iobroker/node_modules/iobroker.tr-064, node: v18.17.0, js-controller: 5.0.17
                      host.iobroker
                         2024-01-17 21:05:02.170	info	instance system.adapter.tr-064.0 started with pid 2476245
                      host.iobroker
                         2024-01-17 21:05:00.932	info	Restart adapter system.adapter.tr-064.0 because enabled
                      host.iobroker
                         2024-01-17 21:05:00.931	info	instance system.adapter.tr-064.0 scheduled normal terminated and will be restarted on schedule.
                      tr-064.0
                         2024-01-17 21:05:00.595	info	terminating
                      tr-064.0
                         2024-01-17 21:05:00.229	info	Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      tr-064.0
                         2024-01-17 21:05:00.225	info	terminating
                      

                      Jede Sekunde disconnect & reconnect...

                      Thomas BraunT copystringC 2 Antworten Letzte Antwort
                      0
                      • T tritanium

                        @copystring

                        So, hier gehts los.... nach 3h dauerhafte re-connects....

                        Vorher keine Logs zum Roborock Adapter....:

                        roborock.0
                           2024-01-17 21:07:21.291	warn	MQTT connection reconnect.
                        roborock.0
                           2024-01-17 21:07:20.291	warn	MQTT connection close.
                        roborock.0
                           2024-01-17 21:07:20.124	warn	MQTT connection reconnect.
                        roborock.0
                           2024-01-17 21:07:19.123	warn	MQTT connection close.
                        roborock.0
                           2024-01-17 21:07:18.974	warn	MQTT connection reconnect.
                        roborock.0
                           2024-01-17 21:07:17.974	warn	MQTT connection close.
                        roborock.0
                           2024-01-17 21:07:17.737	warn	MQTT connection reconnect.
                        roborock.0
                           2024-01-17 21:07:17.734	warn	MQTT connection close.
                        roborock.0
                           2024-01-17 21:07:17.695	warn	Reconnecting mqtt client!
                        linux-control.0
                           2024-01-17 21:05:50.014	info	successful received data from ioBroker (192.168.50.5:22)
                        linux-control.0
                           2024-01-17 21:05:36.041	info	getting data from ioBroker (192.168.50.5:22)
                        tr-064.0
                           2024-01-17 21:05:04.878	info	starting. Version 4.2.18 in /opt/iobroker/node_modules/iobroker.tr-064, node: v18.17.0, js-controller: 5.0.17
                        host.iobroker
                           2024-01-17 21:05:02.170	info	instance system.adapter.tr-064.0 started with pid 2476245
                        host.iobroker
                           2024-01-17 21:05:00.932	info	Restart adapter system.adapter.tr-064.0 because enabled
                        host.iobroker
                           2024-01-17 21:05:00.931	info	instance system.adapter.tr-064.0 scheduled normal terminated and will be restarted on schedule.
                        tr-064.0
                           2024-01-17 21:05:00.595	info	terminating
                        tr-064.0
                           2024-01-17 21:05:00.229	info	Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        tr-064.0
                           2024-01-17 21:05:00.225	info	terminating
                        

                        Jede Sekunde disconnect & reconnect...

                        Thomas BraunT Offline
                        Thomas BraunT Offline
                        Thomas Braun
                        Most Active
                        schrieb am zuletzt editiert von
                        #442

                        @tritanium sagte in Neuer Adapter für Roborock-Staubsauger:

                        node: v18.17.0

                        Aktualisieren...

                        iob nodejs-update
                        

                        Linux-Werkzeugkasten:
                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                        NodeJS Fixer Skript:
                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                        da_WoodyD T 2 Antworten Letzte Antwort
                        0
                        • Thomas BraunT Thomas Braun

                          @tritanium sagte in Neuer Adapter für Roborock-Staubsauger:

                          node: v18.17.0

                          Aktualisieren...

                          iob nodejs-update
                          
                          da_WoodyD Online
                          da_WoodyD Online
                          da_Woody
                          schrieb am zuletzt editiert von
                          #443

                          @thomas-braun und wie erklärt sich dann das?
                          Node.js v18.19.0 (Es gibt eine neuere Version: v18.17.1)

                          gruß vom Woody
                          HAPPINESS is not a DESTINATION, it's a WAY of LIFE!

                          Thomas BraunT 1 Antwort Letzte Antwort
                          0
                          • Thomas BraunT Thomas Braun

                            @tritanium sagte in Neuer Adapter für Roborock-Staubsauger:

                            node: v18.17.0

                            Aktualisieren...

                            iob nodejs-update
                            
                            T Offline
                            T Offline
                            tritanium
                            schrieb am zuletzt editiert von
                            #444

                            @thomas-braun

                            Hallo Thomas,

                            hat denn die Version Auswirkungen aus die MQTT re-connects ?? :-\

                            Thomas BraunT 1 Antwort Letzte Antwort
                            0
                            • da_WoodyD da_Woody

                              @thomas-braun und wie erklärt sich dann das?
                              Node.js v18.19.0 (Es gibt eine neuere Version: v18.17.1)

                              Thomas BraunT Offline
                              Thomas BraunT Offline
                              Thomas Braun
                              Most Active
                              schrieb am zuletzt editiert von
                              #445

                              @da_woody

                              Das erklärt sich durch Caching.

                              Linux-Werkzeugkasten:
                              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                              NodeJS Fixer Skript:
                              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                              1 Antwort Letzte Antwort
                              0
                              • T tritanium

                                @thomas-braun

                                Hallo Thomas,

                                hat denn die Version Auswirkungen aus die MQTT re-connects ?? :-\

                                Thomas BraunT Offline
                                Thomas BraunT Offline
                                Thomas Braun
                                Most Active
                                schrieb am zuletzt editiert von
                                #446

                                @tritanium sagte in Neuer Adapter für Roborock-Staubsauger:

                                hat denn die Version Auswirkungen aus die MQTT re-connects ??

                                NodeJS ist das 'Betriebssystem' für den ioBroker, das wirkt sich natürlich auf alles aus.

                                Heute Nachmittag war eine alte nodeJS-Version der Grund für gescheiterte Logins bei DHL. Aktuelles nodeJS installiert, schon funktionierte es. Da war zuvor auch die Notwendigkeit eines Updates als komplett unnötig angesehen worden.
                                Nein, ein aktuelles, konsistent aufgesetztes nodeJS ist essentiell wichtig.

                                Linux-Werkzeugkasten:
                                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                NodeJS Fixer Skript:
                                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                T 1 Antwort Letzte Antwort
                                0
                                • Thomas BraunT Thomas Braun

                                  @tritanium sagte in Neuer Adapter für Roborock-Staubsauger:

                                  hat denn die Version Auswirkungen aus die MQTT re-connects ??

                                  NodeJS ist das 'Betriebssystem' für den ioBroker, das wirkt sich natürlich auf alles aus.

                                  Heute Nachmittag war eine alte nodeJS-Version der Grund für gescheiterte Logins bei DHL. Aktuelles nodeJS installiert, schon funktionierte es. Da war zuvor auch die Notwendigkeit eines Updates als komplett unnötig angesehen worden.
                                  Nein, ein aktuelles, konsistent aufgesetztes nodeJS ist essentiell wichtig.

                                  T Offline
                                  T Offline
                                  tritanium
                                  schrieb am zuletzt editiert von
                                  #447

                                  @thomas-braun

                                  Danke für die Info :dog:

                                  ...dann werde ich mal die/das Update "eben" machen.....

                                  Thomas BraunT 1 Antwort Letzte Antwort
                                  0
                                  • T tritanium

                                    @thomas-braun

                                    Danke für die Info :dog:

                                    ...dann werde ich mal die/das Update "eben" machen.....

                                    Thomas BraunT Offline
                                    Thomas BraunT Offline
                                    Thomas Braun
                                    Most Active
                                    schrieb am zuletzt editiert von
                                    #448

                                    @tritanium sagte in Neuer Adapter für Roborock-Staubsauger:

                                    ...dann werde ich mal die/das Update "eben" machen.....

                                    Dauert 2 Minuten.

                                    Linux-Werkzeugkasten:
                                    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                    NodeJS Fixer Skript:
                                    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                    da_WoodyD 1 Antwort Letzte Antwort
                                    0
                                    • Thomas BraunT Thomas Braun

                                      @tritanium sagte in Neuer Adapter für Roborock-Staubsauger:

                                      ...dann werde ich mal die/das Update "eben" machen.....

                                      Dauert 2 Minuten.

                                      da_WoodyD Online
                                      da_WoodyD Online
                                      da_Woody
                                      schrieb am zuletzt editiert von
                                      #449

                                      @thomas-braun klar gehts schnell.

                                      ioBroker nodejs updater 2023-10-13
                                      
                                      Recommended nodejs-version is: 18.19.0
                                      Checking your installation now. Please be patient!
                                      
                                      Your current setup is:
                                      /usr/bin/nodejs         v18.19.0
                                      /usr/bin/node           v18.19.0
                                      /usr/bin/npm            10.2.3
                                      /usr/bin/npx            10.2.3
                                      /usr/bin/corepack       0.22.0
                                      
                                      We found these nodejs versions available for installation:
                                      
                                      nodejs:
                                        Installed: 18.19.0-1nodesource1
                                        Candidate: 18.19.0-1nodesource1
                                      
                                      

                                      Node.js v18.19.0 nur ist halt die meldung über eine angeblich neuere weg.

                                      gruß vom Woody
                                      HAPPINESS is not a DESTINATION, it's a WAY of LIFE!

                                      Thomas BraunT 1 Antwort Letzte Antwort
                                      0
                                      • da_WoodyD da_Woody

                                        @thomas-braun klar gehts schnell.

                                        ioBroker nodejs updater 2023-10-13
                                        
                                        Recommended nodejs-version is: 18.19.0
                                        Checking your installation now. Please be patient!
                                        
                                        Your current setup is:
                                        /usr/bin/nodejs         v18.19.0
                                        /usr/bin/node           v18.19.0
                                        /usr/bin/npm            10.2.3
                                        /usr/bin/npx            10.2.3
                                        /usr/bin/corepack       0.22.0
                                        
                                        We found these nodejs versions available for installation:
                                        
                                        nodejs:
                                          Installed: 18.19.0-1nodesource1
                                          Candidate: 18.19.0-1nodesource1
                                        
                                        

                                        Node.js v18.19.0 nur ist halt die meldung über eine angeblich neuere weg.

                                        Thomas BraunT Offline
                                        Thomas BraunT Offline
                                        Thomas Braun
                                        Most Active
                                        schrieb am zuletzt editiert von
                                        #450

                                        @da_woody sagte in Neuer Adapter für Roborock-Staubsauger:

                                        nur ist halt die meldung über eine angeblich neuere weg.

                                        Ja, und? Die war ja eh falsch. War die Anzeige im Admin, oder?

                                        Linux-Werkzeugkasten:
                                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                        NodeJS Fixer Skript:
                                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                        da_WoodyD 1 Antwort Letzte Antwort
                                        0
                                        • Thomas BraunT Thomas Braun

                                          @da_woody sagte in Neuer Adapter für Roborock-Staubsauger:

                                          nur ist halt die meldung über eine angeblich neuere weg.

                                          Ja, und? Die war ja eh falsch. War die Anzeige im Admin, oder?

                                          da_WoodyD Online
                                          da_WoodyD Online
                                          da_Woody
                                          schrieb am zuletzt editiert von
                                          #451

                                          @thomas-braun im info
                                          166c9081-268c-4b27-bf6b-9ac92a107ed4-grafik.png

                                          gruß vom Woody
                                          HAPPINESS is not a DESTINATION, it's a WAY of LIFE!

                                          Thomas BraunT 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          444

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe