Trigger Event from text value?

[KurtLutterman]

I can't figure out how to trigger an event based on the text in the Description device. WeatherXML had variables that I could check contains. How to do it with AK Weather? I need to turn my sidewalk snow mats on if Description contains "snow" or "flurry".

[randy]

If you have the Easy Trigger plugin it has a string based Trigger. The “String” is where long descriptions are stored.

I use 3 virtual devices



and 6 events



each looks to the description of the forecast day

[alexbk66]

HS doesn't have the trigger based on the device string, only the value. Depending on the provider you can use the device value, i.e. AerisWeather, Visualcrossing, YR, but I don't think it's reliable, especially for snow.

[Michael McSharry]

The typical mechanism provided by HS for text-oriented triggers is with Value Status Pairs. In essence a text string is assigned a numeric value. Different strings will have different values. A related mechanism is used to associate icons with a number. When a trigger is setup it will show the text string (Status) to the user so in general the user is unaware of the Device Value that is really being used by the HS event trigger engine.

It depends upon the plug-in developer providing support for VSP and VGP rather than just stuffing text in Device String.

[randy]

The typical mechanism provided by HS for text-oriented triggers is with Value Status Pairs. In essence a text string is assigned a numeric value. Different strings will have different values. A related mechanism is used to associate icons with a number. When a trigger is setup it will show the text string (Status) to the user so in general the user is unaware of the Device Value that is really being used by the HS event trigger engine.

It depends upon the plug-in developer providing support for VSP and VGP rather than just stuffing text in Device String.

However, weather forecasts are usually written as a String and no Status text or value is used. Primarily because the data could never be represented in a normal VSP. Because HS4 has commingled string and Status test, the forecast below is shown as Status, despite the fact it is stored only as a string. That is why I use Easy Trigger’s String based Trigger for these devices.



If the device is viewed using the legacy Device Manager, it is much more clear. There is no stored Status text, only a populated String.



I have dozens of plug-in owned devices that only display Status and use the String exclusively. I wish it was all displayed as it was in HS3 so we could tell where the data is stored. Unfortunately we are still dealing with a few missing items under HS4 that were there for us in HS3.

[MNB]

If you have the Easy Trigger plugin it has a string based Trigger. The “String” is where long descriptions are stored.

I use 3 virtual devices



and 6 events



each looks to the description of the forecast day

randy, a few questions re your virtual devices and associated events.
1) How does "Snow Check" event work?
2) Your "Snow Today Off" Event starts with Manual triggered, why I would have thought it started with easytrigger?
3) One of the things I noticed is that with easytrigger it seems to only show the root device and not any of the children is there some way of getting it to show the associated children e.g. "Description [0]" or "Descr Abbr [0]",

[randy]

randy, a few questions re your virtual devices and associated events.
1) How does "Snow Check" event work?
2) Your "Snow Today Off" Event starts with Manual triggered, why I would have thought it started with easytrigger?
3) One of the things I noticed is that with easytrigger it seems to only show the root device and not any of the children is there some way of getting it to show the associated children e.g. "Description [0]" or "Descr Abbr [0]",

”Snow Check” is a single recurring Trigger Event. I have six Events (on and off for snow today, snow tonight and snow tomorrow) they are all manually triggered and run from this single recurring Event. When we get Conditional Actions, this can be consolidated to a single event.



Easy Trigger displays the full name of the device for me. I have not cleaned up the naming from when HS3 created them.

The Device


The Event



The Full list of features is listed.



Here I have changed the naming to be more HS4 specific.

[MNB]

randy, many thanxs for the examples, I need to digest the "Conditional Actions" under the Snow Check event, it took me a minute or two to figure out how to access it but was finally able to under run another event and selecting the two bottom options (wasn't totally intuitive but finally got there).

I can see from you screen shots that you have access to all of your AK Weather children devices via EasyTrigger, but I on the other had seem to only have access (via EasyTrigger) to the root AK Weather (parent) device only, however I can see via my children devices when viewed in Devices view, any ideas as to why and how to I fix it?

[randy]

randy, many thanxs for the examples, I need to digest the "Conditional Actions" under the Snow Check event, it took me a minute or two to figure out how to access it but was finally able to under run another event and selecting the two bottom options (wasn't totally intuitive but finally got there).

I can see from you screen shots that you have access to all of your AK Weather children devices via EasyTrigger, but I on the other had seem to only have access (via EasyTrigger) to the root AK Weather (parent) device only, however I can see via my children devices when viewed in Devices view, any ideas as to why and how to I fix it?

Easy Trigger takes some home to populate, though usually within 15 minutes or so. Try restarting Easy Trigger or HomeSeer and see if you get more choices.

[alexbk66]

”Snow Check” is a single recurring Trigger Event. I have six Events (on and off for snow today, snow tonight and snow tomorrow) they are all manually triggered and run from this single recurring Event. When we get Conditional Actions, this can be consolidated to a single event.

I could possibly add some trigger in the plugin to simplify your setup, if you could provide some "requirements specification".

[randy]

I could possibly add some trigger in the plugin to simplify your setup, if you could provide some "requirements specification".

For these Events, I am just looking for snow to be in the forecast for today, tonight or tomorrow. This is used to turn our satellite dish heater. The only Trigger I need is if Snow is forecast in the next 24 hours.

[alexbk66]

For these Events, I am just looking for snow to be in the forecast for today, tonight or tomorrow. This is used to turn our satellite dish heater. The only Trigger I need is if Snow is forecast in the next 24 hours.

So possibly a trigger "If description contains"?

[EDIT]

BTW, note that in the main root device I truncate the description string (100 chars I think)

[randy]

So possibly a trigger "If description contains"?

[EDIT]

BTW, note that in the main root device I truncate the description string (100 chars I think)

That is essentially what I do now. Easy Trigger is used for a string match for the description containing “snow”. As far as truncation goes, it has not been a problem for me.

[alexbk66]

That is essentially what I do now. Easy Trigger is used for a string match for the description containing “snow”

I understand, but my question is - will it add any value to AKWeather if I add the trigger directly in my plugin, and can it simplify the use?

[MNB]

Easy Trigger takes some home to populate, though usually within 15 minutes or so. Try restarting Easy Trigger or HomeSeer and see if you get more choices.

randy, that was the ticket, I did a restart this morning and whala I now have children showing up in my EasyTrigger devices.. who da thunk it!, many thanxs for the guidance.

We (east coast) had snow for today and of course your Snow Today is indicating a snow condition. I have to say using the conditional actions really shortens the event, once I grasp what and how it works.