ISY Insteon 3.0.0.54 - Beta 54 for HS3

[bpwwer]

I can't tell which it is. For example, I have sunrise/sunset programs that are supposed to brighten/dim the backlight LEDs on KPLs and SwitchLincs. But too often I've found the LEDs un-dimmed at night, and me or my wife have to drape a towel over the LEDs so we can sleep! (Bad WAF!) This happened on the KPL like 4 nights out of 7 a few weeks ago. I even put in duplicate programs that dim the same lights, but five minutes apart. And that didn't fix it either. So, I'm thinking the KPL is sometimes not very good at accepting a "dim" command.

That sounds more like either noise or some type of signal sucker that's effects the communication. The ISY does keep a log of what it does so the first step would be to check that and see if it really did send out the commands. Is there something else that could happen at that time for example 4 out of 7 nights we're running the dishwasher before we go to bed.

You could set up a test program that just sits in a loop dimming and brightening those LED's and watch them for a bit.

Finding and solving Insteon communication issues is a pain.

I don't consider the event trigger/action method on the HS (or the equivalent on the ISY), to be a real programming language. So what language are you talking about? I make my living programming in C, Visual Basic, or occasionally Perl. (I noticed the property sheets in HsTouch look a lot like those in VB! ) It sounds like you use some language in VS/.net to program the plugins, but that's different than control logic.

I use C# for the plug-ins. HS does allow for vb/vbscripts (or at least it did for HS2) to be run as the trigger action. I haven't really played with HS3 to see what's different. There's a whole subforum here dedicated to scripting with HS3 HS3 Scripting

[CJVann]

CONFIG_CHANGE

My speaker client continuously fills with 'configuration change' notices, and then stops responding / speaking. I noticed the HS log has a lot of ISYInsteon CONFIG_CHANGEs, and I'm wondering if they're related? It seems the speaker client is logging the change first, about 59 seconds prior to the ISYInsteon log entry (both HS3 & Speaker are on the same computer, so the time stamps should be in sync.) I also filed a Bugzilla report with HS on this issue back on HS 3.0.0.206. Are these Speaker Client and or ISYInsteon messages normal?

HS3 3.0.0.208
ISY FW 5.0.2

HS3 Log:
Nov-21 9:54:30 AM Error Sending command to Speaker Client, command 10:Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.Propaga teIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Mess ageData& msgData, Int32 type) at HomeSeerAPI.IFromSpeaker.VRChanged() at Scheduler.clsREMSpeech.c28885f19fb02830d8cfe472bd98e8d98()
Nov-21 9:51:03 AM Error Sending command to Speaker Client, command 10:Object reference not set to an instance of an object.-> at System.Runtime.Remoting.Messaging.LogicalCallContext.Propaga teIncomingHeadersToCallContext(IMessage msg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Mess ageData& msgData, Int32 type) at HomeSeerAPI.IFromSpeaker.VRChanged() at Scheduler.clsREMSpeech.c28885f19fb02830d8cfe472bd98e8d98()


There is also this 'unknown element' entry at startup, but that's surely to be expected since we're in Beta:

Nov-21 9:56:00 AM ISYInsteon CONFIG_CHANGE: Events Saved type = 1 ddd = 0 dac = 0
Nov-21 9:55:40 AM ISYInsteon RESTQueryVariables : ISY variable configuration query found unknown element prec
Nov-21 9:55:40 AM ISYInsteon RESTQueryVariables : ISY variable configuration query found unknown element prec
Nov-21 9:55:40 AM ISYInsteon RESTQueryVariables : ISY variable configuration query found unknown element prec
Nov-21 9:55:40 AM ISYInsteon RESTQueryVariables : ISY variable configuration query found unknown element prec
Nov-21 9:55:40 AM ISYInsteon RESTQueryVariables : ISY variable configuration query found unknown element prec
Nov-21 9:55:40 AM ISYInsteon RESTQueryVariables : ISY variable configuration query found unknown element prec
Nov-21 9:55:40 AM ISYInsteon RESTQueryVariables : ISY variable configuration query found unknown element prec
Nov-21 9:55:40 AM ISYInsteon RESTQueryVariables : ISY variable configuration query found unknown element prec
Nov-21 9:55:40 AM ISYInsteon RESTQueryVariables : ISY variable configuration query found unknown element prec
Nov-21 9:55:40 AM ISYInsteon RESTQueryVariables : ISY variable configuration query found unknown element prec
Nov-21 9:55:40 AM ISYInsteon RESTQueryVariables : ISY variable configuration query found unknown element prec
Nov-21 9:55:40 AM ISYInsteon RESTQueryVariables : ISY variable configuration query found unknown element prec
Nov-21 9:55:40 AM ISYInsteon RESTQueryVariables : ISY variable configuration query found unknown element prec
Nov-21 9:55:22 AM Startup Loading configuration file ...
Nov-21 9:51:00 AM ISYInsteon CONFIG_CHANGE: Events Saved type = 1 ddd = 0 dac = 0

[bpwwer]

My speaker client continuously fills with 'configuration change' notices, and then stops responding / speaking. I noticed the HS log has a lot of ISYInsteon CONFIG_CHANGEs, and I'm wondering if they're related? It seems the speaker client is logging the change first, about 59 seconds prior to the ISYInsteon log entry (both HS3 & Speaker are on the same computer, so the time stamps should be in sync.) I also filed a Bugzilla report with HS on this issue back on HS 3.0.0.206. Are these Speaker Client and or ISYInsteon messages normal?

Normal, well, sort of. The ISY plug-in does register to receive events from HS. The only one it cares about is the configuration changed event and only specific types of configuration changes. It's looking for changes to the event triggers so that it can keep it's internal trigger information up-to-date. You should only see the ISY messages when you edit the event triggers. The message is a debug message that I left on while working on this.

One interesting note is that the configuration change event for triggers has a field for delete/add/change. That's the 'dac' value printed in the message. it should be 1, 2, or 3. I'm not sure what a zero there means.

I would assume the speaker client also registers for events but how it handles them is going to be completely independent of how the ISY plug-in handles them. There shouldn't be any interaction between the two relative to the events.

These events are HS -> client, the clients respond but aren't the ones sending out the events. That is the HS core program.

[quote]
There is also this 'unknown element' entry at startup, but that's surely to be expected since we're in Beta:
[/quote
Yeah, I've seen that too. UDI added some fields and the plug-in doesn't parse them yet. It's a harmless message, mostly there to remind me to update the plug-in's parser.

[CJVann]

ISY program status (true/false) <> HS3 Status

Thank you. Another question for you. HS's status for ISY programs doesn't always agree with the ISY... maybe you can help me figure out what's happening? For the Elk sensor status, I created a program for each to return a true if secure, false if tripped. Eg:

Carbon Monoxide - [ID 0075][Parent 0050][Run At Startup]
If
Elk Zone 'Carbon Monoxide' is Normal
And Elk Zone 'Carbon Monoxide' is not Violated

Then
- No Actions - (To add one, press 'Action')

Else
- No Actions - (To add one, press 'Action')

This program is True, but HS3 is reporting it's False. I've tried restarting HS3 many times, it never syncs up with the ISY. As you see, ISY reports all Elk Sensor Status programs = True, but HS reports some of them are false. I manually ran the Fire program's "IF" from the ISY, and HS then updated from False to the expected True value, to match the ISY.
Note: The ISY's Elk module reports all zones are "Normal".

[CJVann]

Variable graphics are erased.

I set a variable's value based on furnace mode. I've added the associated status for each value (0=Idle, 1=Fan, 2=Heating, 3=Cooling) and the associated graphic for each. However, every time I restart HS3, the status & graphics pairs are deleted. If I remember correctly, at one time this was happening with other devices (Door status = Open or Closed, for example) and you were able to resolve it. Can you take a look at this sometime? Thanks!

[bpwwer]

Thank you. Another question for you. HS's status for ISY programs doesn't always agree with the ISY... maybe you can help me figure out what's happening? For the Elk sensor status, I created a program for each to return a true if secure, false if tripped.

This program is True, but HS3 is reporting it's False. I've tried restarting HS3 many times, it never syncs up with the ISY. As you see, ISY reports all Elk Sensor Status programs = True, but HS reports some of them are false. I manually ran the Fire program's "IF" from the ISY, and HS then updated from False to the expected True value, to match the ISY.

I've tried to reproduce this but can't. My programs seem to stay in sync with the ISY. I've tried changing the program status while HS is off and when it restarts, it picks up the new value of the program fine.

If you turn on debug output, the plug-in will output what it's setting the internal status value for each program as one of the first things it does. You'll see messages like:

setting program <name> to 21

21 means true and 31 means false so you can see if it's getting the right value from the ISY. That may help pin-point where things go wrong.

I set a variable's value based on furnace mode. I've added the associated status for each value (0=Idle, 1=Fan, 2=Heating, 3=Cooling) and the associated graphic for each. However, every time I restart HS3, the status & graphics pairs are deleted. If I remember correctly, at one time this was happening with other devices (Door status = Open or Closed, for example) and you were able to resolve it. Can you take a look at this sometime? Thanks!

Yeah, I can remove the clearing of the status/graphics pairs from variables, that's easy.

[CJVann]

I'm seeing a trend, and wonder if the ISY is not sending the program status to you for programs that the ISY has never previously run. The programs that have previously run match the ISY's program status. The programs that don't normally run and likely have never run (Fire, Carbon Monoxide, glass break security violation) do not match the ISY's program status (All show "False" is HS, but "True" in the ISY).

I manually ran the fire program in the ISY Admin Console, and HS3 updated its status to match the ISY. I then tripped the Carbon Monoxide and Glass Break sensors and HS3 now matches those ISY programs (All are now True after alarms stopped).

I found one more instance of this - I recently added HVAC status programs to indicate if HVAC is running: idle, fan, heating, or cooling. The AC has not been on since I added these programs, and I see in the log file that the plugin skips setting the program status for 'cooling'.

Before I tripped the carbon monoxide & glass sensors, I restarted HS3 with debug mode and filtered the log 3 times. 1) "Setting" 2)"Carbon Monoxide" 3) "Glass Break". Each word of interest is highlight in red font:

Truncated to just the entries for Security Sensors, and HVAC:
Nov-28 10:38:40 AM ISYInsteon GetAllD2DStatus : Setting Sync LR Speakers to 21
Nov-28 10:38:40 AM ISYInsteon GetAllD2DStatus : Setting Back Door to 21
Nov-28 10:38:40 AM ISYInsteon GetAllD2DStatus : Setting Front Door to 21
Nov-28 10:38:40 AM ISYInsteon GetAllD2DStatus : Setting Fire to 21
Nov-28 10:38:40 AM ISYInsteon GetAllD2DStatus : Setting Foyer Garage Door to 21
Nov-28 10:38:40 AM ISYInsteon GetAllD2DStatus : Setting Indoor Motion to 21 ... it skips setting the Glass Break & Carbon Monoxide program status ...
Nov-28 10:38:40 AM ISYInsteon GetAllD2DStatus : Setting Set HVAC = Heating to 31
Nov-28 10:38:40 AM ISYInsteon GetAllD2DStatus : Setting Set HVAC = Idle to 21
Nov-28 10:38:40 AM ISYInsteon GetAllD2DStatus : Setting Set HVAC = Fan to 31 ... it skips setting the HVAC = Cooling program status ...


Carbon Monoxide Log Entries:
Nov-28 10:38:42 AM ISYInsteon ValidateDevices : Updating HomeSeer device Carbon Monoxide
Nov-28 10:38:40 AM ISYInsteon GetAllD2D : Adding Carbon Monoxide / P117
Nov-28 10:38:40 AM ISYInsteon QueryD2D : 352A9029.DE751ISY Programs02Radio Cycle834200648003031702DON255531702DOF011Toggle Toilet (Man)107 43 91 1=ST052062DON2557 43 91 1DOF019Automated Lighting15Gabby's Bedtime86840007020086399431043DOF037Bedtime Lights OFF1920IS1397All Bath Lights OFF1012 47 78 1=DFOF7 43 91 1=DFOF40117DFOF16Gabby's Nightly Lights ON8-18006840032 91 9D 1=ST2551B 5B BA 1DON2553Lights Off again1012 47 78 1=ST012 4778 1=DOF1110Bathroom Light Progs19Toggle Shower (Man)1012 5C 5 1=ST012 5C 5 1DON25512 5C 5 1DOF012Gar Door(s) Open3617 D6 84 1=DOF17 D5 F6 1=DOF20659BEEP20659BEEP13MS Low Battery7614 2D E1 3=ST255IS023EQ114Toilet Off again107 43 91 1=ST07 43 91 1=DOF94Flags (Conditional)18Gabby's Programs117Gabby's Daytime Lights ON814 2D E1 2=ST255342006810032 91 9D 1=ST2551B 5B BA 1DON25518Gabby's Daytime Lights OFF814 2D E1 2=ST034200702001B 5B BA 1DOF06Daytime43600021Gabby's All OFF81B 5B BA 2=DOF50214DON1B 5B BA 1BEEP128009DOF020Sleep time40342003923Den Xmas Controller2517 FC 55 1=ST017 FC 55 1=DOF2422Water Timer81ADD=1INIT24Den Xmas Toggle2527 31 B5 1=ST027 31 B5 1DON27 31 B5 1DOF025Holiday Lights1IS115Low Light Detected414 2D E1 2=ST25514 2D E1 2!=ST053082DON53082DOF027LR.FL Progs129If Low2728 2A C7 2=ST6341012DON28If Off2728 2A C7 2=ST014119DOF038Automate - Set Flag9219 44 24 3=DON19 44 24 3=DFON19 44 24 3!=DOF19 44 24 3!=DFOFINIT0EQ0INIT1EQ126MS Failed Dark Detect761582800242Accent Lights OFF19382061517278DOF041Accent Lights ON19IS120153517278DON39All Lights OFF1930276DOF015691Quiet - Set Flag9219 44 24 4=DON19 44 24 4=DFON19 44 24 4!=DOF19 44 24 4!=DFOFINIT1EQ1INIT0EQ030Automate - Toggle Flag92XOR=135Nighttime400153082DON25563Basement Wet7321 78 84 2=ST25561226540Holiday-Indoor ON25A 36 8B 4=DON138967DON43Porch Lt off/off2512 41 11 1=ST012 41 11 1=DOF4444Toggle Out Hol2521 72 C2 1=ST021408DON25521408DOF045Holiday Outdoor OFF25IS1A 36 8B 5=DOF21408DOF046Cnt ISY Uptime Hrs341ADD=147Food Timer815ADD=1INITEQ-1INIT48Food Timer Start81B 5B BA 6=DONLT01B 5B BA 1BEEP14750Cnt Porch Motion3414 2D E1 1=DONADD=1INIT49Cnt Porch Motion RESET340EQ0INIT051* Query ALL191080000:21:b9:00:fc:ecST52Water Timer Reset81B 5B BA 5=DOF1B 5B BA 1BEEP1EQ-1INIT-12253Water Timer LED8GT2932875DON25532875DOF054Food Timer LED8GT1559129DON25559129DOF055Food Timer Stop81B 5B BA 6=DOFGT-14756Holiday Lights - OFF19IS133844DOF057Gar Door(s) Close3617 D6 84 1=DON17 D5 F6 1=DON20659BEEP58Gar 1 Status3617 D6 84 1=ST054402DON54402DOF059Gar 2 Status3617 D5 F6 1=ST053663DON53663DOF060Gar Door Open7317 D6 84 1=ST017 D5 F6 1=ST0618176061Home: Entry Lt ON6211IS100112 68 98 1=ST012 68 98 1DON15362ELK Programs164Basement Dry7321 78 84 1=ST25561236565Gar Light and Door109512IS223IS11048666Set Occupied True10832IS1512IS4512IS5EQ1693 Notify If Open7231IS117 D6 84 1=ST017 D5 F6 1=ST0468*Gar Open Away7217 D6 84 1=ST017 D5 F6 1=ST023IS111367Gar Door Open Stay7532IS117 D6 84 1=ST017 D5 F6 1=ST0253191146312470Barn Open Away/Stay7532IS123IS111 B7 7F 1=ST25525386146312471Garage Nightlight ON36512IS222 F4 98 1=ST017 D6 84 1=ST25517 D5 F6 1=ST25522 F4 98 1DON14072Gar Door(s) Open6273Elk Keypad Messages6274Garage Nightlight OFF36510IS222 F4 98 1=ST14022 F4 98 1DOF022 F4 98 1ST75Elk Speech6233FLOOD BETA OFF621001008730877Mailbox at Dark623511 BD 72 1=DOF12 41 11 1DFON12 41 11 1DFOF12 41 11 1DFON3232675DON78Radio OFF After Hrs87560025200125 CB 83 1=ST25525 CB 83 1DOF079Deck Light1913 E8 0 1=DON33 33 33 3=ST033 33 33 3!=DON25458DFON3225458DON100Sunset190IS1765DON82Check Armed Status8522 F4 98 3=DON22 F4 98 3=DOF22 F4 98 3=DFON22 F4 98 3=DFOF22 F4 98 3=BRT22 F4 98 3=DIM22 F4 98 4=DON22 F4 98 4=DOF22 F4 98 4=DFON22 F4 98 4=DFOF22 F4 98 4=BRT22 F4 98 4=DIM19 44 24 6=DON19 44 24 6=DOF19 44 24 6=DFON19 44 24 6=DFOF19 44 24 6=BRT19 44 24 6=DIM848383Set if Disarmed8530IS114171DON84Set if Armed8531IS132IS133IS134IS135IS136IS135461DON85Set Armed Status LEDs6286OpenGar1 if Closed10917 D6 84 1=ST25517 D6 84 2DON87Welcome Home6211IS188ISY Sync LEDs132FLOOD BETA ON6225 B8 68 2=DON21 78 84 2=DON5387179101Sunrise190765DOF034Counters136Garage176Email Notifications189Holiday-Indoor OFF25IS1A 36 8B 4=DOF138967DOF090Quiet - Toggle Flag92XOR=131Automate - Set LEDs92IS137368DOF037368DON92House Modes193Quiet - Set LEDs92IS163073DON63073DOF094Porch Light By Motion1914 2D E1 1=DONIS13512 41 11 1DFON352583DOF095Kitchen Sink Light1910 3 50 4=DOF10 3 50 1DON4396If Med2728 2A C7 2=ST19137776DON97If High2728 2A C7 2=ST2557728DON99Closet Lt Timer10698Away -Entry Light1908280031IS11020777DON2020777DOF01580Elk Sensor Status6281ALL Off3622 F4 98 7=DON63742DOF0102Holiday Outdoor ON25IS1A 36 8B 5=DON21408DON103Holiday-All OFF25IS122 F4 D8 8=DOF133844DOF0104Gar Light ON10947507DFON4107105Set Occupied False10817 D5 F6 1=ST017 D6 84 1=ST0512IS2512IS1INIT0EQ0106HS-Weather621211IS185107Timer: Gar Light10917 D6 84 1=ST0547507DOF047507DOF0108Occupied62109If Armed and Exit Foyer621122 Flash Gar Light7222 F4 98 1DFON22 F4 98 1DFOF22 F4 98 1DFON22 F4 98 1DFOF22 F4 98 1DFON22 F4 98 1DFOF22 F4 98 1DFOF110LR Speakers8822 F4 D8 7=DON22 F4 D8 7!=DOFC 4 D3 1DOF0C 4 D3 1DON111Away Lights Off6231IS163742DOF01131 Start Door Timer7217 D6 84 1=ST017 D5 F6 1=ST041123017 D6 84 1ST1517 D5 F6 1ST1569114Sync LR Speakers88C 4 D3 1=ST255C 4 D3 1!=ST018252DOF018252DON115Back Door80510IS3512ISNOT3116Front Door80510IS1512ISNOT1117Carbon Monoxide80510IS7512ISNOT7118Fire80510IS8512ISNOT8119Foyer Garage Door80510IS2512ISNOT2120Glass Break80510IS6512ISNOT6121Indoor Motion80510IS4512ISNOT4510IS5512ISNOT5122Set HVAC = Heating126IS1EQ2123Set HVAC = Cooling126IS1EQ3124Set HVAC = Idle126IS0IS0IS0EQ0INIT0126HVAC1125Set HVAC = Fan126IS1EQ1


Glass Break Log Entries:
Nov-28 10:38:45 AM ISYInsteon ValidateDevices : Updating HomeSeer device Glass Break
Nov-28 10:38:40 AM ISYInsteon GetAllD2D : Adding Glass Break / P120 Nov-28 10:38:40 AM ISYInsteon QueryD2D : 352A9029.DE751ISY Programs02Radio Cycle834200648003031702DON255531702DOF011Toggle Toilet (Man)107 43 91 1=ST052062DON2557 43 91 1DOF019Automated Lighting15Gabby's Bedtime86840007020086399431043DOF037Bedtime Lights OFF1920IS1397All Bath Lights OFF1012 47 78 1=DFOF7 43 91 1=DFOF40117DFOF16Gabby's Nightly Lights ON8-18006840032 91 9D 1=ST2551B 5B BA 1DON2553Lights Off again1012 47 78 1=ST012 47 78 1=DOF1110Bathroom Light Progs19Toggle Shower (Man)1012 5C 5 1=ST012 5C 5 1DON25512 5C 5 1DOF012Gar Door(s) Open3617 D6 841=DOF17 D5 F6 1=DOF20659BEEP20659BEEP13MS Low Battery7614 2D E1 3=ST255IS023EQ114Toilet Off again107 43 91 1=ST07 43 91 1=DOF94Flags (Conditional)18Gabby's Programs117Gabby's Daytime Lights ON814 2D E1 2=ST255342006810032 91 9D 1=ST2551B 5B BA 1DON25518Gabby's Daytime Lights OFF814 2D E1 2=ST034200702001B 5B BA 1DOF06Daytime43600021Gabby's All OFF81B 5B BA 2=DOF50214DON1B 5B BA 1BEEP128009DOF020Sleep time40342003923Den Xmas Controller2517 FC 55 1=ST017 FC 55 1=DOF2422Water Timer81ADD=1INIT24Den Xmas Toggle2527 31 B5 1=ST027 31 B5 1DON27 31 B5 1DOF025Holiday Lights1IS115Low Light Detected414 2D E1 2=ST25514 2D E1 2!=ST053082DON53082DOF027LR.FL Progs129If Low2728 2A C7 2=ST6341012DON28If Off2728 2A C7 2=ST014119DOF038Automate - Set Flag9219 44 24 3=DON19 44 24 3=DFON19 44 24 3!=DOF19 44 24 3!=DFOFINIT0EQ0INIT1EQ126MS Failed Dark Detect761582800242Accent Lights OFF19382061517278DOF041Accent Lights ON19IS120153517278DON39All Lights OFF1930276DOF015691Quiet - Set Flag9219 44 24 4=DON19 44 24 4=DFON19 44 24 4!=DOF19 44 24 4!=DFOFINIT1EQ1INIT0EQ030Automate - Toggle Flag92XOR=135Nighttime400153082DON25563Basement Wet7321 78 84 2=ST25561226540Holiday-Indoor ON25A 36 8B 4=DON138967DON43Porch Lt off/off2512 41 11 1=ST012 41 11 1=DOF4444Toggle Out Hol2521 72 C2 1=ST021408DON25521408DOF045Holiday Outdoor OFF25IS1A 36 8B 5=DOF21408DOF046Cnt ISY Uptime Hrs341ADD=147Food Timer815ADD=1INITEQ-1INIT48Food Timer Start81B 5B BA 6=DONLT01B 5B BA 1BEEP14750Cnt Porch Motion3414 2D E1 1=DONADD=1INIT49Cnt Porch Motion RESET340EQ0INIT051* Query ALL191080000:21:b9:00:fc:ecST52Water Timer Reset81B 5B BA 5=DOF1B 5B BA 1BEEP1EQ-1INIT-12253Water Timer LED8GT2932875DON25532875DOF054Food Timer LED8GT1559129DON25559129DOF055Food Timer Stop81B 5B BA 6=DOFGT-14756Holiday Lights - OFF19IS133844DOF057Gar Door(s) Close3617 D6 84 1=DON17 D5 F6 1=DON20659BEEP58Gar 1 Status3617 D6 84 1=ST054402DON54402DOF059Gar 2 Status3617 D5 F6 1=ST053663DON53663DOF060Gar Door Open7317 D6 84 1=ST017 D5 F6 1=ST0618176061Home: Entry Lt ON6211IS100112 68 98 1=ST012 68 98 1DON15362ELK Programs164Basement Dry7321 78 84 1=ST25561236565Gar Light and Door109512IS223IS11048666Set Occupied True10832IS1512IS4512IS5EQ1693 Notify If Open7231IS117 D6 84 1=ST017 D5 F6 1=ST0468*Gar Open Away7217 D6 84 1=ST017 D5 F6 1=ST023IS111367Gar Door Open Stay7532IS117 D6 84 1=ST017 D5 F6 1=ST0253191146312470Barn Open Away/Stay7532IS123IS111 B7 7F 1=ST25525386146312471Garage Nightlight ON36512IS222 F4 98 1=ST017 D6 84 1=ST25517 D5 F6 1=ST25522 F4 98 1DON14072Gar Door(s) Open6273Elk Keypad Messages6274Garage Nightlight OFF36510IS222 F4 98 1=ST14022 F4 98 1DOF022 F4 98 1ST75Elk Speech6233FLOOD BETA OFF621001008730877Mailbox at Dark623511 BD 72 1=DOF12 41 11 1DFON12 41 11 1DFOF12 41 11 1DFON3232675DON78Radio OFF After Hrs87560025200125 CB 83 1=ST25525 CB 83 1DOF079Deck Light1913 E8 0 1=DON33 33 33 3=ST033 33 33 3!=DON25458DFON3225458DON100Sunset190IS1765DON82Check Armed Status8522 F4 98 3=DON22 F4 98 3=DOF22 F4 98 3=DFON22 F4 98 3=DFOF22 F4 98 3=BRT22 F4 98 3=DIM22 F4 98 4=DON22 F4 98 4=DOF22 F4 98 4=DFON22 F4 98 4=DFOF22 F4 98 4=BRT22 F4 98 4=DIM19 44 24 6=DON19 44 24 6=DOF19 44 24 6=DFON19 44 24 6=DFOF19 44 24 6=BRT19 44 24 6=DIM848383Set if Disarmed8530IS114171DON84Set if Armed8531IS132IS133IS134IS135IS136IS135461DON85Set Armed Status LEDs6286OpenGar1 if Closed10917 D6 84 1=ST25517 D6 84 2DON87Welcome Home6211IS188ISY Sync LEDs132FLOOD BETA ON6225 B8 68 2=DON21 78 84 2=DON5387179101Sunrise190765DOF034Counters136Garage176Email Notifications189Holiday-Indoor OFF25IS1A 36 8B 4=DOF138967DOF090Quiet - Toggle Flag92XOR=131Automate - Set LEDs92IS137368DOF037368DON92House Modes193Quiet - Set LEDs92IS163073DON63073DOF094Porch Light By Motion1914 2D E1 1=DONIS13512 41 11 1DFON352583DOF095Kitchen Sink Light1910 3 50 4=DOF10 3 50 1DON4396If Med2728 2A C7 2=ST19137776DON97If High2728 2A C7 2=ST2557728DON99Closet Lt Timer10698Away -Entry Light1908280031IS11020777DON2020777DOF01580Elk Sensor Status6281ALL Off3622 F4 98 7=DON63742DOF0102Holiday Outdoor ON25IS1A 36 8B 5=DON21408DON103Holiday-All OFF25IS122 F4 D8 8=DOF133844DOF0104Gar Light ON10947507DFON4107105Set Occupied False10817 D5 F6 1=ST017 D6 84 1=ST0512IS2512IS1INIT0EQ0106HS-Weather621211IS185107Timer: Gar Light10917 D6 84 1=ST0547507DOF047507DOF0108Occupied62109If Armed and Exit Foyer621122 Flash Gar Light7222 F4 98 1DFON22 F4 98 1DFOF22 F4 98 1DFON22 F4 98 1DFOF22 F4 98 1DFON22 F4 98 1DFOF22 F4 98 1DFOF110LR Speakers8822 F4 D8 7=DON22 F4 D8 7!=DOFC 4 D3 1DOF0C 4 D3 1DON111Away Lights Off6231IS163742DOF01131 Start Door Timer7217 D6 84 1=ST017 D5 F6 1=ST041123017 D6 84 1ST1517 D5 F6 1ST1569114Sync LR Speakers88C 4 D3 1=ST255C 4 D3 1!=ST018252DOF018252DON115Back Door80510IS3512ISNOT3116Front Door80510IS1512ISNOT1117Carbon Monoxide80510IS7512ISNOT7118Fire80510IS8512ISNOT8119Foyer Garage Door80510IS2512ISNOT2120Glass Break80510IS6512ISNOT6121Indoor Motion80510IS4512ISNOT4510IS5512ISNOT5122Set HVAC = Heating126IS1EQ2123Set HVAC = Cooling126IS1EQ3124Set HVAC = Idle126IS0IS0IS0EQ0INIT0126HVAC1125Set HVAC = Fan126IS1EQ1
3 log entries, displaying


After Tripping Carbon Monoxide & Glass Break sensors...I restarted HS3 and now the plugin is setting those program statuses:

Nov-28 12:20:17 PM ISYInsteon GetAllD2DStatus : Setting Back Door to 21
Nov-28 12:20:17 PM ISYInsteon GetAllD2DStatus : Setting Front Door to 21
Nov-28 12:20:17 PM ISYInsteon GetAllD2DStatus : Setting Carbon Monoxide to 21
Nov-28 12:20:17 PM ISYInsteon GetAllD2DStatus : Setting Fire to 21
Nov-28 12:20:17 PM ISYInsteon GetAllD2DStatus : Setting Foyer Garage Door to 21
Nov-28 12:20:17 PM ISYInsteon GetAllD2DStatus : Setting Glass Break to 21
Nov-28 12:20:17 PM ISYInsteon GetAllD2DStatus : Setting Indoor Motion to 21
Nov-28 12:20:17 PM ISYInsteon GetAllD2DStatus : Setting Set HVAC = Heating to 31
Nov-28 12:20:17 PM ISYInsteon GetAllD2DStatus : Setting Set HVAC = Idle to 21
Nov-28 12:20:17 PM ISYInsteon GetAllD2DStatus : Setting Set HVAC = Fan to 31 ... Still skips setting the Cooling program's status, as that program has never run ...

[CJVann]

Run (if) -- Running Then

Is it possible that "Run" for ISY programs on the Device Management page is not doing an ISY "Run (if)", but instead an ISY "Run Then"?

I have numerous programs that toggle its status between True & False. When I "Run (if)" from the ISY, HS3 & the ISY both show it's status as toggling between True & False as expected.

If I click "Run" from HS, the result is always "Running True/Then" and then "True". It doesn't seem to ever "Run (if)" or change to False if triggered from HS. Here is the ISY program, and the resulting HS log:

 
 Holiday - Toggle - [ID ####][Parent 005C][Not Enabled]
 If
        $Flg_Holiday is 0
 
Then
        $Flg_Holiday  = 1
        $Flg_Holiday Init To 1
 
Else
        $Flg_Holiday  = 0
        $Flg_Holiday Init To 0
 
Allows HSTouch to toggle the state variable "$Flg_Enable_Holiday_Lights", 
to enable or disable automated holiday lighting.
 DISABLE PROGRAM so it doesn't continuously toggle.

Dec-02 11:35:27 PM ISYInsteon Event Queue is now empty.
Dec-02 11:35:27 PM ISYInsteon ISY is idle.
Dec-02 11:35:27 PM ISYInsteon Add : Event added to queue. Queue size = 1
Dec-02 11:35:27 PM ISYInsteon Event Queue is now empty.
Dec-02 11:35:27 PM ISYInsteon TriggerEventHandler : TRIGGER: Checking all triggers for Holiday - Toggle - ISY_PROGRAM
Dec-02 11:35:27 PM ISYInsteon TriggerEventHandler : TRIGGER: Checking triggers on Holiday - Toggle TriggerList TYPE_PROGRAM
Dec-02 11:35:27 PM ISYInsteon TriggerEventHandler : Reason [program status] Trigger [ISY_PROGRAM] Data [22] instance []
Dec-02 11:35:27 PM ISYInsteon TriggerEventHandler : TRIGGER: ISY Program Trigger ISY Programs/House Modes/Holiday - Toggle 22
Dec-02 11:35:27 PM ISYInsteon TriggerEventHandler : TRIGGER: Checking all triggers for Holiday - Toggle - ISY_PROGRAM
Dec-02 11:35:27 PM ISYInsteon TriggerEventHandler : TRIGGER: Checking triggers on Holiday - Toggle TriggerList TYPE_PROGRAM
Dec-02 11:35:27 PM ISYInsteon TriggerEventHandler : Reason [program started] Trigger [ISY_PROGRAM] Data [22] instance []
Dec-02 11:35:27 PM ISYInsteon TriggerEventHandler : TRIGGER: ISY Program Trigger ISY Programs/House Modes/Holiday - Toggle start
Dec-02 11:35:27 PM ISYInsteon NodeUpdateHandler : Setting program status from 21 to 22
Dec-02 11:35:27 PM ISYInsteon NodeUpdateHandler : Update ISY Programs/House Modes/Holiday - Toggle to Running True
Dec-02 11:35:27 PM ISYInsteon parse_event : control = [_5] action = [0] node = [] eventinfo = []
Dec-02 11:35:27 PM ISYInsteon Command Queue is now empty.
Dec-02 11:35:27 PM ISYInsteon parse_event : Entering parse event with _50
Dec-02 11:35:27 PM ISYInsteon ISY Programs/House Modes/Holiday - Toggle now at 22
Dec-02 11:35:27 PM ISYInsteon Add : Event added to queue. Queue size = 1
Dec-02 11:35:27 PM ISYInsteon parse_event : control = [_1] action = [0] node = [] eventinfo = [7F151202 23:35:28151202 23:34:0322]
Dec-02 11:35:27 PM ISYInsteon parse_event : Entering parse event with _107F151202 23:35:28151202 23:34:0322
Dec-02 11:35:27 PM ISYInsteon Event Queue is now empty.
Dec-02 11:35:27 PM ISYInsteon ISY is busy.
Dec-02 11:35:27 PM ISYInsteon Add : Event added to queue. Queue size = 1
Dec-02 11:35:27 PM ISYInsteon parse_event : control = [_5] action = [1] node = [] eventinfo = []
Dec-02 11:35:27 PM ISYInsteon parse_event : Entering parse event with _51
Dec-02 11:35:27 PM ISYInsteon Authorize : Authorize: encoding = xxx
Dec-02 11:35:27 PM ISYInsteon ProcessCommand : Sending run, to ISY Programs/House Modes/Holiday - Toggle Attempt 0
Dec-02 11:35:27 PM ISYInsteon Add : Command for ISY Programs/House Modes/Holiday - Toggle added to queue. Queue size = 1
Dec-02 11:35:27 PM ISYInsteon SetIOMulti : SetIOMulti set 597 to value -11
Dec-02 11:35:27 PM Device Control Device: ISY Programs House Modes Holiday - Toggle to Run (-11) by/from: CAPI Control Handler
Dec-02 11:35:27 PM ISYInsteon Event Queue is now empty.

[bpwwer]

[COLOR=navy]Is it possible that "Run" for ISY programs on the Device Management page is not doing an ISY "Run (if)", but instead an ISY "Run Then"?

It's possible, but that would be a bug in the ISY. There are three valid commands that can be sent: run, runThen, and runElse. My assumption is that the 'run' command is supposed to do a run(if). Based on a review of the code and your log

ProcessCommand : Sending run, to ISY Programs/House Modes/Holiday - Toggle Attempt 0

the plug-in is sending the 'run' command to the ISY. I'm not able to test right now, but you should be able to do the same thing from the REST interface and a browser. It looks like the program ID is 597 so the rest commands would be:

http://<isy>/rest/programs/597/run
http://<isy>/rest/programs/597/runThen
http://<isy>/rest/programs/597/runElse

The docs also do mention that 'runIf' is supported, but 'run' should be used instead.

[CJVann]

The /rest/programs/xxxx/run works okay, and correctly evaluates the program, whether the IF condition returns a true or a false. The Plugin always returns a true condition for all my programs, however it should also be noted that I am running ISY 5.0.2 beta. Here's another sample program. Below, state variable: $Tmr_Food=-1, so the program should return False:

 
 Food Timer LED - [ID 0036][Parent 0008]
 If
        $Tmr_Food > 15
 
Then
        Set Scene '[SYSTEM CONTROLS] / Status LEDs / Perishable Food LEDs' 100%
 
Else
        Set Scene '[SYSTEM CONTROLS] / Status LEDs / Perishable Food LEDs' Off

This program returns:
- True if run from HS
- False if run from the ISY
- False if run from the Rest interface

If there's anything else you'd like me to try, just let me know! Thank you again...

[bpwwer]

Got some time to test and yes, 'run' and 'runif' are behaving differently when using the WSDL api. 'runif' behaves as expected so I'll change the plug-in to use that.

I did have a bit of scare when I set up my test program and used a state variable for the flag. It created a nice infinite loop once it started running. Took a while to get the program disabled as the admin console kept crashing and the html interface was taking forever to respond.

[CJVann]

Got some time to test and yes, 'run' and 'runif' are behaving differently when using the WSDL api. 'runif' behaves as expected so I'll change the plug-in to use that.

I did have a bit of scare when I set up my test program and used a state variable for the flag. It created a nice infinite loop once it started running. Took a while to get the program disabled as the admin console kept crashing and the html interface was taking forever to respond.

Great - thank you! And ... sorry about the infinite loop - ha.

[bpwwer]

Version 3.0.0.23 posted. This should fix the 'run' / 'runif' so that it really does evaluate the if condition and run the appropriate section of the program.

[Riverhawk]

Can light scenes have dimming capabilities in HsTouch?

I'm new so I don't know if my terminology is correct. All my devices are found and functional in homeseer. In my master bedroom I have a switch that actually controls the light load. I created a virtual 3-way switch on the other side of the room with another dimmer. I then created a scene such that when either switch is dimmed, the other paddle knows/displays the current lighting level on the dimmer.

Using HsTouch, I wanted to clean up/hide duplicate entries that control the lighting(the actual load bearing dimmer, the connected 3-way, and the scene for them).

Here's my issue...I have to remove the two individual dimmer entries since using either one on HsTouch doesn't change the state of the other dimmer since it doesn't use the connecting scene. Well, using the scene, I can't seem to dim the lights. Only on or off. I tried to enter a range/slider on the scene entry in homeseer, but I couldn't get it to work. What else can I try to use a scene that correctly disperses light status to all connected dimmers and still be able to dim? Thanks.

[bpwwer]

I'm new so I don't know if my terminology is correct. All my devices are found and functional in homeseer. In my master bedroom I have a switch that actually controls the light load. I created a virtual 3-way switch on the other side of the room with another dimmer. I then created a scene such that when either switch is dimmed, the other paddle knows/displays the current lighting level on the dimmer.

Using HsTouch, I wanted to clean up/hide duplicate entries that control the lighting(the actual load bearing dimmer, the connected 3-way, and the scene for them).

Here's my issue...I have to remove the two individual dimmer entries since using either one on HsTouch doesn't change the state of the other dimmer since it doesn't use the connecting scene. Well, using the scene, I can't seem to dim the lights. Only on or off. I tried to enter a range/slider on the scene entry in homeseer, but I couldn't get it to work. What else can I try to use a scene that correctly disperses light status to all connected dimmers and still be able to dim? Thanks.

Hi Riverhawk,

You have the terminology right and are really close with what you've done. Scenes can be dimmed, but unlike an individual device, they don't have specific brightness values. Since a scene can be composed of different types of devices and those devices can have different on-levels there isn't any way for the Insteon protocol to consolidate those into a single value.

For example, if you have a living room scene that controls 3 lights.

light 1 - A non-dimmable light hooked up to a relay switch
light 2 - A ceiling light that has it's on-level in the scene set to level 128
light 3 - A table lamp that has it's on-level in the scene set to 255

What is the current scene level? The Insteon protocol defines the brightness levels to go from 0 - 255.

You can send a dim or bright command to the scene, which will send the dim or bright command to each individual device. In the scene above, sending a dim command will probably cause light 1 to shut off and the other lights will dim by a small amount. You can keep sending dim commands until all lights are off.

So for HStouch, you need to use dim and bright buttons for your scene, not a slider.