macjeff Posted March 18, 2022 Posted March 18, 2022 2 minutes ago, vbphil said: @macjeffHow did you set all your log levels to Error only? Go into the Node server and go to the LOGS button. Then there is an option in there to set your log level. I like that feature of PG3 which did not exist in PG2. You had to set the log level in configuration or in the ISY Admin if it was programmed in. 1
macjeff Posted March 24, 2022 Posted March 24, 2022 On 3/16/2022 at 12:30 PM, bpwwer said: Ok, thanks. I didn't notice any node servers going into failed state when I tested, but I may have had them stopped at the time. I'll try again to see if I can reproduce what you're seeing. 3.0.50 seems to fix the backup issues
macjeff Posted March 24, 2022 Posted March 24, 2022 Spoke too soon. Backup works under 3.0.50 but a majority of my node servers are not. Either zeros or OLD data showing up. I tried restarting Pg3, IoP, and the entire Polisy. Most weather ones seem to be working. Kasa, WirelessTags, TimeData, Ecobee, Harmony, Pushover, Linktap. all Not working I am going to send you my log file. Everything was fine on 3.0.48 except for backup any way to go back?
Jimbo.Automates Posted March 24, 2022 Posted March 24, 2022 Spoke too soon. Backup works under 3.0.50 but a majority of my node servers are not. Either zeros or OLD data showing up. I tried restarting Pg3, IoP, and the entire Polisy. Most weather ones seem to be working. Kasa, WirelessTags, TimeData, Ecobee, Harmony, Pushover, Linktap. all Not working I am going to send you my log file. Everything was fine on 3.0.48 except for backup any way to go back?There are many posts about this already. We are aware and @bpwwer is looking into it. Sent from my Pixel 6 Pro using Tapatalk 2
macjeff Posted March 24, 2022 Posted March 24, 2022 2 minutes ago, JimboAutomates said: There are many posts about this already. We are aware and @bpwwer is looking into it. Sent from my Pixel 6 Pro using Tapatalk I must not be monitoring the correct topics. I monitor this one for Pg3, and the main one for IoP, and then the individual ones for all the node servers. I will search but anything you want to send me to follow would be great. I have been pretty busy and dont always look at every topic.
bpwwer Posted March 24, 2022 Posted March 24, 2022 I pushed out 3.0.51 that should fix the problem, but I've been waiting for confirmation of that. I was not able to reproduce the issue with any of the node servers I have installed for testing. I suspect there was a case where I expected data from the store that many existing node servers haven't updated yet. 3.0.51 should work with those older entries.
macjeff Posted March 24, 2022 Posted March 24, 2022 It fixed the problem IF I delete and re-install the Node server. I did that with two and they are now working but the others are not. I tried several restarts. I can give you accesss to my system if you need it but PM me. I will PM you a new log file now.
dbwarner5 Posted March 24, 2022 Posted March 24, 2022 46 minutes ago, bpwwer said: I pushed out 3.0.51 that should fix the problem, but I've been waiting for confirmation of that. I was not able to reproduce the issue with any of the node servers I have installed for testing. I suspect there was a case where I expected data from the store that many existing node servers haven't updated yet. 3.0.51 should work with those older entries. Several of my node servers are also not working since 3.0.5... will upgrade to 3.0.51 and see if that corrects them.
dbwarner5 Posted March 24, 2022 Posted March 24, 2022 (edited) No change. Here is my Elk Node server log fyi. thanks. Also fyi, noticed the versions aren't matching, but understand if that is just a UI issue. Version 3.0.51Status: ConnectedFrontend Version: 3.0.50 ELK_3-24-2022_50156_PM.zip Edited March 24, 2022 by dbwarner5
macjeff Posted March 24, 2022 Posted March 24, 2022 (edited) 4 minutes ago, dbwarner5 said: No change. Here is my Elk Node server log fyi. thanks. Also fyi, noticed the versions aren't matching, but understand if that is just a UI issue. Version 3.0.51Status: ConnectedFrontend Version: 3.0.50 ELK_3-24-2022_50156_PM.zip 1.6 MB · 0 downloads Restart pg3 under the system menu or do sudo service pg3 restart that should fix the version mismatch but not the larger issue Edited March 24, 2022 by macjeff 1
bpwwer Posted March 24, 2022 Posted March 24, 2022 Is Elk the only node server now having issues? Try going to the ELK details, selecting log and change the log level to something different, then restart the node server. 1
macjeff Posted March 24, 2022 Posted March 24, 2022 1 hour ago, bpwwer said: Is Elk the only node server now having issues? Try going to the ELK details, selecting log and change the log level to something different, then restart the node server. I am having it on four different note servers now… Wireless tags, purple air, ecobee, pushover. I also had the issue on Kasa and harmony Hub but a reinstall of those fixed.
dbwarner5 Posted March 24, 2022 Posted March 24, 2022 Will try that and let you know. Thanks Sent from my iPhone using Tapatalk
Jimbo.Automates Posted March 25, 2022 Posted March 25, 2022 3.0.52 is out and others are reporting that fixes these issues.Sent from my Pixel 6 Pro using Tapatalk 1
dbwarner5 Posted March 25, 2022 Posted March 25, 2022 will load it now and let you know. @JimboAutomates @bpwwer
dbwarner5 Posted March 25, 2022 Posted March 25, 2022 @bpwwer @JimboAutomates Good news. got them running: -installed 3.0.5.2 -Front end Version matches Version -ALL node servers were not working : Kasa, ecobee, elk, notifications, time date, Weatherflow -One at time, I am changing the log level, stopping the NS, going back to dashboard, waiting, starting it again.. -So far they all are restarting successfully. Log level chosen does seem to matter, just changing it. Only one that seems to still be struggling is Ecobee. It may just need more time? this line seems to be repeating: Thread-37 udi_interface DEBUG Controller:shortPoll: controller:shortPoll: Skipping since discover is still running Will keep an eye on it. Thanks!!
dbwarner5 Posted March 25, 2022 Posted March 25, 2022 Changed the log level one more time, and restarted ecobee.. WORKING.. All back again! yeah! Thanks 1
macjeff Posted March 25, 2022 Posted March 25, 2022 All works fine except two things. Minor issue- Ecobee did take a long time to update but it worked so I am ok I reported this directly to bpwwer but its a Node server from Jimbo called Wireless Tags. Still would not work so I tried an erase and install. Still wont work after that nor will it give me link to authenticate. I sent logs in but screenshots are attached. So it was working before all the updates today which broke it. Then even on the latest PG3 version it fixed all the others but this one had no data. After reinstalling the Node server I only get the 1 node and cant authenticate.
macjeff Posted March 25, 2022 Posted March 25, 2022 9 hours ago, macjeff said: All works fine except two things. Minor issue- Ecobee did take a long time to update but it worked so I am ok I reported this directly to bpwwer but its a Node server from Jimbo called Wireless Tags. Still would not work so I tried an erase and install. Still wont work after that nor will it give me link to authenticate. I sent logs in but screenshots are attached. So it was working before all the updates today which broke it. Then even on the latest PG3 version it fixed all the others but this one had no data. After reinstalling the Node server I only get the 1 node and cant authenticate. This is still not working for me. I have tried everything even a different slot.
macjeff Posted March 25, 2022 Posted March 25, 2022 (edited) I noticed yesterday after the upgrades all of my node servers showed the modification date of 3/24 at the same time. I thought it was due to the upgrades But today I noticed they all changed to 3/25 and all the same time So I did a REFRESH store and the time changes. So this is showing the CURRENT refresh time NOT the modification time. Plus the time there is 4 hours ahead of my time. log times in PG3 are correct so its just the modification time inside PG3 store that is showing both the current time (After refresh) and the wrong time zone. ** Showing the correct time of modification, and only on those modified, is important because thats how I know one of my node servers was updated!!! Edited March 25, 2022 by macjeff
vbPhil Posted March 25, 2022 Posted March 25, 2022 @macjeffHi. My WirelessTag NS is still working this morning on 3.0.52. There's one place you could check on and that's your WirelessTag Manager Account. You should see an authorization for UDI Polyglot V2 Node server. See snapshot. It will show V2 even if you installed PG3. That's a bug that hasn't been fixed. I suppose you might try Revoking it there and re-install the Node Server, especially if you're unable to get the authorization working. Just a thought. Log in to your WirelessTag portal. At the bottom click on Settings and choose Account.
macjeff Posted March 25, 2022 Posted March 25, 2022 (edited) 44 minutes ago, vbphil said: @macjeffHi. My WirelessTag NS is still working this morning on 3.0.52. There's one place you could check on and that's your WirelessTag Manager Account. You should see an authorization for UDI Polyglot V2 Node server. See snapshot. It will show V2 even if you installed PG3. That's a bug that hasn't been fixed. I suppose you might try Revoking it there and re-install the Node Server, especially if you're unable to get the authorization working. Just a thought. Log in to your WirelessTag portal. At the bottom click on Settings and choose Account. The problem is that I deleted what I had. The issue is the Authorization part is broken. I have no access in the portal. If I use Pg2 I get the access and it works. Then I can revoke it as you said, but when I go to pg3 and add it back I dont get the auth page so I cant go any further. The errors clearly tell me its not going to work. I even tried manually putting the auth code in there and it wont work. So whatever you do, dont delete the Node server or you can probably not add it back. Or try adding it to a second slot. See if it works. For now I have to wait for Jimbo. I can go back to Pg2 until its fixed. These errors are in BLUE in the configuration where in Pg2 and before in Pg3 it would say click here to auth REST Server (False) not running. check Log for ERROR No NSDATA Returned by Polyglot key=None data=None Unable to start server, no NSDATA returned client_id=None client_secret=None This is the entire log!!! And it does not grow 2022-03-25 10:16:29,293 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-03-25 10:16:32,410 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.38 Starting... 2022-03-25 10:16:32,624 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.0.52 [ISY: 5.4.1, Slot: 12] 2022-03-25 10:16:32,627 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'} 2022-03-25 10:16:32,629 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-03-25 10:16:32,636 MainThread udi_interface INFO Controller:__init__: WirelessTag Controller: Initializing 2022-03-25 10:16:32,637 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: wtcontroller not found in database. 2022-03-25 10:16:32,638 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {}} 2022-03-25 10:16:32,961 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-03-25 10:16:32,963 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:53:2c:34_12 - MID: 1 Result: 0 2022-03-25 10:16:33,182 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-03-25 10:16:35,644 MainThread udi_interface.interface INFO interface:addNode: Adding node WirelessTagsController(wtcontroller) [None] 2022-03-25 10:16:35,646 MainThread udi_interface.interface INFO interface:setController: Using node "wtcontroller", driver "ST" for connection status. 2022-03-25 10:16:43,377 Thread-5 udi_interface ERROR Controller:handler_nsdata: No NSDATA Returned by Polyglot key=None data=None 2022-03-25 10:16:43,381 Thread-3 udi_interface ERROR Controller:handler_params: oauth2_code not defined, assuming False 2022-03-25 10:16:46,429 Thread-9 udi_interface ERROR Controller:rest_start: Unable to start server, no NSDATA returned client_id=None client_secret=None BTW...thanks for your help!!! Edited March 25, 2022 by macjeff 1
Jimbo.Automates Posted March 25, 2022 Posted March 25, 2022 This is an error because PG3 is not sending the information needed by the NS. Need help from @bpwwer Sent from my Pixel 6 Pro using Tapatalk
macjeff Posted March 25, 2022 Posted March 25, 2022 55 minutes ago, JimboAutomates said: This is an error because PG3 is not sending the information needed by the NS. Need help from @bpwwer Sent from my Pixel 6 Pro using Tapatalk Thanks!!!
Recommended Posts