larryllix

It is not ISY in particlar. I know eprom manufacturers have worked to avoid this problem and technology has advanced. I still hear conflicting reports about this over the years. I try to avoid it when unnecessary.

Been awhile, but I figured I wouldn't need them to be 'init to'ed. I had those lines installed for one but figured out I wouldn't need it and would avoid wear and tear o the eprom memory. However, just looking at it again, despite startup running the program, the counter would be 0, and Occupied would be set False until some event happened again. A function of this importance may warrant the 'wear and tear'. I need to re-exam this. Thanks for the nudge.

For this example I will use my occupancy timer system. Initiator methods Starting the timer process can be done from any program by simply saving the number of minutes you want the timer to timeout into a single state variable. Each device involved sets my occupancy timer to an appropriate time based on the location and probability another MS will reset the timer variable again before the timer time out. I have at least 12 MS devices as well as other devices that initiate this. Motion.Libr - [ID 0019][Parent 000B] If 'Library / Motion.Libr' is switched On <---- MS trigger Then $sMS.Motion.room = $cROOM.LIBRARY <--------------- all rooms are defined by preset constant numbers (not relavent here) Wait 2 seconds <-------- this is so the admin console shows the colour change for debugging (not relavent here) $sHouse.occupied.timer = 120 <-------------------------- initiates programable timer Else - No Actions - (To add one, press 'Action') This is an example using my security system. Note 1 minute is used so the programs will trigger properly to set the occupancy flag to False. Occupied Cancel by arming - [ID 0018][Parent 000B] If $sHouse.armed is $cTRUE Then $sHouse.occupied.timer = 1 Else - No Actions - (To add one, press 'Action') Timer Program This program is Enabled at Startup so that it continues after a power cycle. I have allowed for sleeping times when no motion may be detected but we are still home. Timer countdown continues in the morning. This program is automatically triggered by the program examples above. Occupied.countdowner - [ID 0167][Parent 000B][Run At Startup] If $sHouse.occupied.timer > 0 And From 7:00:00AM To 11:00:00PM (same day) Then Wait 1 minute $sHouse.occupied.timer -= 1 Else - No Actions - (To add one, press 'Action') Self retriggering timer. Enabled to run at startup! -If startup occurs ouside wake timeframe, will self start at beginning of timeframe. -If timeframe commences while .timer is 0, first new occupied.timer value will start again. Using the Timer Counter In my case I set and reset a variable to True or False, as other programs throughout my system expect these values. Others may want to turn on lights, or other indicators system, run programs or lighting scenes directly from this program, instead. Occupied.flagger - [ID 0168][Parent 000B] If $sHouse.occupied.timer > 0 Then $sHouse.occupied = $cTRUE <---- preset constant (integer) variables for convenience and clarity Else $sHouse.occupied = $cFALSE Power up assumes home unoccupied! Shouldn't be long to correct that. Program cannot be combined into "Occupied countdowner" program as it's timeframe end would zero occupied.timer

Yes. Each time I changed the style of ISY element is was reported discovered again. However when I only changed the Portal type definition, it did not. My first failure attempt at routines, and seeing the ISY element reported right through to the Alexa app status, tells me this is not a Portal problem but rather something inside the Alexa app server that is not always set up correctly. When I can create a vocal to vocal routine that works just fine and then create another one, a other night that will not work at all, something is flakey with the process or Alexa server. Sent from my SM-G930W8 using Tapatalk

I have now tried this as a state variable (combining the two doors) defined as a contact (tried MS also) with the same result. The Alexa app device status shows Closed/Open correctly, but it does not trigger the Alexa Routine to vocalise the words. Manual invocation of each routine in the app vocalises both OK.

I don't get this. What am I doing wrong. I have quite a few cases now that vary in triggers as well as vocal outputs using Routines. Without ISY Portal A month ago neighbours came over and I tried to impress the tech-snipers with a simple routine. - Trigger by vocal "Who are our neighbours" - Response "XXXX and YYYY are your next door neighbours" I could never get that routine to work despite trying variations of the wording and triggering it from the Alexa app manually successfully every time. Several days later after testing failed again I deleted it. I had installed another Routine with similar funny neighbour named response, getting the same results. Maybe Alexa didn't like some key word???? All other routines worked first time. With ISY Portal Today I set up another two routines to report my garage door was open/closed. I started simple with an IOLinc sensing the garage door was closed = closed contact. Tried changing wording and a few other sleuthing techniques to no avail. - Trigger from Insteon IOLinc sensing input. - ISY portal defined this as a "contact" device, with vocal name "garage door" - Alexa "Discover" was used and reported one new device by name from the speaker. - Operating garage door shows Open/Close status on Alexa app device page "garage door" - Manually triggering either of the two routines (open/closed) operates the speaker of choice, with appropriate wording, as defined by me in the routine response. - A few hours were allowed and tested again, repeatedly. These two routines will not function. I Haven't tried changing the device to a MS or tried an ISY state variable yet (I want to combine two garage door positions into vocal reports, later) What am I doing wrong here? Why does one routine work fine and the next one refuses to function with very similar triggers and responses?

The Tilt/Pan/Zoom webcam with the acid-filled squirt gun connected to the io/Link might. If you are housing very expensive jewellery,k most of this nonsense isn't going to delay a determined high-tech criminal for too long. Most of us aren't and that is what insurance is for. Most defensive techniques only invite a challenge from the neighbourhood juvenile delinquents. It's the painting over spray paint art on your living rooms walls and water damage from the running taps with plugged sink drains, and the incredible violated feeling of some kid across the street eating chocolates from your freezer, for hours, while he browsed your wife's jeweller,y or even worse things he could have been doing while laying on your bed, watching your VHS tapes. Been there...we moved away within a year. Still missing some keepsakes like family war medals. Alarm system warning stickers and making a home look like somebody is still inside is the best defence again the rascals. Make them pick somebody else's house.

The local switch control, ISY program lines and every scene link have their own levels and ramp speeds and do not interact. Sent from my SM-G930W8 using Tapatalk Fade up and down was an old system that would start the ramp and Stop would make it cease dynamically. IMHO those commands are a waste of time with ISY. Good between linked switches though.

If the first line is If 'control door sensor is switched on' Off is not a problem and will not be detected without a line that detects the Off signal. A second program is not required. However if the first line is If 'Status door sensor is on' Off is a problem and a second program is needed as the off would cancel the 'Wait 10 minutes' line (if used all in one program) Sent from my SM-G930W8 using Tapatalk

Different protocols tie up different hardware. Logically, if a trigger comes in on the zwave i/o and goes out on the Insteon port it should be faster. It would be interesting to hear what happens when a loop flashing an Insteon device is running to swamp the Insteon port, and time the same test zwave trigger/ Insteon out. I know one thing The ISY CPU has no lack of horsepower for the measly HA job. Sent from my SM-G930W8 using Tapatalk

You can have a program disable and enable any other program. Programs can disable themselves but not enable themselves. Folders with programs can be enabled and disabled but programs can stop in midstream unfortunately. Sent from my SM-G930W8 using Tapatalk

I have a very long routine that operates at random between midnight and 3 AM when I am in vacation mode. This entails lights to the appearance of getting out of bed, walking the front foyer, looking outside, travelling downstairs through the basement, peering out the basement walkout, and then reversing that stopping at each bedroom with lights on for about 3-4 seconds each. At the end all lights are turn off sequentially back to the last one being the bedroom lamp again. This comes with a warning. In my previous house, I did this appearance of checking the house with an x10 system back in the 1990s. When back from vacation a neighbour told me they had a neighbourhood gathering around my front door that ended up with police attending. Most of them knew we were always away that week each year. It was contemplated to break down our front door to inspect but the police finally told everybody to go home and they would handle it. I never heard any more about it. Sent from my SM-G930W8 using Tapatalk

You're getting there! Nice going! Sent from my SM-G930W8 using Tapatalk

LOL. The more confusion you can create, the faster you can get the kids running out and away.You hear horror stories about spray painted murals and water falls down staircases. You can't stop them from getting in but you can attempt to limit the length of stay. You may want to limit your alarms to about 40 minutes before giving up for false alarms. I use 12 Insteon MSes allowing one random false every ten minutes sending a notification and a second zone triggers the works. I have had many false while away due to headlights? and dying batteries. Sent from my SM-G930W8 using Tapatalk

I do the same for every light and my doorbell for security scare. A scene works more efficiently for this because devices don't Ack back, tying up Insteon comms as much. Sent from my SM-G930W8 using Tapatalk

Yes exactly! Any lines in the Then after a Wait or Repeat line will not get executed. A very common gottcha' I am working from a small screen and its getting difficult keeping things organized here. Confession...I thought there was else lines in his program. Sent from my SM-G930W8 using Tapatalk

You are going to hate this one. When your Tony Rear Door program becomes true the status condition will become false after A5 turns on. Now your If will get re-evaluated to false and Else will run. There are special two program methods of isolating devices when used in the condition of a program that controls the same device. I am on a small screen so leave it to others to follow. Sent from my SM-G930W8 using Tapatalk

You need at least one wait between your fast on/off lines. Your pounding of the Insteon channel will tie up the comm protocol as well as make it almost impossible for your ISY to handle any other requests on the I/O channels. I doubt the v5 made this any worse. The speed of the ISY engine was improved somewhat when v5 was released. Sent from my SM-G930W8 using Tapatalk

Just uniformity. It's another lighting setting, sometimes in a list of 15 or 20 different scenes for a particular room. With ISY Portal I wouldn't have to go looking for which scene contained the off. More modular. I don't have to worry that changing some code will affect another program using the same scene and cause me hours of sleuthing why it stopped working. I don't worry about the 1000 scene limitation. My lighting is starting to weigh more heavily into nonInsteon lighting as colour becomes cheaper than plain white and I avoid scenes unless needed for speed or Insteon data storm avoidance. Sent from my SM-G930W8 using Tapatalk

I like to use a third scene, 'Sconces Off' but to use it you would turn it On causing all the lights to go off. Sent from my SM-G930W8 using Tapatalk

So nothing is much different for the A /V Network Resources except you have created a special vocal library to handle the needed devices allowing us to map a/v vocals to NRs as if they were devices? Sent from my SM-G930W8 using Tapatalk

This compound logic will never be true as two events are never true at the same time. While ISY is processing one the other will not be being processed and false. Time is Sunset And X10 'A5/On (3)' is Received Sent from my SM-G930W8 using Tapatalk

Where are these network resources located? Is this a direct connection between vocals and these network resources avoiding ISY processing ? Sent from my SM-G930W8 using Tapatalk

So Polyglot can be either cloud or independant now. Even more options for ISY users! It never stops growing. Thanks for the correction guys! ISY forever! Sent from my SM-G930W8 using Tapatalk

Polyglot is not in the 'cloud'. Polyglot is a piece of software that runs on another computer, usually an RPi. Your computer and no cloud required. You are independent of other parties.It provides a base software that many code writers have created plug in software to allow your ISY to talk to Ethernet style hardware like stats, and RGB lighting. Nodelink does the same. The ISY Portal is a cloud service that you pay subscription fees for and can bridge your Alexa or google home cloud services through to your ISY and works extremely well. Sent from my SM-G930W8 using Tapatalk