Michel Kohanim

@larryllix, apologies. I forgot to mention that the update changes the port to 443. So, you don't need the 3000 at the end. With kind regards, Michel

@larryllix, Thanks so very much for the feedback! What you need to do: 1. ssh to polisy 2. sudo pkg update && sudo pkg upgrade 3. sudo pkg install py37-netifaces 4. sudo pkg install py37-cryptography 5. sudo reboot If you upgrade your Polyglot on Pi to 2.2.5, you can back it up and try the restore button. With kind regards, Michel

@Mustang65, So, it's running. Do you know the IP address for your Polisy? If not, please do ifconfig. igb0 is the Ethernet port and wlan0 is the WiFi (if you have one). Once you get the IP address, please try https://<ip> or https:<ip>:3000 … please make sure it's https and not http. With kind regards, Michel

@Mustang65, Can you please do: ps -aux | grep poly and post the result? With kind regards, Michel

@garybixler, Good idea. This said, one of our mail goals was that you could simply unplug the unit without having to worry about things going awry. That's why we use ZFS + SSD. During the development process, we deliberately unplugged Polisy during a variety of operations and nothing got damaged. I am relatively confident that, simply unplugging would not have adverse impact on the operation of the unit except for periodic logs that have not been flushed. In all cases, it's a good idea. With kind regards, Michel

@bmercier, thank you! You are our super hero. With kind regards, Michel

@Mustang65, Please do: sudo pkg update && sudo pkg upgrade There's one more bug: the Polyglot daemon might be running twice. So, please do this: sudo killall daemon sudo service polyglot stop sudo service polyglot start With kind regards,

@MWareman, Thanks so so very much! With kind regards, Michel

Hi @Michael, I cannot reproduce. I even downloaded meta.txz using Windows after it succeeded on Polisy. Is it possible that you are using a proxy? With kind regards, Michel

@bpwwer, Yes! With kind regards, Michel

Hi Gary, I am so very sorry. Working on it right now. With kind regards, Michel

Hi Gary, it might be related to file permissions. Please do this as the admin user: sudo pkg update && sudo pkg upgrade Please let me know if this fixes the issue. We still have another version in the works. With kind regards, Michel

@MWareman, I agree. We had requested for MAC address labels from the factory but got serial numbers instead. Also, there are 3 MAC addresses so, in all cases, we should find a better discovery solution. @garybixler For Tesla (and Ring) it's best to use the cloud because they require and endpoint. With regard to Wireless tag, do you get the same exact error? With kind regards, Michel

@bpwwer, We actually spent a very good amount of time working on discovery: 1. mDNS … would have been ideal but browser support is not cross platform, so we had to abandon for now (but a very good candidate for the future) 2. Force a cloud connection (just like ISY) and then get the local IP address and redirect. Too mothershipy for us. So, had to abandon 3. Yet another Java Finder/Launcher. Sacrilegious, so we had to abandon 4. Hostname and DHCP seemed to be the most natural. Most routers support DHCP hostname … but it seems that more complex network infra doesn't support this So, we'll have to figure something out one way or another. Everyone's feedback is quite welcome. With kind regards, Michel

@mjcumming, are you sure you are using the right UI? https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop With kind regards, Michel

Hello all, Thanks so very much for the feedback. We did find the issue with the spurious node servers. During assembly/testing, there's was an ISY in the lab with those node servers. So, once Polisy started up, it loaded them from ISY. Other things we are working on: 1. File permission and upgrade issues 2. Allowing Polisy to use other ports (including 443) 3. Some minor bugs and a couple of enhancements With kind regards, Michel

@oh2bnMaine, Are you certain you followed the instructions after replacing the PLM? It seems that you are not getting status feedback from your devices: https://wiki.universal-devices.com/index.php?title=INSTEON_No_Status_Feedback_From_Devices With kind regards, Michel

@MWareman, Thank you. The problem with SolarEdge seems to be that the loaded mongo image already included SolarEdge and Darksky. We are fixing that right now. The UI is NOT done yet. That's why you were on the geek batch (without the UI)!!! @simplextech, Thanks so very much for the feedback. With regard to Basic UI, well, that was the whole point of delaying the release date while giving you access to the unit. The UI is in the works and will allow configuration of network, wifi, etc. Bluetooth is a little tricky since, currently, there's not much we can do with it. But, all the drivers are there and are loaded at start up. With regard to loading other packages, well, please note that Polisy is based on FreeBSD. So, someone would need to migrate Node Red and Home Assistant. Based on what I have read on the forums, I am not comfortable sanctioning HA running inside Polisy since it uses Java and large amounts of memory. With kind regards, Michel

Hello everyone, I have also created a forum. Please post your geek experiences here: With kind regards, Michel

@MWareman, Thanks so very much for the update and feedback: 1. Polyglot username is not the same as the OS username. We are hoping that no one has to get to the OS/SSH (except for the geeks) 2. Letsencrypt definitely in our plan 3. Setting hostname is part of the UI (for which we held up the release) 4. Not being to upgrade poly should be resolved soon. We ran into some permission elevation issues (polyglot use does not have permission for many things and we don't want to use root). And update should be available this week and you can update Polyglot using the command: sudo pkg update polyglot 5. Reboot will be done from the UI and will not require sudo. But, from the shell, you need sudo simply because, otherwise, we will lose audit trails 6. Getting SolarEdge is unexplainable. Please do be kind enough to send your UUID to support@universal-devices.com With kind regards, Michel

@MWareman, Thanks so very much for the update and feedback: 1. Polyglot username is not the same as the OS username. We are hoping that no one has to get to the OS/SSH (except for the geeks) 2. Letsencrypt definitely in our plan 3. Setting hostname is part of the UI (for which we held up the release) 4. Not being to upgrade poly should be resolved soon. We ran into some permission elevation issues (polyglot use does not have permission for many things and we don't want to use root). And update should be available this week and you can update Polyglot using the command: sudo pkg update polyglot 5. Reboot will be done from the UI and will not require sudo. But, from the shell, you need sudo simply because, otherwise, we will lose audit trails 6. Getting SolarEdge is unexplainable. Please do be kind enough to send your UUID to support@universal-devices.com With kind regards, Michel

@lilyoyo1 and @TrojanHorse, Please do not waste the bandwidth of our forum with personal attacks. You can DM each other and continue there. With kind regards, Michel

@gviliunas, Thanks so very much! We will definitely look into it. With kind regards, Michel

Hi @gviliunas, Which node server is this? With kind regards, Michel

@larryllix, I sure hope so and, in combination with node servers, that's the plan: to allow integration of novel UI components. But, that's a little farther down the line. @Bumbershoot, You are 99% right! The OS is lean (we have removed a lot of things that we do not need or didn't make sense for our application). And, we developed our own package manager so that we can use regular FreeBSD commands to update/upgrade packages + an update server so that we can upgrade the whole OS (thank you @xKing). All this said, we debated using Jails (like Apple) vs. giving customers elevated permissions. We opted for the latter since, even Apple is having a hard time managing or preventing jail breaks. And, with our limited resources (compared to Apple/Google), we felt that we would be spending more time managing the jails rather than focusing on the application. Of course, as things progress and the nature of support calls, we may opt to completely block this feature or have configurations that do not allow elevated permissions. With kind regards, Michel