docs/control/events.md

3 This file defines the events that dictate how fan control operates. Each event
6 Actions are where fan targets are calculated and set, among other things.
22     "name": "fan(s) missing",
25         "name": "fan inventory",
52 The above event is an example of a method to set the fan target to 15000 when
55 The trigger `init.get_properties` will, on fan control startup, read the Present
57 object in the 'fan inventory' group, update those values in the object cache,
65 the Present property on each member of the group and set the fan target hold to
66 15000 when one or more of them is false. Otherwise, it will clear its fan target
103 Init triggers run when fan control events are enabled on fan control startup.
117    member of the group, and store it in fan control's object cache.
120    group member in fan control's D-Bus service cache map.
239 Most actions set fan targets or floors. This can be done by requesting a target
247 that parameter to help choose a fan floor.
420 below the configured count, active fan target changes are allowed.
438 Sets the fan floor to the defined zone's default fan floor when a service
440 providing the sensors, the fan floor is allowed to be set normally again.
528 data again, active fan target changes are allowed.
535       "name": "fan inventory",
545 with the 'fan inventory' group is lost.
550 of fans meet criterion for the particular condition. A locked fan maintains its
569 This could be used for example, to lock the rotors of a multirotor fan to a high
595 'events.json'. If missing or false, looks in the base fan control directory.
609 floating point types are supported as these are the only valid types for a fan
620       "name": "fan targets",
629 property value of all members of the 'fan targets' group.
712   "name": "fan inventory",
718 Then a oneshot timer of 5000000us will be started when every member of the fan
726   "name": "fan inventory",