Everything posted by macjeff
-
Hue Nodeserver
Jimbo, I can repost this in the PG3 on Polisy forum but any chance you or someone is doing the 4 year old HUE nodeserver to control Hue from ISY?
-
Evapotransporation Bug?
In testing my other issues with Pg3, I have both installed. See the two screenshots. One from pg2 and one from pg3. The Evapotransporation value This is the same for all 15 days that the forecast show
-
WeatherBit PG3 Forecasts not showing in ISY
this is what bothers me 2022-02-17 08:08:54,363 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_0 not found in database. 2022-02-17 08:08:56,457 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_1 not found in database. 2022-02-17 08:09:12,602 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_2 not found in database. 2022-02-17 08:09:28,679 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_3 not found in database. 2022-02-17 08:09:40,773 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_4 not found in database. 2022-02-17 08:09:48,821 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_5 not found in database. 2022-02-17 08:09:56,845 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_6 not found in database. 2022-02-17 08:10:10,891 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_7 not found in database. 2022-02-17 08:10:21,025 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_8 not found in database. 2022-02-17 08:10:29,055 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_9 not found in database. 2022-02-17 08:10:39,193 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_10 not found in database. 2022-02-17 08:10:49,269 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_11 not found in database. 2022-02-17 08:10:55,310 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_12 not found in database. 2022-02-17 08:11:09,463 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_13 not found in database. 2022-02-17 08:11:15,484 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_14 not found in database. 2022-02-17 08:11:25,625 Thread-5 udi_interface.interface ERROR interface:db_getNodeDrivers: forecast_15 not found in database.
-
WeatherBit PG3 Forecasts not showing in ISY
btw I am on the free api. I got a second one and going to run pg2 and pg3 version at same time so I can use pg2 for stuff and help you work out bugs on other version. attached is another log file. ITS UPDATING the controller main after a restart., It seems to be just the forecast that are not updating but they do update after a reinstall of nodeserver WeatherBit_2-17-2022_80241_AM.zip
-
WeatherBit PG3 Forecasts not showing in ISY
forgot to paste the error and see screen shot. Does not show online 2022-02-17 01:02:58,878 MQTT udi_interface.interface ERROR interface:_message: error No valid API calls provided 2022-02-17 01:02:58,879 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'message' {"set":[{"address":"forecast_10","driver":"GV19","value":6,"uom":25},{"address":"forecast_10","driver":"GV0","value":35.3,"uom":17},{"address":"forecast_10","driver":"GV1","value":21.4,"uom":17},{"address":"forecast_10","driver":"CLIHUM","value":41,"uom":22},{"address":"forecast_10","driver":"DEWPT","value":6.1,"uom":17},{"address":"forecast_10","driver":"BARPRES","value":1012.8,"uom":117},{"address":"forecast_10","driver":"GV13","value":801,"uom":25},{"address":"forecast_10","driver":"GV14","value":3,"uom":22},{"address":"forecast_10","driver":"GV4","value":13,"uom":48},{"address":"forecast_10","driver":"GV5","value":21,"uom":48},{"address":"forecast_10","driver":"WINDDIR","value":330,"uom":76},{"address":"forecast_10","driver":"GV6","value":0,"uom":105},{"address":"forecast_10","driver":"GV7","value":0,"uom":105},{"address":"forecast_10","driver":"GV8","value":0,"uom":105},{"address":"forecast_10","driver":"GV18","value":0,"uom":22},{"address":"forecast_10","driver":"GV16","value":5.2,"uom":71},{"address":"forecast_10","driver":"GV10","value":313.6,"uom":56},{"address":"forecast_10","driver":"GV15","value":15,"uom":116},{"address":"forecast_10","driver":"GV9","value":0.11,"uom":56},{"address":"forecast_10","driver":"GV20","value":0.083,"uom":106}]}
-
WeatherBit PG3 Forecasts not showing in ISY
I installed the nodeserver again and worked fine until it errored again. Once it stops it stops updating in the ISY too but polisy still shows it connected. I either have the old values in ISY but if I reboot ISY and it worked. thinking of going back to the Pg2 server for now. I do have all the other weather nodeservers working
-
WeatherBit PG3 Forecasts not showing in ISY
I have installed it multiple times. It all loaded fine this last time. Then I rebooted the ISY and new data is not coming into the ISY but if I look at the nodes in PG3 there is data there (not zeros). So it should show something. I attached a log. Giving up for the night so will try again tomorrow WeatherBit_2-17-2022_122826_AM.zip
-
TimeData Variables
I use variables from nodeservers in emails from TimeData and other nodeservers I upgraded from Pg2 to pg3 and none of the variables work now. This was the pg2 version ${sys.node.n014_timedata.GV10} for Season. I noticed its now TimeData so I changed that but still wont work. I am still on node 14 and still need GV10. Ideas?
-
PG3 on Polisy
An update was posted for a Pg3 nodeserver and I dont see an UPDATE button in the store. I can understand since PG3 allows multiple copies of the same nodeserver How would you know there is any update? And more important how do you install it without totally removing the nodeserver. I had a developer try this and he got the same thing so this is an issue.
-
PG3 on Polisy
already tried that. get the Socket Timeout Error every time I think I need to go into polisy to the correct directory and us a RM command
-
PG3 on Polisy
My issue is that I need a terminal command to manually delete a nodeserver from polisy. Its deleted from both pg2 and pg3 but still shows up in ISY. I deleted the nodes but its still showing up as a server. And if you go to PG3 and go to install it the slot is missing. So I need to clear that slot. Something is messed up.
-
PG3 multiple weatherflows
I need to query the server itself. I have had it where a server goes down and comes back up and the program does not realize it. So I wrote a program that opens another program to query and then runs the first program again. So I just need True or False for online in each one
-
PG3 on Polisy
so after my install failed I am manually deleting nodeservers. One of mine Climacell shows as managed in PG2 and Pg3. It shows up in ISY under list of nodeservers. If I go under the NODESSERVER menu (in the ISY admin console) its not there but if I choose CONFIGURE at bottom of that menu its there under slot 20. Does anyone have a way to delete that or am I just out a slot now??
-
PG3 multiple weatherflows
-
PG3 multiple weatherflows
I think this is the same for all your weather servers. Need a Query in programs. Its in the pg2 version
-
Inventory on PG3
finally got it installed but its failing (says FAILED shortly after load) 2022-02-16 17:03:40 info: NS: Starting Node Server 2022-02-16 17:03:40 info: POLY: Interface starting 2022-02-16 17:03:40 info: POLY: Getting config from environment 2022-02-16 17:03:40 debug: POLY: Log file set to: logs/debug-2022-02-16.log 2022-02-16 17:03:41 info: POLY: MQTT client connected 2022-02-16 17:03:41 info: NS: MQTT Connection started 2022-02-16 17:03:41 debug: POLY: Sending config/getAll to PG3 2022-02-16 17:03:41 debug: NS: Message Sent: { config: {} } 2022-02-16 17:03:41 debug: POLY: _sendMessage: sending {"config":{}} to udi/pg3/ns/system/00:21:b9:02:57:b0_11 2022-02-16 17:03:41 debug: NS: Message Sent: { getAll: {} } 2022-02-16 17:03:41 debug: POLY: _sendMessage: sending {"getAll":{}} to udi/pg3/ns/custom/00:21:b9:02:57:b0_11 2022-02-16 17:03:41 debug: POLY: -> topic is udi/pg3/ns/clients/00:21:b9:02:57:b0_11, processing 2022-02-16 17:03:41 debug: POLY: Converting controller, timeAdded, profileNum 2022-02-16 17:03:41 debug: POLY: Creating Nodes from configuration nodes 2022-02-16 17:03:41 info: POLY: Setting node controller driver ST: 1 2022-02-16 17:03:41 debug: NS: Message Sent: { set: [ { address: 'controller', driver: 'ST', value: '1', uom: 2 }, [length]: 1 ] } 2022-02-16 17:03:41 debug: POLY: _sendMessage: sending {"set":[{"address":"controller","driver":"ST","value":"1","uom":2}]} to udi/pg3/ns/status/00:21:b9:02:57:b0_11 2022-02-16 17:03:41 debug: POLY: Removing nodes that are no longer in the config 2022-02-16 17:03:41 debug: POLY: Setting newParamsDetected flag in the config 2022-02-16 17:03:41 debug: POLY: Do loop detection 2022-02-16 17:03:41 info: NS: Config received has 1 nodes 2022-02-16 17:03:41 debug: NS: Message Sent: { set: [ { key: 'notices', value: {} }, [length]: 1 ] } 2022-02-16 17:03:41 debug: POLY: _sendMessage: sending {"set":[{"key":"notices","value":{}}]} to udi/pg3/ns/custom/00:21:b9:02:57:b0_11 2022-02-16 17:03:41 debug: NS: Message Sent: { set: [ { key: 'customparamsdoc', value: '<h1>ISY Inventory</h1>\n' + '\n' + '<p>The purpose of this Nodeserver is simply to display/report device/node inventory within the ISY.</p>\n' + '\n' + '<ul><li>Inventory Collected<ul><li>Total Nodes</li><li>Scenes</li><li>Insteon</li><li>Z-Wave</li><li>NodeServer Nodes</li><li>Intgeger Variables</li><li>State Variables</li><li>Programs</li><li>Folders</li><li>Network Resources</li><li>Error Log Entries</li></ul></li></ul>\n' + '\n' + '<h2>Configuration</h2>\n' + '\n' + '<ul><li>Default Short Poll: 5 Minutes (300 Seconds)</li><li>Default Long Poll: 10 Minutes (No actions performed)</li><li>Username: This is the admin user of your ISY</li><li>Password: Your ISY admin password</li><li>IP_Address: The IP Adress of your ISY</li><li>ISY_Port: Default 80 unless you have changed it</li></ul>\n' + '\n' + '<h4>User Provided</h4>\n' + '\n' + '<ul><li>Enter your admin user name, password and IP address and port to the ISY controller</li><li>Save configuration</li></ul>' }, [length]: 1 ] } 2022-02-16 17:03:41 debug: POLY: _sendMessage: sending {"set":[{"key":"customparamsdoc","value":"<h1>ISY Inventory</h1>\n\n<p>The purpose of this Nodeserver is simply to display/report device/node inventory within the ISY.</p>\n\n<ul><li>Inventory Collected<ul><li>Total Nodes</li><li>Scenes</li><li>Insteon</li><li>Z-Wave</li><li>NodeServer Nodes</li><li>Intgeger Variables</li><li>State Variables</li><li>Programs</li><li>Folders</li><li>Network Resources</li><li>Error Log Entries</li></ul></li></ul>\n\n<h2>Configuration</h2>\n\n<ul><li>Default Short Poll: 5 Minutes (300 Seconds)</li><li>Default Long Poll: 10 Minutes (No actions performed)</li><li>Username: This is the admin user of your ISY</li><li>Password: Your ISY admin password</li><li>IP_Address: The IP Adress of your ISY</li><li>ISY_Port: Default 80 unless you have changed it</li></ul>\n\n<h4>User Provided</h4>\n\n<ul><li>Enter your admin user name, password and IP address and port to the ISY controller</li><li>Save configuration</li></ul>"}]} to udi/pg3/ns/custom/00:21:b9:02:57:b0_11 2022-02-16 17:03:41 debug: POLY: -> topic is udi/pg3/ns/clients/00:21:b9:02:57:b0_11, processing 2022-02-16 17:03:41 debug: NS: Message Received: { getAll: [ { id: '80fbfd72-5ac1-43e2-88e7-75a5086baa77', uuid: '00:21:b9:02:57:b0', profileNum: 11, key: 'customparams', value: '{removed for security}', dbVersion: 1 }, { id: '81efea6a-c379-45d6-b147-310de947b16d', uuid: '00:21:b9:02:57:b0', profileNum: 11, key: 'customparamsdoc', value: '<h1>ISY Inventory</h1>\n' + '\n' + '<p>The purpose of this Nodeserver is simply to display/report device/node inventory within the ISY.</p>\n' + '\n' + '<ul><li>Inventory Collected<ul><li>Total Nodes</li><li>Scenes</li><li>Insteon</li><li>Z-Wave</li><li>NodeServer Nodes</li><li>Intgeger Variables</li><li>State Variables</li><li>Programs</li><li>Folders</li><li>Network Resources</li><li>Error Log Entries</li></ul></li></ul>\n' + '\n' + '<h2>Configuration</h2>\n' + '\n' + '<ul><li>Default Short Poll: 5 Minutes (300 Seconds)</li><li>Default Long Poll: 10 Minutes (No actions performed)</li><li>Username: This is the admin user of your ISY</li><li>Password: Your ISY admin password</li><li>IP_Address: The IP Adress of your ISY</li><li>ISY_Port: Default 80 unless you have changed it</li></ul>\n' + '\n' + '<h4>User Provided</h4>\n' + '\n' + '<ul><li>Enter your admin user name, password and IP address and port to the ISY controller</li><li>Save configuration</li></ul>', dbVersion: 1 }, { id: '9c41bcd2-aeff-419a-9a37-929fa9e76771', uuid: '00:21:b9:02:57:b0', profileNum: 11, key: 'customtypeddata', value: '{}', dbVersion: 1 }, { id: 'c8be4299-efcc-47fa-80cb-0ff9e6de9b9a', uuid: '00:21:b9:02:57:b0', profileNum: 11, key: 'notices', value: '{}', dbVersion: 1 }, [length]: 4 ] } 2022-02-16 17:03:41 debug: POLY: getAll sub message: { id: '80fbfd72-5ac1-43e2-88e7-75a5086baa77', uuid: '00:21:b9:02:57:b0', profileNum: 11, key: 'customparams', value: '{"removed for security"}', dbVersion: 1 } 2022-02-16 17:03:41 debug: POLY: getAll sub message: { id: '81efea6a-c379-45d6-b147-310de947b16d', uuid: '00:21:b9:02:57:b0', profileNum: 11, key: 'customparamsdoc', value: '<h1>ISY Inventory</h1>\n' + '\n' + '<p>The purpose of this Nodeserver is simply to display/report device/node inventory within the ISY.</p>\n' + '\n' + '<ul><li>Inventory Collected<ul><li>Total Nodes</li><li>Scenes</li><li>Insteon</li><li>Z-Wave</li><li>NodeServer Nodes</li><li>Intgeger Variables</li><li>State Variables</li><li>Programs</li><li>Folders</li><li>Network Resources</li><li>Error Log Entries</li></ul></li></ul>\n' + '\n' + '<h2>Configuration</h2>\n' + '\n' + '<ul><li>Default Short Poll: 5 Minutes (300 Seconds)</li><li>Default Long Poll: 10 Minutes (No actions performed)</li><li>Username: This is the admin user of your ISY</li><li>Password: Your ISY admin password</li><li>IP_Address: The IP Adress of your ISY</li><li>ISY_Port: Default 80 unless you have changed it</li></ul>\n' + '\n' + '<h4>User Provided</h4>\n' + '\n' + '<ul><li>Enter your admin user name, password and IP address and port to the ISY controller</li><li>Save configuration</li></ul>', dbVersion: 1 } 2022-02-16 17:03:41 debug: POLY: getAll sub message: { id: '9c41bcd2-aeff-419a-9a37-929fa9e76771', uuid: '00:21:b9:02:57:b0', profileNum: 11, key: 'customtypeddata', value: '{}', dbVersion: 1 } 2022-02-16 17:03:41 debug: POLY: getAll sub message: { id: 'c8be4299-efcc-47fa-80cb-0ff9e6de9b9a', uuid: '00:21:b9:02:57:b0', profileNum: 11, key: 'notices', value: '{}', dbVersion: 1 } 2022-02-16 17:03:41 info: NS: Discovering 2022-02-16 17:03:41 debug: POLY: -> topic is udi/pg3/ns/clients/00:21:b9:02:57:b0_11, processing 2022-02-16 17:03:41 debug: NS: Message Received: { set: [ { address: 'controller', driver: 'ST', value: '1', uom: 2 }, [length]: 1 ] } 2022-02-16 17:03:41 debug: POLY: -> topic is udi/pg3/ns/clients/00:21:b9:02:57:b0_11, processing 2022-02-16 17:03:41 debug: NS: Message Received: { custom: { notices: '{}' } } 2022-02-16 17:03:41 debug: POLY: -> topic is udi/pg3/ns/clients/00:21:b9:02:57:b0_11, processing 2022-02-16 17:03:41 debug: NS: Message Received: { set: [ { success: true, key: 'notices' }, [length]: 1 ] } 2022-02-16 17:03:41 debug: POLY: -> topic is udi/pg3/ns/clients/00:21:b9:02:57:b0_11, processing 2022-02-16 17:03:41 debug: NS: Message Received: { custom: { customparamsdoc: '<h1>ISY Inventory</h1>\n' + '\n' + '<p>The purpose of this Nodeserver is simply to display/report device/node inventory within the ISY.</p>\n' + '\n' + '<ul><li>Inventory Collected<ul><li>Total Nodes</li><li>Scenes</li><li>Insteon</li><li>Z-Wave</li><li>NodeServer Nodes</li><li>Intgeger Variables</li><li>State Variables</li><li>Programs</li><li>Folders</li><li>Network Resources</li><li>Error Log Entries</li></ul></li></ul>\n' + '\n' + '<h2>Configuration</h2>\n' + '\n' + '<ul><li>Default Short Poll: 5 Minutes (300 Seconds)</li><li>Default Long Poll: 10 Minutes (No actions performed)</li><li>Username: This is the admin user of your ISY</li><li>Password: Your ISY admin password</li><li>IP_Address: The IP Adress of your ISY</li><li>ISY_Port: Default 80 unless you have changed it</li></ul>\n' + '\n' + '<h4>User Provided</h4>\n' + '\n' + '<ul><li>Enter your admin user name, password and IP address and port to the ISY controller</li><li>Save configuration</li></ul>' } } 2022-02-16 17:03:41 debug: POLY: -> topic is udi/pg3/ns/clients/00:21:b9:02:57:b0_11, processing 2022-02-16 17:03:41 debug: NS: Message Received: { set: [ { success: true, key: 'customparamsdoc' }, [length]: 1 ] } 2022-02-16 17:03:49 error: NS: getInv() Error: http://172.16.1.225:58888/rest/networking/resources 2022-02-16 17:03:52 error: NS: uncaughtException REPORT THIS!: TypeError: Cannot read properties of undefined (reading 'toString') at Parser.exports.Parser.Parser.parseString (/var/polyglot/pg3/ns/00:21:b9:02:57:b0_11/node_modules/xml2js/lib/parser.js:312:19) at Parser.parseString (/var/polyglot/pg3/ns/00:21:b9:02:57:b0_11/node_modules/xml2js/lib/parser.js:5:59) at Controller.processNetworkResources (/var/polyglot/pg3/ns/00:21:b9:02:57:b0_11/Nodes/ControllerNode.js:181:14) at Controller.onDiscover (/var/polyglot/pg3/ns/00:21:b9:02:57:b0_11/Nodes/ControllerNode.js:64:14) at processTicksAndRejections (node:internal/process/task_queues:96:5) 2022-02-16 17:03:52 error: POLY: uncaughtException: Cannot read properties of undefined (reading 'toString') TypeError: Cannot read properties of undefined (reading 'toString') at Parser.exports.Parser.Parser.parseString (/var/polyglot/pg3/ns/00:21:b9:02:57:b0_11/node_modules/xml2js/lib/parser.js:312:19) at Parser.parseString (/var/polyglot/pg3/ns/00:21:b9:02:57:b0_11/node_modules/xml2js/lib/parser.js:5:59) at Controller.processNetworkResources (/var/polyglot/pg3/ns/00:21:b9:02:57:b0_11/Nodes/ControllerNode.js:181:14) at Controller.onDiscover (/var/polyglot/pg3/ns/00:21:b9:02:57:b0_11/Nodes/ControllerNode.js:64:14) at processTicksAndRejections (node:internal/process/task_queues:96:5) 2022-02-16 17:03:52 error: NS: uncaughtException: Cannot read properties of undefined (reading 'toString') TypeError: Cannot read properties of undefined (reading 'toString') at Parser.exports.Parser.Parser.parseString (/var/polyglot/pg3/ns/00:21:b9:02:57:b0_11/node_modules/xml2js/lib/parser.js:312:19) at Parser.parseString (/var/polyglot/pg3/ns/00:21:b9:02:57:b0_11/node_modules/xml2js/lib/parser.js:5:59) at Controller.processNetworkResources (/var/polyglot/pg3/ns/00:21:b9:02:57:b0_11/Nodes/ControllerNode.js:181:14) at Controller.onDiscover (/var/polyglot/pg3/ns/00:21:b9:02:57:b0_11/Nodes/ControllerNode.js:64:14) at processTicksAndRejections (node:internal/process/task_queues:96:5)
-
PG3 multiple weatherflows
Sorry I am doing a lot of pg2 to pg3 conversion and was thinking NOAA station ID. I did put the NOAA one in there but now I changed to my tempest station ID. Restarted several times. Still Sunday and Clear and 0's on every day
-
PG3 multiple weatherflows
also I have programs to monitor nodeservers. It first does a query and weatherflow is not there. I need Weatherflow nodeserver to show up under Your Devices in programs and then Query to be there
-
PG3 multiple weatherflows
Got weatherflow running but my forecast data is Sunday with all zeros I used the NOAA forecast code which may be the reason (KJYO) In my case also once fixed I assume forecast zero is today and 1 is tomorrow and so on
-
BUG - Node Server Info is Not Valid
I got it installed now but when I run it I get errors but I know the settings are correct. I can put them into the pg2 version and they work 2022-02-16 15:17:34 info: NS: Starting Node Server 2022-02-16 15:17:34 info: POLY: Interface starting 2022-02-16 15:17:34 info: POLY: Getting config from environment 2022-02-16 15:17:34 debug: POLY: Log file set to: logs/debug-2022-02-16.log 2022-02-16 15:17:35 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:36 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:37 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:38 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:39 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:40 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:41 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:42 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:43 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:44 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:45 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:46 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:47 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:49 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:50 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:51 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:52 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:53 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:54 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:55 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:56 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:57 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:58 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:59 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:00 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:01 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:02 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:03 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:04 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:05 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:06 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:08 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:09 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:10 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:11 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:12 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:13 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:14 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:15 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:16 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:17 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:18 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:19 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:20 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:21 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:22 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:23 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:24 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:26 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:27 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:28 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:29 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:30 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:31 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:32 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:33 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:34 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:35 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:41 info: NS: Starting Node Server 2022-02-16 15:18:41 info: POLY: Interface starting 2022-02-16 15:18:41 info: POLY: Getting config from environment 2022-02-16 15:18:41 debug: POLY: Log file set to: logs/debug-2022-02-16.log 2022-02-16 15:18:41 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:42 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:43 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:44 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:45 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:46 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:47 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:48 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:49 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:50 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:52 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:53 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:54 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:55 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:56 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:57 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:58 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:59 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:19:00 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:19:01 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:19:02 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:19:03 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:19:04 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:19:05 error: POLY: MQTT Error: Connection refused: Identifier rejected
-
PG3 on Polisy
Tried restore and it failed. Well some came over and some did not but the ones in pg2 never deleted and so I basically had two running in the same slot. I tried deleting the one on pg2 and then it deleted the stuff from the ISY so I had to set it up all again on pg3. My log is attached LOOK at 14:39 pg3_2-16-2022_24243_PM.zip
-
PG3 multiple weatherflows
I know it’s not in this topic but I hope this is not the case with Climacell. I use the variables there in lots of weather related emails to show temperature today and tomorrow and things like that. I also used them in programs.
-
PG3 multiple weatherflows
so will the nodes I have now convert when I do the upgrade?
-
PG3 multiple weatherflows
About to upgrade to PG3. Can I add the nodeserver twice once for Tempest and once for Air/Sky Jeff
-
PG3 on Polisy
Ok better than nothing but I hope it will just ignore any that are not ported yet thanks for your help