ase

This is one of the major drawbacks to z-wave. Each manufacturer is free to implement things as they see fit. In order to convert these parameters into readable menu options would require a team of people just inputting the information. This is one of the big reasons why I believe in documentation of everything. Once you get out of the Insteon only realm things can get very tricky, very quickly. You really need to plan out ahead and have an idea of the technical aspects before you even buy. This is very much at odds with the buy an Insteon device and just know it will work. My advice to UDI would be to harness this community to start to buildout a database of these parameters. JMHO

It's everything from everyone right now. The chip fabs are clogged up with orders for chips from OEM manufacturers. People forget the same fabs that are used to make chips for devices like the ones we use here also make chips for auto makers, switches, routers, cellular equipment and so on. We have cable companies upgrading to docsis 3.1, fiber providers pushing up speeds globally, 5g deployments going up. We have a "shortage" of chips for many of the devices used in home automation because, the companies involved just simply do not buy enough bulk to take priority over others. This is why I don't buy into the Insteon is dead hype. They are owned by a capital management firm. These types of firms are kinda like house flippers, they find a way to profit. It may be rebranding, parting out a company, but either way the monetize the company. I think they are being rebranded, and are putting the Nokia brand first. I am seeing outs across the spectrum of products I buy and many of the products I get in hand were manufactured before this problem began. We are just starting to see the stockpiles run out.

One of the tricks I used when I was having issues with this was in the past was to setup a Gmail account just for notifications from my ISY, then set up ISY to use that account to send from and also as the primary address for receiving. Since the E-mail is being sent directly from that account on gmail and to that account, there is zero lag time. Then I set up push notifications for that e-mail account. You can send as text to a phone, but text from an E-mail account always goes though additional Procmail filters to filter as much spam as possible. So this slows the delivery at that point, and larryllix pointed out text is always a lower priority as well. So E-mail to Text is just kinda a crapshoot. UD's E-mail server has been very quick as of current so I just have it send to that same Gmail account and keep the push notifications set on that account. I had set both text and E-Mail and E-Mail won every single time.

My god SMH. I am sad for you. ?

They really are awesome aren't they.

I certainly not trying to aggravate anyone. However, there seems to be some tender egos here(to be nice I won't call anyone what they are called in other forums) Geeky stuff. Looking forward to poking around your new geeky additions. lol On a serious note, lock these boxes down tight, you have done way too much work to let someone reverse engineer them. You don't want someone cloning them. I know you guys aren't making much on them and the programming is golden. I know a lot of people here don't understand how much work that is but I do. And I appreciate how much time and work you have done. I am sure that the me Running VM of Polisy is a bit alarming to you. I am not out to clone, just keep my inlaws off my ***, can't give them any instability or I will never hear the end of it. Have A Great Day

You could use a Z-wave controller with RGBW type LEDs. I don't know how well they would work as I have never tried it myself. I would search Amazon and see. If you have a Z-wave module in your ISY994i you do have some options.

Not interesting at all. The point of my deleted post is that the answer is in plain sight if one looks. Just like putting it all on a VM, it is something a toddler with a PC can do. Too much of this "support" is people who just don't know, giving poor advice. Either way I am done with that, let them screw things up, hopefully they learn from their mistakes. To get the system on A VM is pretty basic just install a FreeBSD VM SFTP all of the files from Polisy over to your pc then upload the files into the proper directories in your FreeBSD VM. Make sure to create the proper pools. Bingo Bango, it will run. Of course if you want full functionality of the software you need to use a PLM and pass the ports, you will also need to edit the network configs to match the VM, but nothing complex. Obviously you can't install any portals or anything, but you can test software stability this way. I am sure this is how they test the software at UDI, it would be much faster than loading to real hardware everytime. lol. Have a great day.

Delete Done With trying to help anyone here! All I get is harassed for helping with the proper ways.

Did you ever get in?

I don't think Insteon is going out of business, at least not liquidation. They are owned by a Capital Investment company at this point, if anything they will gut out the IP and sell it. I am more concerned with them closing down more avenues of access for third party usage than I am about them going under. That said the Idea of Polyglot and Polisy was to make UDI less dependant on Insteon for customers and bring in a more diverse home automation group. ISY is very powerful software and shouldn't be strapped by support for a certain brand. However, the time tested and solid method of allowing users to create their own interactions. It is a very solid method for tech savvy users. Unfortunately the market on the hardware side is just rattled with little more than snake oil products. The a fact in the market right now is that an uninformed newbie doesn't stand a chance of navigating the product selection at the moment. To be brutal, navigating away from Insteon right now only has only real solid path, and that is Z-wave. None of the Nodes on Polyglot are going to give you the peace of mind for the future in terms of compatibility with Polisy or ISY even if UDI implemented a certificate or QC system. Compatibility can only be achieved if the manufacture maintains some local API that is usable to create a node. If the company decides to stop doing that, than game over. So moving away from Insteon it is just better to look at the protocols rather then the brands themselves. Insteon was just the marriage of both a brand and a protocol that worked for most people that were doing this kind of thing. Unfortunately they were a bit ahead of the curve on the consumer front and when the consumers were ready Insteon just didn't do a good job at pitching itself. Myself I think for most things Z-Wave will work great, on the Polyglot side I am going to look at the manufacture and deciding based on what I see as to what I will buy knowing that while it works for me now, an Update of firmware may break that compatibility. So I think for me anyway It will come down to how open is the company with their users. If they are tight lipped like say apple than no go, If they are open then yes.

As asbril said try again. make sure all letter are lower case. Is this ISY994i or Isy on Polisy?

I can't answer for UD, But, what I can say is that several of the products that are listed on thread's official website are already supported via polyglot. The other thing that hit me is the fact none of the products use Thread exclusively. They all have some other protocol available. This doesn't bode well for the protocol. Supporting a new protocol outside of the polyglot framework would be a massive undertaking. If the manufacturers who build on Thread are not fully committed to it why would UD want to spend the time to develop it within ISY? The other big issue is the fact it is IPv6 dependent. That isn't big deal if you live in say an asian market that has been quick on the pick up of IPv6, but, in North America where a huge chunk of the business is, that is nearly a deal breaker. While most devices in the market are capable of running IPv6. In most home deployments, it is off by default. Most North American consumers are not going to be able to enable IPv6 throughout their network. I am sure this is why none of the manufactures are 100 percent committed, they need a fallback. That being said I think it is a wonderful protocol. It is everything I want in a protocol. Network layer based, IP Aware, Encrypted, Mesh, and Open Source. The Fact it is Network level and IP aware means the medium becomes nearly irrelevant. It can communicate via RF, Powerline, Bluetooth, Wifi, Ethernet, or any other medium that can connect two IP nodes. That IPv6 requirement though, that complicates things. If manufactures continue to implement it, I could see it being supported broadly in the future. There just won't be a rush to support it right now, by any company building Home Automation hubs. The American consumer is used to being spoon fed products that require very little work from them. The market is already crowded and confusing to the average American consumer. And as unfair and insane as it seems most of the corporate world places their bets on the American market before all others.

Wow talk about evolution of conversation. At the end of the day I think it comes down to this. Insteon from a technical and simplicity of use perspective, was second to none. Due to corporate level decisions, they have become difficult to deal with and have made decisions that are likely to lead to their demise. They have become non-responsive. Due to this lack of response we are unaware of their status and can only speculate about what is going on. They could be collapsing, they could be working on rebranding(Nokia), or they could be doing nothing at all and it really is just the chip shortage causing availability issues. I think the collapse talk comes down to both hope and dread. Hope that someone will buy them and turn it around. Dread that the investment made in their infrastructure will be a costly mistake. Personally I am building out automation at my in-laws home this winter. I am still building out on insteon for them because this is where I started them out years ago and they understand how to use it. If insteon folds I will replace items as needed with new items they are comfortable using. As for my home I am full insteon and have had very few things quite working. If/when something does break, I will simply pick a device to replace it, insteon, Z-wave or something else that polisy can control. That is the beauty of isy and polisy. I can choose to build things out the way it works for me. Personally I think Insteon is trying to follow the pack and rebrand with the Nokia name. I know when Menards did team up insteon to offer the full line in stores, it was an absolute disaster. Customers were returning damn near every unit sold. It was great for me as I could buy the returned units dirt cheap. However, the problem was people just didn't understand how to install it and make it work, the process was just too technical for the weekend warriors. Then the home automation "revolution" hit and insteon wasn't on physical store shelves. They got lost in the fray of popular brands. If you know GE and it says it works with Samsung SmartThings and hey you have that, you buy the GE item. From the customer forward standpoint Insteon only worked with Insteon and most customers don't know the Insteon brand let alone trust it. Nokia is a known and trusted customer facing brand. Insteon may just be about to do the one thing that is bound to piss everyone of us off, become a consumer grade, easy to use, proprietary based brand. Just another on shelf, end user brand in a sea of them. Personally that is where I think we are heading. The real question is just how far is Richmond Capital willing to go with it.

I gotta call you out here. This isn't a unique model, not by a long shot. This is how nearly all software and technical products are built. Linux for instance powers 100 percent of super computers 80 percent of all servers, 87 percent of all cell phones. Linux has thousands of distos, millions of libraries and software packages. Apple for instance uses Darwin as the bases for all of its OSes. Darwin is simply a disto of FreeBSD, the very same software at the heart of Polisy. What you're thinking of is consumer level products. Products that are designed to be fool proof, that prove the quality of human fools. When it comes to professional products of any kind, in any industry, it is up to the professional to determine how well each item works for the scenario they are dealing with. That is why they are professionals. In software development no single company can produce vast products of quality. Take Microsoft for instance, they are more known for crashes, blue screen of death, and security holes than reliability. Meanwhile Linux which is open source and built on millions of "third-parties" is the most successful OS in history. This not so unique model allows for diversity of choices, diversity of support, openness of code allowing for flexibility. The fact is that this method breeds stability by allowing code to be viewed and modified as needed. That being said, it is possible that in the hands of a novice or a pseudo-professional that this can lead to instability and difficulty. However, that is why it is best to allow true professionals to deal with professional things.

IDK, I think their IP is just a bit too valuable to go to some newbie. Personally I think/hope that they will licence the IP out and allow for several companies to build insteon compatible devices. My wet dream scenario is that they open source it and let a community take it over from their it could become a standard that could be made by anyone kind of like z-wave. That of course would never happen, but one can dream. Well worst case is no one buys the IP and they liquidate. This may lead to reverse engineering that could bring it back as an Open Source project. I guess we will see.

B&H is filling orders on demand and insteon's Amazon store is still filling orders for several products. Smartenit.com still has usb sticks. While the product pool is very tight, it isn't gone just quite yet. As far as someone buying their patents, I have no doubt someone would. My thought would actually be Foxconn, they could integrate it into belkin. Imagine wemo with insteon on board, would be very powerful, an IP aware insteon network.... Another company that comes to mind that has shown interest in home automation, but doesn't have a platform right now is logitech. They keep dipping their toe in, I think insteon would allow them to dive in.

SSH in and run sudo pkg update and then pkg upgrade

Meraki firewalls are layer 7 aware, you may need to add a rule specifically for Portal. I would use a network sniffer to see exactly what port ISY is attempting to use to get out then add a rule for it. Meraki is very paranoid.

If you are using Pi3 or Pi4 you can run 64 bit if that is possible you can download a 64 bit DEB at https://www.mongodb.com/try/download/community or if you need 32 bit you can compile it from source. The other option is to use Ubuntu Server for Pi and just install the version in their repo. On a side note, compiling isn't very hard in most cases you just navigate to the folder, issue the commands ./configure followed my make and then make install and you are done.

Seriously, you need to let it go. I explained what I was doing, I don't answer to you. If you are unable to "get it" then that is on you. You seem to have some type of complex that you "need" to be "right". I am here to help people if I need to break it down for people that is what I will do, if need to use their incorrect terminology to help them I will. Now growup and act like an adult. I will not respond to you any further and any further response from you will just show how petty you are. Go look for a fight elsewhere.

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.