Looks like CHAPS pulled the plug

[bruxy70]

The integration was calling API without the user_id, which is meant for testing and supposed to work for limited queries only.
But it now stopped working, returning "invalid user id". So it looks like the user id parameter is now mandatory.
I did ask them some time ago where one can get a valid user_id, but they did not reply.
So I guess it will be the end of this integration, and I haven't found an alternative (apart from web scraping, but this is specifically banned on their web as well as for Home Assistant).

[vlak6613]

Dear Bruxy, I know this is not the right way to get in touch with you, but I didn't know any other way for a while and I think you can help me. I hope so.
i have a problem with my esphome configuration with an nextion display. Actually I have it completely working, only I get an annoying message. I use a number of sensors that I want to show on page 3. Now I have the config so that this also happens. But if I am now on a different page then I get a warning (yellow) in my log from my esphome (see attachment). I expect to somehow have to point my sensors to page3 but I just don't know how to do this. i hope you can help me with this.

CODE ESPHOME
display:

• platform: nextion
  update_interval: 5s
  lambda: |-
  // Do not wait for ack (this delays the whole procedure a lot, and has no use)
  it.set_wait_for_ack(false);
  auto time = id(sntp_time).now();
  it.set_component_text_printf("hour","%02d",time.hour);
  it.set_component_text_printf("minut","%02d",time.minute);
  it.set_component_text_printf("outside","%2.1f", id(temp).state);
  it.set_component_text_printf("vocht","%2.1f", id(vocht).state);
  it.set_component_text_printf("rain","%2.1f", id(rain).state);
  it.set_component_text_printf("lux","%2.1f", id(lux).state);
  it.set_component_text_printf("luxin","%2.1f", id(lux_woonkamer).state);

WARNINGS
[23:58:09][D][nextion:209]: Got touch page=3 component=1 type=PRESS
[23:58:10][W][nextion:177]: Nextion reported variable name invalid!
[23:58:10][W][nextion:177]: Nextion reported variable name invalid!
[23:58:10][W][nextion:177]: Nextion reported variable name invalid!
[23:58:10][W][nextion:177]: Nextion reported variable name invalid!
[23:58:10][W][nextion:177]: Nextion reported variable name invalid!
[23:58:10][W][nextion:177]: Nextion reported variable name invalid!
[23:58:10][W][nextion:177]: Nextion reported variable name invalid!

[bruxy70]

Try this: https://github.com/Andoramb/Nextion-wall-mount/blob/master/YAML/NextionDisplay.yaml

The ESPHome display component supports pages: https://esphome.io/components/display/index.html#display-pages
But I am not sure if that works on Nextion displays. Try that, let me know.

[Elot]

Isn't possible to use this data? https://opendata.praha.eu/dataset/dpp-jizdni-rady or https://opendata.praha.eu/dataset/jizdni-rady-pid (looks more maintained) It is not API but the data are there...

[bruxy70]

Maybe it is. Home Assistant has GTFS integration. But I did not have the time to try that.
I am actually looking at Golemio - they have REST API.
What I do not like is, they will not search for the best connection. They will only show a timetable of a specific line on a specific stop. So if there is a better alternative connection, I'd have to compare that manually. Also, Goilemio is Prague only. But I guess better than nothing.

[Elot]

I didn't know that Golem.io have implemented PID / ROPID timetables. I Can't google it out. I always end up at opendata.praha.eu

[bruxy70]

https://golemioapi.docs.apiary.io/#reference/public-transport/gtfs-trips/get-all-gtfs-routes

The link is at the bottom of this page (Dokumentace): https://golemio.cz/cs/node/619#datove-zdroje

[Kobtul]

Do you plan to implement Golemio API?
I use small python script to get the data, but I am a bit lost in the Home assistant integrations.
The request for station looks like this:
'https://api.golemio.cz/v2/departureboards/?names=Station-name&preferredTimezone=Europe%2FPrague&orderBySchedule=false&showAllRoutesFirst=false&limit=somelimit'
and x-access-token is necessary in the header.

[halecivo]

Hello @bruxy70 , still no plan to go with Golemio?
I am able to use REST sensor in home assistant to get data I need - finally this project helped me a lot to learn how to configure it.

Having it as integration with simpler configuration could help the others. But in case you don't plan to work on it, I wanted to paste here a link to a project, which helped me.

[bruxy70]

I did not look a Golemio for some time. But last time I looked, it was not able to find a connection between two points. Just a time table of particular line on some station. And that does not help me, as i have multiple options and the first one is not always the fastest. So not I do not plan to develop an integration for that. Go ahead.