ase

As we have discussed for literally days at a time. Both Polisy and Eisy are X86-64 PCs, just like you have sitting on your desk. They are simply smaller format. Polisy OEM was pcengines(https://pcengines.ch) all of the accessories like wifi and Bluetooth cards are available at that site, even wall mounts. Eisy OEM is MELE(https://www.mele.cn/). The OS for both is FreeBSD. In terms of why you were not able to use the backup directly is most likely because your windows based computer probably didn't have the needed options to mount an ext3/4 filesystems. For the best experience when working with systems like Polisy it is best to be working from a Linux or BSD system(windows sucks anyway). In terms of backup you can easily transfer any files with sftp and for full backups simply use dd to make an image. If in the future you want to use either as something other than a home automation controller, you can reflash the bios (I don't know if Eisy is a custom bios) and install OS and software you want.

The hardware is from pcengines and is world renowned for reliability. After reading you past posts, I think there maybe some issues with your power source. The processor used in polisy is a passive cool model and is mounted on the bottom of the board. AMD white papers don't have any design for active cooling on the processor. Polisy shouldn't ever get hot enough to cause any issues. However, just like any electronic device it is sensitive to voltage drops and spikes. Also note that any computer processor is vulnerable to different type of electrical waves. You may want to do some line quality checks.

Try sudo -i to enter root and reissue commands without sudo

I think you may be stuck in a cycle of over thinking. Break down each think into a smaller program and then have a master program set to run each of the programs. It may take some trial and error. But, I find breaking it down into smaller bits helps to find what does and doesn't work and the adjustments are easier.

Do you have a z-wave dongle plugged in? If you do try unplugging it and rebooting the unit. If the error goes away it is likely your z-wave dongle is not responding. This is a known bug in the previous z-wave firmware release. You may need to follow the firmware update procedure posted on this forum.

According to the Insteon Troubleshooting graph, this is most likely caused by excessive noise on the line. I suspect that your new heat pump may be the reason. Compressor motors like those use in heat pumps are known for being rather noisey. Moving this device over to a comparable Z-wave device maybe the only real option at the moment.

You don't need both. http 8080 is fine if you are just using it on your lan.

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.