Test Adapter OctoPrint

frana120500 · 23 Jan 2022, 19:22

@hegse änder mal die source url auf

'http://192.168.178.176:8080/?action=snapshot'

frana120500 · 23 Jan 2022, 19:28

gerade selbst getestet... funktioniert

hegse · 23 Jan 2022, 19:33

@frana120500 sagte in Test Adapter OctoPrint:

@hegse änder mal die source url auf

'http://192.168.178.176:8080/?action=snapshot'

Vielen Dank!
Funktioniert bei mir so http://192.168.178.176/webcam/?action=snapshot
Sehr schön, jetzt muß ich nur noch den Empfänger ändern, meine Frau braucht die Fotos vom Drucker nicht wirklich

frana120500 · 23 Jan 2022, 19:39

@hegse ein kleines Wort

wenn es für dich einfacher ist Blockly zu benutzen sag Bescheid... da sieht der Block etwas einfacher aus

hegse · 23 Jan 2022, 21:04

@frana120500
Jeep, wäre für mich definitiv einfacher.

Edit:
auf die schnelle mit blockly

haus-automatisierung · 25 Jan 2022, 09:13

Bitte beim Thema Adapter-Test und Probleme mit dem Adapter bleiben

SevenUp · 30 Jan 2022, 22:40

EDIT: nun ist alles wieder OK... Auch mit neuen Aufträgen

ich nutze den Adapter erst seit gestern und möchte es gerne für VIS Einbindung nutzen.
Was mir heute aufgefallen ist:

der aktuelle Druck wird unter "Files" nicht angezeigt
unter "Printer Status" wird oft "API not connected" angezeigt, im Log entsprechend "API is offline" und Adapter geht auf gelb. Nach einigen Sekunden ist wieder alles okay.

Was kann ich hier tun?

octoprint.0	2022-01-30 14:57:24.614	debug	(14149) system.adapter.admin.0: logging true
octoprint.0	2022-01-30 14:57:22.291	debug	(14149) API is offline
octoprint.0	2022-01-30 14:57:22.291	debug	(14149) (version) received error - API is now offline: {"message":"timeout of 2000ms exceeded","name":"Error","stack":"Error: timeout of 2000ms exceeded\n at createError (/opt/iobroker/node_module
octoprint.0	2022-01-30 14:57:22.289	info	(14149) error ECONNABORTED from /api/version: timeout of 2000ms exceeded
octoprint.0	2022-01-30 14:57:20.288	debug	(14149) refreshStateTimeout: re-created refresh timeout (printing): id 82 - seconds: 10
octoprint.0	2022-01-30 14:57:20.287	debug	(14149) sending "get" request to "/api/version" without data
octoprint.0	2022-01-30 14:57:20.287	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:57:20.287	debug	(14149) refreshState: started from "timeout (printing)"
octoprint.0	2022-01-30 14:57:12.888	debug	(14149) received 200 response from /api/job with content: {"job":{"averagePrintTime":8170.761188558,"estimatedPrintTime":8168.974748087396,"filament":{"tool0":{"length":10424.098388664424,"volume":25
octoprint.0	2022-01-30 14:57:12.887	debug	(14149) received 200 response from /api/printer with content: {"state":{"error":"","flags":{"cancelling":false,"closedOrError":false,"error":false,"finishing":false,"operational":true,"paused":false,
octoprint.0	2022-01-30 14:57:12.880	debug	(14149) updatePrinterStatus from: "Printing" -> printerOperational: true, printerPrinting: true
octoprint.0	2022-01-30 14:57:12.879	debug	(14149) received 200 response from /api/connection with content: {"current":{"baudrate":250000,"port":"/dev/ttyUSB0","printerProfile":"_default","state":"Printing"},"options":{"baudratePreference":25
octoprint.0	2022-01-30 14:57:11.413	debug	(14149) sending "get" request to "/api/job" without data
octoprint.0	2022-01-30 14:57:11.413	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:57:11.412	debug	(14149) sending "get" request to "/api/printer" without data
octoprint.0	2022-01-30 14:57:11.412	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:57:11.411	debug	(14149) sending "get" request to "/api/connection" without data
octoprint.0	2022-01-30 14:57:11.411	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:57:11.410	debug	(14149) connected to OctoPrint API - online! - status: 200
octoprint.0	2022-01-30 14:57:11.410	debug	(14149) received 200 response from /api/version with content: {"api":"0.1","server":"1.7.3","text":"OctoPrint 1.7.3"}
octoprint.0	2022-01-30 14:57:10.286	debug	(14149) refreshStateTimeout: re-created refresh timeout (printing): id 81 - seconds: 10
octoprint.0	2022-01-30 14:57:10.286	debug	(14149) sending "get" request to "/api/version" without data
octoprint.0	2022-01-30 14:57:10.285	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:57:10.285	debug	(14149) refreshState: started from "timeout (printing)"
octoprint.0	2022-01-30 14:57:01.852	debug	(14149) updatePrinterStatus from: "Printing" -> printerOperational: true, printerPrinting: true
octoprint.0	2022-01-30 14:57:01.852	debug	(14149) received 200 response from /api/connection with content: {"current":{"baudrate":250000,"port":"/dev/ttyUSB0","printerProfile":"_default","state":"Printing"},"options":{"baudratePreference":25
octoprint.0	2022-01-30 14:57:01.721	debug	(14149) received 200 response from /api/job with content: {"job":{"averagePrintTime":8170.761188558,"estimatedPrintTime":8168.974748087396,"filament":{"tool0":{"length":10424.098388664424,"volume":25
octoprint.0	2022-01-30 14:57:01.705	debug	(14149) received 200 response from /api/printer with content: {"state":{"error":"","flags":{"cancelling":false,"closedOrError":false,"error":false,"finishing":false,"operational":true,"paused":false,
octoprint.0	2022-01-30 14:57:00.437	debug	(14149) sending "get" request to "/api/job" without data
octoprint.0	2022-01-30 14:57:00.437	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:57:00.436	debug	(14149) sending "get" request to "/api/printer" without data
octoprint.0	2022-01-30 14:57:00.436	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:57:00.435	debug	(14149) sending "get" request to "/api/connection" without data
octoprint.0	2022-01-30 14:57:00.435	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:57:00.435	debug	(14149) connected to OctoPrint API - online! - status: 200
octoprint.0	2022-01-30 14:57:00.434	debug	(14149) received 200 response from /api/version with content: {"api":"0.1","server":"1.7.3","text":"OctoPrint 1.7.3"}
octoprint.0	2022-01-30 14:57:00.285	debug	(14149) refreshStateTimeout: re-created refresh timeout (printing): id 80 - seconds: 10
octoprint.0	2022-01-30 14:57:00.284	debug	(14149) sending "get" request to "/api/version" without data
octoprint.0	2022-01-30 14:57:00.284	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:57:00.284	debug	(14149) refreshState: started from "timeout (API not connected)"
octoprint.0	2022-01-30 14:56:53.589	debug	(14149) updatePrinterStatus from: "Printing" -> printerOperational: true, printerPrinting: true
octoprint.0	2022-01-30 14:56:53.588	debug	(14149) received 200 response from /api/connection with content: {"current":{"baudrate":250000,"port":"/dev/ttyUSB0","printerProfile":"_default","state":"Printing"},"options":{"baudratePreference":25
octoprint.0	2022-01-30 14:56:53.502	debug	(14149) received 200 response from /api/job with content: {"job":{"averagePrintTime":8170.761188558,"estimatedPrintTime":8168.974748087396,"filament":{"tool0":{"length":10424.098388664424,"volume":25
octoprint.0	2022-01-30 14:56:53.453	debug	(14149) received 200 response from /api/printer with content: {"state":{"error":"","flags":{"cancelling":false,"closedOrError":false,"error":false,"finishing":false,"operational":true,"paused":false,
octoprint.0	2022-01-30 14:56:52.200	debug	(14149) sending "get" request to "/api/job" without data
octoprint.0	2022-01-30 14:56:52.200	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:52.199	debug	(14149) sending "get" request to "/api/printer" without data
octoprint.0	2022-01-30 14:56:52.199	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:52.198	debug	(14149) sending "get" request to "/api/connection" without data
octoprint.0	2022-01-30 14:56:52.197	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:52.196	debug	(14149) connected to OctoPrint API - online! - status: 200
octoprint.0	2022-01-30 14:56:52.196	debug	(14149) received 200 response from /api/version with content: {"api":"0.1","server":"1.7.3","text":"OctoPrint 1.7.3"}
octoprint.0	2022-01-30 14:56:50.284	debug	(14149) refreshStateTimeout: re-created refresh timeout (API not connected): id 79 - seconds: 10
octoprint.0	2022-01-30 14:56:50.283	debug	(14149) sending "get" request to "/api/version" without data
octoprint.0	2022-01-30 14:56:50.283	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:50.282	debug	(14149) refreshState: started from "timeout (API not connected)"
octoprint.0	2022-01-30 14:56:42.284	debug	(14149) API is offline
octoprint.0	2022-01-30 14:56:42.284	debug	(14149) (version) received error - API is now offline: {"message":"timeout of 2000ms exceeded","name":"Error","stack":"Error: timeout of 2000ms exceeded\n at createError (/opt/iobroker/node_module
octoprint.0	2022-01-30 14:56:42.282	debug	(14149) timeout of 2000ms exceeded
octoprint.0	2022-01-30 14:56:40.281	debug	(14149) refreshStateTimeout: re-created refresh timeout (API not connected): id 78 - seconds: 10
octoprint.0	2022-01-30 14:56:40.281	debug	(14149) sending "get" request to "/api/version" without data
octoprint.0	2022-01-30 14:56:40.280	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:40.280	debug	(14149) refreshState: started from "timeout (API not connected)"
octoprint.0	2022-01-30 14:56:32.282	debug	(14149) API is offline
octoprint.0	2022-01-30 14:56:32.282	debug	(14149) (version) received error - API is now offline: {"message":"timeout of 2000ms exceeded","name":"Error","stack":"Error: timeout of 2000ms exceeded\n at createError (/opt/iobroker/node_module
octoprint.0	2022-01-30 14:56:32.281	debug	(14149) timeout of 2000ms exceeded
octoprint.0	2022-01-30 14:56:30.279	debug	(14149) refreshStateTimeout: re-created refresh timeout (API not connected): id 77 - seconds: 10
octoprint.0	2022-01-30 14:56:30.278	debug	(14149) sending "get" request to "/api/version" without data
octoprint.0	2022-01-30 14:56:30.278	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:30.278	debug	(14149) refreshState: started from "timeout (printing)"
octoprint.0	2022-01-30 14:56:22.281	debug	(14149) API is offline
octoprint.0	2022-01-30 14:56:22.281	debug	(14149) (version) received error - API is now offline: {"message":"timeout of 2000ms exceeded","name":"Error","stack":"Error: timeout of 2000ms exceeded\n at createError (/opt/iobroker/node_module
octoprint.0	2022-01-30 14:56:22.279	info	(14149) error ECONNABORTED from /api/version: timeout of 2000ms exceeded
octoprint.0	2022-01-30 14:56:20.278	debug	(14149) refreshStateTimeout: re-created refresh timeout (printing): id 76 - seconds: 10
octoprint.0	2022-01-30 14:56:20.277	debug	(14149) sending "get" request to "/api/version" without data
octoprint.0	2022-01-30 14:56:20.277	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:20.276	debug	(14149) refreshState: started from "timeout (printing)"
octoprint.0	2022-01-30 14:56:13.112	debug	(14149) received 200 response from /api/job with content: {"job":{"averagePrintTime":8170.761188558,"estimatedPrintTime":8168.974748087396,"filament":{"tool0":{"length":10424.098388664424,"volume":25
octoprint.0	2022-01-30 14:56:13.103	debug	(14149) received 200 response from /api/printer with content: {"state":{"error":"","flags":{"cancelling":false,"closedOrError":false,"error":false,"finishing":false,"operational":true,"paused":false,
octoprint.0	2022-01-30 14:56:13.098	debug	(14149) updatePrinterStatus from: "Printing" -> printerOperational: true, printerPrinting: true
octoprint.0	2022-01-30 14:56:13.098	debug	(14149) received 200 response from /api/connection with content: {"current":{"baudrate":250000,"port":"/dev/ttyUSB0","printerProfile":"_default","state":"Printing"},"options":{"baudratePreference":25
octoprint.0	2022-01-30 14:56:11.482	debug	(14149) sending "get" request to "/api/job" without data
octoprint.0	2022-01-30 14:56:11.482	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:11.481	debug	(14149) sending "get" request to "/api/printer" without data
octoprint.0	2022-01-30 14:56:11.481	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:11.480	debug	(14149) sending "get" request to "/api/connection" without data
octoprint.0	2022-01-30 14:56:11.480	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:11.479	debug	(14149) connected to OctoPrint API - online! - status: 200
octoprint.0	2022-01-30 14:56:11.479	debug	(14149) received 200 response from /api/version with content: {"api":"0.1","server":"1.7.3","text":"OctoPrint 1.7.3"}
octoprint.0	2022-01-30 14:56:10.276	debug	(14149) refreshStateTimeout: re-created refresh timeout (printing): id 75 - seconds: 10
octoprint.0	2022-01-30 14:56:10.275	debug	(14149) sending "get" request to "/api/version" without data
octoprint.0	2022-01-30 14:56:10.275	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:10.274	debug	(14149) refreshState: started from "timeout (API not connected)"
octoprint.0	2022-01-30 14:56:01.345	debug	(14149) received 200 response from /api/job with content: {"job":{"averagePrintTime":8170.761188558,"estimatedPrintTime":8168.974748087396,"filament":{"tool0":{"length":10424.098388664424,"volume":25
octoprint.0	2022-01-30 14:56:01.311	debug	(14149) received 200 response from /api/printer with content: {"state":{"error":"","flags":{"cancelling":false,"closedOrError":false,"error":false,"finishing":false,"operational":true,"paused":false,
octoprint.0	2022-01-30 14:56:01.298	debug	(14149) updatePrinterStatus from: "Printing" -> printerOperational: true, printerPrinting: true
octoprint.0	2022-01-30 14:56:01.297	debug	(14149) received 200 response from /api/connection with content: {"current":{"baudrate":250000,"port":"/dev/ttyUSB0","printerProfile":"_default","state":"Printing"},"options":{"baudratePreference":25
octoprint.0	2022-01-30 14:56:00.662	debug	(14149) sending "get" request to "/api/job" without data
octoprint.0	2022-01-30 14:56:00.662	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:00.661	debug	(14149) sending "get" request to "/api/printer" without data
octoprint.0	2022-01-30 14:56:00.661	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:00.660	debug	(14149) sending "get" request to "/api/connection" without data
octoprint.0	2022-01-30 14:56:00.660	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:00.659	debug	(14149) connected to OctoPrint API - online! - status: 200
octoprint.0	2022-01-30 14:56:00.659	debug	(14149) received 200 response from /api/version with content: {"api":"0.1","server":"1.7.3","text":"OctoPrint 1.7.3"}
octoprint.0	2022-01-30 14:56:00.274	debug	(14149) refreshStateTimeout: re-created refresh timeout (API not connected): id 74 - seconds: 10
octoprint.0	2022-01-30 14:56:00.273	debug	(14149) sending "get" request to "/api/version" without data
octoprint.0	2022-01-30 14:56:00.272	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:56:00.272	debug	(14149) refreshState: started from "timeout (API not connected)"
octoprint.0	2022-01-30 14:55:52.275	debug	(14149) API is offline
octoprint.0	2022-01-30 14:55:52.274	debug	(14149) (version) received error - API is now offline: {"message":"timeout of 2000ms exceeded","name":"Error","stack":"Error: timeout of 2000ms exceeded\n at createError (/opt/iobroker/node_module
octoprint.0	2022-01-30 14:55:52.273	debug	(14149) timeout of 2000ms exceeded
octoprint.0	2022-01-30 14:55:50.272	debug	(14149) refreshStateTimeout: re-created refresh timeout (API not connected): id 73 - seconds: 10
octoprint.0	2022-01-30 14:55:50.271	debug	(14149) sending "get" request to "/api/version" without data
octoprint.0	2022-01-30 14:55:50.271	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:55:50.270	debug	(14149) refreshState: started from "timeout (printing)"
octoprint.0	2022-01-30 14:55:42.273	debug	(14149) API is offline
octoprint.0	2022-01-30 14:55:42.272	debug	(14149) (version) received error - API is now offline: {"message":"timeout of 2000ms exceeded","name":"Error","stack":"Error: timeout of 2000ms exceeded\n at createError (/opt/iobroker/node_module
octoprint.0	2022-01-30 14:55:42.271	info	(14149) error ECONNABORTED from /api/version: timeout of 2000ms exceeded
octoprint.0	2022-01-30 14:55:40.269	debug	(14149) refreshStateTimeout: re-created refresh timeout (printing): id 72 - seconds: 10
octoprint.0	2022-01-30 14:55:40.268	debug	(14149) sending "get" request to "/api/version" without data
octoprint.0	2022-01-30 14:55:40.268	debug	(14149) Starting service request
octoprint.0	2022-01-30 14:55:40.268	debug	(14149) refreshState: started from "timeout (API not connected)"
octoprint.0	2022-01-30 14:55:32.638	debug	(14149) received 200 response from /api/job with content: {"job":{"averagePrintTime":8170.761188558,"estimatedPrintTime":8168.974748087396,"filament":{"tool0":{"length":10424.098388664424,"volume":25
octoprint.0	2022-01-30 14:55:32.628	debug	(14149) received 200 response from /api/printer with content: {"state":{"error":"","flags":{"cancelling":false,"closedOrError":false,"error":false,"finishing":false,"operational":true,"paused":false,
octoprint.0	2022-01-30 14:55:32.610	debug	(14149) updatePrinterStatus from: "Printing" -> printerOperational: true, printerPrinting: true
octoprint.0	2022-01-30 14:55:32.610	debug	(14149) received 200 response from /api/connection with content: {"current":{"baudrate":250000,"port":"/dev/ttyUSB0","printerProfile":"_default","state":"Printing"},"options":{"baudratePreference":25
octoprint.0	2022-01-30 14:55:30.810	debug	(14149) sending "get" request to "/api/job" without data

SevenUp · 30 Jan 2022, 22:52

Nun habe ich es aber kaputt gespielt:

Bei mir wurden DP für Thumbnails nicht angezeigt, deshalb habe ich den Adapter neuinstalliert (von v3 auf v3). Danach kommt es zu dem Fehler.
Neuinstallation bringt nichts, "iobroker upload octoprint" und "... all" auch nicht. Sicherheitshalber ein "iobroker fix" löste das Problem auch nicht.

Und nu?

$ ./iobroker upgrade octoprint@3.0.0
Update octoprint from @3.0.0 to @3.0.0
NPM version: 6.14.15npm install iobroker.octoprint@3.0.0 --loglevel error --prefix "/opt/iobroker" (System call)
upload [11] octoprint.admin /opt/iobroker/node_modules/iobroker.octoprint/admin/octoprint.png octoprint.png image/png
Update "system.adapter.octoprint.0"
upload [10] octoprint.admin /opt/iobroker/node_modules/iobroker.octoprint/admin/jsonConfig.json jsonConfig.json application/json
upload [9] octoprint.admin /opt/iobroker/node_modules/iobroker.octoprint/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json
upload [8] octoprint.admin /opt/iobroker/node_modules/iobroker.octoprint/admin/i18n/ru/translations.json i18n/ru/translations.json application/json
upload [7] octoprint.admin /opt/iobroker/node_modules/iobroker.octoprint/admin/i18n/pt/translations.json i18n/pt/translations.json application/json
upload [6] octoprint.admin /opt/iobroker/node_modules/iobroker.octoprint/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
upload [5] octoprint.admin /opt/iobroker/node_modules/iobroker.octoprint/admin/i18n/nl/translations.json i18n/nl/translations.json application/json
upload [4] octoprint.admin /opt/iobroker/node_modules/iobroker.octoprint/admin/i18n/it/translations.json i18n/it/translations.json application/json
upload [3] octoprint.admin /opt/iobroker/node_modules/iobroker.octoprint/admin/i18n/fr/translations.json i18n/fr/translations.json application/json
upload [2] octoprint.admin /opt/iobroker/node_modules/iobroker.octoprint/admin/i18n/es/translations.json i18n/es/translations.json application/json
upload [1] octoprint.admin /opt/iobroker/node_modules/iobroker.octoprint/admin/i18n/en/translations.json i18n/en/translations.json application/json
upload [0] octoprint.admin /opt/iobroker/node_modules/iobroker.octoprint/admin/i18n/de/translations.json i18n/de/translations.json application/json
Adapter "octoprint" updated
process exited with code 0

EDIT:
--> tritt nur mit der alten Admin Oberfläche auf (benötige ich leider weiterhin für den linkeddevices Adapter). Schalte ich auf die neue Oberfläche um, sehe ich auch die Octoprint Config und die Möglichkeit die Plugins zu aktivieren (sah ich in der alten Oberfläche nicht).

haus-automatisierung · 31 Jan 2022, 08:46

@sevenup sagte in Test Adapter OctoPrint:

--> tritt nur mit der alten Admin Oberfläche auf (benötige ich leider weiterhin für den linkeddevices Adapter).

Der ioBroker Admin liegt mittlerweile in Version 5 vor. Leider muss man bei der Adapter-Pflege dann aktuell drei verschiedene Dateien aktualisieren, wenn man z.B. ein neues Textfeld im Admin möchte, welches in allen Versionen funktioniert. Da mir dazu die Zeit beim testen und entwickeln fehlt, habe ich alles rausgeworfen und nur die Admin 5 Konfiguration drin gelassen. Zumal ich selbst die "alte UI" gar nicht mehr verwende.

Hast Du Lust das zu pflegen?

SevenUp · 31 Jan 2022, 10:17

@haus-automatisierung verstehe ich vollkommen! Ich würde auch gerne auf den Admin 5 umsteigen, aber linkeddevices unterstützt es noch nicht... Deshalb schalte ich immer zwischen der alten und neue GUI hin und her und manchmal bleibe ich bei der alten hängen.

Würdest du in der Adapter Beschreibung einen gut sichtbaren Hinweis platzieren, dass man die neue GUI nutzen sollte? Sonst kommt es evtl wie bei mir zu Verwirrungen

hetti72 · 1 Feb 2022, 15:57

Hallo,

ich bin noch recht neu in dem Thema 3d Druckt und Octoprint. Ich habe nun mal eine Frage zum Seriellen reconnect von Octoprint.
Gibt es die Möglichkeit über den Adapter in Octoprint den seriellen Reconnect zum Drucker zu triggern? Ich hab beim ersten Blick über die Objekte nichts passendes gefunden.

Hintergrund: Ich möchte über IOBroker den Drucker mit einem Smart Plug ein bzw. auschalten, der Raspi mit Octoprint soll aber anbleiben. Allerdings verbindet sich Octoprint nicht wieder automatisch mit dem Drucker, wenn dieser ausgeschaltet war.

gruß,
Frank

SevenUp · 1 Feb 2022, 16:07

@hetti72 Hallo Frank,

vielleicht hilft dir dieser Plugin?
https://plugins.octoprint.org/plugins/portlister/

"It also (if you have autoconnect turned on), will automatically connect to the printer (if the new port is the same as the one you’ve selected in connection settings) after a reasonable (long) delay to wait for the printer to actually come on."

Ralf_N · 1 Feb 2022, 17:36

@hetti72

So habe ich das gelöst. Bei mir starte und verbindet sich alles von "alleine"

PS: Drucker UND ! Octopi hängen bei mir an einem Shelly PlugS

da_Woody · 1 Feb 2022, 18:01

@ralf_n sagte in Test Adapter OctoPrint:

Drucker UND ! Octopi hängen bei mir an einem Shelly PlugS

bei mir zwar an einer SP112, aber wozu gibts

da brauch ich kein blockly...

Ralf_N · 1 Feb 2022, 18:11

@da_woody

weeennn ich aber manuell den Drucker ausschalte um etwas fertiges vom Bett zu bekommen und dabei der PI an bleibt ( weil er gerade noch ein Video rendert ) nutzt dir dein "automatisch bei ..." nix

DA greift dann aber mein blockly, wenn ich dann den Drucker einfach nur wieder an mache

@hetti72

Schau dir mal die Funktion im Adapter an. Das könnte deine Lösung sein:

Ralf_N · 1 Feb 2022, 18:15

@da_woody
Nachtrag.

Und wenn Matthias schon so einen geilen Adapter zusammen klöppelt, muss man doch auch seinen Funktionsumfang ausschöpfen !

da_Woody · 1 Feb 2022, 18:19

@ralf_n sagte in Test Adapter OctoPrint:

weeennn ich aber manuell den Drucker ausschalte um etwas fertiges vom Bett zu bekommen

hä? die temperaturen werden nach druck ja automatisch auf 0 gesetzt. da kühlt das bett ab. wozu den drucker ausschalten? wird dadurch nicht schneller kalt... ergibt für mich keinen sinn, aber wie jeder mag...

SevenUp · 1 Feb 2022, 18:34

@ralf_n oder eben den von mir erwähnten Plugin.
Dann kann man sich das Blockly auch sparen

Ralf_N · 1 Feb 2022, 19:34

@sevenup
welches ich bis dato noch nicht kannte.

Klingt intersannt und schau ich mir an.

Thx.

hetti72 · 2 Feb 2022, 14:09

@ralf_n

Vielen Dank,

das ist genau das was ich gesucht habe.

Danke

NEWS

Test Adapter OctoPrint

Support us

578
Online

31.4k
Users

79.0k
Topics

1.3m
Posts

NEWS

Test Adapter OctoPrint

Support us

578Online

31.4kUsers

79.0kTopics

1.3mPosts

578
Online

31.4k
Users

79.0k
Topics

1.3m
Posts