Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Email/notifications from Duet wifi

    Scheduled Pinned Locked Moved
    Duet Web Control
    10
    21
    2.1k
    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.
    • Danalundefined
      Danal
      last edited by Danal

      MQTT is a defacto standard for IOT interaction. The most effective way to use it with a 3D printer that produced MQTT messages would be to configure (not code) a small MQTT broker on an always running machine at your house. PC, Mac, Pi, whatever. Probably mosquito.

      That MQTT broker would receive the messages, and invoke whatever you want to push to your phone. SMS, Email, Pushover, Airship, whatever service you wish.

      Delta / Kossel printer fanatic

      1 Reply Last reply Reply Quote 1
      • Danalundefined
        Danal
        last edited by

        Why not just write a "send email" capability into the Printer? Because that would (more or less) require the printer to contact a web IP address. Bad, bad juju to have IOT devices like printers open anything to the internet.

        Also lack of flexibility. There are dozens, if not hundreds, of notification services. The printer firmware would always be lacking some specific interface.

        MQTT from printer to broker, broker is the one handling internet stuff, and can probably interface to almost anything, either built in, or via command line. Much better juju.

        Delta / Kossel printer fanatic

        1 Reply Last reply Reply Quote 0
        • r123undefined
          r123
          last edited by

          I thought ssl smtp access was just a single port?

          An IOT gadget can’t be made “broadcast only” (thus safe) in its internet access?

          Danalundefined 1 Reply Last reply Reply Quote 0
          • Danalundefined
            Danal @r123
            last edited by

            @r123 said in Email/notifications from Duet wifi:

            I thought ssl smtp access was just a single port?

            An IOT gadget can’t be made “broadcast only” (thus safe) in its internet access?

            Safe is relative. Better that a firmware based device have absolutely zero direct connectivity. In, out, whatever.

            But really, the much bigger reason is... what list of things to support from the firmware? "Just" SMTP?? What about SMTP with authentication? (there are VERY few open mailservers around anymore). With TLS? or some other encryption? or MAPI (a much more secure mail protocol)? Or...

            MQTT for IOT devices. MQTT broker to do anything you want.

            Delta / Kossel printer fanatic

            1 Reply Last reply Reply Quote 0
            • Nightreaverundefined
              Nightreaver
              last edited by

              @dc42 Is there any update on the MQTT progress?
              Will it be available with RRF 2 or only with the new RRF3 ?

              Will it publish all information from the WebIF? Like temps, speed, job status etc?

              dc42undefined 1 Reply Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators @Nightreaver
                last edited by

                @Nightreaver said in Email/notifications from Duet wifi:

                @dc42 Is there any update on the MQTT progress?

                Not yet.

                Will it be available with RRF 2 or only with the new RRF3 ?

                I will not be adding any new features to RRF2.

                Will it publish all information from the WebIF? Like temps, speed, job status etc?

                No, just "major event" messages. Other devices can use HTTP requests rr_status and rr_model to get the data they want.

                Duet WiFi hardware designer and firmware engineer
                Please do not ask me for Duet support via PM or email, use the forum
                http://www.escher3d.com, https://miscsolutions.wordpress.com

                1 Reply Last reply Reply Quote 0
                • Lanovarundefined
                  Lanovar
                  last edited by

                  @dc42 said in Email/notifications from Duet wifi:

                  @Nightreaver said in Email/notifications from Duet wifi:

                  @dc42 Is there any update on the MQTT progress?

                  Not yet.

                  @dc42 Any news on that? 🙂

                  1 Reply Last reply Reply Quote 1
                  • Nightreaverundefined
                    Nightreaver
                    last edited by

                    For those who are interested...

                    I took a similar solution for MQTT and adapted it to duet3d api endpoint.
                    It works fine so far as im using it for myself, tho not all options for MQTT publishing are implemented yet.
                    Feel free to try it and report bugs.

                    https://github.com/Nightreaver/RRF_WebIF_MQTT

                    1 Reply Last reply Reply Quote 1
                    • alankilianundefined
                      alankilian
                      last edited by alankilian

                      I'll definitely try this mid-December after my current printing set is complete.

                      One thing: In my MQTT experience, it's a good idea to have a topic like "State" where you set the last-will to publish with retain a payload of "Offline" and then in the connect routine, publish a payload of Online" with retain.

                      That way, you can check the state easily without looking at any other topics.

                      I see you have a last-will set, but I'm not familiar with those three systems, so I don't know if that's the by-the-book way to use last will. If so, ignore me.

                      Also, it's also good to have a unique device ID in the topic so many devices can all publish to a broker and you can weed them out by which topics you subscribe to.

                      SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

                      1 Reply Last reply Reply Quote 0
                      • Nightreaverundefined
                        Nightreaver
                        last edited by

                        I see, thats what LWT means! I will check up on that topic, thanks

                        alankilianundefined 1 Reply Last reply Reply Quote 0
                        • alankilianundefined
                          alankilian @Nightreaver
                          last edited by

                          @Nightreaver Cool.

                          You can contact me anytime for MQTT-related discussions.

                          I spent 4 years doing commercial MQTT implementations on tiny microcontrollers and have tens of thousands devices in the field talking all day long.

                          SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

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