Design direction

adf999 · October 28, 2024, 1:56pm

I don't want to needlessly go down rabbit holes and would like some design guidance. I want to build a driver for these motion blinds: GitHub - starkillerOG/motion-blinds: Python library for interfacing with Motion Blinds. The hardware consists of a hub that can have x number of blinds. All calls are UDP.

My main question is how best to structure the driver? Should I have one driver for the hub and a separate driver for the blind or a single driver with all code in one place? Is there accepted standard?

djgutheinz · October 28, 2024, 3:16pm

Since a single hub supports multiple blinds, the Hub should be the parent and the blinds the children.

dadarkgtprince · October 30, 2024, 1:55pm

agree with djgutheinz, hub as parent, blinds as children. this allows for neat organization in devices tab

system · October 30, 2025, 1:56pm

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.