ase

May have just been a mistake. Each of Polisy's interfaces have a different mac. They may have just used the wrong one on the sticker. You can use the ifconfig command in the shell and it will display each address. The one used for uuid should be ig0 but it is possible they put ig1's or ig2's on the sticker.

Had the same error. Had to use the trial option. Then it updated the uuid.

Virtual Box works well for this kind of thing. Just make sure to install extensions and allow the usb device to be used buy the guest os.

You can use sudo -i to work within the root user.

You're not allowed to go anywhere. Lol. You're too important. Seriously though Thank you for all you've done over the last 17 years.

No one is proposing a database of every parameter for every device ever made. You seem to have an Issue with reading into things whatever you want. There is a difference in parameters that are of use within the software and many of the device setting based parameters. Those "thousands of parameters" you refer to are often for hard coded items that no users are going to change, nor are they intended to be modified by a user. Many of them cannot be modified via software anyway. There would be no reason to deal with those. Say a thermostat has a parameter to modify temp tolerance, this is set and validated, users are never going to need that in a nice drop down interface. Next your not going to bother tracking parameters for devices that are not currently produced. You also wouldn't track parameters of "low quality" manufacturers. Many of these devices don't have quality documentation. Next most manufacturers assign the parameters across their entire product line. Take zooz for instance every single one of their dimmers use the same parameters to assign dim speed. So once that pattern is established, unless the manufacturers makes a change, the parameters can be applied across their product lines. As for why I referred to UDI in a proactive manner is because as stated above UDI would need to make a few small changes to ISY to allow for either an external database to be imported by users or allow for custom parameters to be added within a device. Either way I have begun contacting manufacturers to get full copies of how they assign parameters. I guarantee you that each manufacturer has a methodology. Now if you have suggestions on how I should format the resulting data I would love to hear it. It doesn't doesn't matter if UDI uses the data or not. There isn't a comprehensive listing of parameters for the commonly used Z-wave devices and most of them have documentation that includes this information but not presented in an understandable format for most. I have helped author some of the world's most used database driven CMSs, I am well aware of how to deal with large data sets. All the best.

I guess what I am alluding to is if we had a database of these parameters, and if UDI were to build this idea into ISY. A customized pull down menu could be created. This way you would simply look up the parameters and then create the relevant pull downs. This puts no work or major changes on to UDI and still allows the user to create the UI the way they want.

No one suggested UDI maintain the database. A database is very simple each person simply adds the parameters as they find them. This requires zero effort for UDI. This concept is called crowd souce. It is how many companies support complex products. I am personally tempted just to host the database on my servers. Further no one has suggested that ISY or Polisy are for non tech people. There are however different levels technical understanding. I don't know your level however, I have written software, designed hardware, administrated networks for f500 companies as well as run my own IT firm. I am willing to bet that I see things very differently than the home grown hobbyist. I would in fact advocate that professionals install home automation due to the technical and electrical aspects. However, the fact remains that will often not be the case. That being the case I believe that professional methods should be taught to those who are looking for guidance. After all the methods are built around safety and future troubleshooting. Part of providing that support as a community is to build out information for common use by users at all technical levels. Nobody expects UDI to step up support, they expect the community to step up, after all they are the ones that derive benefits from it. A community is also an optional thing. The community isn't even just this one, it is people in the home automation community in general. A database of z-wave parameters would help all of the different home automation users. The only real question for me is what format should be used.

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

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.

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.

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.