larryllix

Looks like I spoke too soon. Again my main Alexa Show 10" screen started doing the "I don't know how to do that" response like before. This time, only one of the 10 devices did this, while still operating the ISY Portal devices just fine. All others answered "OK". A power cycle of this device seems to have cleared up this outstanding problem unit, for now. However, my "TV Lights" commands, I have been using for over three years now, will not function anymore on any unit now. Thanks amazon....NOT!

Looks like amazon must have discovered their error and corrected their responses to my requests. Now Alexa just answers with the original "OK" again.Howvere my "T V lights" seems to have become a taboo phrase now so I will have to use "television lights" for that function.

Not that I know of but you never know what gets forced on us sometimes. They are really pushing this phony, so-called "AI" guessing, everywhere.

@bmercier I seems amazon has changed something and caused bad response messages. When I vocally operate ISY Portal device I get back a verbal message "I don't know how to do that". My polISY programs still seemed to still be triggered, most of the times though. Nothing has changed at this end. I now tried to "Discover devices" with nothing new found several times. I have changed some Text in the ISY Portal for "T V lights" to "Tee Vee Lights", same thing happens using the "television lights" verbage command On/Off. This seems to be all some change at amazon's end, or some lack of feedback from ISY Portal to Amazon. Most commands still work but most or all, retort the "I don't know how to do that" error response. All my programs are listed as "switches" to avoid t constant asking "are these are lights?". I use On/Off commands via ISY Portal only. Mostly a heads up. Anybody else experiencing this new problem with Alexa commands?

How can you know the DHCP option is greyed out if you cannot get to the administrative console?

I would doubt the minimum freeBSD O/S likely incorporated into eISY would have USB drivers for this, but who knows?

The adapters are dirt cheap and work well. https://www.amazon.ca/dp/B07VP2WH73?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_3

I don't think the format is readable on the SSD by Windows after imaging the SSD. OUCH!

If your PLM is working well so far, I wouldn't replace it. There were too many with weak power supplies inside in between times. However if your link count is high and you plan to expand you may want to get a more modern USB type PLM. You may want to expand more devices that are not Insteon and then the link capabilty would be sufficient to keep. Getting a new USB type may be a good backup plan also. It sounds like you have a very quiet grid supply but with moving or electrical noisy neighbours moving close to you, you may want to accelerate your backup plans.

STATE is a type of variable found under the Tab STATE at the top of the IoX screen. STATE variables can trigger programs to run while INTEGER variables do not. Most users signify the usage of STATE variables by putting a lowercase "s" at the beginning of the name to avoid confusion in programs later. eg: $sVariableName

Which Great lake were you in?

After my polls SSD crashed and my polisy was rebuilt from the ground up, the F vs C nomenclature still remains on the remote sensors only. The master stat reading shows as C. All values are fine, just the unit scales are incorrect on the Remote sensors in IoX.

Another method. This is based on no direct (Insteon) connection between MS and light control switch. If there is there is more complex way of accomplishing this by disabling the ISY Insteon scene. If switcLinc is switched FAST OFF AND switchLinc is NOT switched FAST ON Then Variable $sDisable.MS = 1 Wait 5 minutes <---- if desired to auto cancel disable. If not, make it hours long Variable $sDisable.MS = 0 Else Variable $sDisable.MS = 0 If MS is switch On AND $sDisable.MS = 0 Then turn on your lights etc. Else -----

Website reports server down since about 3:00 PM today and multiple resolutions promised but still down at 19:25 Not your NS or ISY!! https://status.ecobee.com/#

I recently changed my router ISP / factory set IP address lease time, from 3 days down to 12 hours. Perhaps that resolved mine earlier, on it's own.