Home Assistant Integration

Lyr3x

@izeman this is only working if you are not using SBC mode if I am not mistaken.

I worked on updating the integration to work asynchronous without blocking requests, which is working fine now (still need to merge).
There is quite some rework necessary to get config and options flow running, but I finally understood how the flows should be implemented. Can’t give a timeline yet though.

Configuration via configuration.yaml is working fine including time elapsed and remaining. I also added the progress sensor back and calculating the progress via total layers and printed layers.

nikscha

@Lyr3x I'm gettting an error when setting up the integration, could you help me out?

I have two printers, one running Duet Wifi 2 without SBC (RRF 3.4.5), and one running a Duet 3 Mini5+ WITH SBC (RRF 3.5.0beta3).
However both gave the same error as above. Navigating to 'printerip'/maschine/status also returns the json, so I doubt the issue is related to the printers? What else can I try? It might be noteworty that I run HASS on Docker?

nikscha

@nikscha
Here's the HASS log:

Logger: aiohttp.server
Source: data_entry_flow.py:387
First occurred: 15:43:51 (17 occurrences)
Last logged: 16:20:39

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 81, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 136, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 180, in post
    return await super().post(request, flow_id)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 73, in wrapper
    result = await method(view, request, data, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post
    result = await self._flow_mgr.async_configure(flow_id, data)
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 286, in async_configure
    result = await self._async_handle_step(
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 387, in _async_handle_step
    if not isinstance(result["type"], FlowResultType):
TypeError: 'NoneType' object is not subscriptable

Lyr3x

@nikscha as Said before the config flow is not working. You need to configure it via the configuration.yaml at the moment

nikscha

@Lyr3x Ohh I see. Fair enough. I'm still having problems though:
I added the follwoing to my config:

# Duet Integration
duet3d_printer:
  host: !secret duet3d-host
  name: !secret duet3d-name
  number_of_tools: 1
  bed: true
  sensors:
    monitored_conditions:
      - 'Current State'
      - 'Temperatures'
      - 'Job Percentage'
      - 'Time Elapsed'
      - 'Time Remaining'
      - 'Position'

I also added the entries for host and name to the secrets.yaml.

However HASS wont restart:

Lyr3x

@nikscha oh the readme is still wrong. It is not Job percentage but Progress

nikscha

@Lyr3x that did the trick, thanks!
The integration is working well, can I do anything to test it for you?

Lyr3x

@nikscha thanks will let you know! Of course if something is not working as intended don’t keep it to yourself.

Lyr3x

Configflow is still giving me a headache. I need to refactor the code more to get this working properly.
But I added a home assistant service to send gcodes:

service: duet3d_printer.hevors_send_gcode
data:
  gcode: G28

Feedback appreciated!

nikscha

@Lyr3x Hmm now it doesn't work anymore^^
I updated the integration though HACS, and after a restart the integration was gone from the integration panel. Didn't make any other changes. How can I debug this? Logs are empty too

Lyr3x

Edit: Alright, I just released a new version of the integration. ConfigFlow is now working as well as the service. The binary sensor is still dead. You need to remove the configuration from your configuration.yaml and just setup the integration via UI. I unfortunately need to ask you to reconfigure the Integration later again, because I want to attach the entities to a device. But its in a working mode now! Please do not hesitate with feedback.

@nikscha Yep realized that as well, sorry. I decided to stop trying to patch the stuff I want to remove anyway and fix the config flow setup and remove the configuration.yaml code completely. I already have a working unpolished state. Bear with me a little more. Ill update you all here later!

nikscha

@Lyr3x No worries! It's working now, config flow as well. I suggest naming the fields in the config flow. I tried doing this myself and creating a pull request but honestly I am just not that good at Python ^^
I also tried making a textfield card to send typed Gcodes, but I also gave up and instead asked for help here

I also tested some gcodes, most of them seem to work just fine but I noticed a strange delay when sending a M291 P"X" R"X" S3. This doesn't happen with S2, S1 or S0. Maybe this is intentional behaviour? Sending the same command from within DWC returns instantly though.

Lyr3x

@nikscha what do you mean with naming the fields? They all have labels

I’ll test the gcode tomorrow and see if I can find out what causes the delay!

nikscha

@Lyr3x The fields are prefilled, but it doesn't say what should be in there. This is what it looks like with the prefilled values removed:
What does the checkbox do for example?
Looking at the code I can figure out its the field "has_bed", and I think that should be mentioned in the config flow as well

Lyr3x

@nikscha Interesting. That is not what I see here

Did you remove the integration completely once?
Yeah, the checkbox is the check if you have a hotbed or not

nikscha

@Lyr3x Hmmmm
Not that I know of. Do you want me to test it?

Lyr3x

@nikscha Yep do that, maybe there is something cached from previous iterations. I tried that for you on a fresh local installation. Labels are working as intended
There is also no delay here with M291 P"X" R"X" S3 or any other GCode. It's exactly the same as with DWC

nikscha

@Lyr3x That did the trick, the fields are now named.
The delay is still there tho.
Are you using a SBC?
Nvm I think I just communicated badly.
By "delay" I don't mean the time until the window pops up on DWC, but they time it takes HASS to aknowledge the service call. When calling

service: duet3d_printer.send_code
data:
 gcode: M291 P"X" R"X" S3

from the service tab in dev tools, it takes about 5-10 seconds for the 'call service' button to turn green. This isn't the case with other gcodes.

Lyr3x

@nikscha said in Home Assistant Integration:

service: duet3d_printer.send_codedata: gcode: M291 P"X" R"X" S3

Ah gotcha. That is specific to the API call. It seems to be synchronous or it times out. If you press the OK button, the request is done. The integration does not validate the GCodes but just send them to the DSF API. If you make a similar call via curl you see the exact same behavior.

nikscha

@Lyr3x Yeah that makes sense