v0.4.0

Please note that, in accordance with the "pre-release warning" in the README, this version introduces a couple of changes that might be considered breaking in more stable software. In both cases, the behavior wasn't the original design, but it's possible that some users have got used to how it works now.

Potentially breaking changes

• Remove 'device' record by @Mallonbacka in #69 - if you've got an automation that expects the entity to be connected to a device, point it directly to the entity before upgrading. If you are upgrading, you might also end up with an empty device, which it's safe to delete or ignore.
• Don't save the subsequent departures list in history by @Mallonbacka in #73 - previous versions added a lot of information that was never intended to be saved to the recorder, and this version stops recording it. These data were never easily reachable, nor in an especially user-friendly format. If you're expecting a list of subsequent departures to be available in history (not just the countdown to the next departure), please don't update yet and open a GitHub issue describing your use case.

What else has changed

• Handle non-working Digitransit API key with repair by @Mallonbacka in #77

Full Changelog: v.0.3.2...v0.4.0