MWareman

Well - I reverted Polyglot to the default self-signed cert - with the same result. Putting back a (new) cert (so I avoid cert errors from the browser) results still in this: [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:init:464::initializing [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setThreadScope:153::setting scope to 2 successful [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setJoinable:196::setting joinable to true [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setJoinable:204::setting joinable successful [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setPriority:390::setting priority 6 successful, 0,No error: 0 [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:27::starting to look for LEDs [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:50::opening /dev/led/led1 [T:34373496832][LED:Info]../src/Device/LED/UDXLed.cpp:open:15::opening /dev/led/led1 [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:57::/dev/led/led1 registered successfully [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:50::opening /dev/led/led2 [T:34373496832][LED:Info]../src/Device/LED/UDXLed.cpp:open:15::opening /dev/led/led2 [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:57::/dev/led/led2 registered successfully [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:50::opening /dev/led/led3 [T:34373496832][LED:Info]../src/Device/LED/UDXLed.cpp:open:15::opening /dev/led/led3 [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:57::/dev/led/led3 registered successfully [T:34373496832][Audio:Info]../src/Device/Audio/UDXAudioManager.cpp:registerAllDevices:23::starting to look for the Speaker [T:34373496832][Audio:Info]../src/Device/Audio/UDXAudioManager.cpp:registerAllDevices:33::opening /dev/speaker [T:34373496832][Audio:Info]../src/Device/Audio/UDXAudioManager.cpp:registerAllDevices:40::/dev/speaker registered successfully [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:init:464::initializing [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setThreadScope:153::setting scope to 2 successful [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setJoinable:196::setting joinable to false [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setJoinable:204::setting joinable successful [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:start:112::thread creation successful, ID = 34373499392, 0:n/a [T:34373499392][UDXThread:Info]../src/System/UDXThread.cpp:doRun:62::starting to run [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:66::Home Dir = /var/udx, default = /var/udx [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:70::Logs Dir = /var/udx/logs, default = /var/udx/logs [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:74::Conf Dir = /usr/local/etc/udx.d, default = /usr/local/etc/udx.d [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:78::Log file = /var/udx/logs/log, default = /var/udx/logs/log [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:82::Log file = /var/udx/logs/debug.log, default = /var/udx/logs/debug.log [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:86::Global TZinfo file = /usr/local/etc/udx.d/static/tzinfo.json, default = /usr/local/etc/udx.d/static/tzinfo.json [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:89::flash read file /usr/local/etc/udx.d/.udxr.rom.tmp [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:92::flash write file /usr/local/etc/udx.d/.udxw.rom.tmp [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:95::bios write file /usr/local/etc/udx.d/.udxbios.rom [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:98::bios write file /usr/local/etc/udx.d/.udx.tpm.crypto [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:101::current time info file /usr/local/etc/udx.d/tzinfo.json [T:34373496832][MongoDB:Info]../src/DB/UDXMongoDB.cpp:init:34::creating mongo client for mongodb://localhost:27017 [T:34373496832][Polyglot:Info]../src/Config/UDXPolyglotSettings.cpp:retrieveFromDB:74::successfully retrieved Polyglot settings [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:409::invalid string tag: $oid [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:440::invalid int tag: __v [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:409::invalid string tag: timeStarted [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:301::invalid bool tag: useBeta [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:409::invalid string tag: name [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:409::invalid string tag: key [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:409::invalid string tag: ca [T:34373496832][SysConfig:Warn]../src/Config/UDXRuntimeConfig.cpp:init:107::failed retrieving pg config from db [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:init:464::initializing [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setThreadScope:153::setting scope to 2 successful [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setJoinable:196::setting joinable to false [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setJoinable:204::setting joinable successful [T:34373496832][SysConfig:Error]../src/System/UDXSysConfig.cpp:init:59::Cannot make a secure connection. Bailing out. [T:34373496832][HWMonitor:Error]../src/main.cpp:main:126::failed starting the SysConfig MQ [T:34373496832][Audio:Info]../src/Device/Audio/UDXAudioManager.cpp:end:15::closing ... [T:34373496832][GPIO:Info]../src/Device/GPIO/UDXGpioManager.cpp:end:15::closing ... [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:end:14::closing ... [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:89::stopping [0] running=false [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:99::destroying attributes [0] [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:89::stopping [0] running=false [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:99::destroying attributes [0] [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:89::stopping [34373499392] running=true [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:96::cancelling [34373499392] [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:99::destroying attributes [34373499392] [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:detach:448::detaching [34373499392] MQTT is on the default port: [admin@polisy /var/udx/logs]$ netstat -nab | grep LISTEN | grep 1883 tcp46 0 0 *.1883 *.* LISTEN [admin@polisy /var/udx/logs]$ It is - by default - only listening to 'localhost'. That shouldn't be an issue here though - unless the udx binary is trying to connect to the actual IP instead of 'localhost'. The Polisy itself is beeping up a storm. The udx binary keeps stopping and relaunching - with beeps issued each time..

Hi Michel, I had put a cert in place for Polyglot to use - does that affect the cert MQTT uses as well? I have not changed the port. I do have to renew that cert though. If MQTT is using the same cert as Polyglot that could explain the issue. Michael.

After installing udx: Download https://udx.s3-us-west-2.amazonaws.com/pkg/1.0.26/udx-1.0.26_4.txz sudo pkg install ./udx-1.0.26_4.txz and starting it with: sudo service udx start I am seeing this in the /var/udx/logs/debug.log [T:34373496832][SysConfig:Error]../src/System/UDXSysConfig.cpp:init:59::Cannot make a secure connection. Bailing out. [T:34373496832][HWMonitor:Error]../src/main.cpp:main:126::failed starting the SysConfig MQ And I still get stuck at the 'Please wait, getting configuration...' message....

My 5.1.16 keeps missing scheduled events - and I rely on leak sensors... Do we know if 5.0.16B is likely still this week? Michael.

I have 5.0.16 currently - and twice over the last week I’ve had to restart ISY because time based programs stopped triggering (time offset from sunset). However, I have Flood sensors likely affected by the bug. So, I’m awaiting 5.0.16B before upgrading to the latest.

I'm getting an odd error when I run 'sudo pkg update' [admin@polisy ~]$ sudo pkg update Password: Updating udi repository catalogue... Fetching meta.txz: 100% 820 B 0.8kB/s 00:01 Fetching packagesite.txz: 100% 50 KiB 50.8kB/s 00:01 Processing entries: 0% Newer FreeBSD version for package p5-HTML-Parser: To ignore this error set IGNORE_OSVERSION=yes - package: 1201000 - running kernel: 1200086 Ignore the mismatch and continue? [Y/n]: Processing entries: 100% udi repository update completed. 165 packages processed. All repositories are up to date. It appears that the package 'p5-HTML-Parser' is expecting a newer kernel than Polisy is running

Hit the ‘Send Spokens’ button..

I run Asterisk on a Pi(3). Other than rebooting for kernel updates occasionally it’s been 100% reliable - without underclocking. In total, I have several Pi’s running well (things like Nodelink, the Unifi controller, dedicated DNS servers, ElasticSearch dedicated master node etc). Sounds like either the power supply is not reliable - or you are using a poor quality SD card. Don’t cheap out of these and the Raspberry Pi will be very reliable.

If you have a room named in ISY Portal (assigned to devices) and a room of the same name in Google Home - the devices will be put into the room automatically. The room itself will not be created (to my knowledge). So, create empty rooms in Google Home then try the sync all devices.

Are you absolutely sure your initial variable assignment does not contain the ‘F’? If it does, it likely won’t work. With network and email substitutions this is common and UDI now allow to append .RAW (to get the number without any extra characters). Not sure how to do this inline though - but you could create a network rule to set the variable.

FWIW - I did the upgrade to 2.2.6 when beta - and it was seamless (other than the WiFi starting to connect automatically)

That’s what I thought. My enquiry is more about how do I disable the WiFi interface in a way that won’t break the admin UI when available. Currently, if just commented it out of the rc.conf - but that’s a change that will likely break the admin UI if I don’t reverse it.

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.