Michel Kohanim

@DaveStLou, If you have no node servers installed, the best thing would be to drop the DB: mongo polyglot --eval "db.dropDatabase()" With kind regards, Michel

@garybixler, Can you please do: ps -aux | grep poly What do you see? I suspect that two instances are running. Or, you could simply unplug Polisy and see whether or not can still control your Tesla. With kind regards, Michel

@garybixler, how about the ISY Portal? With kind regards, Michel

Hello everyone, Thanks so very very much for your continued feedback. @gviliunas, thanks so very much for detailed migration instructions. This should be fixed soon. @MWareman, we'll figure out what the issue is with log rotate. Timezone is going to be fixed soon. @garybixler , are you certain that this node server is not running on more than Polisy? With kind regards, Michel

@mwester, I love your ideas. Please keep them coming. With regard to USB2 storage, that's something that we are not going to support but we might have to. @Mustang65 / @mwester, we have to find a better way of locating Polisy. mDNS is probably the best option in the long run. Most OSs support them in a variety of non interoperable ways but they are converging. @DaveStLou, had you configured anything in Polisy before? With kind regards, Michel

@glarsen, No, but it's best to leave it in the second slot. With kind regards, Michel

@MWareman, thanks so very much for the iPad feedback. We'll definitely fix it. vi vs. nano vs. emacs: my personal favorite is vi. I even have vi plugins for eclipse and vs code. If I could, I would get a vi plugin for the forum, outlook, and everything else. Alas, not possible. All this said - and just like anything else human related - the choice between vi/nano/emacs is as subjective as Windows vs. MAC vs. Linux vs. BSD. So, we'll definitely consider adding it. One more comment for those who want to connect to Polisy using serial: please note that we developed our own BIOS/OS so that a) we could add TPM support and b) move the console port from the DB9 on the back to the USB on the front (COM2). Our thinking is that we will be using the DB9 for communications with the PLM. So, how many of you geeks out there want to connect to Polisy using the serial port? With kind regards, Michel

@Bumbershoot, thank you. I am working with @Jimbo and others to find the root cause. It's a simple UDP broadcast. Wtih kind regards, Michel

@mwester, With pleasure. If you don't mind, I'll contact you via DM. With kind regards, Michel

@mwester, thanks so very much for the feedback. To answer your questions: 1. The change in release date was because of the Admin UI that allows you to change hostname, dns entries, time zone, etc. The same Admin UI allows you to do backup/restore of your configurations. If the SSD goes bad, then you will need to boot up with a USB and reflash the new SSD. We are working on making this as easy as replacing the SD card on ISY. Alas, it's not that easy 2. Partitions were based on an 8GB. Once we finalize how to do recovery, we'll update the partitions to take advantage of the whole 32 (for instance, we could have a partition for recovery) 3. The only slot with mSATA is the first one. The other two slots are mPCIe. So, you cannot plugin your SSD into any other slot. You can, however, use one of these adapters and connect to the USB port @MWareman, yes, of course the Admin UI allows you to set the time zone! The issues were due to a bug that was fixed. Clearing the log, yes. Vi, that's what I use all the time @gviliunas, this is a bug that will be fixed today. @Bumbershoot, which node server is not working on Polisy? With kind regards, Michel

@Bumbershoot, My fault. I had you drop the database. Sincere apologies. Did you take a backup? With kind regards, Michel

THANK YOU ALL (especially the log from @Bumbershoot), @xKing fixed it … please do: sudo pkg update && sudo pkg upgrade sudo service polyglot restart The port is 443 but can be set in the Settings. With kind regards, Michel

@Toddimus, YES. Thanks again @Bumbershoot! With kind regards, Michel

@Bumbershoot, THANK YOU THANK YOU. Working on it right now. With kind regards, Michel

@Bumbershoot, THANK YOU! With kind regards, Michel

@Toddimus & @Bumbershoot, Can you please do us a huge favor? 1. Put NODE_ENV=development in the /var/polyglot/.env file 2. Reboot and wait for 5 minutes 3. Send /var/polyglot/log/debug.log to support@universal-devices.com or post @io_guy, Let me check with the team. Just need to make sure we have enough resources for everything. With kind regards,

@Toddimus, What do you get for: pkg info polyglot? With kind regards, Michel

@io_guy, perfect!!! Please try https:// without the port. With kind regards, Michel

@Toddimus, Ok, let's try this: 1. killall and stop 2. mongo polyglot --eval "db.dropDatabase()" 3. reboot Thank you! With kind regards, Michel

@Toddimus, Correct. Apologies. Ok, now, please do sudo service polyglot start And, repeat your experiment with ps and grep. With kind regards, Michel

Hello everyone, Sincere apologies for the radio silence. The crashing issue is definitely related to multiple instances of Polyglot running. We are working on a fix. @Bumbershoot, in the meantime, please do this: sudo killall daemon sudo service polyglot stop sudo service polyglot start Please let me know what you get. @Toddimus, Please the same as above BUT do not do sudo polyglot start. Please let me know what ps shows. With kind regards, Michel

@Toddimus, It's definitely running. Are you certain the IP address has not changed (ipconfig igb0) for whatever reason? With kind regards, Michel

@Toddimus, What do you get from ps -aux | grep poly With kind regards, Michel

@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