DrLumen

You may be getting one from the value changing and one from the update of the the timestamp. <eventInfo> <var type="2" id="9"> <prec>0</prec> <val>1</val> <ts>20180306 13:45:15</ts> </var> </eventInfo> </Event> <eventInfo>[VAR 2 9 ] 1</eventInfo> </Event>

Thanks. I had never seen them before.

How are you getting at the system variables like [Current Day of Month]? I don't see those options.

Just curious if there are any solutions?

One thing to consider is ST is all cloud based. The only way to control devices on the ST hub is via Alexa or their phone app. Timers, sunset/sunrise, scenes, are all set via the app so the programming with it is limited. If your internet goes down, nothing will work. They are trying to shift some control locally but that is a work in progress. But, ST is slick, seamless, refined and stable. I wanted control within my walls so I dumped ST and bought the ISY. The ISY is more flexible but crude compared to ST. I tried to get both to work but ST doesn't want to be second fiddle and Samsung really doesn't support it being a secondary controller. I never could get the ISY to act as a secondary controller but wasn't too motivated as, again, I wanted the primary control in house. As always, YMMV.

PM sent with attached xml.

But seriously, what is the use of having color coded icons if they don't mean anything? Hmmm, Adobe flash required for a Choose Files... button?

I would think it would have been really easy for them. "How many any sheep are in that field?" After a quick look, "None!" larryllix, if your LED's glow at 1%, are they giving off any 'real' luminance? If so, you have an instrumentation error. Anyway, I say 2-3% from past experience. YMMV.

IMO, anything less than 2 or 3% should be shown as off. The issue is when scanning over everything as it scrolls past shows almost every thing as on. But, then I have to check the percentages of them to confirm. Some even show as On and Off - however that is supposed to work. It's getting hard to stay positive about some of this shtuff.

Thanks for the confirmation. It would be nice if they showed as off. I'll have my own UI ready soon though.

I have an odd one, at least I think it is odd. When I use the web interface, almost all the devices show as on but with 0%. They never actually go to an off status. Does everyone see this for ZWave stuff?

Oops, Nevermind.

Or, tape the probe on one of the return lines (closer to the hot tub the better) and insulate it well. Tie wrap or plumbers tape the tag part to the underside of the hot tub or hang from one of the pipes.

Hmm, apparently before I bought my current house, they installed the laminate 'hardwood' floor and used cheap molding and quarter round. The rest of the house has some higher end moulding. I never noticed until now.

One thing you may want to keep in mind, Alexa does not do any security stuff - at least that is what they publish for SmartThings. I added a ST stay mode to the Alexa Good Night and Alexa disabled it and it wouldn't run. I'm not sure how it knew but it did. Which, in way is a good thing, since Alexa is not tied to a particular person's voice, anyone that Alexa could hear could potentially unlock your door(s).

I agree that the ZWave market is fractured and forked. I guess it really goes back to the Sigma certification process either being too loose or they just weren't enforcing it. A true 'standard' would not have these issues. As to the lawsuit, I think there is something there as Hail is not just deprecated but obsolete as of 1/2017. Leviton is still selling these devices as certified when they actually aren't currently certified. Or, the current certification means nothing. Somewhat like sticking a UL label on something that no longer meets code. I can't comment on any of the insteon shtuff. I was and am going to avoid all PLC stuff. Supposedly UPB is good stuff but I will newer know it. I spec'd the optimizers and inverter for my solar array as the quoted Enphase inverters used PL comms for reporting. I have had enough of that with X10. Then, I ended up stepping into another mud pit with Zwave. I think as it matures it will get more reliable. I think companies will eventually just settle on a standard set (or subset) of the commands.

Well, this where my attempt at brevity backfired. In asking the leviton tech to remove hail I asked them, and referred to other devices, that it should send a basic status instead of simply a Hail. Or, to allow a config change that could be set for Hail or basic status messages like some of the aeontech devices have. I tried to impress on him that they are already having issues and it will only get worse. I reminded him that even Samsung doesn't support their switches completely as it relies on a 3rd party device handler. Surely they just wouldn't remove hail without some other notification. But seriously, I highly doubt leviton will do anything. That was likely just to get me off the phone - they had already hung up on me once before then. As to UDI and Hail, I was thinking Michel said they supported it at one time but removed it since it was a deprecated command class (paraphrased). Maybe I misunderstood but that is why I asked to have it put back in. I agree too that it doesn't seem like it would be a big programming change to add a hex code into the codes being recognized. Like I say, i will be glad for the trigger and can then issue my own queries but it would be best if UDI would do the query automatically at the time of the Hail. On a bit of a darker note, there might be grounds for a class action lawsuit against Leviton (and any others still using Hail) since they are pushing devices out that are supposedly Z-Wave certified but yet using an obsolete command structure. If they don't want to play nice then I don't necessarily have to either. As to response time, whether it be fractions of a second or a second or two, it really doesn't matter to me. I would like it instantaneous but quick is good enough for me.

A scene in stage lighting and scene in HA is the same basic principle - just different ways and terminology or mindset if you will. A scene can be any set of instruments (lights) or devices which has levels from 0 - 100 in analog or 0 - 255 for digital. In recent years some have started using the term "looks" but is still a scene. HA co-opted it and it's terminology was twisted because you didn't have any type of multiple static controllers or memory controllers for all those new X10 devices. You could have a scene in a 1978 X10 system as you would manually set the overhead lights off, the track lights (old school ) to a specific value, the table lamps dimmed to a specific level, the coffee percolator on an appliance module perking away, etc. All of those comprised a 'scene'. You could turn off that scene but it was then effectively destroyed (All Off) since it had to be recreated manually. Back in the old days, stage controllers typically had 2 scenes and a crossfade slider. Each scene had a submaster control under a master control slider. If a cross fade was used from scene A to B then A was off. Likewise, if the master was changed to 0, both were off. The issue is with HA, most systems didn't really have a memory master control per se so they tried to co-opt other devices to act as a submaster or master. Of course now, HA is to stage lighting as a skateboard is to a 777. Stage systems are getting into tens of thousands of channels now where 1 single instrument (like a video projector) may use half of a DMX universe (256 channels). Instead of the old static 2 scene controllers they now have midrange controllers able to control 8 universes with untold slews of scenes. Again though, while a set of instruments may be tied to a particular scene intrinsically, typically one instrument does not control another. There are some master/slave relationships between some lights but that is usually because there is not a master controller. Yep, I was one of the first to have an X10 system. I was working at an electrical distributor when Leviton licensed and branded a X10 system. I still have the controller they packaged with the starter kits and it still works. I don't think the design or tech has changed in 40 years. And still buggy. I also still have a NSI (coincidentally bought by Leviton) 64 channel memory lighting controller too. It is my baby and while she was once a powerful and beautiful thing, she is now an infant in an ever changing world. She is mine though and will live on by running the Christmas lights.

Michel, I just got off the phone with Leviton tech support. The tech said he would get it to engineering for info regarding a flash or config type change to eliminate their Hail. I informed him of issue with Samsung and UDI and that the command was obsoleted 1/2017. They are supposed to call me back. I'm holding my breath so if you don't hear from me again... Any chance of getting Hail added back to the Condition triggers in the next release? Please?

Coming from a stage lighting background I guess it is easier to understand a scene since they are used so often. Typically, yes, when all the devices are as defined in the scene and physically set (not just some random occurrence when they match) then that scene is on. When that scene is 'off' everything could be at 0 or another scene is on. Layered scenes gets a little tricky and that is when you can get into Highest Takes Precedence (HTP) or Lowest/Latest Takes Precedence (LTP). Highest and lowest being the level the instruments would use. This could get long so I'll stop there. Anyway, when one scene is off then another is set. Whether by another physical scene, individual device settings or to black but even black could also be considered a 'scene'. It really depends on the nomenclature and whatever 'standard' you want to define and use as scene status. Scenes in HA is a bit different but very likely have roots in entertainment lighting. In stage lighting controls, some set of instruments in a scene is not reliant on some other instrument setting. I know why they do it in HA but to me it is really arbitrary. A single switch is to devine whether it should be party mode or clean-the-house mode.

This is in 5.0.11b.

On 5.0.11b here. I guess that's why...

Just curious, would this not work? If Time is Sunrise + 30 minutes For 12 hours Then Set 'Lime Tree Lights' On Else Set 'Lime Tree Lights' Off Am I missing the meaning or a pitfall of For?

Michel, This was my bad. Once I upgraded to 11b the scenes populated correctly. Then, when I initially saw they were populating, I must have been looking at a switch that didn't have a dim option or there was a program delay. The only options I had for the device were Command, Default and Ignore. I have since tinkered and was able to get the options that made more sense - like the flyout to set device dim levels. It turned out to just be a pothole in my learning curve... As I'm still learning this, I'm not completely sure if I understand what you are saying. I did find the way to set levels for each device in a scene (a plus but not really needed in this scenario). I also realized that the simple action of setting a master scene level in the program which would work as well. I should be able to get it to work without the use of a scene. Luckily, it was only 3 devices but if I had tens or hundreds of devices to control then a scene would definitely be needed. I should know once I replace my motion sensors from zigbee to zwave.

Yeah, it's that Hail signal that is the issue. I will contact Leviton to see if there is a config change that will send the ST messages instead of hails - like some aeon devices support. If not, what is the chance Hail could be added to the triggers? Even if Hail wasn't fully supported with a query, i could do a work around in rest (I think) as long as I can get a trigger. Merry Christmas, BTW! --------Edit I just found Query in the program actions so a rest call would not even be necessary - just a Hail trigger.