I'd be careful about this, they explicitly do not want you to use their websocket as a public api (hence the obfuscation in their protocol), I wrote a JS library and opted not to play cat and mouse with them.

Their site specifies how to use the data [0] under "Services that use our data".

[0] https://www.blitzortung.org/en/contact.php

From the repo:

    Data is served through a public MQTT server (dedicated to serve requests for this component) - thanks to geohash-based topics and some other optimizations it greatly reduces amount of data sent to clients comparing to direct websocket connection to Blitzortung servers (it is also required by Blitzortung data usage policy - third party apps must use their own servers to server data for their own clients).

The Home Assistant integration works very well (once I figured out how to configure it.)

I use it to set off alarms to get out of the pool, and self-power-down sensitive systems.