Thanks for testing guys.
berkinet wrote:On first install of the DoorBird device I mistyped the IP address and Indigo went out for a long, lunch, dinner... I killed Indigo client, reconfigured the device and all is well. Needs some better error handing.
Thanks, I'll take a look
berkinet wrote:I created a motion device. No joy. No reports of motion, neither from the areas that are not masked, nor from the masked areas (as are reported under the old API).
Can you please enable debug looking in the plugin preferences? You should then see a debug message referencing an unknown event. Could you please paste the output? I have firmware 000112, I suspect there is a different event code being used.
berkinet wrote:Created a Doorbell device and a trigger on it's on/off state. That worked. Though, I did notice it triggered twice on a single button press event. Not a big deal, as I can debounce the input in Indigo. But, I wasn't sure if the API sent two events, or the plugin fired twice.
Thanks, I'll take a look
berkinet wrote:And, a comment: I saw that the DoorBird device actually logs Doorbell events, and I assume, motion events. But, there is no way to suppress this logging or trigger on the events. So, maybe you could simplify the plugin and have only one device, the DoorBird, with states to track doorbell press and motion events.
Good pickup, thanks. I've released version 0.2.0 which includes a fix to log the correct names. Could you please update? I like the seperate devices personally, but am open to changing it if there is consensus?
lanbrown wrote: I'm getting this error message:
Code: Select all
DoorBird Error Error in plugin execution ExecuteAction:
Traceback (most recent call last):
File "plugin.py", line 328, in actionControlGeneral
AttributeError: 'Plugin' object has no attribute 'burst'
Also if you stop or reload the plugin, Indigo has to force it to stop.
Thanks. Version 0.2.0 includes a fix to the "burst" error. Could you please update?
Pete