macjeff

Point well taken. I was told when I move to ISY on polisy I wont see as much of the speed issue. and with #7 maybe have it ask for login when it needs it. for now you have to click on the purchases tab and see that its not logged in and log in.

If it was part of the instructions I missed it. I thought it had to be in the ISY for the upgrade to see that you are running it. At least it was only one of the nodeservers and not all of them,. I can afford to lose one slot but not a dozen of them!!!

Here are my thoughts after spending some time doing the upgrade......This is FYI only. I know its beta (maybe alpha) and I love the challenge so please dont take this as an attack. 1. Upgrade needs some work. It did a few of them but then got stuck and failed. I posted the info. I am almost 100% sure due to the failure both Pg2 and pg3 dont have a nodeserver installed but they both show something is in the old slot which says managed. Posted on that too. 2. Installing nodeservers is a LOT slower. 3. It seems updating on the physical ISY is a lot slower after restart of ISY or Polisy. My pg2 things are updated way before my pg3 things. 4. I like the interface but wish there was a restart polisy option (at least I dont see it) to reboot the entire polisy. I do from command line or Pg2 has the option. 5. Updates need some work. As pointed out by Jimbo, no notification but they are coming. 6. Would be nice to be able to roll back to old versions if you have an issue. A lot of my things I run on pi have a menu you can install back versions. 7. Randomly and it could be after I reboot my computer or Polisy I have to login to Portal again. Wonder why its not auto logging in? 8. Love the new store and purchase options but every time I click on Store the first time I log in, it says error getting purchases. I have to then click on purchases and usually they pop up but as in #7 sometimes I have to log in again, and then go back to store and all is well. To summarize- THANK YOU for your work. Its a very good and mostly stable beta. Needs some work, but overall its usable. I hope the developers get rewarded for their hard work,. Again THANK YOU

Its climacell but tI dont think the issue is the nodeserver. Its the fact that Pg2 and Pg3 sees something in a database saying its still installed but its not. I assume the issue was caused by pg3 but both show it as managed so I cant do anything. ISY sees it but wont delete it. Tried running on a PC and two macs to make sure it was not some sort of local JAVA issue

I mentioned this on earlier post and after some PM with some developers I was told to email UD tech support so I did but I want to post basically what I sent them here. A nodeserver got screwed up in PG3 upgrade It was both in Pg3 and Pg2 after the install I did not realize it at first so I configured the Pg3 stuff. Then I realized it, So I deleted it from pg2 but the Pg3 one deleted at the same time. I checked and Both pg2 and pg3 show it as managed now Then I went to reinstall but the slot is still taken. I went into ISY and its there in nodeserver list. I go to configure and delete and get a Socket Error. Rebooted ISY and Polisy and same thing It is not in either the nodeservers (pg2) or ns (PG3) directory when I ssh. So it must be in a database. Any way to fix or am I out a slot?

I agree but I hope someone takes it on. I am buying Pg3 nodeservers so supporting the guys doing this. And reporting bugs too.

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?

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

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.

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

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}]}

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

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

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?

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.

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

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.

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

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

Yes it filled in. New issue- Weatherflow is asking for climacell info? See screenshot

I think this is the same for all your weather servers. Need a Query in programs. Its in the pg2 version

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)

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

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

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