macjeff

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.

I just ordered one myself. Michel said this works. Unlike a PLM it does not use the powerlines for communication. But it still works using the wireless connection. A good solution (only for IoP) if the PLM is gone for good.

Actually not because the PLM needs the RJ-45 into it. YOU CANT plug the RJ-45 into the PLM These 2 cables are a set. They need to be used together as the pinout is not the same as the PLM uses. This is just a passthough. So you end up with a serial cable connector that DOES connect into the original PLM cable. If someone has a link for the original PLM cable or even a short one that does Serial to RJ 45 with the correct pinout for the PLM please post here. I did try using only one of the two adapters and they dont work unless you use them as a pair. The big thing is it allows you for a VERY long cable. My ISY is not in another room than my PLM. My PLM works better for communication in the room its in.