I made an improved NOAA Tides sensor for my family's summer house

So when you do, give me so hints on how to do this as I have not done this in a long while.
Thanks

Basically, the data I’d be looking for are in the NOAA “Real Time files.”

These files are all listed at NDBC - Index of /data/realtime2/.

The file format is defined here.

For example, here are the first (most recent) few lines of a buoy data file:

#YY  MM DD hh mm WDIR WSPD GST  WVHT   DPD   APD MWD   PRES  ATMP  WTMP  DEWP  VIS PTDY  TIDE
#yr  mo dy hr mn degT m/s  m/s     m   sec   sec degT   hPa  degC  degC  degC  nmi  hPa    ft
2025 09 04 11 10 230  4.0  4.0    MM    MM    MM  MM 1012.8  16.8  17.1  14.8   MM   MM    MM
2025 09 04 11 00 230  3.0  4.0    MM    MM    MM  MM 1012.8  16.8  17.2  14.9   MM +0.7    MM
2025 09 04 10 50 220  4.0  5.0   1.0     8   5.2 117 1012.7  16.8  17.2  14.7   MM   MM    MM
2025 09 04 10 40 230  4.0  5.0   1.0    MM   5.2 117 1012.6  16.8  17.2  14.7   MM   MM    MM

Note the “MM” values. Those mean “Missing Data.” From what I’ve seen, these values are missing because that particular sensor only reports on a longer interval than the records are cut. It looks to me like any new values are posted to a new line, but for anything not new, you have to look down to previous lines to see the most recent value. I wonder whether that’s why I keep seeing “unavailable” entities in HA.

Could the NOAA Tides component just be pulling the most recent line? I haven’t had time to dig much deeper, but given that the component also keeps spamming my logs, that project is inching closer to the top of my list.

This HA plugin I updated a few months ago is still working for me.

1 Like

It is working for me as well. There is an warning message that I posted above that it will need fixing again.

I found the last “working” repository seems to be 404 now. I could not find any working repositories for this integration. Don’t kill me, but I used claude to review the current API and make the changes needed to get it working. It is 6 lines of code to change, but it is now working for me. I forked the OG integration, and it’s here for anyone to use.

ptdalen/home_assistant_noaa_tides: A fork of Home Assistant’s NOAA Tides sensor with additional features.

I see in the read me for this fork there is a time_date, beat option. In the docs for Time_date, there is no beat option. Time & Date - Home Assistant.

Also if you are updating this, I have been seeing in my logs for a long time


Logger: py.warnings
Source: custom_components/noaa_tides/sensor.py:226
integration: noaa_tides (documentation)
First occurred: 8:57:04 AM (2 occurrences)
Last logged: 9:03:04 AM

/config/custom_components/noaa_tides/sensor.py:226: FutureWarning: Series.__getitem__ treating keys as positions is deprecated. In a future version, integer keys will always be treated as labels (consistent with DataFrame behavior). To access a value by position, use `ser.iloc[pos]` self.attr["air_temperature"] = self.data[1].air_temp[0]```

Thanks.

I’m using this from hacs to take care of beat time

I had been using the jshufro/NOAA Tides component for years without too many problems.

Recently I found out about Flight-Lab/HA_Noaa_Tides which exposes more tide information details.

Check out the My journey plotting NOAA Tides thread for more details.

I switched over to it and the graphs shown in the above thread from ASBishop and busman.

Take a look.

2 Likes