macjeff

I am running on Polisy and 3.1.18 is the latest for Polisy. Are you running on EISY? If so then yes there is an upgrade. I am only running ONE of your other nodeservers (WirelessTags) It shows version for me. See screenshot I also just updated one other nodeserver and it shows the latest version so its not an update issue.

thanks for your message. we will have to see what @bpwwer says about this. May be a bug or may be intentional. If intentional then how can we tell what version we have. I dont see it anywhere else?

It does not show version number. I confirmed its the correct installed. Before this it showed 3.0.18 and now no version but it is 3.0.20. I attached screenshot and log. See it just shows production and not the version number. Kasa_3-20-2023_84549-AM.zip

What does this mean for the Node Server.... Authentication update Dear Netatmo developer, As of today, when you refresh an Access Token using the associated endpoint https://api.netatmo.com/oauth2/token, Netatmo servers respond with a couple of tokens : an Access Token and a Refresh Token. If the previous Access Token is still valid, the newly returned access token is identical but its expiration time is extended for 3 hours. In any case, the refresh token is not renewed. Starting from the 17/04/2023, this behavior will change to to be compliant with the recommendations of the RFC of the OAuth2 Authorization Framework (section 10.4) and improving the security of the data of our users. When refreshing tokens, Access Token and Refresh Token will be automatically renewed and former tokens invalidated. What does it means for me ? If you were already updating the tokens provided when refreshing your tokens, this change will not impact you. If you do not update the refresh token when refreshing your Access Token, your users will be disconnected after 3 hours as the former tokens will become invalidated. To fix it, you need to update the tokens as soon as you get the newly generated ones. Sincerely, Legrand - Netatmo - Bticino

Thanks. Just curious.

in pg3 Node Server list it shows Timedata was updated last night 2/28/23 at 23:14 but when I check its the same version that i have had for a while. Is this due to just a reupload of the same version?

You might be onto something. I tried healing network and 4 devices failed after it had to retry 1/2 of them at least once. Tried again and different ones failed. Rebooted and healed fine with no retries. Tried the locks and they all worked perfectly the first time. After that the status started getting slower each time I locked and unlocked. Oh and when I rebooted I had the admin console open. The locks all showed no status. Slowly they all came in one at time within a minute (And I was not doing a query on restart) I will update my ticket with this post

I really dont know because I have not tried in years but this is an OLD lock- at least 5 years. You can still buy it but they dont make it anymore.

actually the other day I rebooted it and come to think of it it was better after that has gotten worse but it was never perfect

yes with what they call digital keys you can get through the Yale app which I used at the beginning but have not touched since going to Z wave in the ISY

Yes and yes. The Access Control node seems to show the last activity. Like my front door was last unlocked by me and it says Manual Unlock. And the ISY last locked the Basement Lock and it says RF Lock. I just locked it with ISY and watched it lock and this one was bad. Took about 45 seconds to change to locked in ISY even though it locked it. Again this all worked perfect with ZOOZ module on 5.5.7. I converted to the Zooz to Z-wave. I also re-interviewed the devices and UDI did a remote session and took logs. At least it works and shows status. Just not fast enough on the status part

Mine is YRD446-ZW2-605 and I have 5 of them The 446 is the lock and the 605 is the zw module and it does the same on all 5 locks so its not a lock issue.

Anyone else see issues like this. I have Yale Assure locks with Z-Matter board. I was on 5.5.7 with zooz and this was not an issue. So its actually z-matter with 5.5.7 thats causing it. Lock locks fine within seconds. Manual lock sends instant status Lock from admin console locks instantly but status takes 6-10 seconds (Sometimes longer but thats rare) That would be fine except when you lock with Alexa it checks again in 5 seconds so its like this Me- "Alexa Lock Front Door" Alexa- "Locking hang on...." Alexa waits 5 seconds Alexa should say "The front door is locked" Alexa says "The front door is unlocked" BUT ITS LOCKED. So I do it again and it says locked. The issue is the stays us coming in 1-5 seconds after she checks so when I say it again status is already updated. ***Note I have shown this to Chris and he has looked at it happen via screenshare. Just looking for others who might have the issue.

I will just delete the programs then.

It used to have option in programs for sensor or probe online. Now it does not so when those commands disappeared I guess the ID of the command changes. So now my programs were all messed up because it chose something else like Moisture or Temperature. It was just an online 0 or 1 or true false. But thats gone

I got the issue. When this was updated last they removed the OFFLINE for all the sensors. So the programs are all messed up. Like 245 is Strawberry Water Sensor Probe is Online is False but now it says Strawberry Water Sensor Probe moisture is False which makes no sense. I changed it to 0% but even that would not be correct as offline would probably show the last value. 251 is Outdoor Weather Sensor module online is false. Now says Outdoor Weather Sensor Temperature is false. so I changed those to 0 also which again will probably not work. can you fix? ISY-Events-Log.v5.5.7__Wed 2023.02.22 02.53.28 PM.txt

see image. Is this normal NS 20 is this one.

Sorry. so many post today I just misread it I hope the issue was just a cache issue or something. Fingers crossed!!!

Is this with EISY? I have 100 slots on Polisy and over 25 installable and running fine. Michel saw all mine yesterday and never said a word about a limit.

I’m thinking that one of your solutions pf clearing Java cash and rebooting hopefully cleared it. Please update here if no issues by tomorrow. Hoping that’s all it was

This was a known issue on 5.5.6 of course if you upgraded while the admin console is open you will get this. Once on 5.5.7 it should not happen. if it does I would open a ticket. As just mentioned it has to do with the amount of connections and traffic. I was able to reproduce by just disconnecting a network cable. I can’t make mine do it anymore. also if you have not done a total reboot of EISY and update packages a second time please do. I know on polisy that was needed.

Clear your Java cache. Then use the start Java app to get a new version of everything and it should be fine after that. You have to do this every time the ISY is updated from now on so that admin console up to date to match.

I wish they would alert you on screen. Sometimes I can’t hear the beeps since polisy is on another floor. I have to run really fast after hitting upgrade packages. Lol

Anyone else having these Z wave issues?

even something as simple as pulling the network cable for a minute or so would crash it. If anything was connected and it dropped connection (sometimes it would be the second drop) then it would restart ISY. I am on beta and its fine. I have not tried the official 5.5.7 yet. And with all the issues last weekend, I will wait until Monday most likely.