larryllix

@MWaremanSo far this seems to have worker for an approximate timezone setting. Whether it stays until @Michel Kohanim get it fixed on a more accurate location remains to be seen. You have to know the exact file pathname to your timezone to make the commands work. https://www.itbroker.com/set-the-timezone-in-freebsd/

I have used a few different brands of stats over decades and have to agree that evobee stats have the best features and stability. Compared to others they seem to understand what a thermostat needs to do when it comes to user features and things like multiple scenarios that you don't have to edit every time you switch from heat to a/c and back. User programmable comfort settings up to about ten with dual a/c and heating tables that ISY can switch around easily without ever knowing a single temperature. Accuracy to 0.1 degree but only 0.5 c display. When your temp needs to go under a full degree before it kicks in and you have a big bandwidth between cool and heat that 4 to 5 degree fluctuation can cause a lot of discomfort. User security locks with variable limits. Highly recommended. evobee has their ship together. Two of my sons got into the Nest and after fighting with all their AI fakery they both disabled all that stuff anyway. Sent from my SM-G781W using Tapatalk

Venstar is the only stat that I am aware f that does a local API (application interface). All other are cloud based. However, cloud based is not a real big hurdle as the stat looks after itself and most of the cloud connection is about tweaking the settings, and monitoring to control other devices based on that. All stats require a Node Server as a bridge between ISY and some cloud interface, except for the Insteon stats but I wouldn't trust my system to one of those. I have two and if you don't mind large temperature swings, and overshoot temperatures, upon recovery, on of those could be your easiest. Now I am not sure how well they handle a heat-pump with it's backup heat source handling etc,,

Check the top of your admin console and see if you are located in LA Cal. Sent from my SM-G781W using Tapatalk

No UDI product supports the Insteon Hub AFAIK.

Manual entry is best. I did restore from an ISY backup and got all my programs and variable names in but every single element has to be checked, Insteon devices all reiadded (and then restored to dump old links) and programs re-linked in, variable values endian fixed and NR loaded and resaved. It got my system cloned but about two days work of work. 500 programs, 500 variables.

That term confuses me a lot. I understood NRs were only passive to be called by programs. Does this mean NRs can be self triggering? Sent from my SM-G781W using Tapatalk

No dongle but an internal Zwave card. As I have read here, if you have a green LED sticking out of the case (on back?) you have the 300 version.

V1 is gone V2 is current V3 is coming and requires a polisy.

The 1011 in green indicates the device is online but there is binary data waiting to be written to the device. In Insteon devices this is typically because the device is a battery operated one and the data cannot be written until the device is manually place in Linking mode. I don't know about Zwave but, this is not a bug, but rather a feature of the admin console indicating several factors the user needs to correct or be aware of.

Find the release announcement thread in the forum. Download the correct image, depending on whether you have a PLM connected or not. In your admin console use the pulldown menu Help and select upgrade manually. Backup when indicated and then OK. Sent from my SM-G781W using Tapatalk

El niño? Sent from my SM-G781W using Tapatalk

3. /isy/ is locked permission. I cannot access this file or directory When using sudo, /FILES/ does not exist

The time zone at the top of the admin console changes back to LA Cal. Then program events in the summary tab and variables all show last run / modified based on the LA times.

Grrrrrrrrr..... My timezone, along with sunset and sunrise times, and event times shown for programs and variables just reverted back to LA again.

I have been using variable substitution in the URL portion for years now. My WiFi lights live off them. 4 NRs do my 35 WiFi lights. Trouble is you can only use the same NR with at least one second of Wait between each calling. ISY does the substitution at send time, not at creation time and will use the second variable values for the first NR send. IOW two rapid uses of the same NR may both send the same latest values, not what was asked for.

57 NRs. I only use about half due to NSes, and bulbs styles not used anymore. 498 programs 356 Integer variables 219 state variables Doing it again it would have went much faster. I did a restore from ISY backup. Load every program, NR and store them back again. Each device had to to linked and then a restore removed the old PLM links for each device. Variables had the big endian vs little endian problems. Divide large values by 256^3 and add 256 if negative. I have a about 15 MS 1s and 5 LDs that needed manually linking in high and concealed places. Very time consuming.

I found every NR needed to be loaded into edit mode and then saved again or they just didn't function. It was like polisy just loaded them all but none registered for usage.

I get this most times when I first login. The next logins work fine after inserting my ISY creds. Later the same thing happens again. I will recheck this later and tomorrow to see if it forgets again.

To post a program, right click on it's name in the program tree (list) on the left of the admin console. Select "copy to clipboard" and then paste same into your post.

Some show d.quotations around them and one doesn't.

I think Michel would better suited to figure this out. IIRC he deleted the .env file, uninstalled udx and ISY and then re-installed them, and started them again. It many have involved mongodb also but I cannot remember exactly now.

I had that .env file setup originally for PG1 and when PG2 was released it seemed like some of the definitions actual purposes changed and the git-hub defintions were incorrect. IP addresses and port definitions changed things for more than what was stated. I had my webpage console set to port 80 = no https but it suddenly affected the ISY to polisy connection also. Everything worked except commands from ISY to polyglot. I could never get it to work right again and Michel connected in and deleted ISY and a few other packages and then reinstalled them. Voila! I was off and running again. I have never tried to install an .env file again and just live with the annoying HTTPS browser warnings since.

My settings. I got a not-connected complaint this time. Need settings??

see added .env comment in post above