simplextech

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....

The Phase Coupler link is great. I was looking at SmartHome but the hard wired one they used to carry is now discontinued? Or maybe just out of stock for a long time?

I have also thought about a NodeServer for Lutron. The Caseta Pro, RA2 Select and RA2 share the same integration interface which makes the development easier to support the primary systems. I've not worked with a QS system but I believe it still shares the same interface.

I see the same trouble with every system.... hmm...

Here are the programs. Why is this turning Off when people are in the Kitchen and moving around? Configuration: MSII - On-Only linked to a KPL 6 button Kitchen.Lights-State - [ID 002B][Parent 0018] If 'Kitchen / Motion Sensor / Kitchen.1 Motion' is switched On Then $Kitchen_Motion_State = 1 Wait 5 minutes $Kitchen_Motion_State = 0 Else - No Actions - (To add one, press 'Action') Kitchen Lights - Off - [ID 0011][Parent 0018] If $Kitchen_Motion_State is 0 Then Wait 5 minutes Set 'Kitchen / KPL6 / Kitchen.KPL6.1' Off Else - No Actions - (To add one, press 'Action') People can be in the Kitchen and moving around and the lights turn off.... ???

If you have the Z-Wave board there's the GE Heavy Duty relay and the Aeotec Heavy Duty relay: https://www.amazon.com/GE-Appliance-Required-Works-SmartThings-14285/dp/B00YTCZZF0/ref=asc_df_B00YTCZZF0/?tag=hyprod-20&linkCode=df0&hvadid=216539147262&hvpos=1o3&hvnetw=g&hvrand=4831132666293138423&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9009165&hvtargid=pla-351536326275&psc=1 https://www.amazon.com/Aeotec-Security-controller-electricity-consumption/dp/B00MBIRF5W I have no experience with either but I have thought of getting the Aeotec for a 240V wall heater... I still might.

I don't know. Let me go open one and find out. EDIT: No jumpers No Options either...

Thanks for the scene clarification. I think UDI needs to remove the "on level" adjustment when a "scene" is selected in the program. It leads to this type of topic Starting to get my head around the Insteon world now a little better. I get it that scenes are binary unless adjusted which I do with another scene actually. I was hoping that since there was that 'on option' in the program window it would maybe do something, but I guess not.

Thanks. That clarifies that. So in a program to adjust a scene I either have to adjust the scene 'on level' or adjust a single device member in the 3/4/5 way setup correct? The only annoyance with this is I then have to adjust each scene member for the LED's to reflect the correct level.

Please tell me what is wrong with this and why it does not work. Hallway.Lights-OverNight - [ID 003A][Parent 001E] If From 10:30:00PM To Sunrise (next day) Then Set 'Hallway / Scene / Hallway 3-Way' On 10% Else - No Actions - (To add one, press 'Action')

I should have clarified I sent the info to UDI support

I sent in a fairly decent diagnostic of the Fibaro to support. I hope support for it will improve. From what I gather UDI is doing some fairly large changes in how they are addressing/handling z-wave devices to make adding support easier/faster. I'm hoping that change comes soon but I expect it will be another firmware release to incorporate the changes.

I'm trying to figure this one out as well... anyone know? I've also submitted a request to SmartHome about the Luminance reading updates. On USB power I can query an MSII and it updates. On Battery it's a hit or miss as in sometimes it will query fine and then sometimes nothing or I get an error. Here's the current response I've received about teh Luminance reporting:

@kclenden thanks for this. It was very much what I was looking for. I do something similar with modifying the scene for a motion sensor. Thanks also for testing against a battery device as that saved me another trip to the forum (even though I sit here a lot) I was trying the scene modification methods and was seeing if I could just change something in the scene to modify the off node the open/close sensor creates in the ISY and no luck there either. It seems I'll have to continue with the use of a program and accept the delay. In timing it's not horrible as it's just to turn on the lights when going out on the deck. But when just stepping out to grab some wood for the fire it's nice for the lights to be on.