Skip to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

garybixler

Members

Everything posted by garybixler

  1. GOOD NEWS! I think everything is now working. I had 4 copies of each NS running. I checked earlier today and there were no duplicates. Don't know how additional NSs got started. I will try a fresh install later and see how that goes. Thanks so much for all your effort. Gary
  2. I tried 3.0.11 but still having issues. When first coming up after authorization it seemed to stall after loading one tag. I attached that log. I tried setting Monitor Tags = true but still didn't continue. Did a restart and then discover on admin and all tags loaded. But not all data is correct. Temp is in Celsius or some number close to that for one tag. Probably a restart will fix it. Thanks Gary UPDATE: I think I see multiple node servers running. Will try rebooting. New Text Document.txt
  3. After about 40 minutes the log file popped up as a text file to save. I do have the file but it is 123 MB. Dare I attach such a large file? I could copy paste the desired time span. Thanks Gary
  4. Did you mean the Real-time Polyglot log file? If so it doesn't load into the log area.
  5. This log is rather large but it is from a new reinstall. New Text Document.txt
  6. I did a reinstall and copied the log where the NS seems to come to halt. The first two tags only loaded. Will need to do several restarts and a discover or two to get all the tags and updating. Thanks Gary New Text Document.txt
  7. Maybe some good news. After changing the short poll timer from 5 to 15 seconds and doing a restart things may be working better. The tags seem to be getting updated. Will need to keep checking to verify however. Thanks Gary
  8. Unfortunately not quite working. Only the first two tages are loaded even though they are all shown in the log which I attached. Also the temps are show in celsius. Also the update timer isn't being updated unless the tag is queried. I did get the other two tags to load with a couple of discoveries. Also very strange after they loaded all tags displayed in fahrenheit. Nothing gets updated in the Admin console unless they are queried. Monitoring tags is true. Thanks Gary New Text Document.txt
  9. Same problem. @bpwwerfigured it out and showed me the method in which to show and Kill the duplicate NSs. I thought I tried rebooting but may be mistaking on that.
  10. I included the admin screen shot. The Seconds Since Update should be no longer that 30 secs.
  11. Update: After the third restart the nodes are updating but where tag id 1 and 2 names are reversed. Also I was able to then discover and get the last two tages. The tags are not accurately updating however. CORRECTION: I think the tag names are correct according to the temp readings when I query the tag. But they aren't' updating any data.
  12. Unfortunately the results are the same in version 3.0.8. I deleted the NS and reinstalled. Restarted the Admin console but only the first two tags were installed. Can't get the others through discovery and the first two aren't updating even though I have Monitor Tags true. I attached the entire log. Thanks Gary New Text Document.txt
  13. Hi, I have the Wireless Tag NS up and running. There seems to be a miss match between tag id 1 and 2. I have tag 1 updating every 30 sec and tag 2 updating every 5 min. What is puzzling is that the names are reversed from what is configured at the Tag web server. The other 2 tags are correct. When the NS is first installed it only gets 2 tags out of 4. Later I go in and do a discover and sometimes the other 2 tages will appear. It may take several tries to find the other tags. I have rebooted and reinstalled but always the same. Maybe this is because I have associated a tag that isn't defined yet. The new leak sensor. Thanks for any assistance. Gary
  14. @Jimbo Last night I updated to PG3's latest version and this morning discovered that ELK basically stopped running. I included some of the log. I did try reinstalling but it never gets a connected status. Thanks Gary New Text Document.txt
  15. Thanks so much. Everything looks perfect.
  16. This is the log from the start in PG2. New Text Document.txt
  17. This is what's returned when I do http://192.168.30.63/v1/current_conditions. New Text Document.txt
  18. Update: The log wasn't in debug. A new log after restart. New Text Document.txt
  19. After installing the new version it started but basically hung up on node 2. I included the log. Thanks Gary New Text Document.txt
  20. @bpwwer Yes, the unit itself has an indoor temp and humidity sensor. I was wondering because the PG2 version has an indoor node. Only node one is loaded into the PG3 version. I added a couple of snippets from the PG2 version. Thanks Gary
  21. @bpwwer Hi, Weather link has been running for about a day on PG3 but it stopped updating at about 3 AM. I copied the log shortly before the updating stopped. Also restart didn't work. Had to stop start restart. Thanks Gary New Text Document.txt
  22. No go and showing these two errors. I'll wait for the PG3 update. No hurry. Thanks, Gary REST Server False not running. check Log for ERROR Unable to start server, no NSDATA returned...
  23. I too did the 100 package update and no longer get a response back from check polisy for updates or that the updates were successful. Also it appears that PG3 NSs have stopped logging after the initial node server startup.
  24. Just as a test I moved it back to PG2 and copied the log. Thanks Gary 2022-01-12 21:31:56,228 MainThread polyinterface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-01-12 21:31:57,123 MainThread polyinterface INFO polyinterface:init_interface: Received Config from STDIN. 2022-01-12 21:31:57,125 MainThread polyinterface INFO __init__:<module>: UDI Polyglot v2 Interface 2.1.0 Starting... 2022-01-12 21:31:57,688 MainThread polyinterface DEBUG polyinterface:get_network_interface: gws: {'default': {2: ('192.168.30.1', 'igb0')}, 2: [('192.168.30.1', 'igb0', True)]} 2022-01-12 21:31:57,689 MainThread polyinterface DEBUG polyinterface:get_network_interface: gw: default=('192.168.30.1', 'igb0') 2022-01-12 21:31:57,689 MainThread polyinterface DEBUG polyinterface:get_network_interface: ifad: igb0=[{'addr': '192.168.30.57', 'netmask': '255.255.255.0', 'broadcast': '192.168.30.255'}] 2022-01-12 21:31:57,690 MainThread polyinterface INFO polyinterface:__init__: Connect: Network Interface: {'addr': '192.168.30.57', 'netmask': '255.255.255.0', 'broadcast': '192.168.30.255'} 2022-01-12 21:31:57,691 Interface polyinterface INFO polyinterface:_startMqtt: Connecting to MQTT... localhost:1883 2022-01-12 21:31:57,721 MQTT polyinterface INFO polyinterface:_connect: MQTT Connected with result code 0 (Success) 2022-01-12 21:31:57,723 MQTT polyinterface INFO polyinterface:_connect: MQTT Subscribing to topic: udi/polyglot/ns/1 - MID: 1 Result: 0 2022-01-12 21:31:57,723 MQTT polyinterface INFO polyinterface:_connect: MQTT Subscribing to topic: udi/polyglot/connections/polyglot - MID: 2 Result: 0 2022-01-12 21:31:57,724 MQTT polyinterface INFO polyinterface:_connect: Sent Connected message to Polyglot 2022-01-12 21:31:57,728 MQTT polyinterface INFO polyinterface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-01-12 21:31:57,730 MQTT polyinterface INFO polyinterface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2022-01-12 21:31:57,771 MQTT polyinterface INFO polyinterface:addNode: Adding node WeatherLink(weather) 2022-01-12 21:31:57,773 MQTT polyinterface INFO polyinterface:_gotConfig: Waiting on Controller node to be added....... 2022-01-12 21:31:57,775 NodeServer polyinterface INFO wll:start: Starting node server 2022-01-12 21:31:57,775 NodeServer polyinterface INFO polyinterface:saveCustomParams: Sending customParams to Polyglot. 2022-01-12 21:31:57,777 NodeServer polyinterface INFO polyinterface:addNotice: Sending addnotice to Polyglot: {'key': None, 'value': 'WeatherLink IP Address parameter must be set'} 2022-01-12 21:31:57,778 NodeServer polyinterface INFO wll:start: Node server started 2022-01-12 21:31:57,779 NodeServer polyinterface DEBUG wll:query_conditions: request = http:///v1/current_conditions 2022-01-12 21:31:57,785 NodeServer polyinterface INFO wll:query_conditions: Skipping connection because we aren't configured yet. 2022-01-12 21:32:26,940 MQTT polyinterface INFO polyinterface:removeNotice: Sending removenotice to Polyglot for index {'key': '0'} 2022-01-12 21:32:36,156 MQTT polyinterface DEBUG polyinterface:_message: Received stop from Polyglot... Shutting Down. 2022-01-12 21:32:36,157 MQTT polyinterface INFO polyinterface:stop: Disconnecting from MQTT... localhost:1883 2022-01-12 21:32:36,158 MQTT polyinterface INFO wll:stop: Stopping node server 2022-01-12 21:32:36,160 MQTT polyinterface INFO polyinterface:_disconnect: MQTT Graceful disconnection. 2022-01-12 21:32:36,161 MQTT polyinterface DEBUG polyinterface:_startMqtt: MQTT Done: 2022-01-12 21:32:39,674 MainThread polyinterface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-01-12 21:32:40,949 MainThread polyinterface INFO polyinterface:init_interface: Received Config from STDIN. 2022-01-12 21:32:40,951 MainThread polyinterface INFO __init__:<module>: UDI Polyglot v2 Interface 2.1.0 Starting... 2022-01-12 21:32:41,544 MainThread polyinterface DEBUG polyinterface:get_network_interface: gws: {'default': {2: ('192.168.30.1', 'igb0')}, 2: [('192.168.30.1', 'igb0', True)]} 2022-01-12 21:32:41,545 MainThread polyinterface DEBUG polyinterface:get_network_interface: gw: default=('192.168.30.1', 'igb0') 2022-01-12 21:32:41,545 MainThread polyinterface DEBUG polyinterface:get_network_interface: ifad: igb0=[{'addr': '192.168.30.57', 'netmask': '255.255.255.0', 'broadcast': '192.168.30.255'}] 2022-01-12 21:32:41,546 MainThread polyinterface INFO polyinterface:__init__: Connect: Network Interface: {'addr': '192.168.30.57', 'netmask': '255.255.255.0', 'broadcast': '192.168.30.255'} 2022-01-12 21:32:41,547 Interface polyinterface INFO polyinterface:_startMqtt: Connecting to MQTT... localhost:1883 2022-01-12 21:32:41,583 MQTT polyinterface INFO polyinterface:_connect: MQTT Connected with result code 0 (Success) 2022-01-12 21:32:41,584 MQTT polyinterface INFO polyinterface:_connect: MQTT Subscribing to topic: udi/polyglot/ns/1 - MID: 1 Result: 0 2022-01-12 21:32:41,584 MQTT polyinterface INFO polyinterface:_connect: MQTT Subscribing to topic: udi/polyglot/connections/polyglot - MID: 2 Result: 0 2022-01-12 21:32:41,585 MQTT polyinterface INFO polyinterface:_connect: Sent Connected message to Polyglot 2022-01-12 21:32:41,589 MQTT polyinterface INFO polyinterface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-01-12 21:32:41,592 MQTT polyinterface INFO polyinterface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2022-01-12 21:32:41,637 NodeServer polyinterface INFO wll:start: Starting node server 2022-01-12 21:32:41,641 NodeServer polyinterface INFO polyinterface:saveCustomParams: Sending customParams to Polyglot. 2022-01-12 21:32:41,798 NodeServer polyinterface INFO wll:start: Node server started 2022-01-12 21:32:41,842 NodeServer polyinterface INFO wll:start: Creating node for indoor conditions 2022-01-12 21:32:41,844 NodeServer polyinterface INFO polyinterface:addNode: Adding node Indoor(indoor) 2022-01-12 21:32:41,846 NodeServer polyinterface DEBUG wll:query_conditions: request = http://192.168.30.63/v1/current_conditions 2022-01-12 21:32:41,894 NodeServer polyinterface DEBUG wll:query_conditions: {'data': {'did': '001D0A710A19', 'ts': 1642041161, 'conditions': [{'lsid': 246652, 'data_structure_type': 1, 'txid': 1, 'temp': 30.5, 'hum': 78.4, 'dew_point': 24.6, 'wet_bulb': 28.1, 'heat_index': 30.5, 'wind_chill': 30.5, 'thw_index': 30.5, 'thsw_index': None, 'wind_speed_last': 0.0, 'wind_dir_last': 0, 'wind_speed_avg_last_1_min': 0.0, 'wind_dir_scalar_avg_last_1_min': 0, 'wind_speed_avg_last_2_min': 0.0, 'wind_dir_scalar_avg_last_2_min': 0, 'wind_speed_hi_last_2_min': 0.0, 'wind_dir_at_hi_speed_last_2_min': 0, 'wind_speed_avg_last_10_min': 0.0, 'wind_dir_scalar_avg_last_10_min': 0, 'wind_speed_hi_last_10_min': 0.0, 'wind_dir_at_hi_speed_last_10_min': 0, 'rain_size': 1, 'rain_rate_last': 0, 'rain_rate_hi': 0, 'rainfall_last_15_min': 0, 'rain_rate_hi_last_15_min': 0, 'rainfall_last_60_min': 0, 'rainfall_last_24_hr': 0, 'rain_storm': 0, 'rain_storm_start_at': None, 'solar_rad': None, 'uv_index': None, 'rx_state': 0, 'trans_battery_flag': 0, 'rainfall_daily': 0, 'rainfall_monthly': 58, 'rainfall_year': 58, 'rain_storm_last': 30, 'rain_storm_last_start_at': 1641656881, 'rain_storm_last_end_at': 1641866460}, {'lsid': 246588, 'data_structure_type': 4, 'temp_in': 70.2, 'hum_in': 47.1, 'dew_point_in': 49.1, 'heat_index_in': 68.3}, {'lsid': 246587, 'data_structure_type': 3, 'bar_sea_level': 30.052, 'bar_trend': 0.021, 'bar_absolute': 29.394}]}, 'error': None}
  25. Very odd. It does work fine updating every minute. Also I get an immediate return using a browser. Also sometimes when I use resources for other devices I get a tcp error but the resource works as intended.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.