macjeff

It took a while for mine to come in. Hit discover again in about 15 minutes but I think there still is a bug.

I just checked and mine is correct. As I said in my previous post it took 5 to 10 minutes for numbers to update. Also you can try restarting the note server and the admin console.

UPDATE- Latest version seems to be working. Only thing is the update speed. I cleared the log and it was a good 5-10 minutes before it updated in the ISY. Do I adjust the short or long poll? But the good news is it seems to be working. This developers other node servers seem to be working except LinkTap which is still on PG2. I sent you a PM about that.

its not working for me. Well its working but everything is ZERO It used to work fine. And this is a NEW install. It says self configuring. Maybe its not getting the correct config info? Running on Pg3 on Polisy. Log attached. I put in debug mode and restarted. ST-Inventory_1-12-2023_72404-PM.zip

I installed it on the Polisy and I get FAILED that kind of flashes in the browser. (pg3 3.1.16 which is latest for Polisy) and I tried a couple slots and it never shows up at all in the IOP. 023-01-11 23:03:23 info: NS: Starting Node Server 2023-01-11 23:03:23 info: POLY: Interface starting 2023-01-11 23:03:23 info: POLY: Getting config from environment 2023-01-11 23:03:23 info: POLY: MQTT client connected 2023-01-11 23:03:23 info: NS: MQTT Connection started 2023-01-11 23:03:24 info: POLY: MQTT client connected 2023-01-11 23:03:24 info: NS: MQTT Connection started 2023-01-11 23:03:26 info: POLY: MQTT client connected 2023-01-11 23:03:26 info: NS: MQTT Connection started 2023-01-11 23:03:27 info: POLY: MQTT client connected 2023-01-11 23:03:27 info: NS: MQTT Connection started 2023-01-11 23:03:28 info: POLY: MQTT client connected 2023-01-11 23:03:28 info: NS: MQTT Connection started 2023-01-11 23:03:29 info: POLY: MQTT client connected 2023-01-11 23:03:29 info: NS: MQTT Connection started 2023-01-11 23:03:30 info: POLY: MQTT client connected 2023-01-11 23:03:30 info: NS: MQTT Connection started 2023-01-11 23:03:31 info: POLY: MQTT client connected 2023-01-11 23:03:31 info: NS: MQTT Connection started 2023-01-11 23:03:32 info: POLY: MQTT client connected 2023-01-11 23:03:32 info: NS: MQTT Connection started 2023-01-11 23:03:34 info: POLY: MQTT client connected 2023-01-11 23:03:34 info: NS: MQTT Connection started 2023-01-11 23:03:35 info: POLY: MQTT client connected 2023-01-11 23:03:35 info: NS: MQTT Connection started 2023-01-11 23:03:36 info: POLY: MQTT client connected

3.1.18 is only for the eisy so I can’t even go past 3.1.16

Try a different slot. I’ve had issues with a couple of note servers not really deleting Also the procedure I’m running now for notes servers is to stop it first, restart PG3, and quit the admin console. Then I reinstall the node server. Then I start up the admin console and it should be up at the top. But even with this procedure I get all zeros jeff

I can confirm I even deleted mine in IOX 5.5.3 (new today) and pg3 3.1.16 (polisy version) and it shows all zeros now. Was working before 5.5.2 and if you had it running and did not delete it, it would show old cached values. But once you delete and reinstall you get zeros. Tried in multiple slots.

The problem is the Node Server since one of the latest pg3 or python releases does not stop when you stop or restart it in pg3. So even if you delete it, its still running. Then nothing will install in that slot even though PG3 and ISY thinks. Its stopped. For now I had to go back to the pg2 version AFTER @bpwwer helped me SSH in, manually stop the Node Server, and then manually delete it. We tried again in other slots but its still not stopping. Every other nodesever and the pg2 version is running fine.

As soon as the Node Server starts it works. I can put in my data and everything is fine and then it stops a minute later. If I restart it, it wont work again. I tried not even entering my data and the same thing happens. I attached the complete log file but here is except 2023-01-03 18:33:21,537 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-01-03 18:33:24,104 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... 2023-01-03 18:33:24,182 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.16 [ISY: 5.5.2, Slot: 7] 2023-01-03 18:33:24,183 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '172.16.1.210', 'netmask': '255.255.255.0', 'broadcast': '172.16.1.255'} 2023-01-03 18:33:24,185 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2023-01-03 18:33:24,188 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-01-03 18:33:24,189 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.2'}} 2023-01-03 18:33:24,238 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-01-03 18:33:24,240 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2c:34_7 - MID: 1 Result: 0 2023-01-03 18:33:24,245 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2023-01-03 18:33:27,213 MainThread udi_interface.interface INFO interface:addNode: Adding node Netatmo Weather Station(netatmo_ws) [None] 2023-01-03 18:33:27,216 MainThread udi_interface.interface INFO interface:setController: Using node "netatmo_ws", driver "ST" for connection status. 2023-01-03 18:33:27,337 Thread-1 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-01-03 18:33:27,341 Thread-1 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-01-03 18:33:27,349 Thread-1 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-01-03 18:33:27,352 Thread-1 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-01-03 18:33:27,354 Thread-1 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-01-03 18:33:27,462 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-01-03 18:33:27,609 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-01-03 18:33:27,653 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-01-03 18:33:27,656 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-01-03 18:33:27,660 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-01-03 18:34:57,191 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-01-03 18:35:00,027 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... 2023-01-03 18:35:00,037 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.16 [ISY: 5.5.2, Slot: 7] 2023-01-03 18:35:00,039 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '172.16.1.210', 'netmask': '255.255.255.0', 'broadcast': '172.16.1.255'} 2023-01-03 18:35:00,040 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2023-01-03 18:35:00,043 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-01-03 18:35:00,044 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.2'}} 2023-01-03 18:35:00,083 MQTT udi_interface.interface ERROR interface:_connect: MQTT Failed to connect, invalid identifier 2023-01-03 18:35:28,596 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-01-03 18:35:31,376 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... 2023-01-03 18:35:31,388 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.16 [ISY: 5.5.2, Slot: 7] 2023-01-03 18:35:31,390 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '172.16.1.210', 'netmask': '255.255.255.0', 'broadcast': '172.16.1.255'} 2023-01-03 18:35:31,393 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2023-01-03 18:35:31,397 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-01-03 18:35:31,398 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.2'}} 2023-01-03 18:35:31,431 MQTT udi_interface.interface ERROR interface:_connect: MQTT Failed to connect, invalid identifier Netatmo-WS_1-3-2023_63816-PM.zip

I missed that. I got the announcement and missed the for eisy in the subject well I read what I wanted to read For ISY. LOL thanks!!

I am at the latest iOX firmware (from UPDATE PACKAGES) for Polisy now but cant get Pg3 to update to 3.1.17 even doing manually. Says most recent version is installed. Even tried a reboot of the entire polisy. Any way to force it to get 3.1.17 [admin@polisy ~]$ sudo pkg update Password: Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. [admin@polisy ~]$ sudo pkg install pg3 Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The most recent versions of packages are already installed [admin@polisy ~]$

I think I know the answer but I wanted to ask. I set a program that if Radon levels get high to let me know via alexa. They did but in a couple hours it came right down. The RADON company said ask your home automation guy if you can monitor the 2 day average and not the current reading. They told me (And you can see in the app) that airthings supports that. Can we get that reading into the ISY?

they responded the data was being collected but the access to that data was severed by Rackspace. The issue was fixed at approx 11:30am EDT yesterday.

Looks like its back up. I had to restart my Node Server but seems connected fine now and status now says TRUE not FALSE in the Node Server showing me its online. And the URLS work now.

I have not seen any response from their tech support

Randomly I am getting SQL errors. Go to their Tag Manager online and leave the page on. After a little bit a yellow message comes up with SQL server errors. Those are mentioned in the google group also. I dont think this is anything for us to fix and if they fix it then it should come back on its own. My worries is they are closing down. But I am sure they would have given us a SUNSET notice. Fingers crossed

It went down overnight (only the API). This is their API URL http://mytaglist.com/eth/oauth2_apps.html The Node Server started complaining also with mytaglist.com I confirmed that URL is down and just emailed them. Jeff 2022-12-12 07:36:28,408 MainThread udi_interface.interface INFO interface:setController: Using node "wtcontroller", driver "ST" for connection status. 2022-12-12 07:37:29,367 Thread-10 udi_interface ERROR wtServer:l_error: wtServer:post: Connection error for https://www.mytaglist.com/oauth2/access_token.aspx: HTTPSConnectionPool(host='www.mytaglist.com', port=443): Max retries exceeded with url: /oauth2/access_token.aspx (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x80318b700>, 'Connection to www.mytaglist.com timed out. (connect timeout=60)')) 2022-12-12 07:37:29,368 Thread-10 udi_interface ERROR wtServer:l_error: pull_access_token: Failed 2022-12-12 07:37:29,787 Thread-15 udi_interface ERROR wtServer:l_error: wTagManager:0cd55ae7c718:Tag Manager 2022 #0CD55AE7C718:post: No authorization for url=https://www.mytaglist.com/ethAccount.asmx/SelectTagManager payload={"mac": "0CD55AE7C718"} 2022-12-12 07:37:29,789 Thread-10 udi_interface ERROR wtServer:l_error: wtServer:post: No authorization for url=https://www.mytaglist.com/ethAccount.asmx/GetTagManagers payload={} 2022-12-12 07:37:29,802 Thread-10 udi_interface ERROR wtServer:l_error: wtServer:post: No authorization for url=https://www.mytaglist.com/ethAccount.asmx/IsSignedIn payload={} 2022-12-12 07:37:29,804 Thread-10 udi_interface ERROR wtServer:l_error: wtServer:post: No authorization for url=https://www.mytaglist.com/ethAccount.asmx/GetTagManagers payload={} 2022-12-12 07:37:31,223 Thread-18 udi_interface ERROR wtServer:l_error: wTagManager:0cd55ae7c718:Tag Manager 2022 #0CD55AE7C718:post: No authorization for url=https://www.mytaglist.com/ethAccount.asmx/SelectTagManager payload={"mac": "0CD55AE7C718"} 2022-12-12 07:37:32,177 Thread-21 udi_interface ERROR wtServer:l_error: wTagManager:0cd55ae7c718:Tag Manager 2022 #0CD55AE7C718:post: No authorization for url=https://www.mytaglist.com/ethAccount.asmx/SelectTagManager payload={"mac": "0CD55AE7C718"} 2022-12-12 07:37:33,043 Thread-24 udi_interface ERROR wtServer:l_error: wTagManager:0cd55ae7c718:Tag Manager 2022 #0CD55AE7C718:post: No authorization for url=https://www.mytaglist.com/ethAccount.asmx/Select

No matter what I did I got the WRITING icon in the admin console. i saw a post to go back to beta and it seems to work

Just bought it. I have an OLD roku from like 8 years ago. Dont care about it. Its on old TV But have new 4k stick. It shows up but I keep getting this in the logs also the Stick has WRITING icon (See image) 2022-12-04 16:42:01,729 MainThread udi_interface ERROR roku:updateNode: Adding Roku node ycjfs 2022-12-04 16:42:01,832 Thread-4 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction. 2022-12-04 16:42:01,832 Thread-3 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction. 2022-12-04 16:42:02,696 Thread-6 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction. 2022-12-04 16:42:02,895 MainThread udi_interface ERROR roku:discover: Discovery failed for http://172.16.1.227:80/description.xml: 'data' 2022-12-04 16:42:02,993 MainThread udi_interface ERROR roku:discover: Discovery failed for http://172.16.1.227:80/description.xml: 'data' 2022-12-04 16:42:03,088 MainThread udi_interface ERROR roku:discover: Discovery failed for http://172.16.1.227:80/description.xml: 'data' 2022-12-04 16:42:03,183 MainThread udi_interface ERROR roku:discover: Discovery failed for http://172.16.1.227:80/description.xml: 'data' 2022-12-04 16:42:06,001 Thread-9 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction. 2022-12-04 16:42:11,035 Thread-11 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction. 2022-12-04 16:42:16,016 Thread-13 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction. 2022-12-04 16:42:21,026 Thread-15 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction. 2022-12-04 16:42:26,025 Thread-17 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction. 2022-12-04 16:42:31,045 Thread-19 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction. 2022-12-04 16:42:36,084 Thread-21 udi_interface ERROR roku_node:update_status: App id 562859 is not mapped to an appliction.

I did try to delete from ISY. Due to the update issue and this issue, I am going to erase and reinstall this Node Server. There are only a couple programs that use it so easy to do. I will test the bug with next build. Or you can put out a quick update at a later date and I will test it.

more issues. We can move to another topic but I think the fix for all of the issues is to erase and install. I had two units (an old air and sky) replaced by them. I did this over a month ago 1. Changed the ID for the air and Sky. New ones showed up. 2. Deleted the old nodes Then today when I rebooted the two old nodes came back. I thought I had deleted from the PG3 configuration which auto deleted from the ISY but it did not. I tried to delete today from pg3 and it says error removing node. I will send another Pg3 and weatherflow log to you now since I did this after the last log If erase Node Server is needed I will do that.

I will PM you the entire PG3 log Check between 6:30 and 7:30 am my time

I saw the message (PG3 3.1.15) and it said version 3.0.26 was avaialable I hit restart and it took a while and came up. Message is gone and its running but it still says 3.0.25 not 3.0.26 I can do the reinstall if you want but you had said not to do that unless instructed. WeatherFlow_12-1-2022_72749-AM.zip

I’m not sure if you have iCloud email but one of the secrets and that is you can use iCloud.com, me.com, or Mac.com. So you get three email addresses for the same account. But you could also sign up for a quick Gmail account