I’ve been beating on this for several hours now, and I know that there is something small and stupid that I am overlooking.
I want to expose the changing of the speed of a ceiling fan as a potential trigger for something. (Don’t ask me what, as I have no idea why someone would want to. I just know that as soon as I assume nobody would, someone will find a reason, so I might as well just do it.
It seems that the eventList2 in the json file, and the eventList in the xml file are the pieces that need to be defined. I have those defined in the way that seems consistent with other D_ files that I have seen. However, the events never show up in the list of triggers. In fact, the device itself never shows up in the list of triggers.
Perhaps someone more clueful than myself could take a look and set me straight?
The device type from the json file is different from the one in the device file.
Two observations/hints:
[ul][li]The device_type tag in the Json file is ignored, so you should remove it. DeviceType is used instead.[/li]
[li] and from the device file are obsolete and ignored, so you can remove them.[/li][/ul]
This seeming redundant, but in actuality deprecated features keeps me very confused about what goes where and why. A clean example (reference copy) of what is need for each major Vera version would sure help keep things straight. Especially for someone that wonders in and out of the code on an occasional basis.
I’ve got a possible use case: If the fan hits a certain speed, kick on/off the AC (implies increased heat, for instance).
I use the thermostat in my master bedroom to identify whether to turn on the fan and what speed to run it on (speed increases with temperature). A trigger at 100% would save me from having to write LUUP to manage a Fan/AC interaction too (Apologies if I could have done it with triggers already at this point. I wrote the code when it wasn’t an option to me and “If it ain’t broke…” :))
