This is not specific to this plugin, and can be accomplished with a standard indigo action. Look for "Insert Device State Into Variable" under variable actions.BobRoss wrote:I can't figure where to convert the state to a variable to email it
Timed Devices plugin
Re: Timed Devices plugin
Re: Timed Devices plugin
I must have look at that 1000 times but I guess I never needed it!!
- FlyingDiver
- Posts: 7323
- Joined: Sat Jun 07, 2014 10:36 am
- Location: Southwest Florida, USA
Re: Timed Devices plugin
Why do you need to put it in a variable to email it?BobRoss wrote: I can't figure where to convert the state to a variable to email it
joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177
my plugins: http://forums.indigodomo.com/viewforum.php?f=177
Re: Timed Devices plugin
I travel and it's nice to see what's going on. I don't have to log into the system.
Bob
Bob
- FlyingDiver
- Posts: 7323
- Joined: Sat Jun 07, 2014 10:36 am
- Location: Southwest Florida, USA
Re: Timed Devices plugin
I wasn't asking why you email the data, I was asking why you needed to put it in a variable first. Instead of using the device state directly in your email.BobRoss wrote:I travel and it's nice to see what's going on. I don't have to log into the system.
joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177
my plugins: http://forums.indigodomo.com/viewforum.php?f=177
Re: Timed Devices plugin
Was thinking the same thing.... but with some devices, it can be tricky figuring out what the device state verbiage is. I typically do this when composing an email/text/SMS/Pushover via python.... set the device state to a variable in python and add it to theMessage to get plopped into a something.FlyingDiver wrote:I wasn't asking why you email the data, I was asking why you needed to put it in a variable first. Instead of using the device state directly in your email.BobRoss wrote:I travel and it's nice to see what's going on. I don't have to log into the system.
Bill
My Plugin: My People
My Plugin: My People
- jay (support)
- Site Admin
- Posts: 18413
- Joined: Wed Mar 19, 2008 11:52 am
- Location: Austin, Texas
- Contact:
Re: Timed Devices plugin
Say more?whmoorejr wrote:Was thinking the same thing.... but with some devices, it can be tricky figuring out what the device state verbiage is.
Re: Timed Devices plugin
With some devices, I can look at the home window for that device and scroll down to see all the different states and they are written in pytonese(sp?). onOffState , onTime, etc. Like for a Running Timer device.jay (support) wrote:Say more?
For some devices, they are harder for me to find.... Example; my insteon thermostat. When I was writing a python script to tell me a device state from my thermostat, I made a thermostat device on a control page, then looked at the 22 different states you can choose from to use as a baseline for the verbiage I needed for my python script.
Is this the part where you tell me about the super simple button you click on somewhere that lists all of a devices states in a python reference format?
Bill
My Plugin: My People
My Plugin: My People
- FlyingDiver
- Posts: 7323
- Joined: Sat Jun 07, 2014 10:36 am
- Location: Southwest Florida, USA
Re: Timed Devices plugin
You mean this list?whmoorejr wrote:Is this the part where you tell me about the super simple button you click on somewhere that lists all of a devices states in a python reference format?
- Attachments
-
- Screen Shot 2020-07-08 at 7.37.54 AM.png (306.73 KiB) Viewed 8803 times
joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177
my plugins: http://forums.indigodomo.com/viewforum.php?f=177
Re: Timed Devices plugin
I didn't know you could right-click on that stuff to get the python reference..... but how do you get the python references for states when certain devices don't show custom states? My thermostat shows the controls, but no custom state block below it. Same thing with lights, fans, motion sensors.... without going through everything, it looks like the stuff that works directly without a plugin.FlyingDiver wrote:You mean this list?
The devices that work via plugin typically have that "Custom States" box.
- Attachments
-
- Insteon Thermostat.png (35.04 KiB) Viewed 8793 times
Bill
My Plugin: My People
My Plugin: My People
- jay (support)
- Site Admin
- Posts: 18413
- Joined: Wed Mar 19, 2008 11:52 am
- Location: Austin, Texas
- Contact:
Re: Timed Devices plugin
TL;DR - check the Indigo IOM documentation when you want to access properties/states of built-in device types. Read on for more specific information.
Device types that are directly implemented by Indigo often don't have custom states, because they are not custom devices. Plugins can implement any of the device types Indigo supports or they can define a "custom" device, in which case Indigo shows them in a list. Plugins can also add "custom" states to devices that implement one of the supported classes.
For the standard device definitions, the properties and states for the device are documented in the Indigo IOM documentation. We don't expose them in the Custom States tile because they aren't custom. The original intent was for built-in devices to have direct properties (i.e. my_device.fanMode) and that the states list would be used for things that were custom to the specific model of the device. In practice, and over time, it's become less clear about the distinction between properties and states. Perhaps something we'll address some day, but it would be a big fundamental change so it's not likely to happen soon.
Device types that are directly implemented by Indigo often don't have custom states, because they are not custom devices. Plugins can implement any of the device types Indigo supports or they can define a "custom" device, in which case Indigo shows them in a list. Plugins can also add "custom" states to devices that implement one of the supported classes.
For the standard device definitions, the properties and states for the device are documented in the Indigo IOM documentation. We don't expose them in the Custom States tile because they aren't custom. The original intent was for built-in devices to have direct properties (i.e. my_device.fanMode) and that the states list would be used for things that were custom to the specific model of the device. In practice, and over time, it's become less clear about the distinction between properties and states. Perhaps something we'll address some day, but it would be a big fundamental change so it's not likely to happen soon.
Timed Devices plugin now compatible with Indigo2022.1
Hi kmarkley
I've updated the plugin code to work with the latest version of Indigo (Python 3 and other goodness).
The code did not require much change, and I have already sent you a pull request to you on Github. Hope you can merge it in the main repo and publish a new version. I did not increment the version number etc in the XML as you might want to use your own rules for versioning.
Till then, anyone else interested in it can get the code from: https://github.com/indynz/Indigo-Timed-Devices
I find the plugin really handy. Thanks for creating it @kmarkely!
I've updated the plugin code to work with the latest version of Indigo (Python 3 and other goodness).
The code did not require much change, and I have already sent you a pull request to you on Github. Hope you can merge it in the main repo and publish a new version. I did not increment the version number etc in the XML as you might want to use your own rules for versioning.
Till then, anyone else interested in it can get the code from: https://github.com/indynz/Indigo-Timed-Devices
I find the plugin really handy. Thanks for creating it @kmarkely!
Re: Timed Devices plugin
Hi indy
Thank you for doing this, however I'm seeing device start errors for several types of devices. There are a couple unicode errors that should be easy to fix, and several errors from the change in dictionary indexes. It's also possible that other errors will be revealed once these device types are able to start.
Shouldn't be hard to fix, but I'll obviously need to before releasing a new version.
Thank you for doing this, however I'm seeing device start errors for several types of devices. There are a couple unicode errors that should be easy to fix, and several errors from the change in dictionary indexes. It's also possible that other errors will be revealed once these device types are able to start.
Shouldn't be hard to fix, but I'll obviously need to before releasing a new version.
Re: Timed Devices plugin
Python 3 version compatible with Indigo 2022.1+ is now on the plugin store. Thanks @indy for getting this started.
Re: Timed Devices plugin
Hi @kmarkley --
I use the heck out of this plugin, so if I forgot to say thanks, I want to say it now.
I have a request --
I have been using the heck out of FlyingDiver's Home Assistant Agent plugin. The devices that the plugin bridges from Home Assistant have dynamic custom states. For example, if the AVR is off, there is no volume state.
When I put a timer on one of those variable states, the Timed Devices spams the logs:
I've actually been using this combination for some time, but something recently has made the spamming to the logs much more noisy.
I use the heck out of this plugin, so if I forgot to say thanks, I want to say it now.
I have a request --
I have been using the heck out of FlyingDiver's Home Assistant Agent plugin. The devices that the plugin bridges from Home Assistant have dynamic custom states. For example, if the AVR is off, there is no volume state.
When I put a timer on one of those variable states, the Timed Devices spams the logs:
Is there a way we could quiet some of these notifications? I understand under some circumstances they could be useful, so I'm not saying we should silence them.Timed Devices Error "House AV - Main area volume change" thread error
'key volume_level not found in dict'
I've actually been using this combination for some time, but something recently has made the spamming to the logs much more noisy.