Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Home Assistant Integration

    Third-party software
    10
    15
    592
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • deckingman
      deckingman @nikscha last edited by

      @nikscha This is somthing that I've thought about from time to time, but I can't see a usage case for home assistant integration. For sure, it might be possible to incorporate some commands into a home assistant dashboard but what's the point in simply substituting one dashboard for another? For me, home assistant is about automating tasks whereby there is a trigger which will initiate actions if certain optional conditions are met. So the action might be to start, stop or pause a print, but what would the trigger(s) and optional conditions be which wouldn't otherwise be taken care of by firmware? One could possibly expose certain printer sensors to HA and make use of the long term statistics features but again, I can't really think of a use case for those statistics.

      Ian
      https://somei3deas.wordpress.com/
      https://www.youtube.com/@deckingman

      jens55 1 Reply Last reply Reply Quote 0
      • jens55
        jens55 @deckingman last edited by

        @deckingman, good point about exposing printer sensors. The following could make sense: the printer pauses because of a temperature issue or a filament issue and home assistant could be tasked to email this fact to the user. If I am home and run the printer then I check on the DWC and on a video feed fairly regularly so for me that wouldn't be much of an advantage. If I am not home and an error occurs I can't do anything about it anyway.

        1 Reply Last reply Reply Quote 0
        • MintyTrebor
          MintyTrebor @nikscha last edited by MintyTrebor

          @nikscha
          NodeDSF works with node-red (which also integrates with Home Assistant) and works with both stand alone and sbc/dsf configurations. It exposes Object model, monitors status, send commands, plus a few other things.

          if you look here you can see an example using the node-red dashboard - an equivalent would be achievable in the home assistant dashboarding system.

          Here is my current HA Printer dashboard..
          a3f0de34-a7c1-4091-84b6-bd5a52f9ee97-image.png

          This one is currently using MQTT with Klipper, (I tend to switch between RRF & Klipper for development reasons), but I have used it with NodeDSF previously.

          I also seem to remember someone mentioning MQTT functionality on the roadmap for RRF, but that needs confirmation from the team.

          As to why - my chamber heater is controlled through a smart power socket and I needed a way to incorporate a temp sensor on the Duet Board to trigger the chamber heater on/off - I can do this in HA with NodeDSF. I also use it to control the lighting/led strips using zigbee...

          NodeDSF - Native Node-Red integration with Duet boards.
          BtnCmd - Customise DWC with user defined buttons/layouts/panels (DWC Plugin)
          ReleaseMgr - Duet update info inside DWC.
          Repo

          nikscha 1 Reply Last reply Reply Quote 1
          • nikscha
            nikscha @MintyTrebor last edited by

            @MintyTrebor Thanks, I'll check it out!

            I just found out that there is also a Home Assistant Integration for Prusa:
            https://www.home-assistant.io/integrations/prusalink/

            ca99f286-ee3c-4822-8b29-27c26b793383-image.png

            .

            The octoprint integration looks great too:

            d94bd3fc-b536-4d65-a67f-90e6fd026daa-image.png
            f5e02e1c-4e81-44f7-a7cd-458b1aee2c29-image.png
            dd4ee61f-56fe-4ed4-ac28-a3c52a401070-image.png

            1 Reply Last reply Reply Quote 0
            • oliof
              oliof last edited by oliof

              spelunking the commits for the upcoming v3.5 release it looks like RRF will grow native MQTT support soon. EDIT: Probably not on all boards, I haven't had time to read this PR completely.

              <>Creality CR-20 IDEX Duet3 mini 5+<>RatRig V-Minion SKR RRF 1.1<>

              Baenwort nikscha 2 Replies Last reply Reply Quote 3
              • Baenwort
                Baenwort @oliof last edited by

                I'm hoping to use Home Assistant to turn on a HEPA filter that is powered off a HA plug strip. This way depending on the filament configuration it either turns on automatically at the start of a print and off once a certain time after completion or turns on after print completion and runs for a timer.

                HA can control the fan and timer and just needs duet to tell it the print reached a milestone (set on the duet side when start or end of print macro is triggered per filament.

                I've also got MotionEye cameras that feed into HA and if I could start or stop a print from HA I would have those buttons on the page with the camera views.

                Last reason I'd like HA integration is I have touchscreena around the house that control things in HA and if duet had integration I could just walk up to one of those and change tabs with the existing build instead of having to larch something else or modify the build.

                1 Reply Last reply Reply Quote 0
                • nikscha
                  nikscha @oliof last edited by

                  @oliof Uhh that would be a nice start!
                  I'm hoping that prusas release of their "PrusaLink" integration for Home Assistant will cause RRF to get one too

                  1 Reply Last reply Reply Quote 0
                  • pkos
                    pkos last edited by pkos

                    While waiting, you can easily use this:
                    https://github.com/iz3man/duet3d/blob/main/duet3d.yaml

                    Just add the lines to your configuration.yaml, modify for your printer and restart HA.

                    Voron 2.4 (Duet 3 6HC + 3HC standalone), Voron SW (Duet 3 mini 5+ standalone), Voron Trident (Duet 3 mini 5+ standalone), Voron 0.1

                    Proschi78 1 Reply Last reply Reply Quote 2
                    • Proschi78
                      Proschi78 @pkos last edited by

                      @pkos Nice 👍

                      Love my Duet 3 Mini.
                      https://www.instagram.com/proschi3d https://youtube.com/@proschi3d

                      1 Reply Last reply Reply Quote 0
                      • nikscha
                        nikscha last edited by nikscha

                        @pkos Thanks! But I don't think this is compatible with RRF 3 anymore 😕
                        @izeman (hoping this is the right user ^^)

                        pkos 1 Reply Last reply Reply Quote 0
                        • pkos
                          pkos @nikscha last edited by

                          @nikscha It works 🙂 I've been using it for ages now, although I don't have a very elaborate layout. I mostly have HA watch hotend temp and once it's been at 45C for 2 minutes after a print - it switches the printer off.

                          My code is as follows:

                            - platform: rest
                              name: Voron_24 Status
                              resource: http://<ip_here>/rr_status?type=3
                              value_template: "{{ value_json.status }}"
                              json_attributes:
                                - temps
                                - fractionPrinted
                              force_update: true
                          
                            - platform: template
                              sensors:
                                voron_24_head_temp_current:
                                  value_template: "{{ states.sensor.voron_24_status.attributes.temps.current[1] }}"
                                  friendly_name: Hotend Temp
                                voron_24_bed_temp_current:
                                  value_template: "{{ states.sensor.voron_24_status.attributes.temps.current[0] }}"
                                  friendly_name: Hotbed Temp
                                voron_24_print_percentage:
                                  value_template: "{{ states.sensor.voron_24_status.attributes.fractionPrinted }}%"
                                  friendly_name: Print progress 
                          

                          And this is how I put display it in Lovelace.

                          964cc527-896b-446d-bb7d-ba148869390b-image.png

                          The important bits here (if you know this, forgive me, if not - maybe it will help) - is to keep the naming consistent. HA will convert the name from the first sensor into an entity_id.
                          So in my case, here it reads Voron_24 Status. HA will take it, convert it internally to voron_24_status and this is what you use below in the actual sensors.

                          And since I am waaaaaay too lazy ( 😉 ) I am going to wait for MQTT to come along before solving issues like not zeroing out of entries when the printer is off 🙂

                          See if that will work and if you get stuck, ping me and I'll be happy to help.

                          Voron 2.4 (Duet 3 6HC + 3HC standalone), Voron SW (Duet 3 mini 5+ standalone), Voron Trident (Duet 3 mini 5+ standalone), Voron 0.1

                          1 Reply Last reply Reply Quote 0
                          • repier37
                            repier37 last edited by

                            @nikscha I could not make it work either using RRF3.
                            I ended up modifying another integration to make it work with RRF 3.
                            You can find it on my repo :
                            https://github.com/repier37/hass-Duet3D
                            Basically I just added authentication to the integration I forked to be able to retrieve data.
                            It is still using the rr_status command that is planned to be removed in RRF3.5 if I recall correctly, but it should work with earlier version. It should not be too hard to move to rr_model as it should only be changing json parsing.

                            paulg4h 1 Reply Last reply Reply Quote 1
                            • paulg4h
                              paulg4h @repier37 last edited by

                              @repier37

                              Many thank's for your work!

                              Hopefully we can expect a update do see the RRF 3.5 working too.

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post
                              Unless otherwise noted, all forum content is licensed under CC-BY-SA