Retreiving the device ID that triggered an Action

Hi, excuse the newbie question if this is obvious, but could not find any working solution so far (first script)

Objective: catch any device that is broadcasting 'battery low".

Approach: Setup a trigger with the "from" popup set to anydevice and button/group set to 2. This way I get the a trigger for any battery operated device I add. then I want to write a python script that sends an e-mail with the name of the actual device that triggered this action.

Problem: I tested a script,

Code: Select all

emailAddress = "my email address"
emailSubject = "Battery Low, python script version"
emailBody  = "triggered at " + str( indigo.server.getTime() ) + "\n"
emailBody += str(indigo.triggers[1288696085]) + "\n"
emailBody += str(indigo.triggers[1288696085].globalProps)
indigo.server.sendEmailTo(emailAddress, subject=emailSubject, body=emailBody)


but I can't figure out how to retrieve the device object that is responsible for the trigger. I printed the info about the trigger but it never changes, no matter what device triggers it.

Hopefully, I missed something simple. If not this should be a feature request...

Thanks in advance.

[jay (support)]

A couple of problems:

1. Group 2 is for TriggerLincs but group 3 is for Motion Sensors.
2. Indigo doesn't pass information to the action about how the action was triggered because there are a bunch of different ways that can happen. The best choice is to just have individual triggers for each battery-powered device - some amount of setup but once it's done maintenance is quite low. You can create a shared script if you want to have a single python method that you call from multiple places.

Passing triggering information to script actions is already on the request list.

1. Group 2 is for TriggerLincs but group 3 is for Motion Sensors.

But group 2 for the TriggerLincs doesn't indicate battery low, right? Group 2 is used only in "multi-scene mode" on the TriggerLincs I think.

[jay (support)]

Just checked with Matt (much more up on INSTEON than me) and no, the TL doesn't support low-battery warnings apparently (hur dur). I have no clue what multi-scene mode is either.

A couple of problems:
[list=1][*]Group 2 is for TriggerLincs but group 3 is for Motion Sensors.

You are right, I tried to find back where I got this info but only found documentation supporting your point.

I'll go for the brute force approach and create individual triggers...

Passing triggering information to script actions is already on the request list.

Appreciated. Love my system nonetheless. Thanks for the quick response.

1. Group 2 is for TriggerLincs but group 3 is for Motion Sensors.

But group 2 for the TriggerLincs doesn't indicate battery low, right? Group 2 is used only in "multi-scene mode" on the TriggerLincs I think.

Found out that through jumpers, the behaviour is configured as

Jumper Installed: Open = Group 1 On, Closed = Group 1 Off;
Jumper Uninstalled: Open = Group 1 On (or off), Closed = Group 2 On (or Off)