larryllix

Wasn't 2025 one of the dividing lines to determine if the year was 2000-2025 or 1926-1999 depending on the two digit year, above or below the value '25' ? The skill may still have to be enabled again. Alexa cuts off unused connections. AI... you know!

Mine dead also. Ontario Canada

You can calibrate the sensor on the main unit only. I found sensors with varying distances to the wall makes a big difference. Don't place sensors above the stat electronics or you'll get about 3-4F higher readings. Careful with the calibration and repeat after sitting for a few hours keeping in mind the math the stat does on the front face. Use the CSV file reports for more accuracy. The sensors in the main stat are placed at the bottom to eliminate heat influences from the electronics. This is a big problem with many stats where WiFi is a big heat source. The user cannot compensate for it as the manufacturers would like you to believe. Trying to compensate makes the stat sensitive to draughts across the sensor and you will get heat waves from your HVAC system. Yeah, I am very sensitive to 0.5c changes. That is why I am stuck on ecobee stats. I don't like the 3-5F temperature swings built into other brands.

IIRC, those "climates" are spare climates/time segments for custom heat schedules that you can name in your schedule tables on the ecobee stat. I have several custom named schedules like Afternoon, Evening, and Wee Hours, that show up as selectable in my ISY. I might mention that these are safer to use than meddling with the setpoints. They can also eliminate the possibility of programs ramping setpoints to the top or to the bottom in the event of an ISY program logic runaway error. Your stat will not show the actual temperature accurately. The displayed reading will be a result of all your remote sensor's average and possibly the result of a advanced setback or setup compensation. For accurate reading see the downloadable spreadsheet information available in the ecobee webpages. It gives 15 minute updates to every sensor including stat readings and averages to 0.1c resolution accuracies. Stat rounds off to 0.3c. This is why the ecobee stats are so accurate and can operate to such tiny differentials to eliminate heat waves better than most other brands.

Browsers these days are updated every week or so and have so much power now, it would be nice to rid ourselves of another compiler/interpreter base in our systems. After using TinkerCad, browser based 3D CAD design, for a few months, it is hard to believe all that can be done inside a browser now, and with such little delay anywhere. True cloud power! Let e-ISY be (y)our cloud server, right on your own LAN!

Awesome! A long awaited opportunity for the HTML5 people to link into ISY with hundreds of different angles. Let the debugging begin to a more exciting future! Will ISY be the official controller to go to Mars? Let's get Elon on the phone.

This is very common practice in some areas with large multi-unit buildings. It saves on some conductor size. However we used to get complaints from electricians about bulbs popping due to the 125vac on them and heats running at 216vac. Utilities tend to attempt a compromise by running voltage at 125/216vac instead of 120/208vac. The voltage levels are within specs and the 216v is not too bad for 220vac appliances. Cheaper incandescent bulbs never liked it though and after being called, many electrician troubleshooters didn't understand why the 120v was so high. However, since Insteon and X10 signals use the zero crossing of the phase voltage, I am not sure how well passing one phase's signals over to another phase, that is 120 degrees out of phase, could possibly work well.

Did you try reloading IoX? I haven't seen it happen in the last few years but occasionally the admin console would do a screwed up load and programs would be missing or elements missing.

IIRC, In the end of porting from my ISY994 to my polISY, after attempting to copy it over, I just printed out all my programs and re-entered them manually into my new polISY box. However, I had just moved from a larger home to a smaller apartment and my HA needs were much smaller and quite different. I started from scratch using variables for almost all lighting scenes as the operations are much more debuggable, and simpler, to write more complex deviations to the standard trigger on and time off processes.

Be sure to save the IoX finder's url results. It makes it much easier to load them back in later when things get finicky again. Sent from my SM-S711W using Tapatalk

Already wired Ethernet extensions are available and may avoid the switched pair confusion that can happen. Sent from my SM-S711W using Tapatalk

Is your ISY IP address dictated in the DHCP IP address reservation table in your router? This sounds a lot like IP address overlap when people attempt to lock down IP addresses other than their router....sometimes it works and sometimes it doesn't.

IIRC this was an old feature that has since been gone for years and many versions. It is not related to this subject matter anyway.

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.