[Feature Request]: get the displayed data in any HA sensor, maybe text sensor

[fft1010]

The request

Hi,
many thanks for adding my last feature request. I do have another idea, and just wanted to ask, if this could be done without being to time intensive for you. I like to have the displayed data

in an extra HA sensor. My goal is to have a small display at the exit of our house to display the first few lines on either a full sized ePaper with an ESP or a shelf display with OpenEpaperLink.

Displaying the formatted data (maybe separated by a colon) would be so much easier on such small devices as an ESP.

many thanks for considering.

Juergen

[github-actions]

Hi @fft1010, thanks for opening this issue! 👋

🚀 Feature Request

Thanks for the idea! We'll review it and see how it fits into the roadmap.

[FaserF]

Implemented and available now in the latest beta release 2026.01.1 https://github.com/FaserF/ha-db_infoscreen/releases/tag/2026.01.1

[fft1010]

HI,
I just installed the 2026.01.01 I can confirm that the Gear "somehow" works. What happens:
a.) If you install a new direction (aka Sensor), you are ask a couple of things, e.g. "VIA", "Gleise", ... It seems that this is for the finalrewind URL. If you than klick on the gear and than "Filter" they are not there, which IMHO is confusing. IMHO the existing already in charge config should be displayed. If you klick in the dropdown you see a selection. I try to write down a stepo by step what I am doing, and explain what the sensor shows:

1.) Fresh new "Eintrag hinzufügen"
Station: Hagsfeld Reitschulschlag, Karlsruhe
Datenquelle: KVV
Anzahl der nächsten Abfahrten 10 (IMHO doesn't matter what I write in there for the KVV API)
Gleise: 1, 3 (mind the SPACE!!! after the ,)
Zeige nur Abfahrten über Hagsfeld Jenaer Straße
Rest empty.
-> give s fresh new sensor :-) that looks good

2.) Klick on gear:

Allgemeine Einstellungen looks like:

Changed to 8, 8, instead of 4, 3
-> new loading of the API -> sensor looks great
Not I wanted to disable Stadtbus, which let me open "Filter Einstellungen"

The "ß" was my killer. It is encoded in the above which does not work with the API. See here API Call:

https://dbf.finalrewind.org/Hagsfeld%20Reitschulschlag,%20Karlsruhe?efa=KVV&via=Hagsfeld+Jenaer+Straße%2C+Karlsruhe&platforms=1%2C+3

It than works
If I than switch on the ePaper the sensor is empty. If I disable ePaper again, the sensor stays empty. If I klick on "Detaillierte Information" the api call refrash is tried many times, without luck it seems. I once got out with "disable station" while it realoded, and than HA said, I had to restart Home Assistant for final configuration.

So I could not get the ePaper Sensor to run.

all the best
Juergen

[fft1010]

Another hint:
If you once save something on "Anzeige Einstellungen" my API call from above is not working any more.

[FaserF]

bugs are now fixed