macjeff

Thanks!!!

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

as a test I went back to Pg2 version and working fine. I will leave there until I am asked to test again for pg3 version

Just tried this theory. Did not work. Even tried installing in a different slot. I cant get by the errors. Kind of wish I did not try the delete and install.

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

This is still not working for me. I have tried everything even a different slot.

Jimbo- sure you saw it but latest version 3.0.52 fixed all my node servers except wireless tags (and Ecobee seems slow but thats no big deal)

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.

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.

Restart pg3 under the system menu or do sudo service pg3 restart that should fix the version mismatch but not the larger issue

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.

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.

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?

3.0.50 seems to fix the backup issues

Here is a summary of my testing and reports---- I setup a test. Created variable. Exposed variable to Alexa as motion sensor in portal. Set 1 as motion. Discover devices on alexa and it shows up Setup trigger that has Alexa announce TEST SUCCESSFUL when its device shows motion (variable is 1) In ISY, I change variable to 1. Instantly see it change in Alexa app and should fire routine. I have had it work first try even after a reboot but sometimes it does not. If it does not, I just disable and re-enable the skill in the Alexa app. (NOT PORTAL) and everything works instantly. Confirmed the same problem happens with real motion sensors in ISY as well as Locks in ISY. You cant trigger routines from lights and switches as of now but they work fine in alexa even when motion and contact sensors are not. I also confirmed Contact Sensors have the same issue. This is what I reported. I tried with Hue Motion sensors and one other brand motion sensor and it works every time so that is why Amazon wants to push off on the ISY skill.

I want to be clear this is what they said. I am actually on a conf call now and the discussion is how amazon has gone down hill from their sales to alexa to the web services. I will keep on this. I cant argue I have other motion sensors and its only this skill. I thought it was a IoP thing but someone posted they are having issue with old 4.7 firmware so that rules out IoP. They did tell me the more tickets the better and Michel gave me permission to scream at them LOL So feel free to overwhelm them with tickets. But if there is something I should add to mine let me know.

I am about to scream. Amazon OF COURSE said all other skills work. They also said the skill has not been updated in several years and yes it may be blocked but its not due to a problem on Amazons side. It may be the skill is not following current protocols. So I asked for it to be escalated and asked for someone to explain to me EXACTLY what needs to be done on our (speaking on behalf of Universal Devices) side. They said they will call me back within 3-5 days.

I am going to try and call Amazon today. I have a master ticket in with them. They say its on the Universal Devices side but the fact that someone posted they are seeing the same issue with 4.7 tells me its on their side since 4.7 is old firmware that worked fine for me for years and I have a huge setup.

Mine works fine to disconnect but I am just using IoP, Portal, and Alexa. No IFTTT. Very important- DONT disconnect from Portal or you will lose your devices. Go to alexa app, search for the ISY skill. Disable it. Immediately re-enable it. You should be good to go. BUT everytime your ISY reboots you have to do this again. Thats even with the 5.4.1_2 version which is the latest as of this post. Michel is working on why this is happening. He said we are being blacklisted on startup for some reason and thats why the disconnect and reconnect fixes the issue.

yes confirmed working

3.0.47 It came in about a day or so ago via sudo pkg upgrade. There was a bug in 3.0.46 with backup he was fixing so I was checking every night for an update. So I guess that broke it.

I have the same issue now. I tried rebooting. Do you want me to PM you my logs? Jeff api_key is not defined, must be running local version or there was an error retreiving it from PG3? Must fix or add custom param for local invalid_grant: The authorization grant, token or credentials are invalid, expired, revoked, do not match the redirection URI used in the authorization request, or was issued to another client. Token expired -160978.383796 seconds ago, so will have to re-auth...

Not in my house. I have an ethernet drop in every room including the one with the breaker boxes. I have moved PLM to every room and the best room is where I have it now. Isssue is lots of metal in that room so Z-Wave does not get through. So I have to move my ISY out of the room and the PLM stays there.

THANKS. So now you can get your adapter and the cables I recommended and make a 50 foot PLM cable.

Someone has to make a PLM cable. But I just put a post in IoP about a wireless only PLM replacement that Michel said will work with IoP not ISY 994i.