Jump to content

macjeff

Members
  • Posts

    914
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

macjeff's Achievements

Advanced

Advanced (5/6)

110

Reputation

  1. 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.
  2. 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
  3. I sent mine to you yesterday with debug + Modules.
  4. 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
  5. macjeff

    NOAA Alert Issue

    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.
  6. macjeff

    NOAA Alert Issue

    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)
  7. macjeff

    NOAA Alert Issue

    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
  8. macjeff

    NOAA Alert Issue

    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
  9. I was replying to Matthew Jocko so you should address Matthew for me JAVA cache does need to be cleared but if not it gives you issue when logging in. His is that it wont show up at all.
  10. Have you tried replacing EISY local with the IP address? Can you SSH into it? Also a second reboot is needed sometimes. You may have to do manually.
  11. First Apple TV can be used as a hub and without an apple tv or a full time mac, homekit wont be available outside your home. That's good, but if you're looking for push notifications, unless UD Mobile works on AppleTV, which it doesn't as of now, you will only get Security notices (Locks, garage doors, window sensors, etc) As far as the date, it is in late Alpha now. It is not ready for prime-time beta testing yet.
  12. Its also iOS. On the App Store.
  13. I have seen this in testing. Reported it but not much they can do. I think adding a second reboot may be necessary to instructions.
  14. sorry that I am the one who always finds the issues. But having the alerts was really nice for the storm. Jeff
  15. We had a winter storm watch. Worked perfectly and programs ran. That changed to warning. Also worked perfectly. Warning has expired for about 10 hours now. But its not clearing on my end. So it looks like it cleared fine when a new warning replaced it but NOT when the alert went back to NONE I ran the URL that I see in logs (logs attached) and I can see it seems to have issue. I restarted the nodeserver and it worked fine and Alert changed to none but I cant do that after every alert. Can you please take a look? Logs were in ERROR but changed to dubug and did Query a few times. Logs are before the restart. I just did one AFTER restart and added after restart to name https://api.weather.gov/alerts.atom?zone[0]=VAC107&amp;limit=500&amp;active=1 correlationId "1953878" parameterErrors 0 parameter "query.amp;limit" message 'Query parameter "amp;limit" is not recognized' 1 parameter "query.amp;active" message 'Query parameter "amp;active" is not recognized' title "Bad Request" type "https://api.weather.gov/problems/BadRequest" status 400 detail "Bad Request" instance "https://api.weather.gov/requests/1953878" NOAA_1-7-2025_103852_AM.zip NOAA_1-7-2025_103856_AM.zip NOAA_1-7-2025_104445_AM AFTER RESTART.zip
×
×
  • Create New...