macjeff

I assume if I delete those keys, it will just work now without the username and password. I just wanna make sure I don’t have to enter in new keys for that info

1. so I was running the last release (3.1.14) and working fine. Tested your beta (3.1.16) and I get bad configuration. ** see image for what I had in 3.1.14 that errors in 3.1.16 2. in both 14 and 16 I am getting bad config on garage. Do the ID have to be 200's? So lets fix for 16 so I can move forward. Whats wrong with this "type": "garage", "name": "VirtualGarage1", "ratgdo": "False" that also gives bad configuration. THANKS Jeff

FYI- This fixed Admin Console but I use the variable (Thunderstorms) in emails. They still said Thunderstoms (no r) until I rebooted the EISY. Now its ok.

Log into your account. Look at the top where it says your plan. If it says RESTRICTED then you have been restricted. If you cant log in at all they have banned your email (that happened in the past) if it says free plan then it should be working.

Thanks. I switched from Weatherbit. Not sure if you saw the other posts but it hit limit and I did not catch it so they killed the API KEY. So I created a new one. Then they sent me email that I violated their terms of 1 API key per location and blocked my IP. I emailed them back but they said no appeals. It was an accident. I fixed it as soon as I saw. Been running it for years. Hopefully this keeps working.

I just started using this. Thunderstorms is coming in spelled wrong!!! Spelled ThunderSTOMS (no R) can you please fix?

It is really a Love/Hate relationship with them. After a year of no issues, something happened and my setting for short poll got set too low and I hit limit. They deactivated my API because I did not realize for a few days. So I created a new API. 24 hours later that was restricted. So I tried another and it wont let me create one. I tried on cellular and it works. This confirmed they blocked my IP. For now I upgraded the account but it is 45 a month or 40 if you pay for a year. I CANT AFFORD THAT. The upgrade does give you tech support so I emailed them and asked if they can do something to work with me. Anyone else have any experience with this.

Weatherbit confirmed it was disabled for too many calls on consecutive days. So I created a new one and its working and set to 5000 as indicated in last post. Going to email Benoit as to WHY this setting reset itself from 5000 to 2500 on BOTH my EISY (one was disabled though as they also wont let you use the same API on two devices) The last day it worked was last Thursday and I have not rebooted it in a month. STRANGE.

That most likely is the problem. Verified with another EISY. Somehow my setting went to 2500. It was 5000 which is about every 90 min. 2500 is under so its timing out. I have screenshots of my settings and it was 5000 a month ago. This should not have happened.

I have 2500 and 43200 for my polls. that has worked until now.

Bob- can you confirm its working now? They told me its up and running and my API is valid. Restart your nodeserver and see if you can error Query failed with 403 : {"error":"API key not valid, or not yet activated. If you recently signed up for an account or created this key, please allow up to 30 minutes for key to activate."} a57d9a9dd7364655b6b16cfaaa801b8a been using it for a year now with no issues

Thats correct. I have found always install the latest Pg3x before EISY-UI latest update. It has had issues a few times. But remember EISY-UI is alpha. The latest release Friday is pretty stable.

try one Assuming you waited until the AC said time to reboot (it takes a while to do some of the upgrades) Try one more reboot..

Netatmo API - API Domain Name Change Dear Netatmo developer, We hope this message finds you well. We are writing to inform you of an upcoming change to our API domain configuration. As part of our ongoing efforts to streamline and improve our services, we will be retiring the domain api.netatmo.net and consolidating all API traffic under the existing domain api.netatmo.com. Effective Date:September 8, 2025 To ensure uninterrupted service, we kindly ask you to update your applications to use api.netatmo.com exclusively before the above date. The structure and functionality of the API remain unchanged — only the domain name is affected. Sincerely, Legrand - Netatmo - Bticino

Try again. At first it was not installing the new version but now I am at 1.2.5 (not 1.2.4)

I have many generation doorbells and noticed today none of them are showing battery, I ignored it since even my gen 1 are hardwired, but I think it should show 100% when you are hardwired now that I think of it. Not sure if it ever showed 100% or not.

same issue here. Worked for a few hours after authentication Ring Status shows 100% operational. LOL

Yes got it with WARNING in both release and beta. Not every time but when I restart I see the error. Sent you logs from both.

I am running the beta to support a new device. Can I replace the production since its working? I hate having to install twice to get one device working along with the other older devices

I sent mine to you yesterday with debug + Modules.

I am seeing this too after tryiing to add a new device. I got an EP25 (homekit model but its also wifi) I will send you the log file

see preious post but need to add this my zone is western Loudoun which is part of the PUBLIC ZONE list. There is also a county zone list. If you use that list its the entire county. We are in a LARGE county. If you use the entire county we could be under a winter storm warning with snow while the other half (Eastern Loudoun) is rain. Go here. Look in public zone and you will find eastern and western loudoun https://alerts.weather.gov/?reset=true Then on same page look in COUNTY zone and find LOUDOUN. Thats working. (VAC107) But I have had the VAZ505 in there since day 1 and always worked until now. So it is working for the COUNTY but not the PUBLIC zone that it used to.

See screenshot showing VAZ506 (see url) Shows active watch and warning. See NOAA. NOTHING And logs attached but issue is they may be gone by the time you get this. But you can plug in and see if you do before midnight EDT. I did just restart 025-05-05 18:05:14.200 Thread-4 (start) udi_interface DEBUG noaa:query_alerts: Parse XML and set drivers 2025-05-05 18:05:14.200 Thread-4 (start) udi_interface DEBUG noaa:query_alerts: <?xml version="1.0" encoding="UTF-8"?> <feed xmlns="http://www.w3.org/2005/Atom" xmlns:cap="urn:oasis:names:tc:emergency:cap:1.2"> <id>https://api.weather.gov/alerts.atom?zone%5B0%5D=VAZ505&amp;limit=500&amp;active=1</id> <generator>NWS CAP Server</generator> <updated>2025-04-29T00:00:00+00:00</updated> <author> <name>w-nws.webmaster@noaa.gov</name> </author> <title>Current watches, warnings, and advisories for Western Loudoun (VAZ505) VA</title> <link rel="self" href="https://api.weather.gov/alerts.atom?zone%5B0%5D=VAZ505&amp;limit=500&amp;active=1"/> </feed> 2025-05-05 18:05:14.200 Thread-4 (start) udi_interface DEBUG noaa:query_alerts: Parse XML and set drivers 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:query_alerts: No alerts found. 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV21 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:query_alerts: No alerts found. 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV21 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV21, 0.000000) 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV21, 0.000000) 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV22 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV22 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV22, 0.000000) 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV23 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV23, 0.000000) 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV24 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV24, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV25 to 0.0 to Polyglot 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV25, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV26 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV22, 0.000000) 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV23 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV23, 0.000000) 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV24 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV24, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV25 to 0.0 to Polyglot 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV25, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV26 to 0.0 to Polyglot 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV26, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV27 to 0.0 to Polyglot 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV27, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV26, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV27 to 0.0 to Polyglot 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV27, 0.000000)

I will monitor. There are no warnings now but the next time there is I will check. One issue we have. VAZ506 is the county but since the western half of Loudoun county where I live is higher elevation they split it mainly for Winter. VA505 is Western Loudoun When I searched BOTH yesterday until 10pm last night there was a watch. I will email you when one is issued again if not working. thanks

Had a severe thunderstorm watch and warning. Neither showed up. watch is still in effect for 3 more hours. My zone is VAZ505 I tried a few others with active alerts and same issue. So most likely they changed their format again NOAA_5-3-2025_70932_PM.zip