Not sure if this is the issue, but I just checked my flow and the flow you linked to in the first post and as you can see below it has the ‘unit of measurement’ as ‘cm’
I found this as I wanted to see if there was some integration for the Creality K1 Max, this was helpful but as I don’t run NodeRed, I couldn’t use it. But I began thinking that this must go do an custom_component of it. So with some digging in to the websocket and testing and from getting the javascript from the printer and with help of Gemini I have made a custom_component, that I installed.
I haven’t tested it while printing and for the moment I have just the fans, lamp, temperature, print progress, total layer count, material length and working layer. But it seems to work but as I haven’t yet printed with it active I don’t know the sensors for layers and material. I haven’t uploaded it yet as I want to test it some more and add some more. But if it is someone who want to test it out just say and I will get it up on github.
Just wanted to thank you guys for your findings and the inspiration for a custom_component.
Now the component uploaded to GitHub - hurricaneb/hass_creality_k1 if you want to test it. I have tested it wile printing and layers, progress and so on worked. But test and see how it works for you.
I hope the up keep for it not gonna be to big. But it depends on how much HomeAssistant changes about things.
@hurricaneb Henrik, does it work with the K1C too? your wiki only mentions k1 and k1 max. maybe add a clarification, if you actually dont know, i can try with my K1C if you like.
Hello. Yes, mine is also working with K1C. As I have understand it so K1, K1C and K1 Max all have the same firmware so it is the same websocket communications with it.
I can see that material length has ‘sort of’ been covered but I was wondering if anyone can advise me how to show the value in metres? I know it’s not difficult for me to divide the figure myself but wondered if there was a way to make it work in HA.
Loving this integration, and it works far more reliably than the Creality app.
and after trying to fix my many K1C creality bugs like oozing filament on pause and pause when filament is empty but has still 35cm of filament in the pipe, i finally gave up on emailing creality on FW updates and stuff (im still under warranty, its just 6 months old) and changed over to Klipper with the Gruppy helper script, and added Moonraker as HA extension.
I then discovered that PLR is missing in Klipper, so i programmed a PLR command line tool for my K1C, its available on github.
and then i finally fixed my timelaps issues, the oozing filament, the stop cycle when filament empty detected. and so many more things.
Dont know whats the issue with creality not fixing their shit, i should have gone through the courts and insisting on my statutory right to rectification… but im way to lazy for that.