larryllix

I didn't think the ecobee remote sensors send a battery voltage. My stats just report no response from a sensor when the battery gets too low. That indicates to me it's just a time out lack of response.

Either way you will likely have purchase the USB to microIDE adapter. I did this to upgrade my polisy and I can't believe how easy it was. The adapter was about $11 CAD and came in 2 days from Amazon without Prime. The hardest part was taking the screws out of the case and putting them back in again. Sent from my SM-S711W using Tapatalk

The difference is "status" vs "control" verbage. "Switched" is a bit of an assumption by users now.

If your polisy BIOS is too old things may not update and brick the polisy. @Michel Kohanim gave me a link to a USB/micro -IDE programmer on amazon. I removed the SSD inside the polisy and ran the programmer with image he supplied and my polisy came right up. Then I updated to the latest version and I was back in business. IIRC the USB/microIDE programmer adapter was about $11 CAD. Contact UDI support, and open a ticket. They will help you through it pronto.

Remove the system and give a rebate. We have seen this before and it usually doesn't result in a happy ending.

No screenshots. Right click on the program title in the program tree and select "copy to clipboard" Then paste it into a code box in your post. '<>' All the details will be there and the format much clearer.

Just enter the admin console and click "upgrade" on the rightmost tab. Then open your java setup app under "Control Panel" in Windows, and delete all java files (three check boxes) Re-install Iox Finder https://isy.universal-devices.com/start.jnlp Execute the start.jnlp file it installs in your computer. It will install a further link with a nice UDI avatar in it. Move to your favourite launch position. When executed it should automatically find your polisy, or eISY. If not manually install your device URL into to and show it the way. Note:java will likely complain about installing a new version. Do it.

First time for this one.

I own two polisys and two ISY994s. The ISY994s won't do what I want without a RPi as a bridging unit to talk to my WiFi bulbs so I upgraded to a polisy. The polisy contains my own software and works quite well. I run v5.8.0 and AFAIK the polisy and Eisy are equivalent to each other, as far as firmware goes, for home automation things. If you have a polisy, I would stick with that for the next few years unless you see some clear reason to upgrade for some reason. If your ISY994 does the job, for the same logic, keep it working. Get a few more years out of it.

I have owned many routers over the years and not one ever had a separate area for static IP assignments. I use many static IP address but, they are always fixed within the routers LAN assigned area and made static by using the router's DHCP reservation table. I have experienced way too many IP address collisions over the years, and the results are not always obvious because your router is not aware of them. Collisions can plague your system for months before finding them with random unrelated devices acting strangely. It's your only option with ISY devices now.

Static IP addresses need to be assigned by your router's DHCP reservation table to avoid potential massive LAN problems. UD and followers got tired of newbies constantly messing up their LANs and it was eventually disabled in ISY boxes Sent from my SM-G781W using Tapatalk

ewwww... cloud dependence ? Sent from my SM-G781W using Tapatalk

I am only a very seldom user of ISY mobile and only use it on vacation out of the country mostly. I have used some graphic gui interfaces on other softwares and prefer less gui for so many devices, over the visual scanning over tiny icons and trying to remember what they are supposed to be with their 16x16 bit graphic blurs. The other option would be graphic displays of rooms with icons strewn around the picture. Text lists of objects with real words that describe objects work much better for me. Maybe 4K monitors or phone screens are not enough as I haven't ever carried a magnifying glass, yet. Coming from am 8 bit and text environment I find the mobile app very worktable, not fancy but I have no idea how one would improve the idea...4 directional scrolling to look for that temperature sensor? Sent from my SM-G781W using Tapatalk

I have heard many claims regarding Java running under a unix workalike but nobody ever seems to know how to make it actually work. Sent from my SM-G781W using Tapatalk

Copy and paste your program into a post here using admin console so others may see something. Sent from my SM-G781W using Tapatalk

Do you have a condition in your folder?

WoL is an option inside the Win low level setup and could be disabled. Also, as I was informed here, when polISY/eISY was newer and didn't support WoL, some devices use a different command protocol than the older WoL style that ISY uses.

Looks like more of the same problem. You have changed platforms and the names of the programs have not been arsed into the proper links to make your system work. As per @paulbates in the other thread. Try editing each program and saving it. Don't forget to hit the "save" button after. IIRC you must edit the program before saving it or the ISY AI may assume it isn't required. This is the problem I was attempting relay in my last post. Internal linking inside ISY is done by numeric location, not names. Programs don't run other programs by their names, but rather by their numeric location. When moving ISY contents to another platform, the problems, I had, were due to not "recompiling" the system and expecting it to work with everything scrambled into new locations.

Be very careful and aware that links inside ISY are based on the numeric location of items such as programs, variables, and networking module elements, etc..., and not their names. If you have deleted a program and reinstalled it the reference number will likely be different and things like ISY Portal/ Alexa/GH connections will not work anymore. They do not work by names.

I do not use any looping timer programs without as many as four times each day that restart each program. In addition they all use the [Run at Startup] to restart them upon power failures or reboots. DST time changes have been argued about here for almost a decade. There are many different types of cases where no one algorithm is not going to work. I really doubt a complete solution will ever be offered. Any X minute loop programs will never execute any logic between 2:00 AM and 3:00 AM when the clocks move forward, be totally confused, and cannot offer a solution, that pleases all cases, when every minute between 2:00 AM to 2:59 AM occurs twice during the same night. It would seem the only solution for automation programs using loop timing is to stop the governments from changing the clocks twice per year.

@Geddy I think you hit the head on the nail there. There is no such ISY syntax as And ( switchB is on or switchC is on ) It seems like the OP is using multiple "Switched on " logic statements, dependent on each other, which can never be both true at the same time. Again ACTUAL PROGRAM NEEDED

One thing I did a lot of work on was "Intelligent Setback" during heating. After having many different brands and models I have discovered that no thermostat has that feature. I experimented with a lot of algorithms to accomplish this but none were really perfect. The calculation of times based on outside weather and inside temperatures got out of hand for ISY calculations, and screwed up occasionally. Later I went to a multiple stage system where ISY would use distinct weather points to pick one stage that determined the setback time. Next, I discovered that playing with temperatures was too complicated and required to many "what-ifs" in the programming so I settled on using climates in the ecobee stats, and ISY just picked one at the smartest time. That proved to be the safest method as I had a few run-aways with ISY controlling temperatures and, using preset climates eliminated that risk factor. However, there were severe limits in my previous home. It was so efficient that it needed no heat in the winter if the sun shone and, it had so much thermal mass, heat would be turned on about 2 AM and off at 5 AM to get heat for the next afternoon. Getting it to cool down again for the nights sleep became a problem as turning the heat off at 3 PM caused us to be too cool to watch TV, at nights, but still too warm to sleep at 11 PM. Of course, multiple zones and stats don't ease the complexities of it all. But along came a solution...moved to an apartment with one ecobee and now try to reject the pressurised building air, they love to run at the sweating temperatures. Open a window and you create a relief where all the building heat/pressure exits through your unit. I run a window A/C all winter despite sub freezing temperatures now and it competes with my 2-3 gallon a day humidifier. Am I crazy yet? I check the door peephole for white coats every day.

I have a drop in MagicHome RGB/RGBW/RGBCW bulb and strip controller software that can be dropped into EISY and almost eliminates any popcorn effects on groups up to 10 devices. It takes some doing to get it setup up but scenes can be created inside ISY programming on-the-fly. No previous setup required. MagicHome/LEDenet devices are WiFi and some are dual BT and come with an included remote. I have a dozen of them in drawers now. LOL Anybody interested PM me.

I think if you investigate further you will find that the ecobee thermostats can do all that without any outside interventions. There are sync options with multiple options to synchronise built in, including fan cycling periods, vacation modes, climate selections etc.. etc..

I formerly tried to control my ecobee stats for various things I thought they wouldn't do properly. Later I learned the thermostats are smarter than my ISY and allowed my ecobees to control my ISY and stopped messing with the ecobee smarts. Every time you override the ecobees smarts it upsets their history of response times vs climate settings, and they become confused and have to start accumulating history vs temperature response times again. I have found the vacation modes in my latest ecobee more reliable and easier to set than my ISY programming so I allow the ecobee stat to be the boss and set my ISY modes. I can count on two fingers the number of times I have had to manually override a temperature setting in the last year and a half now. If you want to sync two ecobee stats, just select the sync feature and select which options you want to synchronise and ecobee will do it itself. Sync.stat.vacation - [ID 0093][Parent 005C][Run At Startup] If // Run at Startup enabled 'Living Room / Ecobee.stat - LivRm' Climate Type is Vacation Then $sHouse.vacation = $cTRUE $sHouse.armed = $cTRUE Else $sHouse.vacation = $cFALSE $sHouse.armed = $cFALSE