larryllix

Watching on the news. This is a terrible fire, spreading faster than they can control the outbreaks. The aerial view shows continuous tree outbreaks while we watch it working it's way to Hollywood Blvd.

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.

I use the WiFi 6 for my devices that need/use the higher speeds and arbitration it offers. When I attempted to use the wireless back channel for router connections I had nothing but problems with my 5 different ASUS routers trying to create a 3 router mesh. It definitely slows down data rates echoing data. Hardwired was the only way they seemed to work properly but then ASUS still had problems with disallowing some devices to patch through to the Internet frequently. A few of the routers worked better after being factory repaired. Cooling fans and vertical mounting also helped a lot when high data rates were encountered. My single Netgear Nighhawk router always worked more reliably in my 3800 sq.ft. home, and had better reach for it's signals, than the crippled strength signal mesh setup. I had to disable all the smart switching as many devices would not tolerate changing APs. It wasn't a good thing for devices that ever physically move or if the router logic thought a better AP would be better and switched the AP for that device.

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.