Jump to content

Initial Feeback


Michel Kohanim

Recommended Posts

2 hours ago, Michel Kohanim said:

@garybixler,

Can you please reboot Polisy and let me know whether or not you still get duplicate events.

With kind regards,
Michel

Michel,

No duplicate events after reboot. It only seemed to have happened after doing the last upgrade (2.2.5) until I rebooted Polisy after that.

Thanks

Gary

Link to comment
Share on other sites

I was able to get my nodeservers all migrated to Polisy. With only a couple of issues (once I got past the login snafu):

  • HarmonyHub - Required manual copy of the yaml and hubs.json files as @Jimbo has noted.
  • HolidaysGoogle - I needed to re-authenticate wtih Google.
  • WeatherPoly - I had to point my CumulusMx custom http url to the polisy IP the nodeserver can see the data there.
  • Presence-Poly is complaining about about the missing bluetooth module as others have noted. Once I get that resolved, I will be back to normal.

 

Link to comment
Share on other sites

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:
92a0178c2aba27b0758a9e615d9a3c55.jpg

It’s happening on Chrome/Windows and iPad/Safari for me...

Link to comment
Share on other sites

@MWareman,

We do have 2.2.6 and still testing which should solve some of these issues. If you wish to give it a try:

sudo pkg update && sudo pkg upgrade

We also made going between dev (beta) and production easier. But, that will require installing polyglot-beta.

Also, we have a resize script to give us back the 24GB not currently used on the SSD.

With kind regards,
Michel

Link to comment
Share on other sites

3 hours ago, Michel Kohanim said:

@MWareman,

We do have 2.2.6 and still testing which should solve some of these issues. If you wish to give it a try:

sudo pkg update && sudo pkg upgrade

We also made going between dev (beta) and production easier. But, that will require installing polyglot-beta.

Also, we have a resize script to give us back the 24GB not currently used on the SSD.

With kind regards,
Michel

image.png.a125b4d25ef1772c6ed8521c8e8b889c.png

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?

image.png.e66d449c89096df5f9f8a4bf5a5f0739.png

 

Link to comment
Share on other sites

12 hours ago, Michel Kohanim said:

@MWareman,

We do have 2.2.6 and still testing which should solve some of these issues. If you wish to give it a try:

sudo pkg update && sudo pkg upgrade

We also made going between dev (beta) and production easier. But, that will require installing polyglot-beta.

Also, we have a resize script to give us back the 24GB not currently used on the SSD.

With kind regards,
Michel

Installed, powered up without any snags or delay, and running fine. Installed polyglot v2.2.5 with beta selected. v2.2.6 not offered.

Thanks!!

Link to comment
Share on other sites

Michel

 Hi, I just did the latest update and the duplicate events returned on all nodes after restarting Polyglot.

Example for wireless tags.

2019-11-06 07:03:34,108 [Controller] [DEBUG] Home:0 Tesla:abe9250b593a93:wTag12F:set_seconds: 193

2019-11-06 07:03:34,108 [Controller] [DEBUG] Home:0 Tesla:abe9250b593a93:wTag12F:set_seconds: 193

2019-11-06 07:03:34,110 [Controller] [INFO ] Updating Driver abe9250b593a93 - GV14: 193, uom: 25

2019-11-06 07:03:34,110 [Controller] [INFO ] Updating Driver abe9250b593a93 - GV14: 193, uom: 25

2019-11-06 07:03:34,112 [Controller] [DEBUG] Home:Light Sensor 7:6d16a649e2f3e2:wTag26F:set_seconds: 193

2019-11-06 07:03:34,112 [Controller] [DEBUG] Home:Light Sensor 7:6d16a649e2f3e2:wTag26F:set_seconds: 193

2019-11-06 07:03:34,112 [Controller] [INFO ] Updating Driver 6d16a649e2f3e2 - GV14: 193, uom: 25

2019-11-06 07:03:34,112 [Controller] [INFO ] Updating Driver 6d16a649e2f3e2 - GV14: 193, uom: 25

 

I then did a power reset on the Polisy and all  was good after that. No duplicates.

Thanks Gary

 

Link to comment
Share on other sites

No duplicates after restarting polyglot. It all seems to clear after power resetting the Polisy. If it happens again after an upgrade I will just restart Polyglot again after the initial restart without power resetting the Polisy to see if that alone will clear any duplicates.

I was using the restart from the webpage.

Thanks Gary

Link to comment
Share on other sites

I've observered that MQTTS client disconnects and connects over and over again in the Polyglot logs as frequently as once every second.

2019-11-6 11:29:13 [polyglot] info: MQTTS: Client Disconnected:
2019-11-6 11:29:13 [polyglot] info: MQTTS: Client Connected:

I stopped my AVRemote nodeserver and the behavior stopped. This wasn't happening prior to migrating. Would that indicate it's a nodeserver issue or a Polyglot issue?

Link to comment
Share on other sites

Hmmm. I'm also observing similar behavior in the  Ping nodeserver. This from that nodeserver's log:

2019-11-06 13:02:06,858 [Interface ] [INFO ] Sent Connected message to Polyglot
2019-11-06 13:02:07,590 [Interface ] [INFO ] MQTT Connected with result code 0 (Success)
2019-11-06 13:02:07,592 [Interface ] [INFO ] MQTT Subscribing to topic: udi/polyglot/ns/1 - MID: 183 Result: 0
2019-11-06 13:02:07,593 [Interface ] [INFO ] MQTT Unexpected disconnection. Trying reconnect.
2019-11-06 13:02:07,593 [Interface ] [INFO ] MQTT Subscribing to topic: udi/polyglot/connections/polyglot - MID: 184 Result: 0
2019-11-06 13:02:07,594 [Interface ] [INFO ] Sent Connected message to Polyglot
2019-11-06 13:02:07,945 [Interface ] [INFO ] MQTT Connected with result code 0 (Success)
2019-11-06 13:02:07,947 [Interface ] [INFO ] MQTT Subscribing to topic: udi/polyglot/ns/1 - MID: 159 Result: 0
2019-11-06 13:02:07,948 [Interface ] [INFO ] MQTT Subscribing to topic: udi/polyglot/connections/polyglot - MID: 160 Result: 0
2019-11-06 13:02:07,950 [Interface ] [INFO ] Sent Connected message to Polyglot
2019-11-06 13:02:07,950 [Interface ] [INFO ] MQTT Unexpected disconnection. Trying reconnect.
2019-11-06 13:02:08,677 [Interface ] [INFO ] MQTT Connected with result code 0 (Success)
2019-11-06 13:02:08,679 [Interface ] [INFO ] MQTT Subscribing to topic: udi/polyglot/ns/1 - MID: 58 Result: 0
2019-11-06 13:02:08,680 [Interface ] [INFO ] MQTT Unexpected disconnection. Trying reconnect.
 
 
Link to comment
Share on other sites

I too was experiencing this.  I never did determine exactly which nodeserver was causing it. (I have Sonos, MyQ, AVRemote and Meteobridge). I restarted Polyglot several times and it just stopped displaying those errors, no idea why.  Interestingly, whether related or not, during this time I could not get ISY to talk to the SONOS nodeserver (it worked the other way around - Polyglot to SONOS).  Once this disconnect/reconnect thing stopped, SONOS began working properly, so maybe it was the SONOS nodeserver that was causing it.

Link to comment
Share on other sites

Installed my Polisy today, after my wife brought it home from the USA late last week. Other than the problem with loose MSATA and Wireless cards inside that had to be rectified before startup, all went well. It didn't take long to find the device, as Ubiquiti's UniFi software controller promptly reported it.

DHCP correctly got addressing from our network, which was a pleasant surprise as we run a fair-sized Ubiquiti network here with multiple subnets, and nothing in the 192.168.x.y ranges except our guest network. That said, Polisy is attempting to auto-connect to our guest SSID for its wireless connection. I assume that's because the SSID handling guests is open with no Internet access until authorized. So Polisy gets assigned a guest ip address and then does nothing, as far as wireless is concerned. Will there be a means of joining a specific wireless network?

Updates via command line all went well, and it appears that I've got current everything that needs to be present. I expect I avoided a few issues because I'm later than many in installing.

Some observations:

  • Fit and finish on the case is excellent and the metallic blue color is great. 8) Almost a shame it's gonna live in our utility room.
  • There was no white label on the appropriate Ethernet port as stated in the Quick Setup Guide, not that that's a problem. :shock:
  • There are no labels on the box whatsoever, other than the "Polisy" name and UD logo.
  • No slots for wall mounting. :-( 

I noticed somewhere in the earlier messages on this thread that the DB-9 is for possible use as a connection to the PLM. Will there be support for the USB version of the PLM? Also, am I correct that there's a slot for an SD card inside? If so, what's the intent? Ditto for the two USB 3 ports. I might well have missed discussion of those elsewhere since I haven't read many other threads on the Polisy box yet, so sorry if this is well-known already.

And one last note: This device is installed in San Felipe, Baja, Mexico, and works just fine, for what that's worth. Just because we're retired expats doesn't mean we can't have our house as smart as we'd like. :-)

Link to comment
Share on other sites

@asbril, it should be.
@MWareman, apologies for not being clear. If you want to install the beta, you must do:
sudo pkg delete polyglot 
sudo pkg install polyglot-beta
With kind regards,
Michel


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...
Link to comment
Share on other sites

@DaveStLou and @glarsen,

Can you please send your Polisy logs to support@universal-devices.com ?

@MexicanRadio, thanks so very much for the feedback. Please send an email to sales@universal-devices.com so that we can extend your warranty due to the loose components inside.

1. Yes, you will be able to configure your WiFi and it will connect to the correct SSID
2. Yes, we are planning to support USB PLM (amongst other things). The problem with USB PLM is that it's Wireless only
3. SD Card slot inside: we don't plan on using it at all. That's the whole point of using SSD instead

With kind regards,
Michel

Link to comment
Share on other sites

On 11/6/2019 at 4:43 PM, glarsen said:

I too was experiencing this.  I never did determine exactly which nodeserver was causing it. (I have Sonos, MyQ, AVRemote and Meteobridge). I restarted Polyglot several times and it just stopped displaying those errors, no idea why.  Interestingly, whether related or not, during this time I could not get ISY to talk to the SONOS nodeserver (it worked the other way around - Polyglot to SONOS).  Once this disconnect/reconnect thing stopped, SONOS began working properly, so maybe it was the SONOS nodeserver that was causing it.

Interesting I have the WeatherPoly (similar to Meteobridge) and AVRemote amongst others.

Link to comment
Share on other sites

On 11/7/2019 at 6:15 AM, MWareman said:

 


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

 

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.

Link to comment
Share on other sites

Michel

Hi, I physically relocated a device supported by a node server. After moving I had to restart Polyglot to get it to poll again. I may have restarted Polyglot a second or third time. 

What I started to see on the logs of all the nodes was tripple events. Example:

2019-11-08 10:18:04,683 [Controller] [DEBUG] Home:1 test:11ce08fb58c09a:wTag12F:set_seconds: 207

2019-11-08 10:18:04,683 [Controller] [DEBUG] Home:1 test:11ce08fb58c09a:wTag12F:set_seconds: 207

2019-11-08 10:18:04,683 [Controller] [DEBUG] Home:1 test:11ce08fb58c09a:wTag12F:set_seconds: 207
2019-11-08 10:18:04,684 [Controller] [INFO ] Updating Driver 11ce08fb58c09a - GV14: 207, uom: 25
2019-11-08 10:18:04,684 [Controller] [INFO ] Updating Driver 11ce08fb58c09a - GV14: 207, uom: 25
2019-11-08 10:18:04,684 [Controller] [INFO ] Updating Driver 11ce08fb58c09a - GV14: 207, uom: 25
2019-11-08 10:18:04,686 [Controller] [DEBUG] Home:0 Tesla:abe9250b593a93:wTag12F:set_seconds: 0
2019-11-08 10:18:04,686 [Controller] [DEBUG] Home:0 Tesla:abe9250b593a93:wTag12F:set_seconds: 0
2019-11-08 10:18:04,686 [Controller] [DEBUG] Home:0 Tesla:abe9250b593a93:wTag12F:set_seconds: 0
2019-11-08 10:18:04,687 [Controller] [DEBUG] Home:Light Sensor 7:6d16a649e2f3e2:wTag26F:set_seconds: 2
2019-11-08 10:18:04,687 [Controller] [DEBUG] Home:Light Sensor 7:6d16a649e2f3e2:wTag26F:set_seconds: 2
2019-11-08 10:18:04,687 [Controller] [DEBUG] Home:Light Sensor 7:6d16a649e2f3e2:wTag26F:set_seconds: 2
2019-11-08 10:18:04,688 [Controller] [INFO ] Updating Driver 6d16a649e2f3e2 - GV14: 2, uom: 25
2019-11-08 10:18:04,688 [Controller] [INFO ] Updating Driver 6d16a649e2f3e2 - GV14: 2, uom: 25
2019-11-08 10:18:04,688 [Controller] [INFO ] Updating Driver 6d16a649e2f3e2 - GV14: 2, uom: 25
 
I also entered this command requested in an earlier request. 

[admin@polisy ~]$ ps -aux | grep poly
polyglot 27773   8.8  2.8 724668 115152  -  S    10:06       0:43.06 /usr/local
polyglot 27774   0.2  0.6  44728  26536  -  Is   10:06       0:03.45 python3 ./
polyglot  1189   0.0  1.8 306628  72892  -  Ss   Wed07       1:04.56 node ./nod
polyglot  1830   0.0  0.1  10768   2336  -  Is   Wed09       0:00.01 daemon: /u
polyglot  1834   0.0  1.9 312804  78396  -  Ss   Wed09       2:16.38 node ./nod
polyglot 26133   0.0  1.7 303696  69532  -  Ss   09:05       0:09.31 node ./nod
polyglot 27775   0.0  0.7  50604  30192  -  Is   10:06       0:04.29 python3 ./
polyglot 27776   0.0  1.5 295852  63568  -  Ss   10:06       0:04.79 node ./nod
admin    27801   0.0  0.1  11248   2696  0  S+   10:12       0:00.01 grep poly
[admin@polisy ~]$

I did another Polyglot restart from SSH but still shows triple events. 

I did a power reset on the Polisy and that cleared the triple logging.

Reentered  previous command.

[admin@polisy ~]$ ps -aux | grep poly
polyglot 1062  13.1  3.4 727004 142828  -  S    10:29    0:30.85 /usr/local/bin
polyglot 1214   0.5  1.5 294736  62908  -  Ss   10:29    0:04.78 node ./nodeser
polyglot 1212   0.1  0.7  45716  27436  -  Is   10:29    0:03.48 python3 ./wll.
polyglot 1061   0.0  0.1  10768   2184  -  Is   10:29    0:00.00 daemon: /usr/l
polyglot 1213   0.0  0.7  51172  30636  -  Is   10:29    0:04.03 python3 ./wire
admin    1234   0.0  0.1  11248   2696  0  S+   10:33    0:00.01 grep poly
[admin@polisy ~]$

 

Thanks Gary
 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...