Niklas Kunz

Thanks for opening an issue! Indeed, the `daemon` doesn't persist any button mappings across reboots at the moment. Since the Pi Tool was designed with desktop usage in mind, it's...

Just to chime in here: For persistence and regarding the daemon code, I think what @themasch outlined is the way to go. In terms of CLI usage, I wouldn't expose...

@themasch: Good point with potential conflicts of persisted button mappings in the GUI. Indeed there would have to be a few changes to the GUI code if the daemon persists...

Technically a web interface should be possible, yes. The Pi Tool was built using web technologies, so instead of launching it as an Electron application it could additionally be served...

There exists documentation for the websocket API in `daemon/README.md` now! Anyone that wants to try implementing a command-line client for it, feel free to do so! I'll gladly provide guidance...

That's a good point, thanks for pointing it out. I reopened the issue.

Upon further investigation, it seems like `Axon.Compiler.recur_model_funs` can never match on a `%Axon.Node{op: :block}` with multiple parents (https://github.com/elixir-nx/axon/blob/main/lib/axon/compiler.ex#L464). Instead, the "generic" case (for built-in `Axon.Layers` nodes) matches (https://github.com/elixir-nx/axon/blob/main/lib/axon/compiler.ex#L665), which leads...