bigDvette

I've setup a program to notify me when it happens, it may go weeks or a month.

I've had to turn off all my scenes that use an elk output as a trigger. It seems they randomly reset/go on-off audit triggers my scene which in this case shuts down the whole house.

FYI - even when on current version, dashboard says there is a new version available. Not sure what causes that but the store says 4.0.4 and the node server detail screen says 4.0.4.

I also have all the zones and schedules and will keep an eye on it.

Thanks! It's my last PG2

the other day all my node server except one did not show the product store blue tag. I couldn't get them to come back. I deleted and re-installed and they came back. I was in a hurry and didn't feel like reporting it. However I noticed at the time my purchases was empty as well. Today I saw a message come by. I knew I had a mix of trial and purchased node servers previously and was trying to figure which ones I had bought while the bugs were being worked out on others. here is the error. 4/22/2022, 16:28:59 [pg3] error: unhandledRejection REPORT THIS!: [object Promise], reason: TypeError: store.getPurchaseEntry is not a function

That made it 1 setup further. The error now seems to be about the controller (not bridge) not being a parent. Discovering nodes on Rachio Controller Rachio-Lake (80a589e0a70c) 2022-04-22 15:35:35,866 Thread-8 udi_interface INFO rachio-poly:discover: 16 Rachio zones found on "Rachio-Lake" controller. Adding to ISY 2022-04-22 15:35:35,867 Thread-8 udi_interface ERROR rachio-poly:discover: Error discovering and adding Zones on Rachio Controller Rachio-Lake (80a589e0a70c): 'RachioController' object has no attribute 'parent' 2022-04-22 15:35:35,867 Thread-8 udi_interface INFO rachio-poly:discover: 2 Rachio schedules found on "Rachio-Lake" controller. Adding to ISY 2022-04-22 15:35:35,868 Thread-8 udi_interface ERROR rachio-poly:discover: Error discovering and adding Schedules on Rachio Controller Rachio-Lake (80a589e0a70c): 'RachioController' object has no attribute 'parent' 2022-04-22 15:35:35,868 Thread-8 udi_interface INFO rachio-poly:discover: 3 Rachio Flex schedules found on "Rachio-Lake" controller. Adding to ISY 2022-04-22 15:35:35,869 Thread-8 udi_interface ERROR rachio-poly:discover: Error discovering and adding Flex Schedules on Rachio Controller Rachio-Lake (80a589e0a70c): 'RachioController' object has no attribute 'parent'

What? I'm asking if there will be a VENSTAR pg3 node server since I am in the VENSTAR thread not generically.

Any chance at a PG3 Node server? Happy to beta test.

@bpwwerany doc on the custom typed config params at the bottom. See there is a save changes and refresh but no doc and no add. Just curious. I have new version setup and am testing.

I am seeing same behavior. Also, the node server is not receiving the rest call from weewx. It is setup the same, I configured the same port and on PG2 it was working fine. As said above, if you restart the node server it deletes all the nodes on ISY (you can watch them go) and then recreates them. If I hit stop it doesn't act like it stops, have to refresh the browser to see it is not running. 2-01-31 23:01:47,800 MainThread udi_interface.interface INFO interface:addNode: Adding node WeatherPoly(controller) [None] 2022-01-31 23:01:47,939 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getAll 2022-01-31 23:01:47,940 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getAll 2022-01-31 23:01:47,943 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: load {'Port': '8081', 'Units': 'us', 'IncomingUnits': 'metric', 'humidity-inside': '23', 'humidity-main': '3', 'pressure-station': '10', 'pressure-trend': '18', 'rain-daily': '9', 'rain-hourly': '47', 'rain-monthly': '19', 'rain-rate': '8', 'rain-yearly': '20', 'rain-yesterday': '21', 'temperature-dewpoint': '4', 'temperature-heatindex': '41', 'temperature-inside': '22', 'temperature-main': '2', 'temperature-max': '26', 'temperature-min': '28', 'temperature-windchill': '24', 'wind-avgwindspeed': '5', 'wind-gustdir': '46', 'wind-gustspeed': '40', 'wind-winddir': '7', 'wind-windspeed': '6'} 2022-01-31 23:01:47,945 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {} 2022-01-31 23:01:47,945 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking Port / 8081 2022-01-31 23:01:47,946 Command udi_interface.interface DEBUG interface:_handleInput: Key nsdata should be passed to node server. 2022-01-31 23:01:47,947 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking Units / us 2022-01-31 23:01:47,949 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking IncomingUnits / metric 2022-01-31 23:01:47,949 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking humidity-inside / 23 2022-01-31 23:01:47,950 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking humidity-main / 3 2022-01-31 23:01:47,951 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking pressure-station / 10 2022-01-31 23:01:47,951 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking pressure-trend / 18 2022-01-31 23:01:47,952 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-daily / 9 2022-01-31 23:01:47,952 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-hourly / 47 2022-01-31 23:01:47,953 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-monthly / 19 2022-01-31 23:01:47,954 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-rate / 8 2022-01-31 23:01:47,954 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-yearly / 20 2022-01-31 23:01:47,955 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-yesterday / 21 2022-01-31 23:01:47,956 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-dewpoint / 4 2022-01-31 23:01:47,956 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-heatindex / 41 2022-01-31 23:01:47,957 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-inside / 22 2022-01-31 23:01:47,957 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-main / 2 2022-01-31 23:01:47,958 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-max / 26 2022-01-31 23:01:47,959 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-min / 28 2022-01-31 23:01:47,959 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-windchill / 24 2022-01-31 23:01:47,960 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking wind-avgwindspeed / 5 2022-01-31 23:01:47,961 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking wind-gustdir / 46 2022-01-31 23:01:47,962 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking wind-gustspeed / 40 2022-01-31 23:01:47,962 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking wind-winddir / 7 2022-01-31 23:01:47,963 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking wind-windspeed / 6 2022-01-31 23:01:47,963 Thread-1 udi_interface.custom DEBUG custom:clear: CUSTOM: Clear ...saving 2022-01-31 23:01:47,964 Thread-1 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2022-01-31 23:01:47,965 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'notices', 'value': {}}]} 2022-01-31 23:01:47,967 Thread-1 udi_interface INFO weatherstation:set_configuration: Check for existing configuration value 2022-01-31 23:01:47,967 Thread-1 udi_interface INFO weatherstation:map_nodes: Trying to create a mapping 2022-01-31 23:01:47,968 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 23 to humidity-inside 2022-01-31 23:01:47,969 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 3 to humidity-main 2022-01-31 23:01:47,969 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 10 to pressure-station 2022-01-31 23:01:47,970 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 18 to pressure-trend 2022-01-31 23:01:47,971 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 9 to rain-daily 2022-01-31 23:01:47,971 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 47 to rain-hourly 2022-01-31 23:01:47,972 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 19 to rain-monthly 2022-01-31 23:01:47,973 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 8 to rain-rate 2022-01-31 23:01:47,973 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 20 to rain-yearly 2022-01-31 23:01:47,974 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 21 to rain-yesterday 2022-01-31 23:01:47,975 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 4 to temperature-dewpoint 2022-01-31 23:01:47,977 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getNsInfo 2022-01-31 23:01:47,978 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 41 to temperature-heatindex 2022-01-31 23:01:47,979 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getNsInfo 2022-01-31 23:01:47,980 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 22 to temperature-inside 2022-01-31 23:01:47,981 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 2 to temperature-main 2022-01-31 23:01:47,982 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 26 to temperature-max 2022-01-31 23:01:47,983 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 28 to temperature-min 2022-01-31 23:01:47,983 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 24 to temperature-windchill 2022-01-31 23:01:47,984 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 5 to wind-avgwindspeed 2022-01-31 23:01:47,984 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 46 to wind-gustdir 2022-01-31 23:01:47,985 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 40 to wind-gustspeed 2022-01-31 23:01:47,986 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 7 to wind-winddir 2022-01-31 23:01:47,986 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING 6 to wind-windspeed 2022-01-31 23:01:47,987 Thread-1 udi_interface INFO weatherstation:map_nodes: Try to create node definition profile based on config. 2022-01-31 23:01:47,989 Thread-1 udi_interface INFO write_profile:write_profile: write_profile: Writing profile/nodedef/nodedefs.xml 2022-01-31 23:01:47,993 Thread-1 udi_interface INFO write_profile:write_profile_zip: write_profile_zip: profile/version.txt as version.txt 2022-01-31 23:01:47,997 Thread-1 udi_interface INFO write_profile:write_profile_zip: write_profile_zip: profile/nls/en_us.txt as nls/en_us.txt 2022-01-31 23:01:48,000 Thread-1 udi_interface INFO write_profile:write_profile_zip: write_profile_zip: profile/editor/editors.xml as editor/editors.xml 2022-01-31 23:01:48,003 Thread-1 udi_interface INFO write_profile:write_profile_zip: write_profile_zip: profile/nodedef/nodedefs.xml as nodedef/nodedefs.xml 2022-01-31 23:01:48,006 Thread-1 udi_interface INFO write_profile:write_profile: write_profile: done. 2022-01-31 23:01:48,007 Thread-1 udi_interface.interface INFO interface:installprofile: Sending Install Profile command to Polyglot. 2022-01-31 23:01:48,007 Thread-1 udi_interface.interface WARNING interface:installprofile: installprofile() is deprecated. Use updateProfile() instead. 2022-01-31 23:01:48,008 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'installprofile': {'reboot': False}} 2022-01-31 23:01:48,010 Thread-1 udi_interface INFO weatherstation:discover: Creating nodes. 2022-01-31 23:01:48,011 Thread-1 udi_interface INFO weatherstation:discover: Creating Temperature node 2022-01-31 23:01:48,013 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-31 23:01:48,013 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Temperatures(temperature) [None] 2022-01-31 23:01:48,015 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-31 23:01:48,016 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'temperature', 'name': 'Temperatures', 'nodeDefId': 'temperature', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV0', 'value': 0, 'uom': 17}, {'driver': 'GV2', 'value': 0, 'uom': 17}, {'driver': 'GV4', 'value': 0, 'uom': 17}, {'driver': 'ST', 'value': 0, 'uom': 17}, {'driver': 'GV15', 'value': 0, 'uom': 17}, {'driver': 'GV16', 'value': 0, 'uom': 17}, {'driver': 'GV1', 'value': 0, 'uom': 17}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,019 Thread-1 udi_interface INFO weatherstation:discover: Creating Humidity node 2022-01-31 23:01:48,020 Thread-1 udi_interface.node DEBUG node:_updateDrivers: Update humidity default ST to 0 / 51 2022-01-31 23:01:48,022 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2022-01-31 23:01:48,022 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Humidity(humidity) [None] 2022-01-31 23:01:48,024 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2022-01-31 23:01:48,025 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'humidity', 'name': 'Humidity', 'nodeDefId': 'humidity', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV0', 'value': 0, 'uom': 51}, {'driver': 'ST', 'value': 0, 'uom': 51}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,026 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {} 2022-01-31 23:01:48,028 Thread-1 udi_interface INFO weatherstation:discover: Creating Pressure node 2022-01-31 23:01:48,030 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Barometric Pressure(pressure) [None] 2022-01-31 23:01:48,030 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'pressure', 'name': 'Barometric Pressure', 'nodeDefId': 'pressure', 'primaryNode': 'controller', 'drivers': [{'driver': 'ST', 'value': 0, 'uom': 23}, {'driver': 'GV1', 'value': 0, 'uom': 25}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,032 Thread-1 udi_interface INFO weatherstation:discover: Creating Wind node 2022-01-31 23:01:48,033 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Wind(wind) [None] 2022-01-31 23:01:48,034 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'wind', 'name': 'Wind', 'nodeDefId': 'wind', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV4', 'value': 0, 'uom': 48}, {'driver': 'GV2', 'value': 0, 'uom': 14}, {'driver': 'GV1', 'value': 0, 'uom': 48}, {'driver': 'GV0', 'value': 0, 'uom': 14}, {'driver': 'ST', 'value': 0, 'uom': 48}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,036 Thread-1 udi_interface INFO weatherstation:discover: Creating Precipitation node 2022-01-31 23:01:48,037 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Precipitation(rain) [None] 2022-01-31 23:01:48,038 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'rain', 'name': 'Precipitation', 'nodeDefId': 'precipitation', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV1', 'value': 0, 'uom': 105}, {'driver': 'GV0', 'value': 0, 'uom': 105}, {'driver': 'GV3', 'value': 0, 'uom': 105}, {'driver': 'ST', 'value': 0, 'uom': 24}, {'driver': 'GV4', 'value': 0, 'uom': 105}, {'driver': 'GV6', 'value': 0, 'uom': 105}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,039 Thread-1 udi_interface INFO weatherstation:discover: Deleting orphaned light node 2022-01-31 23:01:48,040 Thread-1 udi_interface.interface INFO interface:delNode: Removing node light 2022-01-31 23:01:48,041 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'light'}]} 2022-01-31 23:01:48,042 Thread-1 udi_interface INFO weatherstation:discover: Deleting orphaned lightning node 2022-01-31 23:01:48,043 Thread-1 udi_interface.interface INFO interface:delNode: Removing node lightning 2022-01-31 23:01:48,043 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'lightning'}]} 2022-01-31 23:01:48,049 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2022-01-31 23:01:48,178 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-31 23:01:48,179 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-31 23:01:48,182 Thread-3 udi_interface INFO weatherstation:start: Starting WeatherPoly Node Server 2022-01-31 23:01:48,184 Thread-3 udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2022-01-31 23:01:48,185 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '26b33782-5f46-4357-928c-eb11e240c36c', 'uuid': '00:0d:b9:52:c1:80', 'profileNum': 9, 'address': 'controller', 'name': 'WeatherPoly', 'nodeDefId': 'WeatherPoly', 'nls': None, 'hint': '0x00000000', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 1, 'enabled': 1, 'timeAdded': 1643689747722, 'timeModified': 1643689747722, 'dbVersion': 1} 2022-01-31 23:01:48,185 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'installprofile': {'reboot': False}} 2022-01-31 23:01:48,355 Thread-3 udi_interface.interface DEBUG interface:setCustomParamsDoc: Sending customparamsdoc to Polyglot. 2022-01-31 23:01:48,356 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'customparamsdoc', 'value': '<h2>Configuration</h2>\n\n<p>The WeatherPoly node server has the following user configuration\nparameters:</p>\n\n<ul>\n<li>Port : The TCP port to listen on for connections from weather software.</li>\n<li>Units : The units used to display the data. Valid settings are: \'metric\', \'us\', or \'uk\'. The default is \'metric\'</li>\n<li>IncomingUnits: The units used by the data provider. Valid settings are \'metric\', \'us\', and \'uk\'. Default is \'metric\'.</li>\n</ul>\n\n<p>A mapping between the incoming data fields and the node server\'s nodes must be configured. The key is a node and data type combination and the value represents the incoming data field. How a data field is represented depends on the weather software.</p>\n\n<p>Valid nodes are: temperature, humidity, pressure, rain, wind, light, and lightning. See <a href="NODE_VALUE.md">node-value combinations</a> for a full list of node-values that can be used.</p>\n\n<h3>Cumulus software</h3>\n\n<p>Cumulus software allows you to configure what text string is used to represent each value. See the Cumulus documentation for a list of valid tags. A Cumulus HTTP API value of:</p>\n\n<p>http://<node server ip>:8080/cumulus?temp=&lt;#temp>&amp;humidity=&lt;#humidity></p>\n\n<p>Will send temperature and humidity data. This can be mapped to node server nodes using:</p>\n\n<p>temperature-main : temp\nhumidity-main : humidity</p>\n\n<h3>acuparse</h3>\n\n<p>acuparse software for Acurite weather stations https://github.com/acuparse/acuparse can be configured to send data to a generic service. To configure acuparse to send data to WeatherPoly, set the generic URL to:</p>\n\n<p>http://<node server ip>:8080/acuparse</p>\n\n<h4>Configure WeatherPoly with the following mapping:</h4>\n\n<ul>\n<li>temperature-main = tempf</li>\n<li>temperature-dewpoint = dewptf</li>\n<li>humidity-main = humidity</li>\n<li>pressure-sealevel = baromin</li>\n<li>wind-windspeed = windspeedmph</li>\n<li>wind-winddir = winddir</li>\n<li>wind-avgwindspeed = windspdmph_avg2m</li>\n<li>rain-rate = rainin</li>\n<li>rain-daily = dailyrainin</li>\n</ul>\n\n<p>Input units should be set as US.</p>\n\n<h3>WeeWX</h3>\n\n<p>WeeWX data is supported through an extension to WeeWX called weewx-crt which can output the data in Cumulus Real Time format. The weewx-crt extension is configured by setting the realtime_url to:</p>\n\n<p>http://<node server ip>:8080/weewx</p>\n\n<h4>Configure WeatherPoly mappings:</h4>\n\n<p>The real-time data file is a fixed format file with the weather values separated by spaces. This is split so that the space separated value\'s index is mapped to the node servers nodes-values. For example:\n* temperature-main = 2\n* temperature-dewpoint = 3\n* humidity-main = 4\n* etc.</p>\n\n<h3>MeteoBridge</h3>\n\n<p>MeteoBridge data is supported using the Home Weather Station weather network configuration. For the API URL use</p>\n\n<p>http://<node server ip>:8080/</p>\n\n<p>MeteoBridge will send a space separated list of values. These are mapped to the node server\'s nodes using the value\'s position in that list. The table below shows the values and numeric position.</p>\n\n<h4>MeteoBridge Field list</h4>\n\n<p><a href="METEOBRIDGE.md">MeteoBridge field list</a></p>\n'}]} 2022-01-31 23:01:48,358 Thread-3 udi_interface INFO weatherstation:discover: Creating nodes. 2022-01-31 23:01:48,359 Thread-3 udi_interface INFO weatherstation:discover: Creating Temperature node 2022-01-31 23:01:48,359 Thread-3 udi_interface.interface INFO interface:delNode: Removing node temperature 2022-01-31 23:01:48,360 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'temperature'}]} 2022-01-31 23:01:48,362 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Temperatures(temperature) [None] 2022-01-31 23:01:48,363 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'temperature', 'name': 'Temperatures', 'nodeDefId': 'temperature', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV0', 'value': 0, 'uom': 17}, {'driver': 'GV2', 'value': 0, 'uom': 17}, {'driver': 'GV4', 'value': 0, 'uom': 17}, {'driver': 'ST', 'value': 0, 'uom': 17}, {'driver': 'GV15', 'value': 0, 'uom': 17}, {'driver': 'GV16', 'value': 0, 'uom': 17}, {'driver': 'GV1', 'value': 0, 'uom': 17}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,364 Thread-3 udi_interface INFO weatherstation:discover: Creating Humidity node 2022-01-31 23:01:48,365 Thread-3 udi_interface.interface INFO interface:delNode: Removing node humidity 2022-01-31 23:01:48,366 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'humidity'}]} 2022-01-31 23:01:48,368 Thread-3 udi_interface.node DEBUG node:_updateDrivers: Update humidity default ST to 0 / 51 2022-01-31 23:01:48,368 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Humidity(humidity) [None] 2022-01-31 23:01:48,369 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'humidity', 'name': 'Humidity', 'nodeDefId': 'humidity', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV0', 'value': 0, 'uom': 51}, {'driver': 'ST', 'value': 0, 'uom': 51}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,371 Thread-3 udi_interface INFO weatherstation:discover: Creating Pressure node 2022-01-31 23:01:48,371 Thread-3 udi_interface.interface INFO interface:delNode: Removing node pressure 2022-01-31 23:01:48,372 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'pressure'}]} 2022-01-31 23:01:48,374 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Barometric Pressure(pressure) [None] 2022-01-31 23:01:48,375 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'pressure', 'name': 'Barometric Pressure', 'nodeDefId': 'pressure', 'primaryNode': 'controller', 'drivers': [{'driver': 'ST', 'value': 0, 'uom': 23}, {'driver': 'GV1', 'value': 0, 'uom': 25}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,376 Thread-3 udi_interface INFO weatherstation:discover: Creating Wind node 2022-01-31 23:01:48,377 Thread-3 udi_interface.interface INFO interface:delNode: Removing node wind 2022-01-31 23:01:48,377 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'wind'}]} 2022-01-31 23:01:48,379 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Wind(wind) [None] 2022-01-31 23:01:48,380 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'wind', 'name': 'Wind', 'nodeDefId': 'wind', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV4', 'value': 0, 'uom': 48}, {'driver': 'GV2', 'value': 0, 'uom': 14}, {'driver': 'GV1', 'value': 0, 'uom': 48}, {'driver': 'GV0', 'value': 0, 'uom': 14}, {'driver': 'ST', 'value': 0, 'uom': 48}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,381 Thread-3 udi_interface INFO weatherstation:discover: Creating Precipitation node 2022-01-31 23:01:48,382 Thread-3 udi_interface.interface INFO interface:delNode: Removing node rain 2022-01-31 23:01:48,383 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'rain'}]} 2022-01-31 23:01:48,385 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Precipitation(rain) [None] 2022-01-31 23:01:48,386 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'rain', 'name': 'Precipitation', 'nodeDefId': 'precipitation', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV1', 'value': 0, 'uom': 105}, {'driver': 'GV0', 'value': 0, 'uom': 105}, {'driver': 'GV3', 'value': 0, 'uom': 105}, {'driver': 'ST', 'value': 0, 'uom': 24}, {'driver': 'GV4', 'value': 0, 'uom': 105}, {'driver': 'GV6', 'value': 0, 'uom': 105}], 'hint': 16777215, 'private': None}]} 2022-01-31 23:01:48,387 Thread-3 udi_interface INFO weatherstation:discover: Deleting orphaned light node 2022-01-31 23:01:48,388 Thread-3 udi_interface.interface INFO interface:delNode: Removing node light 2022-01-31 23:01:48,389 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'light'}]} 2022-01-31 23:01:48,390 Thread-3 udi_interface INFO weatherstation:discover: Deleting orphaned lightning node 2022-01-31 23:01:48,391 Thread-3 udi_interface.interface INFO interface:delNode: Removing node lightning 2022-01-31 23:01:48,391 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'lightning'}]} 2022-01-31 23:01:48,393 Thread-3 udi_interface INFO weatherstation:start: WeatherPoly Node Server Started. 2022-01-31 23:01:48,494 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-31 23:01:48,495 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-31 23:01:48,497 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': 'ed9085ae-f475-4e41-8967-aa58daebfbfd', 'uuid': '00:0d:b9:52:c1:80', 'profileNum': 9, 'address': 'temperature', 'name': 'Temperatures', 'nodeDefId': 'temperature', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643691483025, 'timeModified': 1643691708348, 'dbVersion': 1} 2022-01-31 23:01:48,574 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': '<h2>Configuration</h2>\n\n<p>The WeatherPoly node server has the following user configuration\nparameters:</p>\n\n<ul>\n<li>Port : The TCP port to listen on for connections from weather software.</li>\n<li>Units : The units used to display the data. Valid settings are: \'metric\', \'us\', or \'uk\'. The default is \'metric\'</li>\n<li>IncomingUnits: The units used by the data provider. Valid settings are \'metric\', \'us\', and \'uk\'. Default is \'metric\'.</li>\n</ul>\n\n<p>A mapping between the incoming data fields and the node server\'s nodes must be configured. The key is a node and data type combination and the value represents the incoming data field. How a data field is represented depends on the weather software.</p>\n\n<p>Valid nodes are: temperature, humidity, pressure, rain, wind, light, and lightning. See <a href="NODE_VALUE.md">node-value combinations</a> for a full list of node-values that can be used.</p>\n\n<h3>Cumulus software</h3>\n\n<p>Cumulus software allows you to configure what text string is used to represent each value. See the Cumulus documentation for a list of valid tags. A Cumulus HTTP API value of:</p>\n\n<p>http://<node server ip>:8080/cumulus?temp=&lt;#temp>&amp;humidity=&lt;#humidity></p>\n\n<p>Will send temperature and humidity data. This can be mapped to node server nodes using:</p>\n\n<p>temperature-main : temp\nhumidity-main : humidity</p>\n\n<h3>acuparse</h3>\n\n<p>acuparse software for Acurite weather stations https://github.com/acuparse/acuparse can be configured to send data to a generic service. To configure acuparse to send data to WeatherPoly, set the generic URL to:</p>\n\n<p>http://<node server ip>:8080/acuparse</p>\n\n<h4>Configure WeatherPoly with the following mapping:</h4>\n\n<ul>\n<li>temperature-main = tempf</li>\n<li>temperature-dewpoint = dewptf</li>\n<li>humidity-main = humidity</li>\n<li>pressure-sealevel = baromin</li>\n<li>wind-windspeed = windspeedmph</li>\n<li>wind-winddir = winddir</li>\n<li>wind-avgwindspeed = windspdmph_avg2m</li>\n<li>rain-rate = rainin</li>\n<li>rain-daily = dailyrainin</li>\n</ul>\n\n<p>Input units should be set as US.</p>\n\n<h3>WeeWX</h3>\n\n<p>WeeWX data is supported through an extension to WeeWX called weewx-crt which can output the data in Cumulus Real Time format. The weewx-crt extension is configured by setting the realtime_url to:</p>\n\n<p>http://<node server ip>:8080/weewx</p>\n\n<h4>Configure WeatherPoly mappings:</h4>\n\n<p>The real-time data file is a fixed format file with the weather values separated by spaces. This is split so that the space separated value\'s index is mapped to the node servers nodes-values. For example:\n* temperature-main = 2\n* temperature-dewpoint = 3\n* humidity-main = 4\n* etc.</p>\n\n<h3>MeteoBridge</h3>\n\n<p>MeteoBridge data is supported using the Home Weather Station weather network configuration. For the API URL use</p>\n\n<p>http://<node server ip>:8080/</p>\n\n<p>MeteoBridge will send a space separated list of values. These are mapped to the node server\'s nodes using the value\'s position in that list. The table below shows the values and numeric position.</p>\n\n<h4>MeteoBridge Field list</h4>\n\n<p><a href="METEOBRIDGE.md">MeteoBridge field list</a></p>\n'} 2022-01-31 23:01:48,697 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2022-01-31 23:01:48,830 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-31 23:01:48,832 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-31 23:01:48,834 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': 'c0746f83-7cb1-4edf-8c14-61f22ab5b991', 'uuid': '00:0d:b9:52:c1:80', 'profileNum': 9, 'address': 'humidity', 'name': 'Humidity', 'nodeDefId': 'humidity', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643691483092, 'timeModified': 1643691708604, 'dbVersion': 1} 2022-01-31 23:01:48,878 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2022-01-31 23:01:48,920 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-31 23:01:48,921 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-31 23:01:48,923 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '4c6a8d07-a50e-41d1-a158-83f9b7a4f3fb', 'uuid': '00:0d:b9:52:c1:80', 'profileNum': 9, 'address': 'pressure', 'name': 'Barometric Pressure', 'nodeDefId': 'pressure', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643691483263, 'timeModified': 1643691708754, 'dbVersion': 1} 2022-01-31 23:01:49,215 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-31 23:01:49,217 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-31 23:01:49,220 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '23280b2a-9a68-4027-b460-107ae2707b06', 'uuid': '00:0d:b9:52:c1:80', 'profileNum': 9, 'address': 'wind', 'name': 'Wind', 'nodeDefId': 'wind', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643691483403, 'timeModified': 1643691708972, 'dbVersion': 1} 2022-01-31 23:01:49,413 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-31 23:01:49,415 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-31 23:01:49,417 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '8ae43c48-33df-4d74-86fe-34ff286e9810', 'uuid': '00:0d:b9:52:c1:80', 'profileNum': 9, 'address': 'rain', 'name': 'Precipitation', 'nodeDefId': 'precipitation', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643691483547, 'timeModified': 1643691709071, 'dbVersion': 1} 2022-01-31 23:01:49,453 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'light', 'success': False}] 2022-01-31 23:01:49,621 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'lightning', 'success': False}] 2022-01-31 23:01:49,941 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2022-01-31 23:01:50,145 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'temperature', 'success': True}] 2022-01-31 23:01:50,337 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'humidity', 'success': True}] 2022-01-31 23:01:50,578 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'pressure', 'success': True}] 2022-01-31 23:01:50,723 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'wind', 'success': True}] 2022-01-31 23:01:50,807 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'rain', 'success': True}] 2022-01-31 23:01:51,075 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'light', 'success': False}] 2022-01-31 23:01:51,204 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'lightning', 'success': False}] 2022-01-31 23:01:57,188 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-31 23:01:57,190 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-31 23:01:57,987 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-31 23:01:57,988 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-31 23:02:02,190 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-31 23:02:02,192 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll

@bpwwerare there plans to support P3 with WeatherPoly? Thanks in advance.

Just an update for anyone else and some theories which may or may not be true. My original z-wave issues were that I didn't have the right Zooz stick. If ordering it is the 700 and has a yellow cap. Michael fixed the link in first post I think. Don't setup portal until after you have restored your 994. It seems to get confused. Michael fixed it in 15 minutes on his side and all was good. I think me losing policy in my finder for a while was because of a node server. The weather poly node server defaults to port 8080. So does IoP. So one or the other was clobbering and not able to communicate. Restarting stuff didn't have to work, I powered down. I have the 1amp power supply. I did run in to some funny business (weird behavior). I had a lovely 5amp brick and swapped it out and weirdness went away. My scenes wouldn't work for a while. Turned out it was either the 8080 port problem or a flood of messages I was getting from the node server. I disabled all my pg2 node servers and re-imported and just let it do its thing and my scenes came back. Then I turned on PG2 and let it start (that is how I realized weather poly was on port 8080 as it was complaining. If you are using ELK module, take pictures of your programs. Unlike the zwave stuff, it doesn't leave nice comments ... Just a response 0 or result 0 line. Luckily I exported my programs to xml and have been around enough to be able to read them in their XML format. As a bonus @Michel Kohanimit would be nice if the 994 had an option that if safe mode kicks in you can still get to your programs in admin console. Then you could have the old one up and go back and validate some stuff. Maybe it exists. Maybe not, I couldn't get the 994 programs to come up without the PLM attached I used to have about 22 zwave devices. I got rid of my zwave locks before I did this upgrade and I have a blended homebrige setup (would love an august lock node server for more than 1 lock). 9 of those zwave devices were repeaters. I have a spread out house. The door locks were the weak link. Now, I have 9 devices (2 repeaters and 7 fan switches). It seems everything is faster. My zwave used to seem like it churned. I did have to go re-save all my network resources. Didn't realize I needed to re-input the mail credentials to send alerts. I had a few programs that enabled themselves even though they used to be disabled before the migration. I don't think it is because they had zwave devices in them, but not sure. I have 1 pg3 node. I use 11 node servers, I got rid of ping NS and turned off Roomba because it just seems to be flaky. I installed Sonos in PG3 as I needed to update room names on the nodes anyway. A lot of the NS I use aren't available in PG3 so I think I will wait a little longer. (WeatherPoly, Ventar, Rachio, MyQ, Hue). I started at like 5pm and was done by 11pm making all the changes/fixes and a big portion of that was spent on home bridge, changing my weewx to point at new weather poly port, Alex integration and the stumper was I was using occupancy sensor in portal and couldn't get it to work, moved to occupancy sensor 2 and got everything back up. Thanks for all the earlier posts and the how-to for research. It's not super simple, but what is that's worth it... And now I only have 1 box. @Michel Kohanimdid I read somewhere that we might be able to do ISY to ISY integration other than through network resources in the near future or share node servers between multiple ISYs? Thought I read that somewhere but can't find it. Cheers!

I can control devices after restoring buy none of my scenes work. None of them and I don't get anything in event viewer. Anyone else seen this problem?

Michael linked the correct zooz device above. Their naming is confusing. The zst10 come in 2 flavors. A 500 series and a 700. Michael had linked to zooz page which linked to thesmarterhouse for the 500. If yours didn’t t have a yellow cap it is a 500series. That seems to be my problem. I’m hoping they will refund mine as it was open box and says sales final but it wasn’t expensive so may not be worth the shipping.

yes, if not I don't believe zwave even shows in the menu.

I purchases the zoo s2 zst10 stick. I can see if find when plugged in to my MacBook. When I insert in Polisy it does not show up in ISY on policy and just says not responding. What should the device in /dev be named? When insert it the cuaU0 and lock/init show up as well as ttyU0 and lock/init. But it doesn't register in ISY. I did have to update my polisy manually as I have one of the originally shipped units. Not sure how else to debug.

Davis weather stations have. 2 second loop packet so it was sending very variable 12, every second. I commented out all the logger.info and it still streamed a lot. I think it is a polyglot setting potentially as harmony also has a tendency to be chatty. i had asked the question if you wanted help with the custom crt.py in terms of getting other variables. I store my lake level in weewx and pull it out and do math on the variables so I’ve figured out the sql methods. i noticed you I had some comments in the file to come back later.

wow, this thing does a lot of info logging that I can't turn off. My polisy becomes unresponsive when running WeatherPoly. My guess is that my crt.py is bound to LOOP and not archive. I ended up copying CRT.py and modifying the class and section so I could have 2 instances running (1 bound to loop for my realtime weather station and 1 bound to archive for ISY). not sure if slowness was due to the logging or the actual processing of variables.

Not sure if I missed instructions somewhere, but finally figured out I had to map the nodes form this list: https://github.com/bpaauwe/WeatherPoly to positions in the url. I can't see the url coming in so I looked it up in CRT.py. I added your changes to my CRT.py file that I use to publish data for a local weather page using the realtime.txt. I can create the variables for yesterday records you have commented out if anyone would like them. I'm mostly writing this to document what I had to do to get it working. If mapping temperature-main = 2 was incorrect then I'd like to know the right method. Also, in the CRT.py temp is line 3 but the first 2 or dates so trail and error got me there. I have a request. I actually pull in some other weather data through some extensions to weewx. In particular I pull in the lake level from the geological site. Could we add node category and maybe call it environment. I'd like variables for lakelevel (current, max_year, min_year, max_month, min_month, min_day, max_day) . It could just be water level so it is more generic. All these are in feet of elevation so convert from meter to feet ... I could see other variables like snow in this category. If I still had polyglot on my raspberry instead of the polisy I'd hack the files to see I could get it working.

@Michel Kohanim, I have this problem as well. Sent in a ticket. Can't access polisy on any ports. Router shows no attempts to connect, tried all same steps as @garybixler.

So I don't understand the behavior of the echo integration (and now that I have dug in the mobilinc integration. The scenario is I have a lot of 3 way or KPL controlled devices (lamps, lights, fans ...). So naturally those are setup in groups. For the purpose of this discussion we have the following: Lamp_01 - Load control Lamp_11 - Slave switch Lamps - Lamp Scene with Lamp_01 as responder only (lamplinc) and Lamp_11 as controller/responder In mobilinc when in the devices page, if I click on the icon for Lamp_11 it will turn on the lamp and both devices show status of on. If I go in to the device and on the screen click ON, only Lamp_11 switch changes status to on and Lamp_01 stays off (and therefore lamp not on) The second behavior is also what the echo does. I don't want the echo to control the scene because I can't dim the scene through echo and it doesn't properly report back status. If I control the Lamp_01 switch, my devices are out of sync but the light goes on. If I control the slave switch, the lamp doesn't go on. I don't want to write programs to control every light and maybe I am doing something wrong. Any advice?

Ok, I put in a ticket. I have to say, something seems like a bug. Essentially it always treats it as a self signed cert. The issuer always says my domain name. it doesn't change when I install the cert and intermediate cert. Surely this can be tested on a system. I am running most resent firmware 4.6.2.

Oh, good questions. I am not local to my ISY, I am over a VPN. Not sure how I can use HTTP as I am using the dashboard.jnlp java app to get as I thought that is the app you have to use. When I click on server, when I was completely re-doing the cert I would click new. If I got disconnected and had to log back in to load the cert, I would enter password. So to complete start over I would click new, but when I was trying to get the new one to work I would put in password.

Yes Michael I did exactly that. I clicked server, then it asked me if I wanted existing or new i selected new and gave new password. Generated a CSR, went to godaddy, processed, waited and then went in and pasted my cert and imported intermediate bundle. I’ve actually done that whole process 8 times since midnight to no avail. Any suggestions?