Rolf Vreijdenberger

Hi @kernc, I've done some work on using udev rules in combination with systemd unit files to allow the input device to be predictable via the udev rules and using...

a template unit file can only accept 1 parameter, of which the device would be the logical option. it would be my preferred way to go also. then there is...

> I would opt for EnvironmentFile, so that the udev rule and systemd service can be left intact sounds good > I'd imagine most users type in their one chosen...

go through all devices in /dev/input by using 'cat /dev/input/eventX' and try to type some stuff. when you see things appear in stdout, you found the correct device. (X is...

simplest way would be to create an extra field in your backend of choice (say for example postgres) that stores that data. the way to store the data would be...

HI @Aracon , in essence it would be very nice to be able to add contextual parameters. this would involve a statemachine configuration on a transition (or states) in a...

a json string can be implemented in any backend so that would be my preferred choice. the fact that it is possible to have chained rules and composite commands is...

the lack of having chained rules and composite commands will be offset by the fact that you can highly configure your commands/rules via a json configuration or the like. This...

+1 on static ip. I am using 3 esp32 based projects for home assistant, wled, esphome for generic stuff and espresense. Of these 3 wled and esphome offer static ip...

+1. great library and work, thanks for that. But when moving forward while trying to use the library directly, we cannot work with the velocity for which changes are implemented....