@demlak @hyperx Can you please provide some more details on the requirements you have?
Looking at “pimatic-piblaster” as it stands today, it only provides a dimmer device. Did you consider using “pimatic-johnny-five” at some point? Note, “raspi-io” as part of “pimatic-johnny-five” now supports software PWM which works very well (see JohnnyFivePwmOutput which works well with Raspberry). I’ll also integrate “pi-io” into “pimatic-johnny-five” which is a developing, faster replacement for “raspio-io” which has a native code integration with pigpio. It claims to support PWM and Servo pulses on any number of GPIOs simultaneously. Needless to say, johnny-five integrates numerous device types including servos.
Another alternative may be “pimatic-gpio” which is also based on “onoff” - it is missing the Dimmer, however, as no software PWM is provided with “onoff” as far as I can tell.
I can imagine you guys are doing other fancy stuff using pi-fast-gpio, but the question really is why should pimatic should be talking to pigpiod and what should this look like in terms if device types, predicates, and actions provided. If it is about controlling servos it’ll great if you provide a rough outline of what the device type (including actions and predicates) should provide for. We should also discuss the co-existance with other drivers like “pimatic-johnny-five” and “pimatic-gpio”.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law