mkluge / iot_control Goto Github PK

I'd like to add an auto-off feature. If a raspi GPIO is switched on then it switches itself off after minutes. This should happen locally on the raspi so that the garden doesn't get flooded because the wifi is interrupted or the mqtt broker fails or whatever.

Basically, this is simple with HA MQTT. But if goes against the architecture of iot_control. The 'mqtthass' component doesn't know about the 'iotraspigpio' cpmponent's details and 'iotraspigpio' is not supposed to send MQTT messages.

What would be a clean solution?

Option A: The backends already know the devices. Should the devices get to know the backends as well? And then call them directly? Sounds wrong, doesn't it?

Option B: The device get a pointer to the iotruntime object. And the iotruntime gets a "switch me <on/off> in time" functionality. This could be equivalent to a MQTT message arriving but triggered locally. The time could be in granularity of the iotruntime.update_intervall -- in every loop iteration it checks if anything is due from an ordered list of scheduled events ( == option B1). Or it could use a background thread via Python's threading.Timer ( == option B2).

Which one would you like?

Basically copy the GPIO backend but have it run local shell commands. The commands are configurable in the config file.

currently only reading channel 0

currently names are fix, should be fixed

values change with different light settings, but seem a bit low
maybe calculation is wrong

switch status changes should got into the backends as new values