larryllix

Are we almost there yet? [emoji2] Sent from my SM-S711W using Tapatalk

I am on 5.8.xx also. Me thinks that is the O/S version of FreeBSD.

More retries doesn't mean they will take effect every communication attempt. Retries only take effect when a device doesn't get and ACK back, showing successful communication transmission from the receiving device. Most communication packets do not take any retries unless you have bad comms, having interference on your power lines or RF noise in your air. Note that "Retries" are not "Echoes" that Insteon does between devices, to support it's mesh featured protocol structure.

Use the Restore for each device in the admin console. Insteon devices can lose one channel of comm upon being volt jolted.

Christmas and New Years breaks. That is unusual from my experiences.

I had to use the UD mobile app to enable the Portal connection again. The mobile app now contains enables that defaulted to disabled. https://forum.universal-devices.com/topic/44358-geographic-location-restrictions/#comment-388687

Also should be noted that part of the WiFi spec for 5GHz is that it shares frequencies with aeronautical radar and anytime a 5GHz router sees any radar usage it is required to shut down immediately and change frequencies. This only applies to the middle half-dozen channels or so (IIRC). This can cause you hiccoughs in data streaming. Most devices will never show this up to the user but some are sensitive to it. If you are near any airport or in a flight path, choose your 5GHz band channels carefully and possibly consider disabling auto-selection by locking your router onto one the unshared channels.

A month or so back I did a sync in the newer UDMobile app and it disabled my Alexa connection from inside the mobile app. It took me a week to stumble onto enable switches for every function and re-enable them again.

I have a polISY Pro. IIRC it includes the NR module with Pro. I remember I could pass values back and forth each direction. For some time I was using my ISY for sensing and detection and my polISY to send all the commands. It got to a pint where I had to commit to the new hardware and abandon the ISY due to complications and needin two PLMs if I continued.

I did this while moving over from my ISY994 to my polISY. For each parameter, write a program and Netwrok Resource, to detect and trigger each Network resource (on ISY994) that sends the value into a variable using the target's (eISY or polISY) REST interface. Once you have done one parameter (trigger program, and NR) the rest are just copies with the target variable changed. The speed is amazing. It will appear native to the target machine.

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.

I had years of minor troubles with my Champain GDO causing Insteon interference. However it was minor and I always thought it would be my PV inverter system. Years later I installed another GDO system with a battery backup inside and my Insteon comms went to about 10% successful, even though it was further away. After unplugging one and then the other I ordered two Insteon FilterLincs and it solved my Insteon noise problems. It wasn't the motors, but rather their cheap power supplies. When the motors ran it didn't bother the Insteon comms, only the power supplies plugged in.

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