[70_OctoPrint.pm] zum Steuern von OctoPrint 3D Drucker

Begonnen von michael.winkler, 31 Dezember 2017, 16:56:28

Vorheriges Thema - Nächstes Thema

Micky79

#105
Hallo zusammen.
Ich habe auch gerade eben das Modul installiert. Leider wird bei mir auch kein Status angezeigt sondern nur "??".
Bei online steht true.

Die set Kommandos gehen aber. Also Printer auf Home fahren etc.

Hier mal ein Verbos 5:

2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_GetStatus] called function
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_SendCommand] called function CMD = 
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_SendCommand] using unencrypted connection via HTTP
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_SendCommand] - append to queue http://192.168.178.219:5000/api/job?&apikey=Xxxxxxxxxxxxxxx
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_HandleCmdQueue] - send command url  = http://192.168.178.219:5000/api/job?&apikey=xxxxxxxxxxxxxx
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_HandleCmdQueue] - send command data =
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_HandleCmdQueue] - send command head = Content-Type: application/json
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_SendCommand] called function CMD = 
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_SendCommand] using unencrypted connection via HTTP
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_SendCommand] - append to queue http://192.168.178.219:5000/api/printer?exclude=state,sd&apikey=xxxxxxxxxxxxxxxxxxxxxxx
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] called function
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] [readings_job] Data = {
  "job": {
    "averagePrintTime": null,
    "estimatedPrintTime": null,
    "filament": null,
    "file": {
      "date": null,
      "display": null,
      "name": null,
      "origin": null,
      "path": null,
      "size": null
    },
    "lastPrintTime": null,
    "user": null
  },
  "progress": {
    "completion": null,
    "filepos": null,
    "printTime": null,
    "printTimeLeft": null,
    "printTimeLeftOrigin": null
  },
  "state": "Operational"
}
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] [readings_job] JSON =
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] [readings_job] JSON = NODATA
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_HandleCmdQueue] - send command url  = http://192.168.178.219:5000/api/printer?exclude=state,sd&apikey=xxxxxxxxxxxxxxxxxxx
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_HandleCmdQueue] - send command data =
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_HandleCmdQueue] - send command head = Content-Type: application/json
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] called function
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] [readings_printer] Data = {
  "temperature": {
    "bed": {
      "actual": 17.6,
      "offset": 0,
      "target": 0.0
    },
    "tool0": {
      "actual": 17.1,
      "offset": 0,
      "target": 0.0
    }
  }
}
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] [readings_printer] JSON =
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] [readings_printer] JSON = NODATA



Komisch ist, dass er die Daten findet, Aber kein Reading anlegt.

Woran kann das denn liegen?


Viele Grüße Micky

michael.winkler

Zitat von: Micky79 am 25 November 2018, 00:25:09
Hallo zusammen.
Ich habe auch gerade eben das Modul installiert. Leider wird bei mir auch kein Status angezeigt sondern nur "??".
Bei online steht true.

Die set Kommandos gehen aber. Also Printer auf Home fahren etc.

Hier mal ein Verbos 5:

2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_GetStatus] called function
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_SendCommand] called function CMD = 
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_SendCommand] using unencrypted connection via HTTP
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_SendCommand] - append to queue http://192.168.178.219:5000/api/job?&apikey=Xxxxxxxxxxxxxxx
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_HandleCmdQueue] - send command url  = http://192.168.178.219:5000/api/job?&apikey=xxxxxxxxxxxxxx
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_HandleCmdQueue] - send command data =
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_HandleCmdQueue] - send command head = Content-Type: application/json
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_SendCommand] called function CMD = 
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_SendCommand] using unencrypted connection via HTTP
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_SendCommand] - append to queue http://192.168.178.219:5000/api/printer?exclude=state,sd&apikey=xxxxxxxxxxxxxxxxxxxxxxx
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] called function
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] [readings_job] Data = {
  "job": {
    "averagePrintTime": null,
    "estimatedPrintTime": null,
    "filament": null,
    "file": {
      "date": null,
      "display": null,
      "name": null,
      "origin": null,
      "path": null,
      "size": null
    },
    "lastPrintTime": null,
    "user": null
  },
  "progress": {
    "completion": null,
    "filepos": null,
    "printTime": null,
    "printTimeLeft": null,
    "printTimeLeftOrigin": null
  },
  "state": "Operational"
}
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] [readings_job] JSON =
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] [readings_job] JSON = NODATA
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_HandleCmdQueue] - send command url  = http://192.168.178.219:5000/api/printer?exclude=state,sd&apikey=xxxxxxxxxxxxxxxxxxx
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_HandleCmdQueue] - send command data =
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_HD_HandleCmdQueue] - send command head = Content-Type: application/json
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] called function
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] [readings_printer] Data = {
  "temperature": {
    "bed": {
      "actual": 17.6,
      "offset": 0,
      "target": 0.0
    },
    "tool0": {
      "actual": 17.1,
      "offset": 0,
      "target": 0.0
    }
  }
}
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] [readings_printer] JSON =
2018.11.25 00:16:07 5: OctoPrint 3D_Drucker [OctoPrint_ReceiveCommand] [readings_printer] JSON = NODATA



Komisch ist, dass er die Daten findet, Aber kein Reading anlegt.

Woran kann das denn liegen?


Viele Grüße Micky
Kannst du mal ein List von deinem Device schicken?

Micky79

Klar, hier bitte:

nternals:
   CHANGED   
   DEF        192.168.178.219 5000
   INTERVAL   45
   NAME       3D_Drucker
   NR         167
   STATE      ???
   TYPE       OctoPrint
   READINGS:
     2018-11-26 20:37:22   online          true
     2018-11-26 20:37:22   progress_completion_percent 0
   helper:
     ADDRESS    192.168.178.219
     PORT       5000
     RUNNING_REQUEST 0
     CMD_QUEUE:
Attributes:
   apikey    xxxxx
   event-on-change-reading .*
   icon       it_printer
   room       Werkzeugkeller
   userReadings progress_completion_percent { sprintf("%d", ReadingsNum($NAME, "progress_completion", 0)) }


michael.winkler

Zitat von: Micky79 am 26 November 2018, 20:39:59
Klar, hier bitte:

nternals:
   CHANGED   
   DEF        192.168.178.219 5000
   INTERVAL   45
   NAME       3D_Drucker
   NR         167
   STATE      ???
   TYPE       OctoPrint
   READINGS:
     2018-11-26 20:37:22   online          true
     2018-11-26 20:37:22   progress_completion_percent 0
   helper:
     ADDRESS    192.168.178.219
     PORT       5000
     RUNNING_REQUEST 0
     CMD_QUEUE:
Attributes:
   apikey    xxxxx
   event-on-change-reading .*
   icon       it_printer
   room       Werkzeugkeller
   userReadings progress_completion_percent { sprintf("%d", ReadingsNum($NAME, "progress_completion", 0)) }
Auf Seite 1 habe ich die aktuelle Version hochgeladen. Ich schätze mal dass du noch die 0.0.10er Version verwendest. Falls es damit immer noch nicht funktioniert solltest du noch mal ein Verbose 5 Log erstellen und mir zuschicken.

DoubleD

@michael.winkler

könnte man die aktuelle Z-Position mit in die Readings mit aufnehmen?

Ich finde das Modul super habe aber nur wegen der Z-Position zusätzlich ein MQTT laufen. Das würde ich gerne los werden. ;-)

Vielen Dank für die tolle Arbeit

Gruß
Daniel

michael.winkler

Zitat von: DoubleD am 26 November 2018, 21:29:40
@michael.winkler

könnte man die aktuelle Z-Position mit in die Readings mit aufnehmen?

Ich finde das Modul super habe aber nur wegen der Z-Position zusätzlich ein MQTT laufen. Das würde ich gerne los werden. ;-)

Vielen Dank für die tolle Arbeit

Gruß
Daniel
Wie kommst du an diesen Wert?

DoubleD

@michael.winkler
Über das mqtt plugin.
Die ZPosition gibt es dort als reading.
Ich hatte gehofft das es den Wert auch in der API gibt und Du ihn im Modul nur nicht auswertest.

Gruß Daniel

DasQ

#112
Hab das Plugin auch installiert und läuft 1A, Danke dafür!  ;) :)

etwasw OT: gibts da irgend eine möglichkeit das mit dem MQTT2 server zu kombinieren?
mir erstellt es jedesmal ein neues MQTT2_device

anbei meine readings da raus

defmod MQTT2_3XSei5RXFLMaGu29ehJjQb MQTT2_DEVICE 3XSei5RXFLMaGu29ehJjQb
attr MQTT2_3XSei5RXFLMaGu29ehJjQb IODev MQTT2_Broker
attr MQTT2_3XSei5RXFLMaGu29ehJjQb readingList 3XSei5RXFLMaGu29ehJjQb:octopi/temperature/bed:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/temperature/bed:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/ZChange:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/CaptureStart:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/CaptureDone:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/temperature/tool0:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/progress/printing:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/PrintCancelling:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/PrinterStateChanged:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/MetadataAnalysisStarted:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/PrintCancelled:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/MetadataStatisticsUpdated:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/PrintFailed:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/MovieRendering:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/MovieDone:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/MetadataAnalysisFinished:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/FileAdded:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/UpdatedFiles:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/UpdatedFiles:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/FileSelected:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/PrintStarted:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/Upload:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/PositionUpdate:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/Home:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/PrinterReset:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/Disconnecting:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/Disconnected:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/Connecting:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/Connected:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/FirmwareData:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/ClientClosed:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/ClientOpened:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/PrintDone:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/SettingsUpdated:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/event/Error:.* { json2nameValue($EVENT) }\
3XSei5RXFLMaGu29ehJjQb:octopi/mqtt:.* mqtt
attr MQTT2_3XSei5RXFLMaGu29ehJjQb room MQTT2_DEVICE
attr MQTT2_3XSei5RXFLMaGu29ehJjQb stateFormat state_id

setstate MQTT2_3XSei5RXFLMaGu29ehJjQb OPERATIONAL
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:24 _event MovieDone
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:46:40 _timestamp 1542653200
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:46:40 actual 29.62
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 15:27:44 baudrate 0
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 15:21:32 config_hash dc6b3f08b9e84b098176330fd8c76f74
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 15:27:55 data_EXTRUDER_COUNT 1
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 15:27:55 data_FIRMWARE_NAME Marlin 1.1.8 (Github)
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 15:27:55 data_MACHINE_TYPE 3D Drucker
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 15:27:55 data_PROTOCOL_VERSION 1.0
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 15:27:55 data_SOURCE_CODE_URL https://github.com/MarlinFirmware/Marlin
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 15:27:55 data_UUID cede2a2f-41a2-4748-9b12-c55c62f367ff
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 18:54:30 e 0.0
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 15:21:32 effective_hash 59effdfda2585fa8eb4dce6810abf53e
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 15:26:44 error Printer requested line 1 but no sufficient history is available, can't resend
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 18:54:30 f 6000.0
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:22 file /home/pi/.octoprint/uploads/CFFFP_cul_case_deckel.gcode
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:22 filename CFFFP_cul_case_deckel.gcode
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:24 gcode CFFFP_cul_case_deckel.gcode
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 13:04:45 idle false
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:22 location local
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:24 movie /home/pi/.octoprint/timelapse/CFFFP_cul_case_deckel_20181119184948.mpg
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:24 movie_basename CFFFP_cul_case_deckel_20181119184948.mpg
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:24 movie_prefix CFFFP_cul_case_deckel_20181119184948
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:48:17 mqtt disconnected
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:22 name CFFFP_cul_case_deckel.gcode
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:18 new 10.0
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:18 old 6.0
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:22 origin local
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:22 path CFFFP_cul_case_deckel.gcode
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 15:27:44 port AUTO
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:22 progress 100
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 15:26:44 reason error
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 18:45:00 remoteAddress 192.168.1.57
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:59:04 result_dimensions_depth 100.70500000000001
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:59:04 result_dimensions_height 5.8
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:59:04 result_dimensions_width 48.474999999999994
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:59:04 result_estimatedPrintTime 3209.2534963811695
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:59:04 result_filament_tool0_length 3640.41381
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:59:04 result_filament_tool0_volume 0.0
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:59:04 result_printingArea_maxX 134.237
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:59:04 result_printingArea_maxY 155.347
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:59:04 result_printingArea_maxZ 6.0
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:59:04 result_printingArea_minX 85.762
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:59:04 result_printingArea_minY 54.642
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:59:04 result_printingArea_minZ 0.2
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:22 size 265382
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:22 state_id OPERATIONAL
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:22 state_string Operational
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:22 storage local
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 18:54:30 t 0
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:46:40 target 0.0
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 19:35:22 time 2733.7367238998413
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:58:59 type gcode
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:08:32 type_1 machinecode
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 17:08:32 type_2 gcode
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 18:54:30 x 220.0
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 18:54:30 y 210.0
setstate MQTT2_3XSei5RXFLMaGu29ehJjQb 2018-11-19 18:54:30 z 12.77

Fhem on MacMini/Ubuntu.
Absoluter Befürworter der Konsequenten-Kleinschreibung https://de.wikipedia.org/wiki/Kleinschreibung
Infos zu Klimawandel http://www.globalcarbonatlas.org

Micky79

Danke. Die aktuelle Version funktioniert jetzt einwandfrei.

:)

Viele Grüße Micky

michael.winkler

Zitat von: DoubleD am 28 November 2018, 12:04:28
@michael.winkler
Über das mqtt plugin.
Die ZPosition gibt es dort als reading.
Ich hatte gehofft das es den Wert auch in der API gibt und Du ihn im Modul nur nicht auswertest.

Gruß Daniel
Nein, über die API steht dieser Wert leider nicht zur Verfügung.

JamesB

Servus Michael,

hab mit meiner Installation noch mal getestet. Es scheint einiges zu funktionieren. Aber STATE bleibt immer noch auf ???

Internals:
   DEF        10.0.0.164
   INTERVAL   45
   NAME       AnyCubicI3
   NR         211
   STATE      ???
   TYPE       OctoPrint
   READINGS:
     2018-12-02 15:37:02   online          true
   helper:
     ADDRESS    10.0.0.164
     PORT       80
     RUNNING_REQUEST 0
     CMD_QUEUE:
Attributes:
   apikey     27F...
   icon       it_printer
   room       1.3 Haus
   verbose    5


2018.12.02 15:38:32 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_printer] JSON =
2018.12.02 15:38:32 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_printer] JSON = NODATA
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_GetStatus] called function
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_SendCommand] called function CMD = 
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_SendCommand] using unencrypted connection via HTTP
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_SendCommand] - append to queue http://10.0.0.164:80/api/job?&apikey=27F...
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_HandleCmdQueue] - send command url  = http://10.0.0.164:80/api/job?&apikey=27F...
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_HandleCmdQueue] - send command data =
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_HandleCmdQueue] - send command head = Content-Type: application/json
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_SendCommand] called function CMD = 
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_SendCommand] using unencrypted connection via HTTP
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_SendCommand] - append to queue http://10.0.0.164:80/api/printer?exclude=state,sd&apikey=27F...
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] called function
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_job] Data = {
  "job": {
    "averagePrintTime": 12069.247750401497,
    "estimatedPrintTime": 8416.80638152569,
    "filament": {
      "tool0": {
        "length": 4139.749620000004,
        "volume": 0.0
      }
    },
    "file": {
      "date": 1543688909,
      "display": "AI3M_FZ_Konsole_A_07_00-Halterung-Lager-2x.gcode",
      "name": "AI3M_FZ_Konsole_A_07_00-Halterung-Lager-2x.gcode",
      "origin": "local",
      "path": "AI3M_FZ_Konsole_A_07_00-Halterung-Lager-2x.gcode",
      "size": 4074073
    },
    "lastPrintTime": 12015.591122865677,
    "user": "dummy"
  },
  "progress": {
    "completion": 66.81986307069117,
    "filepos": 2722290,
    "printTime": 8611,
    "printTimeLeft": 4058,
    "printTimeLeftOrigin": "estimate"
  },
  "state": "Printing"
}
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_job] JSON =
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_job] JSON = NODATA
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_HandleCmdQueue] - send command url  = http://10.0.0.164:80/api/printer?exclude=state,sd&apikey=27FA...
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_HandleCmdQueue] - send command data =
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_HandleCmdQueue] - send command head = Content-Type: application/json
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] called function
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_printer] Data = {
  "temperature": {
    "bed": {
      "actual": 90.1,
      "offset": 0,
      "target": 90.0
    },
    "tool0": {
      "actual": 220.1,
      "offset": 0,
      "target": 220.0
    }
  }
}
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_printer] JSON =
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_printer] JSON = NODATA
ESXi - Debian / 2 x Raspberry PI 3 / CUNX / KS 300 / HM

michael.winkler

Zitat von: JamesB am 02 Dezember 2018, 15:45:17
Servus Michael,

hab mit meiner Installation noch mal getestet. Es scheint einiges zu funktionieren. Aber STATE bleibt immer noch auf ???

Internals:
   DEF        10.0.0.164
   INTERVAL   45
   NAME       AnyCubicI3
   NR         211
   STATE      ???
   TYPE       OctoPrint
   READINGS:
     2018-12-02 15:37:02   online          true
   helper:
     ADDRESS    10.0.0.164
     PORT       80
     RUNNING_REQUEST 0
     CMD_QUEUE:
Attributes:
   apikey     27F...
   icon       it_printer
   room       1.3 Haus
   verbose    5


2018.12.02 15:38:32 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_printer] JSON =
2018.12.02 15:38:32 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_printer] JSON = NODATA
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_GetStatus] called function
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_SendCommand] called function CMD = 
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_SendCommand] using unencrypted connection via HTTP
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_SendCommand] - append to queue http://10.0.0.164:80/api/job?&apikey=27F...
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_HandleCmdQueue] - send command url  = http://10.0.0.164:80/api/job?&apikey=27F...
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_HandleCmdQueue] - send command data =
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_HandleCmdQueue] - send command head = Content-Type: application/json
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_SendCommand] called function CMD = 
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_SendCommand] using unencrypted connection via HTTP
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_SendCommand] - append to queue http://10.0.0.164:80/api/printer?exclude=state,sd&apikey=27F...
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] called function
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_job] Data = {
  "job": {
    "averagePrintTime": 12069.247750401497,
    "estimatedPrintTime": 8416.80638152569,
    "filament": {
      "tool0": {
        "length": 4139.749620000004,
        "volume": 0.0
      }
    },
    "file": {
      "date": 1543688909,
      "display": "AI3M_FZ_Konsole_A_07_00-Halterung-Lager-2x.gcode",
      "name": "AI3M_FZ_Konsole_A_07_00-Halterung-Lager-2x.gcode",
      "origin": "local",
      "path": "AI3M_FZ_Konsole_A_07_00-Halterung-Lager-2x.gcode",
      "size": 4074073
    },
    "lastPrintTime": 12015.591122865677,
    "user": "dummy"
  },
  "progress": {
    "completion": 66.81986307069117,
    "filepos": 2722290,
    "printTime": 8611,
    "printTimeLeft": 4058,
    "printTimeLeftOrigin": "estimate"
  },
  "state": "Printing"
}
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_job] JSON =
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_job] JSON = NODATA
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_HandleCmdQueue] - send command url  = http://10.0.0.164:80/api/printer?exclude=state,sd&apikey=27FA...
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_HandleCmdQueue] - send command data =
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_HD_HandleCmdQueue] - send command head = Content-Type: application/json
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] called function
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_printer] Data = {
  "temperature": {
    "bed": {
      "actual": 90.1,
      "offset": 0,
      "target": 90.0
    },
    "tool0": {
      "actual": 220.1,
      "offset": 0,
      "target": 220.0
    }
  }
}
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_printer] JSON =
2018.12.02 15:38:51 5: OctoPrint AnyCubicI3 [OctoPrint_ReceiveCommand] [readings_printer] JSON = NODATA

Welche Version hast du im Einsatz?

jeti

Hallo zusammen
bei mir läuft nun die v0.0.11 aber ich bekomme gar keine Verbindung...
Device sieht so aus:

Internals:
   DEF        192.168.1.189 5000
   INTERVAL   45
   NAME       JGaurora
   NR         69
   STATE      ???
   TYPE       OctoPrint
   READINGS:
     2018-12-03 21:20:09   online          false
   helper:
     ADDRESS    192.168.1.189
     PORT       5000
     RUNNING_REQUEST 0
     CMD_QUEUE:
Attributes:
   DbLogExclude .*
   apikey     D1CBF2F26A9C418BB070F1EFD262D5A2
   icon       it_printer
   room       Technik


IP stimmt  ;D und API Key auch, ich hatte vor kurzem ein ältere Version am laufen, habe dann mit MQTT experimentiert und das frühere device gelöscht...
Wohin muss ich noch gucken?

Danke und Gruß

JamesB

ESXi - Debian / 2 x Raspberry PI 3 / CUNX / KS 300 / HM

michael.winkler

Zitat von: jeti am 03 Dezember 2018, 21:26:28
Hallo zusammen
bei mir läuft nun die v0.0.11 aber ich bekomme gar keine Verbindung...
Device sieht so aus:

Internals:
   DEF        192.168.1.189 5000
   INTERVAL   45
   NAME       JGaurora
   NR         69
   STATE      ???
   TYPE       OctoPrint
   READINGS:
     2018-12-03 21:20:09   online          false
   helper:
     ADDRESS    192.168.1.189
     PORT       5000
     RUNNING_REQUEST 0
     CMD_QUEUE:
Attributes:
   DbLogExclude .*
   apikey     D1CBF2F26A9C418BB070F1EFD262D5A2
   icon       it_printer
   room       Technik


IP stimmt  ;D und API Key auch, ich hatte vor kurzem ein ältere Version am laufen, habe dann mit MQTT experimentiert und das frühere device gelöscht...
Wohin muss ich noch gucken?

Danke und Gruß
Bist du dir sicher dass der Port 5000 stimmt? Ansonsten mal ein Verbose 5 LOG erstellen