ase

NP. I had to do that with both polisys I have.

This is a date issue with in BSD itself. This is an issue with BSD date time. You need to set the date and time in BSD. Certs are date time sensitive. You need to ssh into the unit. run the sudo date yyyymmddhh so if I were to set the time now I would run it as sudo date 202112100314

I wanted to call it what he "understood" it to be. Different objective. If a person only understands a mug to be a cup and you want to explain something about a mug to them you call it a cup so they understand. Again what we "say" is important. Sorry you can't catch me up in a logical conundrum buddy. One post is pointed at solving a person's problem and using their "terminology" so that they understand, the other post is to point out that if he understood the terminology that the group uses the miscommunication wouldn't happen. I was pointing out the fact that terminology in any method is user sensitive. Hence why communication seems simple and yet people take 7 year college courses on it. My point was that words are how we think. You would be hard pressed to find a non-tech understands the term "firmware" yet to the highly technical most of what is called firmware isn't even firmware. There is not only a gap between non-tech users and technical users but between their experience level and their background. Then to top it off we have ubiquitous language that is used incorrectly or technical terms that become ubiquitous. Look at the term Xerox, it comes from Xerographic. Xerox itself wasn't a word until the company comes about. I don't think to many people have ever asked their assistant to go make a xerographic. Kodak, another non-word. Yet if I tell you to take a picture with a kodak, and Xerox it, you know what I mean. UDI is actually quite good with technical terms, unfortunately the terms used within this industry are not singular in definition nor are they ubiquitous it the public "zeitgeist". Many of the terms come from different sources and are either technical in their own right or BS marketing jargon.

I like most of what you said, except what we call it matters. If you don't think terminology matters, just watch the show air disasters. Communication is the key, and is often a huge problem. I will take you statement from above as an example. "Once fully operational, users will not need the Isy to manage and control devices since polisy will be able to do the same thing." Stop and think about how that is phrased for just a second. Are you saying ISY the hardware won't be needed or ISY the Software won't be needed. Those are two totally different statements with the very same words, depending on what the person reading them understands. I mean if we want to get technical ISY has never been hardware, the ISY994i Hardware is actually a custom board with NXP's Coldfire Chip. Firmware Technically is a low level SOFTWARE that controls the chips themselves. So technically speaking ISY has never been a Firmware from the strictest sense of the word, it has alway been a program the runs on top of some OS. I have no Idea which OS was used with the Coldfire chips. So again depending on the knowledge of the reader a statement like we see here could mean something very different. Coming from 25+ years in computers, with and in depth understanding of Linux and BSD, having worked in many programing languages and having been on the hardware integration side as well. I am going to see things very different from someone who has little background in these things and is just trying to control some lights and a sprinkler system from their phone. What I am getting at here, is language is the single most important aspect. Miscommunication is at the heart of most of the worlds big disasters. Language is how we think and therefore how we act.

Didn't want to further confuse the poor guy, so I wanted him to differentiate polisy hardware from the software, he said he didn't understand Node and so on.

ISY is not a box, it is a program. 994i is the box. ISY is currently defaulted to install on the Polisy Hardware(which is just a PC from PCengines). Polisy hardware runs FreeBSD as an OS, Polisy the program runs on top of that OS the same as ISY does. At the OS level both programs are unaware of each other. Polisy(the software) is just a connection point for NON-Insteon and NON-Zwave hardware to communicate with ISY. ISY is still the "Brain" that orchestrates the automation. Since the two programs are unaware of each other on the OS they still operate as if separate(different hardware). For Polyisy and ISY to communicate with each other Polisy(program) Needs to find the ISY, if being run on Polisy(hardware) it will just be the IP address and port 8080 with the username and password for the ISY(program) Now PolyGlots are just small scripts that allow Polyisy to communicate with those other services or hardware(Tesla, Roomba, NOAA, and so on).

If you haven't cleared the cache, you can use pkg file in /var/cache/pkg to restore isy back to 5.1.1. You will need to uninstall isy 5.2.0 with sudo pkg delete isy (this will remove all configuration so you need to have a backup of isy if you don't have a backup, use sftp to copy /var/isy/FILES/CONF) then reinstall isy from cached pkg in /var/cache/pkg. sudo pkg install isy-5.1.1_7.pkg. I had both build 7 and 5, I reinstalled 7.

I used http on 8080 and https on 8443. That is the correct ports for the proper protocols. NMAP scan showed that isy was not listening on either port. Once the unit was downgraded back to isy-5.1.1_7 and backup files placed back into /var/isy/FILES/CONF/ and a restart, it listened and functioned perfectly. Upgrading once again caused unit to stop listening again, restored works again. So it is obvious that there is an issue with ISY-5.2.0_52.

Downgraded back to isy-5.1.1_7 restored backup and everything works. Reinstalled isy-5.2.0_52 and it doesn't listen on either 8080 or 8843 again.

I just run pkg upgrade and it upgraded ISY to 5.2.0 however now ISY is does not appear to be listening on any port. I can still access via portal and UD mobile.

Here is a walk thru on how to use SSH on a mac. https://www.servermania.com/kb/articles/ssh-mac/ Follow instructions