make-all / metlink-nz Goto Github PK

Signed up for an API key here: https://opendata.metlink.org.nz/dashboard

Added the home assistant integration, paste API key, no matter what I try it won't accept it:

"The api key provided is not valid. Check you have subscribed to the Metlink Open Data API."

Only thing is I have signed up the the Metlink Open Data API.

When using the integration on both the companion app in or browser (Safari/Edge Chromium) on iOS 14.6 device - the entities card displays 'Invalid Timestamp' for each stop that is monitored.

The integration runs fine on Android.

Hi there. I've recently noticed that my sensor for tracking the trains running from PAEK to WELL has started reporting as unknown. It has been running fine for the last 2 years, and I would blame an update to HA, but it's the only metlink sensor that's not working...

What works:

• My sensors for PAEK>WAIK and WELL>PAEK are working as expected in HomeAssistant.
• Querying the API directly through the Metlink Developer Portal preview and from Terminal via the provided curl script.

I've attached a screenshot of the Dev Portal, and the current sensor behaviour.

There are also errors being reported in the HA logs (I've attached a screenshot of the top level entry, but if you need more detail I'm happy to get it out for you).

Thank you for providing a very niche but very useful add-on!

Hi Jason

Nice Integration!

Quick question. If "Number of Departures to Track" is set to 3 then is it possible to show the next 3 departures on a card? If so which one would you use?

SteveW

Hi there,

Thank you for writing this integration. I have the below issue after pasting in my valid API key using the UI integration.
Error: "The api key provided is not valid."

When I configure the integration in my sensor.yaml; results are unavailable (I configure my sensors in a sperate file).

Sensor.yaml

• platform: metlink
  api_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  stops:
  • stop_id: 3244
    route: CP
  • stop_id: 5008
    destination: 3244
    num_departures: 3

I get this error when trying to reconfigure the integration:

Error
Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

Cheers,
Liviu