Everything posted by macjeff
-
Error updating RAINRT
more issues. We can move to another topic but I think the fix for all of the issues is to erase and install. I had two units (an old air and sky) replaced by them. I did this over a month ago 1. Changed the ID for the air and Sky. New ones showed up. 2. Deleted the old nodes Then today when I rebooted the two old nodes came back. I thought I had deleted from the PG3 configuration which auto deleted from the ISY but it did not. I tried to delete today from pg3 and it says error removing node. I will send another Pg3 and weatherflow log to you now since I did this after the last log If erase Node Server is needed I will do that.
-
Error updating RAINRT
I will PM you the entire PG3 log Check between 6:30 and 7:30 am my time
-
Error updating RAINRT
I saw the message (PG3 3.1.15) and it said version 3.0.26 was avaialable I hit restart and it took a while and came up. Message is gone and its running but it still says 3.0.25 not 3.0.26 I can do the reinstall if you want but you had said not to do that unless instructed. WeatherFlow_12-1-2022_72749-AM.zip
-
WeatherBit Weather - Prob. with updates
I’m not sure if you have iCloud email but one of the secrets and that is you can use iCloud.com, me.com, or Mac.com. So you get three email addresses for the same account. But you could also sign up for a quick Gmail account
-
WeatherBit Weather - Prob. with updates
I had to open a new account with a new email. They only allow one api per email to be issued.
-
3.0.14 wont start
yes. It would stop on the MQTT error.
-
3.0.14 wont start
Nothing worked. Start or restart would show up 1, 2, 3, 4 and by the time it hit 5 seconds it would stop counting but would still say connected. I did a reboot of pg3 and now ok.
-
3.0.14 wont start
Yes. Restarting does not work at all. The reinstall is the only way I have been able to update recently. I have reported the bug and waiting for the fix. I am running now fine on KASA. Just had to reboot PG3
-
3.0.14 wont start
would a Pg3 reboot fix?
-
3.0.14 wont start
I have polyglot 5729 0.0 1.3 102320 51952 - I Tue07 1:02.36 python3 ./kasa-poly.py (python3.9) admin 31538 0.0 0.1 12840 2420 0 S+ 14:55 0:00.01 grep kasa I might be doing something wrong but did kill 31538 and it says no such process what am I missing?
-
3.0.14 wont start
I will do this later on today but I can’t do now
-
3.0.14 wont start
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
-
3.0.14 wont start
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
-
WeatherBit Weather - Prob. with updates
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.
-
WeatherBit Weather - Prob. with updates
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
-
Version 3.0.13 on store but labeled as 3.0.12
-
WeatherBit Weather - Prob. with updates
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
-
WeatherBit Weather - Prob. with updates
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
-
WeatherBit Weather - Prob. with updates
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
-
WeatherBit Weather - Prob. with updates
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
-
WeatherBit Weather - Prob. with updates
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
-
Support thread for: ISY on Polisy (IoP) v5.4.4 (May 25, 2022)
Seems to have worked fine for me except one Node server is posting wrong data. It is weatherbit but probably a different issue.
-
Polisy - Support thread for: PG3 v3.1.6 - v3.1.16 (December 9, 2022)
again I did manually do it about 6pm my time eastern. I will PM you the log
-
Polisy - Support thread for: PG3 v3.1.6 - v3.1.16 (December 9, 2022)
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
-
Polisy - Support thread for: PG3 v3.1.6 - v3.1.16 (December 9, 2022)
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.