MWareman

Admin UI? Is there some administrative interface other than what Polyglot provides on TCP/443? I don't see anything else listening (though I'm not sure what port 45235 is). A HTTP request to this results in: Received: / {}. Code: 500 Command / failed Port 27017 is MongoDB and 1883 is MQTT. Michael.

Turns out - not my fault.... ish.... The Wifi interface had (unexpectedly) connected to my Guest network - and the guest network has a captive portal. What I thought was my proxy was not in fact.... Two things I suspect.. 1) The wired connection should always have a lower interface metric. Currently, the wireless interface has a metric of 0 - meaning you cannot set the wired interface lower... 2) Really - it should start down - and require configuration to bring it up... either at the CLI (for the geek batch) or UI (for production). either way - wired should likely be necessary for initial config anyway. I've had to comment out the wlan0 entries in /etc/rc.conf just to get it to stop connecting to my Guest Wifi! finally - was able to install Poly's again... but... #***** WARNING ***** #Polisy rc.conf will get updated by Polisy management services. #Manual changes to this file may render your system inoperational ## Prior to updating to 2.2.6 - this didn't happen. Is this something new? Is there a better way to disable wifi (or at least stop it promiscuously connecting to open networks!) that will not break any future plans? Another issue with 2.2.6 - going into any Poly and viewing it's log does not filter the log only for that Poly. The entire log is streamed for all. not sure when that changed - but it makes debugging Polys *much* more difficult... Michael.

Thanks! Fighting an issue of my own doing now. My proxy is apparently breaking the system again (pkg broken due to cert error and Polyglot unable to get Polys from GIT). And the proxy service is now shut down... it’s very odd. I don’t think it’s a Polisy thing though...

I enabled "Use Beta Firmware' and tried again - with the same result. Should I just install polyglot-beta-2.2.6_1 over the top?

Another new one. I’ve tried seeing if there are any updates (none) and restarting Polyglot, but the same symptom afterwards. Clicking ‘Add Nodeserver’ get stuck at this screen without updating: It’s happening on Chrome/Windows and iPad/Safari for me...

True. But you cannot change the color. If you have a need/desire to be able to adjust the color of the light you pretty much have to go the smart bulb route.

Sun Poly seems to error on a timezone related issue. I suspect a difference between Linux and FreeBSD and the Poly auther may need to fix this one... 2019-11-03 10:55:28,672 [NodeServer] [ERROR] Exception in thread NodeServer: Traceback (most recent call last): File "/usr/local/lib/python3.7/threading.py", line 926, in _bootstrap_inner self.run() File "/usr/local/lib/python3.7/threading.py", line 870, in run self._target(*self._args, **self._kwargs) File "./sun-poly.py", line 30, in start self.tz = get_localzone() File "/var/polyglot/.local/lib/python3.7/site-packages/tzlocal/unix.py", line 165, in get_localzone _cache_tz = _get_localzone() File "/var/polyglot/.local/lib/python3.7/site-packages/tzlocal/unix.py", line 90, in _get_localzone utils.assert_tz_offset(tz) File "/var/polyglot/.local/lib/python3.7/site-packages/tzlocal/utils.py", line 38, in assert_tz_offset raise ValueError(msg) ValueError: Timezone offset does not match system offset: -28800 != -21600. Please, check your config files.

Here is mine: [admin@polisy ~]$ ls -la /var/polyglot/log total 63667 drwxr-xr-x 2 polyglot polyglot 3 Oct 23 18:13 . drwxr-xr-x 9 polyglot polyglot 12 Oct 31 04:51 .. -rw-r--r-- 1 polyglot polyglot 65053805 Nov 3 10:45 debug.log Mine is a bit quieter than yours I guess - but it still takes a long time to stream to the browser. This really should be rotated out daily and the log rotation mechanism configured to remove old files after some period of time.

Just saw that 2.2.5_6 is available. Upgraded to it and the iPad issue is fixed. Thank you!

I never knew about that one. I've always just used Notepad++ on the Windows system which has no issue with Unix formatted text files...

I 'Deleted' both orphaned Darksky Poly's from the ISY admin interface - and they disappeared from PGC and Polisy after a bit. This time I installed Darksky on Polisy - and it's working perfectly there. No issues at all.

Nope. It shows 'Install'. And two copies already installed as 'Unmanaged'... When I get home I'm going to try just deleting the nodes from ISY...

This is the one I linked above: Here is another one: http://www.atmos.albany.edu/daes/atmclasses/atm350/vi_cheat_sheet.pdf Michael.

I just added the Camera nodeserver - and selected slot 10 to install it to. It installed to slot 3. Slot 3 happened to be free at the time - but installing to the wrong slot is likely a bug. Thanks.

What’s the correct process to remove a Poly that’s showing as ‘Unmanaged’ on both Polisy and PGC? In trying to get Darksky PGC running I now have a few instances showing up apparently not managed anywhere... Do I just delete from the ISY admin console? (Want to make sure I do the right thing!)

The Polisy UI menu is not usable on an iPad. You can touch primary menu options (‘Home’, ‘Dashboard’, ‘Log’) but when trying to go to the store or settings sub menus you can not activate the menu option with tough. This issue is not present on PGC (you can select different ISYs just fine).

Nah...

Only real advantage is I’ve never come across a *nix system that didn’t already have it installed. Knowing vi has saved me so many times that now I’m slower with other tools. Knowing how to edit with vi helps with other tools as well (like sed and awk)

I thought this was a geek batch? (That being said - I have nothing against nano for those that are vi challenged....)

+1 on this! A new log should be created each day - and the UI should default to streaming only the days log. Prior days should be viewable - but not by default. There should also be an option to delete logs older than a certain number of days automatically. Maybe default it to 14. It's easy enough to install and setup logrotate when we have root. However - without root users are in for a poor experience after the system has been running for more than a few weeks.

I use vi - and knowing how to use vi is a true geek qualification...

Interesting. I upgraded to a newer build of 2.2.5 yesterday and I swear the option was not there. I just logged into Polisy again and now I see it.... To set a port in the .env file, put this in there: HOST_PORT=443 (or whatever port you want). That being said - this was useful before Polyglot had the UI option. It probably shouldn’t be used now that it can be configured in the UI - but it really should work first!

Is port 443 defined in your .env? If so - that would override the database setting. That being said - I’ve not yet see the setting option to change the polyglot listening port. The only port setting is in the ISY connection settings (the port that the ISY is listening on).

I was looking at the logs - and noticed the time was off. A closer look: Polisy was preconfigured to the Pacific timezone. @Michel Kohanim This should probably be a UI configurable option. For the geeks: "sudo cp /usr/share/zoneinfo/America/Chicago /etc/localtime" (replace America/Chicago with the appropiate timezone of course!)

I just installed py37-cryptography-2.6.1 on mine - and Polyglot started just fine. The installer also installed dependencies: py37-six: 1.12.0, py37-cffi: 1.13.1, py37-pycparser: 2.19, py37-asn1crypto: 0.24.0 These modules were needed for the LutronCaseta module (see initial reference of mine while resolving the dependencies for @avandeputte). Could those of you with Polisy not serving the page after this module also have this Poly installed? The py37-cryptography-2.6.1 module itself does not appear to cause Polyglot to fail if you don't have any Poly that depends on it (it seems).