Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter OctoPrint

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Test Adapter OctoPrint

    This topic has been deleted. Only users with topic management privileges can see it.
    • U
      UncleB last edited by

      Ist es möglich das man über den Adapter ein Screenshot der Webcam abholt?

      Hintergrund:
      Ich finde das Script von @Sven_Topp um sich über den aktuellen Status des Drucks über Telegram informieren zu können super...
      Eine der nützlichsten Funktionen, nach Fertigstellung des Drucks bekommt man n Screenshot der Webcam aufs Handy gesendet..
      Seit dem man bei Ocotprint einen Benutzer mit Passwort erstellen muss, funktioniert das ganze so leider nicht mehr, da man sich mit dem Script dann irgendwie bei OctoPi anmelden müsste um an den Screenshot zu gelangen..
      Dafür reichen meine Kenntnisse nicht aus..

      da_Woody haus-automatisierung 2 Replies Last reply Reply Quote 0
      • da_Woody
        da_Woody @UncleB last edited by

        @uncleb ich verwende telgram nicht, aber es gibt mehrere möglichkeiten.
        du kannst dir das Access Anywhere - The Spaghetti Detective plugin in octoprint installieren.
        da bekommst du bei druckproblemen und ende eine email mit foto per email. bei einem problem kannst du entscheiden, oder der druck abgebrochen, oder fortgesetzt werden soll. oder du installierst OctoRemote aufs handy, dann kannst du steuern, live zusehn u.s.w.

        1 Reply Last reply Reply Quote 0
        • haus-automatisierung
          haus-automatisierung Developer Most Active @UncleB last edited by

          @uncleb sagte in Test Adapter OctoPrint:

          Eine der nützlichsten Funktionen, nach Fertigstellung des Drucks bekommt man n Screenshot der Webcam aufs Handy gesendet..

          Also ich habe bisher immer mJPEGstreamer separat auf dem Pi installiert und damit eine USB-Kamera zu einer IP-Kamera gemacht. Das hat dann nichts mit OctoPrint zu tun und ich kann einfach über eine URL die Snapshots holen und per Telegram versenden.

          https://youtu.be/NiTXB4lZv0A?t=704

          1 Reply Last reply Reply Quote 0
          • H
            hegse last edited by

            Hallo.

            Habe mir die beliebte Logitech C270 Webcam geholt und sie in Octoprint eingebunden. Das funktioniert auch wunderbar. Wenn ich jetzt allerdings ein Bild via Telegram über Iobroker versenden möchte passiert gar nix.
            Nutze folgendes Script (irgendwo mal gefunden):

            /* BILDSPEICHERUNG
            soll bei Aktion Webcam Bild speichern und per telegram senden
            Skript ist normalerweise inaktiv und wird per ScriptEnabled ausgelöst
            */
            
            var source_url = 'http://192.168.178.176/webcam/?action=stream', // Kamerabild zB http://kameraserver:9090/image1.jpg
                dest_path = '/opt/iobroker/temp/cam/';
            
            var request = require('request');
            var fs      = require('fs');
            
            
            // Bild an telegram schicken (immer Dienst 3)
            function sendImage (pfad) {
                setTimeout(function() {
                    sendTo('telegram.0', pfad);
                    log('Webcam Bild per telegram verschickt');
                }, 2 * 1000);
            }
            
            // Bild speichern
            function saveImage() {
                request.get({url: source_url, encoding: 'binary'}, function (err, response, body) {
                    fs.writeFile(dest_path + 'image1.jpg', body, 'binary', function(err) {
            
                    if (err) {
                        log('Fehler beim Bild speichern: ' + err, 'warn');
                    } else {
                        log('Webcam Bild gespeichert');
                        sendImage(dest_path + 'image1.jpg');
                    }
                  }); 
                });
            }
            
            
            // bei Skriptstart ausführen
            saveImage();
            
            // selbständig Skript wieder anhalten (nach 12s)
            setStateDelayed('javascript.' + instance +  '.scriptEnabled.' + name.slice(10), false, 12*1000);
            

            Verzeichnis ist vorhanden, funktioniert mit meinen Reolink Kameras. Liegt es am Stream das kein Bild abgegriffen und gespeichert wird?

            frana120500 1 Reply Last reply Reply Quote 0
            • frana120500
              frana120500 @hegse last edited by

              @hegse änder mal die source url auf

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

              frana120500 H 2 Replies Last reply Reply Quote 0
              • frana120500
                frana120500 @frana120500 last edited by

                gerade selbst getestet... funktioniert

                1 Reply Last reply Reply Quote 0
                • H
                  hegse @frana120500 last edited by

                  @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 1 Reply Last reply Reply Quote 0
                  • frana120500
                    frana120500 @hegse last edited by

                    @hegse 🙂 ein kleines Wort

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

                    H 1 Reply Last reply Reply Quote 0
                    • H
                      hegse @frana120500 last edited by hegse

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

                      Edit:
                      auf die schnelle mit blockly
                      Screenshot_20220123-220231_Chrome.jpg

                      1 Reply Last reply Reply Quote 0
                      • haus-automatisierung
                        haus-automatisierung Developer Most Active last edited by

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

                        1 Reply Last reply Reply Quote 2
                        • S
                          SevenUp last edited by SevenUp

                          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?

                          2022-01-30 14_52_01-objects - ioBroker.png

                          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
                          


                          1 Reply Last reply Reply Quote 0
                          • S
                            SevenUp last edited by SevenUp

                            Nun habe ich es aber kaputt gespielt: 😕
                            2022-01-30 23_42_37-instances - ioBroker.png

                            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 1 Reply Last reply Reply Quote 0
                            • haus-automatisierung
                              haus-automatisierung Developer Most Active @SevenUp last edited by

                              @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? 🙂

                              S joergeli 2 Replies Last reply Reply Quote 1
                              • S
                                SevenUp @haus-automatisierung last edited by

                                @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 🙂

                                1 Reply Last reply Reply Quote 0
                                • H
                                  hetti72 last edited by

                                  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

                                  S Ralf_N 2 Replies Last reply Reply Quote 0
                                  • S
                                    SevenUp @hetti72 last edited by

                                    @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."

                                    H 1 Reply Last reply Reply Quote 0
                                    • Ralf_N
                                      Ralf_N @hetti72 last edited by Ralf_N

                                      @hetti72

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

                                      cce73410-7d37-4e4c-98d2-655c70336017-image.png

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

                                      da_Woody S 2 Replies Last reply Reply Quote 0
                                      • da_Woody
                                        da_Woody @Ralf_N last edited by

                                        @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
                                        743004dc-11c1-4f65-b858-f0d6b342ea1b-grafik.png
                                        da brauch ich kein blockly...

                                        Ralf_N 2 Replies Last reply Reply Quote 0
                                        • Ralf_N
                                          Ralf_N @da_Woody last edited by

                                          @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:

                                          0e761a15-94bf-49bc-ae64-f5e82fa2bb76-image.png

                                          da_Woody H 2 Replies Last reply Reply Quote 0
                                          • Ralf_N
                                            Ralf_N @da_Woody last edited by

                                            @da_woody
                                            Nachtrag.

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

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            822
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            adapter entwicklung adatper updates developer testen
                                            49
                                            461
                                            69231
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo