macjeff

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

I had to open a new account with a new email. They only allow one api per email to be issued.

yes. It would stop on the MQTT error.

Nothing worked. Start or restart would show up 1, 2, 3, 4 and by the time it hit 5 seconds it would stop counting but would still say connected. I did a reboot of pg3 and now ok.

Yes. Restarting does not work at all. The reinstall is the only way I have been able to update recently. I have reported the bug and waiting for the fix. I am running now fine on KASA. Just had to reboot PG3

would a Pg3 reboot fix?

I have polyglot 5729 0.0 1.3 102320 51952 - I Tue07 1:02.36 python3 ./kasa-poly.py (python3.9) admin 31538 0.0 0.1 12840 2420 0 S+ 14:55 0:00.01 grep kasa I might be doing something wrong but did kill 31538 and it says no such process what am I missing?

I will do this later on today but I can’t do now

it does show I have 3.0.14 now. It just wont start up. I will do an erase and install later if you say to. Except for a few programs, this Node server is very simple to reinstall

It said an update is needed. I was on 3.0.13. I did the restart method and waited. It installed (or it said it did) but never restarted. I get an error in the logs. If I hit start it will say already running. If I wait a couple minutes I can hit start and it says started successfully but then the error comes back in log. It was working fine. I tried doing a manual reinstall but same issue. (go to store, click install, and click the reinstall same slot button) Log Attached Kasa_11-16-2022_63106-AM.zip

not sure why they are doing this but has to be due to their new "limits" and they have to force you to get a new API key to enforce the limits.

Mine is working now and what I had to do is a pain. First I had to get a new API. Mine has not changed but they deactivated it. Maybe I was on old plan. Second I had to change the rules to cover the new limits like lower forcast to 7 from 16. If I were you I would use a new email and get a new API. Try putting that one in and see what happens. Jeff

See screenshot from store. It installs 3.0.13

Can you verify that the only way to get 16 days forecast now is to pay $40 a month. I don’t need 16 days enough for $40. I can deal with seven. Not sure if I need to buy the hobbyist which I would do that but it’s still only Seven days forecast and it’s OK. I will stop the weather emails for a few days until you fix it. I leave on my trip Friday afternoon so hopefully it might be done by then but if not I can do it while on vacation. I know this is their fault so thanks for all your efforts

I assumed that so I got a new API as a test and it did not work so that verified it’s not a timed out type of thing