macjeff

I will do this later on today but I can’t do now

it does show I have 3.0.14 now. It just wont start up. I will do an erase and install later if you say to. Except for a few programs, this Node server is very simple to reinstall

It said an update is needed. I was on 3.0.13. I did the restart method and waited. It installed (or it said it did) but never restarted. I get an error in the logs. If I hit start it will say already running. If I wait a couple minutes I can hit start and it says started successfully but then the error comes back in log. It was working fine. I tried doing a manual reinstall but same issue. (go to store, click install, and click the reinstall same slot button) Log Attached Kasa_11-16-2022_63106-AM.zip

not sure why they are doing this but has to be due to their new "limits" and they have to force you to get a new API key to enforce the limits.

Mine is working now and what I had to do is a pain. First I had to get a new API. Mine has not changed but they deactivated it. Maybe I was on old plan. Second I had to change the rules to cover the new limits like lower forcast to 7 from 16. If I were you I would use a new email and get a new API. Try putting that one in and see what happens. Jeff

See screenshot from store. It installs 3.0.13

Can you verify that the only way to get 16 days forecast now is to pay $40 a month. I don’t need 16 days enough for $40. I can deal with seven. Not sure if I need to buy the hobbyist which I would do that but it’s still only Seven days forecast and it’s OK. I will stop the weather emails for a few days until you fix it. I leave on my trip Friday afternoon so hopefully it might be done by then but if not I can do it while on vacation. I know this is their fault so thanks for all your efforts

I assumed that so I got a new API as a test and it did not work so that verified it’s not a timed out type of thing

they changed it again. This could be it 50 calls/day 7 day forecasts NON-COMMERCIAL USE ONLY 95.0% Uptime If I am correct I need to do 1725 seconds for short poll Tried it and still no luck. Also reinstalled Node server with a old API and another one with New api same on both but seems to get stuck on this. Sent data in PM to @bpwwer DEBUG Controller:start: *** Waiting for all nodes to be added

Update- The forecast is a day off!!! So it must be showing old data. I am seeing Friday as today and Saturday as tomorrow and its Saturday now

Mine are at 300 and 600 I am getting the forecast just fine but the main status page reports all zeros. I only noticed because I updated the ISY to the new 5.4.5 firmware and then checked each Node server I also changed nothing except for the PG3 update the other day and the ISY update today. will send you logs via PM Jeff

Seems to have worked fine for me except one Node server is posting wrong data. It is weatherbit but probably a different issue.

again I did manually do it about 6pm my time eastern. I will PM you the log

Figured out a way. If you go into the MORE INFO there is a reinstall button. Bet most people would not even know its there but it worked. Now on 2.01

So I restarted the Node server and it DID NOT update Climacell. I tried multiple times. So does that mean I have to erase and reinstall the Node server? Thats a pain with lots of programs and info set to variables.

it shows up in the store but I posted on your PG3 support thread Climacell is updated. PG3 used to tell me when there is an update. Now it is not. Going to leave it for the day on old version in case you want me to test something later. But that blue box saying upgrade is not there. I am clearly on 2.0 and 2.01 is out. Is that a bug in the new Pg3 .14 update? I did try another browser to make sure it was not cache

@bpwwer Noticed Climacell is updated. PG3 used to tell me when there is an update. Now it is not. Going to leave it for the day on old version in case you want me to test something later. But that blue box saying upgrade is not there. I am clearly on 2.0 and 2.01 is out.

you can always log into ISY portal and I think its under information you can get the address to plug into admin console so you can log in from outside the ISY location. I also open a port through the router to make sure I can get in but make sure you use a 5 digit port like 44444->8443 and/or 33333->8080 I would go with https though. 4 digit ports are more frequently hacked, but the ISY portal method is your safest. Jeff

If it’s formatted http//111.11.11.11:8080 or https//111.11.11.11:8443 then try a polisy or at least an IOP reboot. mine rebooted automatically for some reason but maybe it’s only because of another update

All I know is that I switch the trigger of the routines to virtual buttons from ISY variables and they worked perfectly when the ISY variables were not triggering.

Open your old file in a text editor. The addresses are in there. Most end with /desc

I did notice it said DISCONNECTED for a while also with a red banner. All I did is refresh the page and then it said connected. I also see this if I try to restart a couple node servers in a row it gets confused. I will hit restart on one. go back to dashboard, go to another and sometimes it still says name of previous Node server. Again refresh the browser works. I know its not your issue here but it slows me down having to refresh all the time.

If you need any help with it let me know. I have 99 buttons installed and using over 70 of them!!! Install Node server Put in your access code (see Node server to get one) Name your buttons Then in Alexa create a routine (or if existing routing there is a change trigger option under the ... menu in each routine) Then in the ISY go to that button and click the PUSH BUTTON button. The routine will trigger. Even when Alexa was down it worked perfectly.

maybe they need to move off those buggy Amazon Web Servers LOL Just kidding. I saw app update for iOS today also. But yes I have seen intermittent issues. I gave in and used a Pg3 Node server called Virtual Buttons to trigger alexa rather than use variables as motion or contact sensors. It continues to work flawlessly. I also setup a program that updates a variable every hour and that variable should trigger alexa to say TEST SUCCESSFUL and send me a notice (of course not overnight LOL). It missed a few so they are having issues. But virtual buttons works every time.

check your ISY. Mine restarted after running it and I did not realize it. Make sure you can get in with admin console. I think the restart was from all the other package updates But also try reloading the page as sometimes the cache messes things up. If its still not working then wait for @bpwwerto respond. I would personally try a reboot of the entire polisy. One more thing. Did you wait when updating for the 4 or 5 beeps. It took a while for mine to update. Just some thoughts.