This is very nice. I built a Hypercube printer with a Duet wifi board a couple of years ago. If I ever have a reason to setup a second printer again, I will be looking for your component. Thanks!
I’m considering buying a Duet3D upgrade for my duplicator i3 printer, after my Melzi board died. Being able to use it with Home Assistant, even without octoprint, is a big plus for me. I added this topic to my favorites!
Hi, small news on the integration.
I just restarted the to code the integration (some misshaps with the last iteration).
Will keep you posted as much as possible.
The first tests I ran gave good results for the new integration with GUI configuration.
I will put the dev code on github as soon as possible. In the first time, it will be manual install, and I will investigate later how to add it to HACS
Is this still being worked on or is there an alternative for Reprap-based printers to be integrated into Home Assistant? Home Assistant has been giving me an error message and eventually ignored the integration, apparently because it doesn’t have a manifest that is required of integrations these days.
At the moment I had to stop working on the integration because of my studies and family. I hope being able to work on it this summer but no guarantee at this moment. I will put the code I have in a couple weeks but it is not working for now. Sorry for that.
This implementation is not working anymore. The rr_status is deprecated, and a password is also not required.
Forked your repo and refactored the code heaviy to comply with the current custom component framework and also with the new DSF machine/status endpoint:
This integration is configured via the UI and I also added a service to send GCodes from Home Assistant to DSF. Happy to get feedback!
All entities are getting created successfully now and values are updated, however I am not satisfied that the entities are not linked to a device and that there is no proper config flow. The position entity is also not working as intended as the X,Y,Z values are just added as a string, so the visualization is not working. Will work on those topics as well in the next days.
I do not use a standalone Duet 3, so I can’t test with it properly, but as rr_model should also return the Object Model it should be work OOB if I add a configuration option. Thanks for the hint!
Do you want to test it? I can implement that tomorrow
With the help of @smoki3 we implemented the standalone mode as well. You can now choose “Standalone” during the setup to fetch data. So the integration supports now both: SBC (/machine/status) and standalone ( /rr_model?key=<key>).
Currently, the service call is not yet implemented for the standalone mode. Will do this later
Thanks Lyr3x for doing what I wanted to do from a long time but did not manage due to a lack of time.
I took your version and added in it the authentication, I created a pull request on your github.
In the mean time, if someone want to try out my version, you can get it on my repo
Quick update, I am currently working on porting the octoprint card for this duet integration.
Seems to work at home, should wwwomeone want to give it a try, and report any issues: