🌘 Lunar Phase Integration for Home Assistant

VietNgoc · October 4, 2024, 8:51pm

Hi @Mats789 , for integration you can add another json file with translation from en.json and make PR to repo here and for the custom card I have guideline here. Looking forward to the PR

If you don’t want to follow these steps, you can translate these files and send me a PM.

https://github.com/ngocjohn/lunar-phase-card/blob/564c0e8feb72471db8daaca401479a3517a1f41a/src/localize/string.json

https://github.com/ngocjohn/lunar-phase/blob/f0f50ff0e4dd25d5e5e01be04b39dc977eaa9a46/custom_components/lunar_phase/translations/en.json

RickFurtado · October 19, 2024, 1:35am

I’m having an issue with the integration that may be a bug, or I’m missing something.

My last full moon was yesterday, Oct. 17. If I look at the Lunar Phase card the next full moon is Nov. 16. But the sensor still says that the next full moon is Oct. 17, this is messing up other templates and automations that pull from this sensor.

Why is the Lunar Phase Card showing a different value than the sensor it should be reading from?

Edit: Reloading the integration fixed the issue, hoping I won’t have to do this every full moon though.

VietNgoc · October 20, 2024, 12:51pm

HI @RickFurtado , I admit I know about this bug. The problem is mostly with timestamp sensors. They update normally for a few days, then for some reason they stop writing to the state. I have no idea for what reason this is happening. In the debug log, the data is correct, but the sensors are just not updating

For the lovelace card, the js library is used and the data is updated as soon as it is added to the dashboard. There is no problem. I will try to find a better way to update the data for integration.

nicknol · October 20, 2024, 6:14pm

@VietNgoc
thanks for letting me know that you’re aware of this bug/challenge. And I agree with @RickFurtado, building reliable automations require reliable sensors.

What do you think about create a service or action (since 2024.10) to reload the integration. We could schedule a regular reload and the sensors are updated, at least once a night.

VietNgoc · October 20, 2024, 8:26pm

You can definitely set up automation for reload integration, that will be the best option until I come up with a solution.

the command to reload the integration

action: homeassistant.reload_config_entry
data: {}
target:
  device_id: d64f95437572d8e12d2e92ea32b8dafc

you can get the device id from the integration url, or use template in automation, replace entity id with your sensor id

target:
  device_id: "{{ device_id('sensor.prague_moon_phase') }}"

RickFurtado · October 20, 2024, 10:40pm

That’s what I did until/if there’s a resolution. Thank you for your attention to this @VietNgoc.

nicknol · October 21, 2024, 5:35am

I do the same.
thanks @VietNgoc

cyn · October 23, 2024, 3:07pm

Anyone else using this in the US? I’m using America/Denver time zone and Next Full Moon appears off by 1 day (11 and a half hours). According to Google Calendar Next Full Moon is 11/15 2:29pm, lunar phase integration says 11/16 1:58am

VietNgoc · October 26, 2024, 4:49pm

v1.6.0

New Features

Add Moon horizon graph by @ngocjohn in Add Moon horizon graph by ngocjohn · Pull Request #26 · ngocjohn/lunar-phase-card · GitHub

The graph displays the altitude of the Moon throughout the day. It also includes moon phase information and moon rise/set times.
2024-10-26 04 14 59
If you enjoy these new features, consider giving the repo a to show your support!
Full Changelog: Comparing v1.5.0...v1.6.0 · ngocjohn/lunar-phase-card · GitHub

Amberlilly · October 27, 2024, 8:06am

Same here in Europe, Zurich.
In integration next full moon is set for Nov 16, 8.58 am. But timeanddate.com as few other full moon calendars have next full moon already 10 hours earlier. Nov 15, 22.28 pm.

RickFurtado · October 27, 2024, 3:33pm

Same, Lunar Phase is late on the next full moon by 16.5 hours for me both in the card and the entity state.

@VietNgoc I love the concept of this integration, but I think you need to focus on functionality and accuracy before fancy new features. The new moon-to-horizen graph is cool and all that, but there’s no accesible data. And quite frankly considering other inconsistancies I won’t trust its accuracy. I’ll keep the integration for a bit in hopes that these issues can be resolved, but it’s not going to last if all it is is pretty and cool.

I appreciate your work on this and remain hopeful.

VietNgoc · October 27, 2024, 5:01pm

Hi @RickFurtado , the card is not using data from the integration. There I claim it is without problem. I’m still working on the integration bug.

postmaster11 · November 13, 2024, 7:09pm

Hi! Cool project, thank you!
Would like to print the next fullmoon on an oled display. How should I create the sensor in yaml (platform?)? I searched the suggestions from the code-editor but didn’t find anything moon-related . Thanks for your help and best regards!

nickrout · November 14, 2024, 5:01am

My lunar phase integration creates a sensor called sensor.christchurch_next_full_moon (Christchurch is my location). It contains the date and time of the next full moon.

How are you setting up your OLED? Assuming it is esphome.

If so you can import that sensor into esphome with Home Assistant Sensor — ESPHome

postmaster11 · November 14, 2024, 12:00pm

Hey - thanks a lot for your reply! I think that’s more or less what I’ve tried yesterday, but currently the sensor seems not to receive any data.

Code for the sensor:

  - platform: homeassistant
    entity_id: sensor.schafisheim_next_full_moon
    id: next_fullmoon
    name: "Next FullMoon"

And for the oled:

if (id(next_fullmoon).has_state()) {
        it.printf(64,63, id(font1), TextAlign::BOTTOM_CENTER , "%d.%B %Y", id(next_fullmoon).state);

my sensor:
sensor.schafisheim_next_full_moon

I’ve not tried to used entity-id instead of entity, but as far as I understood both should be possible. Will try anyway…

I wasn’t sure about the “platform” I should reference to and therefore tried “homeassistant”. Do you think this is correct or do you maybe see another mistake I made?
I can successfully print time, date, temperature, humidity and WiFi-status to this display, communication seems to work fine.
Thanks you and best regards!

nickrout · November 15, 2024, 4:40am

Could you please let me know what you see in the esphome log regarding this?

I think on reflection that you need to import it as a text sensor

postmaster11 · November 15, 2024, 7:19am

I changed my code to a text_sensor:

text_sensor:
  - platform: homeassistant
    entity_id: sensor.schafisheim_next_full_moon
    id: next_fullmoon
    name: "Next FullMoon"

This is what the display is currently showing (left display, bottom line)

I checked the logs on the device-api, the sensor is not mentioned there. The only thing I could find about lunar-phases is in the core-log:

Logger: homeassistant.helpers.frame
Source: helpers/frame.py:189
First occurred: November 13, 2024 at 7:46:38 PM (1 occurrences)
Last logged: November 13, 2024 at 7:46:38 PM

Detected that custom integration 'lunar_phase' calls async_forward_entry_setup for integration, lunar_phase with title: Schafisheim and entry_id: 01JCKDJP373R9GH0Z0DKZ1J1TC, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/lunar_phase/__init__.py, line 50: await hass.config_entries.async_forward_entry_setup(config_entry, "sensor"), please create a bug report at https://github.com/ngocjohn/lunar-phase/issues

And after installing the new code, the device seems to have connection-issues. When I start the log-output in esphome it takes longer to connect to the device and after a few seconds the connection breaks. Submitting sensor-values seems to work fine so far.

Do you think the sensor-syntax should work like that? Is there another place to search logs?
Thanks for your help and have a great day - cheers!

VietNgoc · November 15, 2024, 11:57am

Sorry mate, I have no idea how ESP Home works. But the sensor has a timestamp class. Isn’t there any way to calculate the state to the normal date in esphome?

something like this?

edit:
After a quick look at how esphome works, I thought you could create a new sensor using the helper that only shows the state from integration as ‘text’. So you can then simply import it into esphome as a normal text sensor.

postmaster11 · November 15, 2024, 6:44pm

Thanks a lot for your time and help! And not a very used coder, I’m learning day by day.
What I don’t understand: why do I need this helper-sensor? Is it not possible to use the sensor lunar-phases creates?
I’ve found this
Publish timestamp into text_sensor - ESPHome - Home Assistant Community

and therefore tried the following - without success so far:

text_sensor:
  - platform: homeassistant
    entity_id: sensor.schafisheim_next_full_moon
    id: next_fullmoon
    name: "Next FullMoon"
    device_class: timestamp

I still guess that platform is wrong.
However, I’m not really used with templates. Thanks to your screenshot I managed to create the sensor, now I’ll try to get the string to my display.
Will report progress, thank you very much!

nickrout · November 15, 2024, 7:08pm

I find dates and times very bloody confusing.

This

text_sensor
  - platform: homeassistant
    entity_id: sensor.christchurch_next_full_moon
    id: nfm 
    name: "Next Full Moon"

does get the date and time into esphome. You can see it in the esphome log

'sensor.christchurch_next_full_moon': Got state '2024-11-16T08:58:14+00:00'
[23:20:26][D][text_sensor:064]: 'Next Full Moon': Sending state '2024-11-16T08:58:14+00:00'

By the way, your log is not the esphome log, it is the HA log.