ncoig

Add me to list. Local connection works, two different devices suddenly 404 blocked using an active portal sub. -N

I don't mean to disagree, but I'm trying to do so without being disagreeable! I have an open/close sensor (TriggerLinc v.43) on my pantry door -- I had setup a scene for the light with two members: the light, and the sensor, both as controllers. If I left the door open and turned the light off, the sensor would change status to "off" or "closed" according to ISY. As a result, I removed the light switch and re-added it as a responder only so that I could see from the ISY if the door was actually open or not. Hopefully this helps someone if they happen upon this information. -N

Thank you for the idea - regrettably, this isn't the primary concern -- rather I need to be able to control the load-bearing switch directly, but have it respond as the scene to keep the other indicators on KPL's in sync. Thanks, though! -N

I recently encountered something I couldn't reproduce or explain, figured it may be worth noting. So on restoring the ISY from a backup, I've noted, and in the various materials here have read, that at the end of the restoration, the Console should prompt to restore network settings if they are disparate from that which is stored in the ISY. On the backup of my old house (taken under 4.7.3), a restore does just that. However, I started anew, and have noted that none of my new backups (under 4.7.3, 4.7.5, 4.8, 4.9, or 5.3) ask for that at the end. I have tried this sequence of restoration of both statically set and dynamically configured ISYs, with various firmware versions, and keep coming up with the same thing - the backup I took 18 months ago will prompt for network restoration on any ISY, any firmware, but my recent backup never asks. I've noted the location data doesn't seem to always restore, either... Are there times when parts of backups just aren't taken? -N

...and I should have added that I have come up with this solution, I just don't think it's very elegant... but it does seem to work without adverse effects... Scene UD-Den Fan - [ID 0xxx][Parent 0xxx] If Status 'Den / Den Fan*' is Off Then Set Scene 'Den / Den Fan (MW)' Off Else Set Scene 'Den / Den Fan (MW)' Fade Up Set Scene 'Den / Den Fan (MW)' Fade Down HOWEVER --- this method does not work on lighting that is dimmable, so it's useless for the problem originally posted... -N

Hey All, So we all know that when you have multiple switches, KPL buttons, etc., as members of a scene, and you press any of the members' buttons (assuming all are CONTROLLERS) of the scene, that the remaining members will update with the correct status, whether that be the rocker switches' status bars, or a KPL button light, etc. We also know that if you use the ISY, or Agave, or REST or what have you, to control the load-bearing DEVICE versus the SCENE, the remaining members of the scene will NOT update, and thus not reflect the true/current status of the load being called upon. The solution, of course, is to control the SCENE in the ISY versus the load-controlling switch, which is all well and good, however there are some instances where things like a Lamplinc or other non-updating module can cause issues if controlled locally, or, particularly in my instance, if controlled by Google Home - causing the device to respond appropriately, but the remaining members to not reflect the correct and current status, as outlined above. Yes, you can have Google Home control the SCENE versus the DEVICE, but then the device won't show up on your Google Home Hubs or in the Assistant app as a device at all - just a phantom that you can control by voice, but no other way. (at least in my experience) Real world example and current problem: Among others, I have a Living Room string of 8 can lights on a 5-way circuit, with 4 KPLs all having a single button set to control the load. If I configure in the portal for Google Home to control the SCENE, versus the load-controlling DEVICE, voice commands are fine and all works correctly, but there is no visual presence in the Google Home app or in display devices like the Google Home Hub (now Nest Hub?) that show the device so you can touch versus speak commands. Conversely, if I add it as a singular DEVICE in the portal, it shows (annoyingly in all lower case in abject defiance of my grammatically correct entry, but that's another matter) up in the list, but manipulation of the device doesn't update the scene, so 3 of the four KPLs show the incorrect status. In years past, I simply had an updating program that would watch for status changes and update the KPL every so often, which worked well enough, but in this installation, there are far too many of these instances to be practical, and I feel doing so would be too taxing on the ISY to continually scan for changes, and likely cause sluggishness elsewhere. So has anyone come up with a clever way around this? I can just monitor the status of the switch in a program, and when the status changes from OFF to ON, or vice versa, I can activate the scene or deactivate it, but that kills any dimming control, because activating the scene goes to the pre-determined on rate, which results in, for example, the light turning on to 20% as I ask, then ramping the rest of the way to the scene's set 70%. I can manually program a watch program for each scene, but I was hoping for something that was simpler - and simply querying the scene doesn't update the members as I'd hoped. Any ideas? I searched for this but found nothing on point -- if it's there, kindly point me that way. Regards, -N

Just wanted to thank you for taking the time to do this write-up. I had been using more primitive means (curl) via tasker and while it got the job done, your routines here prove to tickle my inner OCD. It's also helped me to refine my routines for using my smartwatch to control my home, and receive status of modules as well so that I'm not just "toggling" in the dark. Thanks again, -N

Why would this matter ? It's been a while but I had insteon devices before I had my ISY and when I installed that, it discovered existing scenes... -N

They are all state variables.

So I recently tried to pare down my lines of code in the ISY, and combined a few things into single programs versus more. Evidently I should have left it alone, but I need understand the WHY of my failure... I know that if a THEN or ELSE statement contains a WAIT and the conditions change during the WAIT, it changes the evaluation, however, in my simple program, the state doesn't change, the program still shows "TRUE" yet my variable doesn't change and programs dependent on that variable don't fire. WHY? My program: If Elk Area 'The xxx Estate' 'Armed State' is Armed Away Then Wait 8 minutes $House_Occupied = 0 $Night_Mode = 0 Else - No Actions - (To add one, press 'Action') The purpose of this (not that it matters) is because I don't want my HVAC settings going up and down over and over if I leave, then run back up the stairs to get something and have to disarm/arm the system in quick succession, as well as leaving lights on until I'm well gone. -N

I'm not sure I follow -- "previous information"? In any event, here's the Event viewer after my programs runs and tries to set the brightness for 8 Switches: Thu 02/07/2013 07:53:20 PM : [ Time] 19:53:22 0(0) Thu 02/07/2013 07:53:20 PM : [iNST-TX-I1 ] 02 62 14 D7 F1 0F 11 FF Thu 02/07/2013 07:53:21 PM : [iNST-ACK ] 02 62 14.D7.F1 0F 11 FF 06 LTONRR (FF) Thu 02/07/2013 07:53:21 PM : [iNST-SRX ] 02 50 14.D7.F1 12.9F.81 2B 11 FF LTONRR (FF) Thu 02/07/2013 07:53:21 PM : [std-Direct Ack] 14.D7.F1-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 02/07/2013 07:53:23 PM : [ 14 D7 F1 1] ST 255 Thu 02/07/2013 07:53:23 PM : [iNST-TX-I2 ] 02 62 1B 9C B6 1F 2E 00 01 07 37 00 00 00 00 00 00 00 00 00 00 93 Thu 02/07/2013 07:53:23 PM : [iNST-ACK ] 02 62 1B.9C.B6 1F 2E 00 01 07 37 00 00 00 00 00 00 00 00 00 00 93 06 (00) Thu 02/07/2013 07:53:24 PM : [iNST-SRX ] 02 50 1B.9C.B6 12.9F.81 27 2E 00 (00) Thu 02/07/2013 07:53:24 PM : [std-Direct Ack] 1B.9C.B6-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Thu 02/07/2013 07:53:24 PM : [iNST-TX-I2 ] 02 62 1D 35 5A 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C Thu 02/07/2013 07:53:24 PM : [iNST-ACK ] 02 62 1D.35.5A 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C 06 (00) Thu 02/07/2013 07:53:25 PM : [iNST-SRX ] 02 50 1D.35.5A 12.9F.81 2B 2E 00 (00) Thu 02/07/2013 07:53:25 PM : [std-Direct Ack] 1D.35.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 02/07/2013 07:53:25 PM : [iNST-TX-I2 ] 02 62 1D 35 BB 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C Thu 02/07/2013 07:53:25 PM : [iNST-ACK ] 02 62 1D.35.BB 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C 06 (00) Thu 02/07/2013 07:53:26 PM : [iNST-SRX ] 02 50 1D.35.BB 12.9F.81 2B 2E 00 (00) Thu 02/07/2013 07:53:26 PM : [std-Direct Ack] 1D.35.BB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 02/07/2013 07:53:26 PM : [iNST-TX-I2CS] 02 62 1F B6 D5 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C Thu 02/07/2013 07:53:26 PM : [iNST-ACK ] 02 62 1F.B6.D5 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C 06 (00) Thu 02/07/2013 07:53:27 PM : [iNST-SRX ] 02 50 1F.B6.D5 12.9F.81 2B 2E 00 (00) Thu 02/07/2013 07:53:27 PM : [std-Direct Ack] 1F.B6.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 02/07/2013 07:53:27 PM : [iNST-TX-I2CS] 02 62 1F B6 DA 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C Thu 02/07/2013 07:53:27 PM : [iNST-ACK ] 02 62 1F.B6.DA 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C 06 (00) Thu 02/07/2013 07:53:28 PM : [iNST-SRX ] 02 50 1F.B6.DA 12.9F.81 2B 2E 00 (00) Thu 02/07/2013 07:53:28 PM : [std-Direct Ack] 1F.B6.DA-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 02/07/2013 07:53:28 PM : [iNST-TX-I2CS] 02 62 1F BB F7 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C Thu 02/07/2013 07:53:28 PM : [iNST-ACK ] 02 62 1F.BB.F7 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C 06 (00) Thu 02/07/2013 07:53:28 PM : [iNST-SRX ] 02 50 1F.BB.F7 12.9F.81 2B 2E 00 (00) Thu 02/07/2013 07:53:28 PM : [std-Direct Ack] 1F.BB.F7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 02/07/2013 07:53:29 PM : [iNST-TX-I2CS] 02 62 20 42 40 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Thu 02/07/2013 07:53:29 PM : [iNST-ACK ] 02 62 20.42.40 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Thu 02/07/2013 07:53:29 PM : [iNST-SRX ] 02 50 20.42.40 12.9F.81 2B 2F 00 (00) Thu 02/07/2013 07:53:29 PM : [std-Direct Ack] 20.42.40-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 02/07/2013 07:53:30 PM : [iNST-ERX ] 02 51 20 42 40 12 9F 81 11 2F 00 00 01 0F FF 20 A2 17 12 9F 81 FF 1F 06 93 Thu 02/07/2013 07:53:30 PM : [Ext-Direct ] 20.42.40-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Thu 02/07/2013 07:53:30 PM : [iNST-TX-I2CS] 02 62 20 42 40 1F 2E 00 01 07 7F 00 00 00 00 00 00 00 00 00 00 4B Thu 02/07/2013 07:53:30 PM : [iNST-ACK ] 02 62 20.42.40 1F 2E 00 01 07 7F 00 00 00 00 00 00 00 00 00 00 4B 06 (00) Thu 02/07/2013 07:53:30 PM : [iNST-SRX ] 02 50 20.42.40 12.9F.81 2B 2E 00 (00) Thu 02/07/2013 07:53:30 PM : [std-Direct Ack] 20.42.40-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Let me know if you need anything further. Many thanks, Neil

Howdy: So from what I can see the LED brightness setting is somewhat of a mystery. I sought to program something to soften the brightness of these LEDs at night, and bring them back up to full brightness in the morning. Simple enough, but several (new) switches don't seem to want to respond. What I find particularly curious is that the program seems to "know" the difference between those switches that use a % (1-100) and those who use this oddball 15/7 scale for on/off, HOWEVER, when trying to set the brightness on my 2487S v.41 (KPL Relay) the programming suggests it's a value of 1-100; but if I click "LED Brightness" in the interface, I get the "on / off" style of input. Am I missing something? Probably yes, but please do point out my folly! -N