larryllix

I discovered the ISY mobile app added disables to the Alexa / portal account connection and it defaulted to disabled. Look in the mobile app and see if it needs to be re-enabled. Sent from my SM-S711W using Tapatalk

Therecl are small devices that wire into octagon boxes that provide enough current to accomplish this. AFAICT they are most capacitors inside do there is no heat generated due to their leading power factor not having any Watts. Sent from my SM-S711W using Tapatalk

You're spoiled by high level language tools. ISY language takes much more creativity to debug complex programming constructs but it can and has been done. Sent from my SM-S711W using Tapatalk

It seems the non-nuetral devices have all disappeared since low current light bulbs have appeared on the market. The low draw and distorted waveforms have made it next to impossible to create enough energy to support a decent rf transmission for most protocols without a neutral wire. Sent from my SM-S711W using Tapatalk

BTW: ISY arithmetic has logical operators in its repertoire. IIRC there is AND, OR, and XOR.

One the techniques I used for a while was to trigger Else, just to make the indicators more useful. If a trigger is switched On Then . . . . do a bunch of stuff ......Wait 2 seconds so I can see the green flash ..... Run 'This Program (Else)' Else ..... must be empty or just turning off the same devices.

Yeah, and we have reprinted our 2,487 page manual but 287 items have changed and it is out of date now. Its a different world now. Not like the good ol' days.

...and the admin console has changed in many ways. . . . . "Please listen carefully to the menu options as they may have changed recently".

Are you clicking the "SAVE" button each time you make a change before closing the Admin Console?

My Polisy and previous ISY994 remembers the last directory path I used. I am using Win 11 on two different machines. I think the path is remebered by ISY device from the last backup done. After program or other changes a pop-up on closing would be a nice feature.

Likely a tight loop somewhere in your ISY program code. Do a search for that device in the admin console and examine each program that contains that device. These can be tough to find if you are using complex logic that may involve more than one program that interact.

The X10 devices will still require a phase coupler to get signals across the legs of a 120/240 v grid system. I ran a dual system fr a few years but found that some Wait 1-2 seconds were required to allow some signals to dissipate their ACKs before sending the other protocol. I am not sure whether it was after Insteon signals or after X10 signals, now. Although Insteon has anti-clash detection for it's own signals included, the two did not play together all that well on the same PLM. They can co-reside OK but some Waits had to be inserted to stop clashing in certain places.

No gibberish but just another poor attempt at AI (guessing) what was asked in lieu of knowing about any devices. It was a very weird experience. I had to install an Insteon wall switch, which I wanted to do some day anyway, that gave me Fast On/Off, Dim up/down, and third tap capabilities to even control my lights via ISY program logic and wizardry. Dependent? Definitely with mostly all WiFi lighting. I had no idea until now.

I discovered a new switch in the ISY mobile app that enables/disables the account permission. This seems to have coincided with my using "Sync" with my polISY in the mobile app. It seems it installed defaulted to disable. I am guessing the "geographical restrictions" was a generic message applied in lieu of more detailed error reports, as programmers tend to do, until the fine polish is put on their programs. After allowing the mobile app to allow permission the accounts connected again and all devices seem to be working fine after a "Discover" via Alexa. Thanks.

Paul is referring to the Insteon device, not the PLM. Every Insteon device should be factory reset before connecting to the EISY via PLM. It avoids a lot of troubles later on. After factory resetting an Insteon device you can use "Restore" to refresh all the links already set up in EISY or if not installed yet, install it as new. Right click on the device in the device tree to see options.

@LeeG I had the idea he may have wrote the low level code to I/F with the PLM. He knew the Insteon codes too well. He was our guru and we miss him.

It's an AI clone!

Just for the confusion that may happen here. The thread subject matter shifted to order of operations of program lines. I think we killed the order of operations of programs, again.

This is still an issue (next day). I tried some of the old tricks, including resetting every device's location, removing the apartment number, to comply with the suggested location address, changing the country to US, etc.. Skill still is not allowed to be enabled "due to geographic restrictions". This also happened years ago, when the skill was first being developed, but has worked without problems for many years, until yesterday again. Based on the sudden nonsense answers Alexa gave us for most device control attempts, this appears to be an amazon bug, so far. Contact with them has been unfruitful, so far.

@bmercier My Alexa speakers suddenly have started to spout nonsense to me. When asked to turn on all lights, it responds with I don't have any spaghetti. This seem to be only ISY relate topics. After many trials to repair this I finally unlinked the ISY Portal account from Alexa and when I attempted to reconnect it it tells me I am not allowed to enable the skill due to geographic restrictions. I have gone through the setup of all my Alexa speakers and standardised my location exactly the same. Any ideas?

Yes, I remember the conversation about order of execution a year or so back, and after some testing I found to be nonsense on my system.

You are only editing the IoX copy of the programs so the changes need to be installed into the ISY machine. Now I am beginning to wonder if the method of updating variable names and values has had the same logic applied to them, where you now need to save them also. That wasn't the case a few versions ago but you may not find them in the pulldown menus of the program editing page.

Each element that can cause triggers likely has a list/stack of other elements to check should the value change. There is no looping required. IIRC, spread sheets did this looping for value changes. Of course there may be a background looping algorithm, as we know the code exist anyway, for power up conditions, where there are no triggers happen to update the database.

I think the IoX Launcher must fire out a generic "are you out there" packet and any ISY machine is supposed to answer. Sometimes the router isn't ready on time. I had a lot of problems with fast power blinks where equipment would see the power blink and re-initialise but the router would not, and not ask for any equipment to report in, for registration in the DHCP table.

Agreed, but the Else redirect is required if a Control On off is present in the If section. This avoids further program usage to permit [Run at Startup] to function since, as you above logic, a Control X condition will never be true unless that event called the evaluation. Run at Startup would always evaluate False and run Else, and not start any looping program lines.