Initial Feeback

[MWareman]

@MWareman,
This means two things: udx cannot connect to MQTT. Have you changed MQTT port or certificates?
With kind regards,
Michel

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.

[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..

[Michel Kohanim]

@MWareman,

What version of Polyglot do you have? UDX gets the certs from Polyglot's mongodb. And, as far as I know, there is no tag called "key".

With kind regards,

Michel

[io_guy]

Bug Report - Polisy does not respect secondary DNS servers.  My primary was down and Polisy did not use the secondary.

[Michel Kohanim]

@io_guy,

We'll definitely look into it. Is this on igb0?

With kind regards,
Michel

[MWareman]

@MWareman,
What version of Polyglot do you have? UDX gets the certs from Polyglot's mongodb. And, as far as I know, there is no tag called "key".
With kind regards,
Michel

Sorry for the delayed response. Sporadic internet access for a few days...

Polyglot is 2.2.8. Also, Just now, I couldn’t logon to the web UI (the logon button did nothing) and I had to reboot Polisy to be able to logon.

Michael.

[io_guy]

7 hours ago, Michel Kohanim said:

@io_guy,

We'll definitely look into it. Is this on igb0?

With kind regards,
Michel

Yes

[Mustang65]

On 12/27/2019 at 8:10 PM, io_guy said:

Bug Report - Polisy does not respect secondary DNS servers.  My primary was down and Polisy did not use the secondary.

I have rebooted Polisy at least 5 times and I enter DNS server 1 (8.8.8.8) and DNS server 2 (8.8.4.4), then SAVE, when I reboot Polisy the DNS server 1 and 2 have 0.0.0.0. Will not save my entered DNS servers.

Don

[Michel Kohanim]

@Mustang65,

This is how DNS works: 

1. It's assigned per interface (i.e. igb0, 1, 2, wlan0)
2. There's a max of 3 for the whole system
3. If any of the interfaces go down, the DNS for that interface is also removed

So, you have to make sure you are choosing the right interface (i.e. igb0). Are you?

@MWareman , if you are still having Polisy beep incessantly, I suspect Mongodb is corrupted. Please try:

https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Polisy_Keeps_Beeping

If your network is not class C (255.255.255.0), then the issue could be a bug with Polyglot where it cannot find ISY. What you can try is to update /var/polyglot/.env with:
ISY_HOST='x.y.w.z' where x.y.w.z is your ISY's IP address

With kind regards,
Michel

[MWareman]

@MWareman , if you are still having Polisy beep incessantly, I suspect Mongodb is corrupted. Please try:

https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Polisy_Keeps_Beeping

If your network is not class C (255.255.255.0), then the issue could be a bug with Polyglot where it cannot find ISY. What you can try is to update /var/polyglot/.env with:

ISY_HOST='x.y.w.z' where x.y.w.z is your ISY's IP address

With kind regards,

Michel

 

Michel,

 

Thanks for the suggestions. I do have a bigger network than /24 - so although there is no indication of any failure to connect to ISY I added that line to the .env. It did not change the status (even after rebooting Polisy).

 

So, onto the MongoDB possibility. The status command showed MondoD was running. So - I stopped it and then renamed the old data folder. After rebooting Polisy the issue returned. I had to put back the original MongoDB directory because all the nodeservers went to an ‘Unmanaged’ State - but the fact there is no apparent behavioral difference between a virgin database and my original one suggests no corruption.

 

The UDX binary still cannot make a secure connection to MQTT and the Polisy is still beeping.

 

Michael.

[Michel Kohanim]

Hi Michael,

Can you please send /var/udx/logs/debug.log to support@universal-devices.com ?

With kind regards,

Michel

[MrBill]

Sorry if this is already covered but what is this?

 

 

While I do have xfinity as an internet provider, this isn't one of my SSIDs, nor an IP address on my network.   I assume some neighbor with xfinity managed all-in-one modem/router/wifi that's open wifi?  wtf?  is Polisy bridging this with my ethernet connection?  if so, what a security issue.

Is the fix to UNCHECK "interface enabled"? 

I don't think Polisy should just be joining random wifi networks?  who are what does that?

 

EDIT TO ADD: second screenshot I dint'nt clip enough the first time around .

[MWareman]

1 hour ago, Michel Kohanim said:

Hi Michael,

Can you please send /var/udx/logs/debug.log to support@universal-devices.com ?

With kind regards,

Michel

Sent!  Thanks..

[mbking]

I have successfully configured my Polisy Pro and have been online with it for about 48 hours now. I started the transition with my ISY at 5.0.16B and Polyglot running on a RPi at version 2.2.3.  I have 2 node servers: Hue Emulator and Ambient Weather. The process followed the installation guidelines with a few exceptions.

1) I wasn't sure if I should update Polyglot to the latest version, but others appeared to do that before installing Polisy and it made sense to do so.  I wanted to be able to download and restore my node servers to Polisy.  I allowed beta versions of the firmware and Polyglot was successfully updated to 2.2.8.  I downloaded a backup of my Polyglot configuration.

2) Since I have a program on the RPi that sends the equipment room temperature to the ISY, I needed to keep the RPi running without Polyglot running.  To do this, I disabled the service with the following commands:

   sudo systemctl stop polyglot-v2

   sudo systemctl disable polyglot-v2

I shutdown the RPi to be on the safe side and then restarted after Polisy was up and running.

3) I reserved an IP for Polisy.

4) Followed startup instructions for Polisy.  Light sequence for me was basically as described with a few differences I didn't capture.  Once left light was steady and no beeping, I used https://polisy_ip_address to login.  I'm on Safari, so as I ran into with the RPi, I couldn't connect to Polisy. Got the "This Connection Not Private" message.  Safari would not let me ignore the message.  The solution was to select "Details" in the error message.  A Certificates icon is displayed for Polisy.  Drag the icon to the Desktop.  The file is Polisy.cer.  Open the Keychain app.  Drag Polisy.cer to the Certificates folder in Keychain.  Once there, highlight the file and select Get Info.  Open the Trust folder and select Always Trust for all items.  Now I can login to Polisy.

4) Updated software on Polisy.  As Michel says, be patient.  I wasn't.  There isn't any feedback while the update process is working.  I stepped away for awhile.  You do get a complete message at the end of the update. Reboot Polisy.

5) Polisy did not automatically find my ISY.  I added it manually.

6) Restored Polygot configuration with the backup I saved earlier.  Both node servers showed up and connected.

7) The Ambient Weather node started working without an issue.  The Hue Emulator was connected to the ISY, but my Harmony remotes were not communicating with the Emulator.  The solution was to go into each remotes configuration, select the Hue device to edit, select Re-Pair Bridge, and then Refresh.  Control from the remote was restored.

All in all, this was a relatively painless process with a few unexpected bumps in the road.  Hopefully others who are using a Mac can benefit from my experience.  And if there was an easier way to do what I did, I'd be happy for the advice.

[larryllix]

On 12/19/2019 at 2:04 PM, DaveStLou said:

Following these instructions, it's working for me now...

How do I run the download line in FreeBSD?

I cannot see any of those setup menus buy polyglot seems to service ISY OK.

[gviliunas]

@larryllix Are you asking for the command line to upgrade Polisy via a Putty ssh session?

if so, 

sudo pkg update && sudo pkg upgrade

After entering this, you will be prompted for the admin password. It is "admin"

[larryllix]

6 hours ago, gviliunas said:

@larryllix Are you asking for the command line to upgrade Polisy via a Putty ssh session?

if so, 

sudo pkg update && sudo pkg upgrade

After entering this, you will be prompted for the admin password. It is "admin"

I have done the O/S upgrade and udx install/start, but can't figure out how to run line 2 and 3 from @Michel Kohanim 's instructions as shown below.
My credentials did not change with this.
I cannot see my Polyglot config. The command just hangs on "loading config.....", so I figured I have to complete the instructions from Michel.

 

On 12/19/2019 at 1:09 PM, Michel Kohanim said:

Hi everyone, to install udx without having to worry about dependencies, please:

1. If you have already installed udx:
sudo service udx stop
sudo pkg delete udx
2. Download https://udx.s3-us-west-2.amazonaws.com/pkg/1.0.26/udx-1.0.26_4.txz
3. Go to the directory in 2:
sudo pkg install ./udx-1.0.26_4.txz

With kind regards,
Michel

 

Here is where my sticks now.

 

 

[simplextech]

4 hours ago, larryllix said:

1. If you have already installed udx:
sudo service udx stop
sudo pkg delete udx
2. Download https://udx.s3-us-west-2.amazonaws.com/pkg/1.0.26/udx-1.0.26_4.txz
3. Go to the directory in 2:
sudo pkg install ./udx-1.0.26_4.txz

For step 2.

SSH into the Polisy and change to a temp directory like /tmp

wget  https://udx.s3-us-west-2.amazonaws.com/pkg/1.0.26/udx-1.0.26_4.txz

If wget is not installed then: sudo pkg install wget

then do the pkg install of the file as shown in step 3.

[larryllix]

1 minute ago, simplextech said:

For step 2.

SSH into the Polisy and change to a temp directory like /tmp

wget  https://udx.s3-us-west-2.amazonaws.com/pkg/1.0.26/udx-1.0.26_4.txz

If wget is not installed then: sudo pkg install wget

then do the pkg install of the file as shown in step 3.

Is this only to install udx, as it already shows it as runnng?

[simplextech]

Just now, larryllix said:

Is this only to install udx, as it already shows it as runnng?

Yes.  that was only for installing UDX.  If UDX is already installed and running DO NOT do that.

 

[MWareman]

On 1/2/2020 at 4:53 AM, larryllix said:

I have done the O/S upgrade and udx install/start, but can't figure out how to run line 2 and 3 from @Michel Kohanim 's instructions as shown below.
My credentials did not change with this.
I cannot see my Polyglot config. The command just hangs on "loading config.....", so I figured I have to complete the instructions from Michel.

 

 

Here is where my sticks now.

 

 

@larryllix - Is your Polisy beeping every few seconds as well?  If so - your symptoms exactly match mine...

[Michel Kohanim]

All,

You don't have to download UDX; that's only for the geek batch. So, @larryllix, please do NOT do anything. And, if you have, please see below:

For Geek batch:

sudo service udx stop
sudo pkg delete udx
sudo pkg install udx
sudo service udx start

@MWareman, I responded to your ticket.

With kind regards,
Michel
 

[MWareman]

10 minutes ago, Michel Kohanim said:

 

@MWareman, I responded to your ticket.

With kind regards,
Michel
 

Thank you!  I just responded. 

Since the top suspect appears to be the MongoDB - is there a way to definitively determine this? We tried 'deleting' it and letting it recreate - but the issue was still there. Also - there appear to be no operational issues with Polyglot (other than the Polisy settings daemon not working). Wouldn't MongoDB corruption affect Polyglot in other ways?

Michael.

[MWareman]

@larryllix Did you import a custom SSL cert into Polyglot?

I did - and just wanted to see if this was common between us..

Thanks!

Michael.

[garybixler]

I did the latest updates on Polisy a little while ago and now I have no access what so ever to the Polisy after configuring the new IP config pages. Tried everything.

1 Used the reset to DHCP switch on the front.

2  No hardware address shows up on the switch.

3 Logs on APs sh no clients trying to access. Tried setting them to open and still no access.

4 Removed wi-fi card with not results.

Looks like all interfaces are disabled. Appreciate any suggestions

Thanks Gary

Light and Beep pattern when powered up.

3 lights solid

1 light solid

After 10 to 15 seconds

Beep

3 lights flash once

2 lights flash sever times

beep

1 light solid normal state