danielsmith-eu / home-assistant-themeparks-integration

A Home Assistant integration that shows Theme Park waiting times using the ThemeParks.wiki API

home-assistant-themeparks-integration

A Home Assistant integration that shows Theme Park waiting times using the ThemeParks.wiki API

Now available in the default store!

How it works

When you add the themeparks integration you choose a themepark from the list. It then adds an entity for each ride, which looks like this:

The state of each entity is the current wait time, and is updated every 5 minutes, so you can either use the entity card to show this, or the history card to show the history:

You can of course add whichever rides you need to.

Advanced usage

A smart move would be to set automations when your ride of choice hits a low wait time, and then turn that automation on when you are at the park.

Todo / Missing Features

• The device added for a theme park doesn't show any information or link to the entities. Looks like a quick fix.
• No customisations.
• API access is in the Integration, this should be move to PyPi so that we can add this to HA without using HACS.

home-assistant-themeparks-integration's Issues

Feature Request: Extract more data from API to entity attributes, or more sensors (was: Changing API)

Hy!

First off: great integration!
I use it to track the Efteling themepark.
However, i did notice that not all rides (like the single rider que) are available.
I know of a different api that does show more including opening hours, busyness indication etc.
https://queue-times.com/nl/parks

Would you concider switching to that api or even make a seperate integration for it?

issue called async_setup_platforms instead of awaiting async_forward_entry_setups

running into this issue with the custom integration
running:
Home Assistant 2023.2.2
Supervisor 2023.01.1
Operating System 9.5

Logger: homeassistant.helpers.frame
Source: helpers/frame.py:77
First occurred: 3:10:55 PM (2 occurrences)
Last logged: 3:11:14 PM

Detected integration that called async_setup_platforms instead of awaiting async_forward_entry_setups; this will fail in version 2023.3. Please report issue to the custom integration author for themeparks using this method at custom_components/themeparks/__init__.py, line 45: hass.config_entries.async_setup_platforms(entry, PLATFORMS)

Walibi Holland not showing up in entities

Hi! Thanks for making this integration.

Unfortunately Walibi Holland does not work. I added multiple theme parks: Efteling, Europa-Park, Phantasialand and Walibi. Everything seems to work except Walbi Holland. It does not create any sensors. However all the other parks do create multiple sensors for every attraction.

I get these logs, all attractions show up and it is doing a "Running do_live_lookup in ThemeParkAPI" for every device added, but only one does not find any "Parsed API item":

[custom_components.themeparks.sensor] Calling do_live_lookup in ThemeParksCoordinator
[custom_components.themeparks] Running do_live_lookup in ThemeParkAPI
[custom_components.themeparks.sensor] Calling do_live_lookup in ThemeParksCoordinator
[custom_components.themeparks] Running do_live_lookup in ThemeParkAPI
[custom_components.themeparks] Parsed API item for: Anton Pieck Plein
[custom_components.themeparks] Time found

Thank you in advance,
Remy

Feature Request: Is it possible to hide some rides/attractions?

This is awesome, I love using this integration. Is it possible to hide some of the entities?

For example, there is no reason anyone would ever want to know the wait time of It's A Small World, at Magic Kingdom. I'd like to be able to hide that ride, among a few others.

Maybe it's possible already, I just don't know how to?

Feature Request: Allow polling time to be modified (was: Update Time)

What is the default refresh time for wait times and do we have the ability to adjust?

TIME_MINUTES was used from themeparks, this is a deprecated constant which will be removed in HA Core 2025.1

Logger: homeassistant.const
Source: helpers/deprecation.py:205
First occurred: 19:28:53 (1 occurrences)
Last logged: 19:28:53

TIME_MINUTES was used from themeparks, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTime.MINUTES instead, please create a bug report at https://github.com/danielsmith-eu/home-assistant-themeparks-integration/issues

Ride entities are not added to Theme Park device in Home Assistant 2024.6.1

Issue:
When adding a new integration entry for any Theme Park, Ride entities are created but not added as part of the Theme Park device. They are also not linked to the integration (because of the former, possibly?). Filtering the Entities table by the Theme Parks integration shows no entities, but the individual ride entities can be found as unlinked entities just fine.
See the attached screenshots below.

Symptoms:
Ride entities are "orphaned" and do not show under a given Theme Park device in HA. Enabling debug logging for the integration shows a potentially suspicious line regarding entities being added:

2024-06-09 20:33:14.066 INFO (MainThread) [custom_components.themeparks.sensor] Entities to add (count: <method-wrapper '__len__' of list object at 0x7fb958d33c00>): [<entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>, <entity unknown.unknown=unknown>]

See extended debug log:
home-assistant_themeparks_2024-06-09T18-33-17.359Z.log

Expected behavior:
I expect ride entities be created as part of their Device, just like other integrations do. I expect this to also solve the issue of these entities not being filterable by the Theme Park integration in the Entities table.

Home Assistant version:
HA Core 2024.6.1, running in a docker container.

After park hours the sensor is no longer available

It seems after the park has closed, there is not only no sensor data, but the sensor altogether has been removed. I was going to try and force a state for some trouble shooting, but it no longer exists.

How to set up

I don't see the list if available theme parks.

The information does not appear

Good morning,

First of all thank you for doing this integration as I was very interested in it a few months ago.

It seems that after adding the integration and adding "Disneyland Paris" and "PortAventura World" among others, no information appears.

It is the latest version.

Thank you. Regards.