Eric Callahan

As of right now Klipper does not have the ability to request data from its clients (ie: Moonraker). The `action_call_remote_method` is fire and forget, it can send data to Moonraker...

I don't think its a good idea to "hack" in a response using macros as it doesn't resolve waiting/notification on the other end. If Klipper is going to request information...

Thanks. Indeed it appears that Gen 2 shelly devices have changed authentication methods. For the time being I have noted in Moonraker's documentation that only Gen 1 devices support authentication...

Ok. I suspect that the heater problem is a sorting issue, I think I can resolve that quickly. I'll need to dig into the "T-1" issue, it seems strange that...

I pushed some changes in commit 54abd2748652b431469f18a46698f1223fffd4e1. I believe that this will fix the sorting issue and properly assign the correct tools. I had to dig into the PanelDue code...

It isn't currently possible to create a custom dialogs through Moonraker. You can create Macros though. It should only send `T-1` if you select the active extruder, at least according...

That might work until I can figure out why the extruder is showing up as active when I set the hstat field to standby. FWIW, Moonraker's PanelDue module is intended...

TLS support has been added with the `enable_tls` option. That said, if you are using a self signed cert you need create your own CA and install the root certificate...

I'm not sure this is the correct behavior. It could unintentionally remove a saved profile when the user runs `BED_MESH_CLEAR`. For example: ``` BED_MESH_PROFILE LOAD=bed60 ..do stuff BED_MESH_CLEAR BED_MESH_CALIBRATE PROFILE=bed80...

> I'd argue that they did. Isn't that the point of the BED_MESH_CLEAR? If I am misunderstanding how BED_MESH_CLEAR is supposed to work, I am sorry. But in that case,...