asbril

With the greatest respect (and I mean that....), I think that @TRI0N is right that it would be useful to have a program that restarts a nodeserver when it stops working. That does not reflect (badly) on any nodeserver but nodeservers occasionally stop working and then require a restart. Having (the option to create) a program in the Administrative Console that does the restart would be very useful.

I have seen the notion of Network resources multiple times, but I don't know what it really means. Can someone, in simple words, explain what Network resources are ? Thanks !!!!

2.05 still not getting the 3 Chromecast devices, after setting false to true and rediscover in AVRemote Controller in Administrative Console.

Yes, but now it does not (yet) discover my Google Home and Chromecast devices. (I did change false to true in the ns).

2.05 was installed but is not running.

I use both the PG3 ns and the HA Integration, but I have not noticed much battery usage. I have programed that at home the sentry mode is off.

That is what I have done and it works

Good points and questions...... I don't have State variables set up in UD Mobile and will have study how to do that. Thanks !!!!

I created this program : When I run THEN it works and the Amps setting goes to 15, but nothing happens when I run IF, even though the Iphone is home. Anyone has a suggestion ?

I wonder whether you can get the authtentication code from the Google API site. That is how the authentication works with the Home Assistant Integration for the Google calendar.

I see your issue. The setup has changed since I did it a long time ago. I tried with another Google account that I have and it did not work. I suggest that you ask the developer Firstone. He has been very helpful to me whenever needed. I vaguely remember that Google may have made changes to (some of) their API's. I hope that you get it to work. It is the nodeserver that I use most and if you need some guidance on how to use it (once you have it authenticated) then don't hesitate to contact me.

I don't know if this helps, but when I installed this wonderful nodeserver, when I click on the authenticate link I do that with right click and "Open link on new tab". That way I can easily do a copy paste of the authentication code into the nodeserver configuration.

That is a good point @tazman. I have my Tesla setup to de-activate Sentry mode while at home. The Sentry mode uses considerable energy, so @someguy's 7 day use at the airport parking would make perfect sense if using Sentry mode.

Bingo ! Thanks

Dialog boxes working again but deleting ns not working.

"Confirm" and "Cancel" are greyed out. In fact the same with Restart PG3, and I had to power cycle eisy to get the upgrade.

Thanks @bpwwer

1. The good news....... : It's not me 2. The bad news...... : a bit of annoyment

I understand what I did wrong (deleting NS from AC), but what do I do now ? Thanks for your help pg3_3-16-2023_21737-PM.zip

This is what I have now...... When I was not able to remove the not working nodeserver in slot 21, I added it (also) in slot 19. After a while it occurred to me to replace the Tesla "Refresh Token", a specific requirement for the Tesla ns and the nodeserver started to work again. Now I need to remove the Tesla ns from slot 19, but it does not let me. Maybe I need a sudo command ????

My Tesla nodeserver stopped working and restart did not help. I decided to re-install the ns and first deleted it from the Administrative Console and then pressed delete in the PG3 Dashboard. This is what I get : I tried several times but no luck. What should I do ? Thanks

Others may know better than me, but sometimes more nodes appear when you do a Zwave - Synchronize - Update with interview. At least it is something that I have seen. And in some cases more nodes appear after an exclusion/inclusion. Probably not the way it is supposed to be, but remember that the fact that there are different manufacturers may create challenges for UD, though they try to cover as much as they can.

I believe that it is a known issue that likely will be resolved in a future update. I would not worry too much about it. When there are sgnificant updates there is always mention in this forum.

Yes, same here.

For whatever reason my eisy suddenly became very slow to respond to commands. I am not aware having changed anything that I could think of which may have caused the slow response time. I rebooted eisy but it was still slow and then I power-cycled the eisy. As with the reboot, after the power cycle it took some time to synch everything and initially it was still slow when the synch window closed ended. After another 15 to 30 minutes, the eisy response time was back to normal and now I realize that even though the synch window closed after some time, the eisy was still busy in the background which impacted the response time. Probably, that may have been the situation after the reboot and the power cycle (in this case) may not have been necessary. In other words (and this is my tip ) , restarting eisy may require more time than the synch window shows.