larryllix

@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.

I understand but it was between Alexa and ISY Portal which I had no control over.

I had routers that ran too warm. Vertical mounting resolved all those heat problems. They had vent holes though. Polisy does not. Never seen an eISY.

Thanks. Nothing was offline. ISY Portal showed my ISY as offline but any locale ISY operations, including NR worked 100%. Alexa app showed ISY Skill accounts connected but every device was shown disconnected. It all fixed itself later without any further action from me. Amazon just didn't like us?

Back up again also, polisy Pro.

My SSD on both polISYs crashed a few eeks ago. My main polisy Pro was imaged with an mSATA to USB adapter and came back up fully with a few hours of work, no problem. However my back-up polisy would never come back up despite re-imaging successfully about 6 times UD support predicted it was the SSD and suggested to buy a new one, which was right on the money and the backup polisy is working fine again, Michel made a comment to me that rings in my brain that. cheaper SSD tend to not last long. By cheaper I believe he meant smaller SSD drives as they have a lot less memory area to swap memory into and basically wear out too soon. I bought a 64GB SSD to replace the factory unit but thinking again I would get a much larger SSD because of the previous paragraph I posted. The suggested imager program would not work with the larger drive and I had to download another free imager that worked fine.

@bmercier My polISY cannot be found by Alexa. I have disabled and renabled the accounts successfully as well as using "discover" in Alexa and it find no new devices. However all devices are shown with flags as disconnected now.

The receptacle wasn't a split receptacle like on your kitchen counter or other cooking surface, was it? Bad signal noise creators are small PSU like USB chargers, and Garage door openers have been found to be very bad sometimes. Start un plugging things, especially cheap and old things.

There is some frequency, signal strength and bandwidth adjustments that need to be made on the tags, especially at subzero temperatures. I only interrogate my tags every 30 minutes for general temperature and humidity probing. Also, I do not use the NR, I use a custom written kumoapp to push the readings into polISY State variables.

I found the CAO Tags to have a very long range. I detected the one in my car about half a mile away when my wife was driving home, once. It reconnected and gave me the connected flag. However, I also found that the angle of the tag was critical as my mailbox at the end of the driveway, about 40 feet from the house, and through layers of brick to the far end of the house had to be turned the correct angle. I used one for my garage door position sensing and found when bolted to a metal surface it didn't have a good range either.

I use the CAO Wireless tags and Alexa can interrogate and say their temperatures to 0.001C degrees. The Tags require a new CR2032 battery about every 8-10 months but they can transmit through the metal freezer case to the master receiver in the house easily and reliably.

Will this web server run on PolISY also? UPDATE: Announcement post says no. @bmercierWill polISY run this in the future?

Simplest way is to create STATE variables with meaningful names. Then use ISY Portal to emulate MS devices from each one with 1 value = On , 0 value = Off. Now use Alexa app to create Alaxa Routines using those pseudoMS elements as triggers to do whatever you want Alexa to do. After I defined a group of dedicated STATE variable I created an ISY program that is triggered by any STATE variable becoming a non-zero value and WAIT 10 seconds and then set the whole group of STATE variable back to 0 again. This saves many programs, one for each STATE variable by just writing one program for all. To use: Set $sAlexa.do.whatever to 1 Reset sSay variables - [ID 006F][Parent 0002][Run At Startup] If // [Run at Startup] enabled $sSay.motionOutsideDoor is not 0 Or $sSay.occupancyTimerExpiring is not 0 Or $sSay.securityViolated is not 0 Or $sSay.welcomeHome is not 0 Or $sSay.systemArming is not 0 Or $sSay.systemDisarmed is not 0 Or $sSay.goodBye is not 0 Or $sSay.turnOnLights is not 0 Or $sSay.systemArmed is not 0 Or $sz_40 is not 0 Or $sSay.blindLowBatt is not 0 Or $sSay.blindJammed is not 0 Or $sz_43 is not 0 Or $sz_44 is not 0 Or $sz_45 is not 0 Or $sz_46 is not 0 Or $sz_47 is not 0 Or $sz_48 is not 0 Then Wait 10 seconds $sSay.motionOutsideDoor = 0 $sSay.occupancyTimerExpiring = 0 $sSay.securityViolated = 0 $sSay.welcomeHome = 0 $sSay.systemArming = 0 $sSay.systemDisarmed = 0 $sSay.goodBye = 0 $sSay.turnOnLights = 0 $sSay.systemArmed = 0 $sz_40 = 0 $sSay.blindLowBatt = 0 $sSay.blindJammed = 0 $sz_43 = 0 $sz_44 = 0 $sz_45 = 0 $sz_46 = 0 $sz_47 = 0 $sz_48 = 0 Else - No Actions - (To add one, press 'Action')

On my ecobee thermostats (I have owned three now) there are internal records of thermostat sensors every 15 minutes. These spreadsheets records can be downloaded from the thermostat and show the actual sensor reading in 0.1c degrees, whereas the display and the api sending values are only 0.5c degree resolution. The thermostat face displays the compensated / anticipator resultant temperature the thermostat is regulating the HVAC equipment to. ecobee stats offer a settable on/off differential of down to 0.3c degrees. ecobee stats also insulate the sensor for the electonics heat extremely well with distance, air diversion channels, insulation, and heat reflectors I have had several Honeywell programmable stats and they do the same thing, displaying the compensated temperature and not the sensor actual temperature. The evidence there was to turn the stat to lower heat setpoint and watch the displayed reading drop by 2-3c degrees. Once you consider the 0.5c "looseness" before the stat contacts will close the temperature swings may exceed 4c degrees or about 7-8F degrees in real applications. I have owned a few other top tech stats (in their era) and they did the same thing with readings that didn't reflect the actual sensor temperatures. Venstar T78/900? was another that did the same thing. Nest stats have the same problem. I find homes with Nest stats have waves of heat and periods of cold at times that I cannot tolerate comfortably. The 2441TH Insteon stats do not have this anticipation / prediction so the lowest on/off differential you can get is about 3c degrees plus the time delay for the warm air to enter the casing and change the sensor reading. The resultant temperature swings are way too large for many (myself included) to tolerate. However, IRC, the readings you get via protocol, are the readings you also see on the stat front.