simplextech

The sensors update the Ambient Weather system every 60 seconds and the data feed to the nodeserver is real-time as changes happen. Wireless Tags are also great and I've been thinking about buying some too

I use Temp/Humidity sensors that connect to my Ambient Weather station. I have one of the sensors in the bathroom and a very simple program: Bathroom.Humidity - [ID 0020][Parent 0001] If 'Ambient Weather / WS-1401-Addon' Sensor 1 Humidity >= 75% Then Set 'Bathroom / sw.Bathroom.Fan' On Else - No Actions - (To add one, press 'Action') I have other programs that check if the fan is on and for how long and then turn it off. But just a very simple humidity check mainly used if someone is in the shower without the fan on...

Use of the "is not off" comes into play with Dimmers. On = 100% Off = 0% What's 42%? Not On but Not Off...

Welcome. Like I said it's a good system and the developers put a lot of focus on ST device compatibility. I think most ST devices work so do most Iris devices (not v1 though). So it's a good "joining" of systems and after almost of year of me fighting them they gave in with a integration option

Hubitat Elevation is a new kid on the block which is built around being a local processing. We all call it a local SmartThings as it's very much a clone of the ST system. I'm working on an integration currently. The initial prototyping has been released and I posted about it here: As an integrator as well but more on the software side of things I try to keep things local if possible and if it makes sense. Hubitat is a good system with some minor growing pains but it's worth looking at. Almost all of the current users are former SmartThings users! I have a first public release version of the hub and it's been improving greatly in the last year.

Updates from overnight showing the temp/humidity updates for the NYCE Motion Sensor:

Here's some eye candy and some preliminary logs. This is going faster than I anticipated. 2019-03-13 00:25:57,696 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:25:57,697 [NodeServer] [DEBUG] {'installedAppId': None, 'name': 'motion', 'value': 'active', 'hubId': None, 'descriptionText': 'Zooz 4-in-1 Sensor: motion is active', 'deviceId': 465, 'unit': None, 'displayName': 'Zooz 4-in-1 Sensor', 'locationId': None, 'source': 'DEVICE'} 2019-03-13 00:25:57,699 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:25:57,721 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:25:57,722 [NodeServer] [DEBUG] {'installedAppId': None, 'name': 'motion', 'value': 'active', 'hubId': None, 'descriptionText': 'Zooz 4-in-1 Sensor: motion is active', 'deviceId': 465, 'unit': None, 'displayName': 'Zooz 4-in-1 Sensor', 'locationId': None, 'source': 'DEVICE'} 2019-03-13 00:25:57,723 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:26:03,193 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:26:03,195 [NodeServer] [DEBUG] {'installedAppId': None, 'name': 'motion', 'value': 'active', 'hubId': None, 'descriptionText': 'Dome Motion Sensor motion is active', 'deviceId': 468, 'unit': None, 'displayName': 'Dome Motion Sensor', 'locationId': None, 'source': 'DEVICE'} 2019-03-13 00:26:03,196 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:26:11,512 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:26:11,513 [NodeServer] [DEBUG] {'installedAppId': None, 'name': 'motion', 'value': 'inactive', 'hubId': None, 'descriptionText': 'Zooz 4-in-1 Sensor: motion is inactive', 'deviceId': 465, 'unit': None, 'displayName': 'Zooz 4-in-1 Sensor', 'locationId': None, 'source': 'DEVICE'} 2019-03-13 00:26:11,515 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:26:11,538 [NodeServer] [DEBUG] ----Device Info---- 2019-03-13 00:26:11,539 [NodeServer] [DEBUG] {'installedAppId': None, 'name': 'motion', 'value': 'inactive', 'hubId': None, 'descriptionText': 'Zooz 4-in-1 Sensor: motion is inactive', 'deviceId': 465, 'unit': None, 'displayName': 'Zooz 4-in-1 Sensor', 'locationId': None, 'source': 'DEVICE'} I have a ZigBee NYCE Ceiling motion sensor added and working. Motion is REAL TIME and the other values update based on standard interval of the sensor. Also to note Z-Wave devices are also being supported in this integration and I'm going to see if I can include the built-in native apps from Hubitat which will also include full Lutron Caseta Pro / RadioRA integration capability. The integration is with the Hubitat Elevation hub. I'll post full details and information once I get this further along. So... probably tomorrow sometime.

Then give me a little time. Prototyping has started for a polyglot to interface the system.

So it's not specifically about SmartThings? More about the Zigbee devices? So.... Zigbee integration is of interest? If so the up-side is I've been considering developing this for iSY as I'm also working on an integration for HomeSeer as well. It will not be using SmartThings as that is primary cloud based which I do no like. In summary... IF the hub/interface etc was in the $100-$150 range total and integrated with ISY that is of interest?

Can I ask why specifically SmartThings? If the goal is for temperature readings there are other z-wave sensors that report temperature and other means of getting temperature. I will agree the Multipurpose sensor from ST is a good sensor but it is Zigbee.

This is what I've been doing... my event viewer is scrolling too much to be able to watch there

It's not. That was a dummy program that I used to copy/paste from and things I'm toying with so ignore the Then statement it's not relevant. I'm just trying to make sure I understand the use structure of time within ISY versus what the editor allows

I think I found a new tagline

Here's the reason I'm asking about the time: Test.Program - [ID 0007][Parent 0001] If From 12:00:00AM To 12:00:00AM (same day) Then In 'ms.FR-Desk.Motion' Set 'Family Room / fl.FR-Light' To default Else - No Actions - (To add one, press 'Action') From the "editor" stand point it allows it to be entered. From a logical stand point it's the same time and not valid. I've seen this issue/question before about other systems and the valid is use should be... Test.Program - [ID 0007][Parent 0001] If From 12:00:00AM To 11:59:00PM (same day) Then In 'ms.FR-Desk.Motion' Set 'Family Room / fl.FR-Light' To default Else - No Actions - (To add one, press 'Action') So I'm asking/double checking that I'm not missing something with how time works with ISY. However the (same day / next day) is a really nice feature for spanning a time period across two days

This may seem a bit silly however it is a common discussion point with other controllers and I've learned each vary somewhat and have their own uniqueness. This is what my current understanding of the ISY time program scheme is and I'm looking for corrections/updates/addendum to ensure I understand what and how the ISY is working so to best structure my own programs efficiently and correctly. Programs and Time....time to program.... FROM -> TO If the time FROM -> TO is the first line of the program the "trigger" for the program is the FROM Time for the THEN clause or the TO time for the ELSE clause. If there is a CONDITION (AND) to the IF clause and the time is between the FROM->TO time period the THEN clause is executed Time period In the programs there is the nice drop down of same day / next day which is great. Question is about actual time/hour. Is 12:00 TO 00:00 valid or does it have to be a 12:00 TO 23:59? Is the same true though for a 00:00 to 06:00 (same day). Can the time reference use the 00:00 for either beginning or ending of the time knowing that is midnight and follow a 24 hour clock correctly using the same/next day drop down? This is a issue with other systems where it's a 12 hour clock of 00:00 to 23:59 and causes quite the confusion at first.

I agree that it is weird. Some of this is my learning curve with the ISY and unique properties but some of it is boggling that it works for one program but not an almost identical one. The only solid thing I could say could be the problem was the structure/order without the parens for the AND with the group of OR statements and that was causing it to register true on a single door within the logic flow. This is probably what it was and is one of those 'ism's of the hard coded nature of the language used in the programs. I'm going to start a new thread to discuss "Time" that's a favorite and fun one that I see asked for every system and is a common HS thread

The two programs that were posted acted very differently. I did modify them to have the time restriction as the very first item and then put the multiple OR statements inside an AND block and so far both are behaving correctly. The 'ism's...

I agree there are the 'isms to learn. But why do the same program act differently? BTW I did and normally do start with the time restrictions as the first item and it was not working as expected so I thought maybe change the trigger order... but none the less why do two programs of the basic same structure behave differently?

Ok.... but why is one program completely ignore the time segment and the other one honors it? Well honors it except for one door

Riddle me this..... The below program works and honors the time designation of From/To with the EXCEPTION of oc.Garage.Ext.Door-Opened. I can open any of the other two doors and the lights do NOT come on. This is the intention. However if I open the Garage Ext door the lights come on? Garage.Lights-On - [ID 000A][Parent 0001] If 'CL Bedroom / oc.CL-Bedroom.Int.Door-Opened' is switched On Or 'Garage / oc.Garage.Ext.Door-Opened' is switched On Or 'Laundry Room / oc.Laundry.Door-Opened-Opened' is switched On And ( From Sunset - 1 hour To Sunrise (next day) ) Then Set 'Garage / sc.Garage.Lights' On Else - No Actions - (To add one, press 'Action') Now this one: This one is similar with the difference of two doors. The garage exterior door is in this list as well. This program completely ignores the From/To time designation and turns on. Deck.Lights-On - [ID 0002][Parent 0001] If 'Living Room / oc.LVR.Door-Opened-Opened' is switched On Or 'Dining Room / oc.Dining-Room.Door-Opened' is switched On Or 'Garage / oc.Garage.Ext.Door-Opened' is switched On And ( From Sunset - 1 hour To Sunrise (next day) ) Then Set 'Deck / sc.Deck.Lights' On Else - No Actions - (To add one, press 'Action') Questions: Why is the time designation ignored in the first program for the Garage Ext Door? Why is the second program completely ignoring the time designation? Am I not understanding the time rules with ISY?

The only issues I've had with GE switches was I had the LED's go out on two different switches. Coming from z-wave now to Insteon I prefer the touch/feel of the Insteon switches over the GE switches. The Zooz switches have a nicer touch I think and more options at a cheaper cost and I never had a problem quality wise with them. The HomeSeer switches are excellent with lots of features but higher price tag as well. Innovelli has a new switch in development and they look to have some decent stuff. I have not used/tested anything from them other than speaking with them about their offerings.

Yes that is a nice setup with Home Assistant. I'm very used to using Z-Seer with HomeSeer for Z-Wave so I was interested to see if there was another tool or something someone was using for ISY Z-Wave diagnostics. Yes... There's very little rhyme or reason as to how a route is selected. Even when using a tool to manually set the route it can change to something unexpected on the next network heal.

Generally all powered z-wave devices act as repeaters. Curious are you running the z-wave with the ISY? If so what are you using to view the routing and network information with ISY?

I'm actually finding a lot of this useful. I'm new to the Insteon world so this is interesting. I find no issues with debating the technologies as I have found that each have their own strength/weakness and this type of back and forth often brings out hidden gems.

Hamburger, cheeseburger but I want a Hot Dog! With Onions....