For instance HHZ should return results for Helmholtzstraße but instead we get the ones for Pulsnitzer Straße.

curl -X "GET" "http://widgets.vvo-online.de/abfahrtsmonitor/Haltestelle.do?ort=Dresden&hst=HHZ"
[[["Dresden"]],[["Pulsnitzer Straße","Dresden","33000290"]]]

Removing ort=Dresden from the request seems to fix the mixup.

curl -X "GET" "http://widgets.vvo-online.de/abfahrtsmonitor/Haltestelle.do?&hst=HHZ" [[["Dresden"]],[["Helmholzstraße","Dresden","33000742"]]]

Hi Kilian,
could you check if you get results for Albertplatz? At the moment I can't, but there might be results as you can see here.

Thanks in advance :)

<div style="border: 3px solid #4991C5; font:1.5em; font-family:tahoma,calibri,arial; font-weight:bold; color:#1A4369; padding:5px; margin:10px; text-align:center"> The specified URL cannot be found. </div><!--0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234-->

While investigating the issue of no results being shown in alfred_dvb I discovered that the bug actually originates from some changes on the server side in the expected arguments of HTTP GET requests made by dvbgo.

The paramter lim=0 in a request like http://widgets.vvo-online.de/abfahrtsmonitor/Abfahrten.do?hst=Helmholtzstraße&lim=0&ort=Dresden&vz=0 causes the response to always be []. Simply removing it by commenting out line 24 params.Set("lim", "0") in dvb.go fixes this.

However, new strange behavior can then be observed:

• Stop queries of length 1 will deliver an HTML response body containing an error message
  see issue #5
• Some DVB short names for stops get misinterpreted and therefore results for the wrong stop are shown
  see issue #6

Is currently a regiobus

Since EFA is going to be shut down at some point in the rather near future, it seems like a good idea to use the chance to migrate to use the WebAPI instead and also replace the widgets endpoint while at it.

Big upside is a whole bunch of new data being supplied by the WebAPI.