StateID for Aeon Labs door sensor?
Posted:
Mon Oct 30, 2017 8:38 pm
by CraftGeek
I can't find the stateid that reports the On/Off state of the Aeon Labs DSB29 door sensor. I have looked through all their documentation and tried many guesses.
It is not in the properties of the device nore can I find a way for indigo to force it to report.
Does anyone know what it may be?
Re: StateID for Aeon Labs door sensor?
Posted:
Tue Oct 31, 2017 2:27 am
by FlyingDiver
CraftGeek wrote:I can't find the stateid that reports the On/Off state of the Aeon Labs DSB29 door sensor. I have looked through all their documentation and tried many guesses.
It is not in the properties of the device nore can I find a way for indigo to force it to report.
Does anyone know what it may be?
Why ask this in a Better Email thread? Wouldn't the Z-Wave forum be better?
I suspect it's just "onState" per:
http://wiki.indigodomo.com/doku.php?id= ... ce_class&s[]=onstate#class_properties2
Re: StateID for Aeon Labs door sensor?
Posted:
Tue Oct 31, 2017 5:07 am
by CraftGeek
FlyingDiver wrote:
I asked here first because, from what I can tell, the term stateID is used mostly by this plug-in. I was hoping that someone else that relies on it and has the same brand of sensors as I may have found the information already.
onState didn't work so I'll try the Z-Wave forum.
Re: StateID for Aeon Labs door sensor?
Posted:
Tue Oct 31, 2017 8:23 am
by matt (support)
Hi Sean,
I moved the posts over to the Python Scripting sub-forum.
The device state name should be "onOffState", so it would be accessible via:
dev.states["onOffState"]
but that particular state on sensor device is more easily accessible via the slightly differently named property:
dev.onState
Re: StateID for Aeon Labs door sensor?
Posted:
Tue Oct 31, 2017 8:28 am
by FlyingDiver
I think his issue is trying to use it in a substitution field, since that's the only way this could be applicable to BetterEmail.
So what's the correct value for XYZ in an %%d:1234:XYZ%% pattern?
%%d:1234:onOffState%% ?