Travel-Status-DE-IRIS-2.04.tar.gz (signature)

• Update station and meta databases for rail replacement service around Düsseldorf / Wuppertal / Hagen / Dortmund

Travel-Status-DE-IRIS-2.03.tar.gz (signature)

• Add missing geocoordinates for two stations
• Update meta database

Travel-Routing-DE-DBRIS-0.08.tar.gz (signature)

• Deutsche Bahn have rolled out a rather aggressive Akamai EdgeSuite WAF configuration, and too-frequent requests made with this module may cause the corresponding IP address or range to be blocked for yet-to-be-determined amounts of time. Send more plausible requests with randomized user agent strings and additional headers to maybe hopefully slightly reduce the risk of this happening.
• New dependency: UUID

Travel-Status-DE-DBRIS-0.23.tar.gz (signature)

• Deutsche Bahn have rolled out a rather aggressive Akamai EdgeSuite WAF configuration, and too-frequent requests made with this module may cause the corresponding IP address or range to be blocked for yet-to-be-determined amounts of time. Send more plausible requests with randomized user agent strings and additional headers to maybe hopefully slightly reduce the risk of this happening.
• New dependency: UUID

Travel-Status-DE-IRIS-2.02.tar.gz (signature)

• Update station database

Travel-Status-DE-HAFAS-6.25.tar.gz (signature)

• Update service definitions. Fixes BVG service.

Just in case you're as curious as I was: yes, you can absolutely build a USB to DMX converter that uses a single UART both for receiving ASCII DMX frames via USB (e.g. using an FT232 or CH340G chip) and for sending out DMX frames to a MAX485 or similar. Just not at the same time, but that's what we've got TDMA (time division multiple access) for.

Or, to use a concrete example: yes, an Arduino Nano (ATMega328P with USB-to-serial on-board) can be turned into a USB-to-DMX converter by adding an RS485 adapter and writing a bit of firmware.

The idea is quite simple:

• Every 250 or so milliseconds, disable the UART receive interrupt, configure the UART for DMX output (250 kbaud, 8 data bits, 2 stop bits, no parity), and transmit a DMX frame
• Once done, configure the UART for serial input (e.g., 57600 baud, 8 data bits, 1 stop bit, no parity) and enable the receive interrupt
• Once a complete DMX frame has been received on the USB side, update the DMX output frame accordingly
• Rinse and repeat, making sure not to output any serial data via UART – it's scrictly DMX only

The single drawback is that, while DMX output is running, UART input will be lost – there's no receive interrupt, and even if there was, it would be gibberish due to incompatible UART configuration. However, 57600 baud is not that fast compared to 250 kbaud, so if the PC just transmits its desired DMX frame a few times in quick succession, one of them is bound to be received.

I implemented this in multipass as uart-to-dmx-mega328 and so far it's working reliably. Of course, it's not suitable for anything where you need sub-second scale timing accuracy. But if all you need are some static or slowly fading background hues, it works just fine. In my case, the Neutrik XLR plug used to transmit the DMX signals to a light fixture is probably by far the most expensive item in the entire setup, save for the light fixture itself.

Travel-Status-DE-DBRIS-0.22.tar.gz (signature)

• Further fixes for fundefined fvalues
• Update train and operator names (patch by Lili Chelsea Urban)

There's two noteworthy aspects:

Path Adjustments in libvirt / qemu

I'm running Home Assistant OS as a virtual machine on my home server. The HASS OS VM image relies on an OVMF file for booting; this file moved to a different path.

So, in order to make Home Assistant boot again after the upgrade to Debian 13, edit /etc/libvirt/qemu/hassos.xml (or similar) and change /usr/share/OVMF/OVMF_CODE.fd to /usr/share/OVMF/OVMF_CODE_4M.fd.

paho.mqtt.client changes

The upgrade from python3-paho-mqtt 1.6.1 to 2.1.0 came with some changes in its API. In order to make it happy (and not spew any warnings), replace paho.mqtt.client.Client() with paho.mqtt.client.Client(callback_api_version=paho.mqtt.client.CallbackAPIVersion.VERSION2).

Apart from that, everything went smoothly.

Travel-Status-DE-DBRIS-0.21.tar.gz (signature)

• Formation: Fix uninitialized value warnings

Travel-Status-DE-DBRIS-0.20.tar.gz (signature)

• Formation::Group: Update carriage name list (patch by Lili Chelsea Urban)
• Fix a variety of uninitialized value warnings

Travel-Status-DE-IRIS-2.01.tar.gz (signature)

• Update DB InfraGO delay / QoS codes

Travel-Status-DE-DBRIS-0.19.tar.gz (signature)

• DBRIS->new, ->new-p: Add optional num_vias key
• Journey: rename train, train_no to trip, trip_no. The former accessors are now deprecated and will issue a run-time warning when used.
• Journey->trip, ->trip_no: Improve handling of combined operator / line number prefixes; avoid using trip number as type / line number
• Journey: New accessors: types, type_at
• Location: new accessors: operator, trip_type
• dbris-m: Add -Or / -Oa options (show next stops of all departures)
• dbris-m: Add --route-entries option
• dbris-m: Provide more detailed operator information, if available

Travel-Status-DE-HAFAS-6.24.tar.gz (signature)

• station: Fix result->station->{eva} key

Travel-Status-DE-VRR-3.18.tar.gz (signature)

• Services: Fix VVS / update its API URL (patch by amélie)