1.3.0 (2024-10-27)
- homeassistant: append textual steamid (steam_x:y:z) to the mqtt device name (9193d1a)
- homeassistant: publish cs2mqtt as a bridge device; use it as via_device for game state devices (98148ec)
1.2.1 (2024-10-13)
- homeassistant: show "inactive" for bomb when value is null instead of "unknown" (7292ef1)
1.2.0 (2024-10-02)
- mqtt: publish offline message to all availability topics on graceful shutdown (30db192)
1.1.2 (2024-09-17)
- homeassistant: use
availability_mode: allfor mqtt entities (32e8991)
1.1.1 (2024-09-15)
- mqtt: ensure no broker reconnect is attempted on graceful shutdown (4e0def7)
- mqtt: publish offline message to system availability topic on graceful shutdown (5248c52)
1.1.0 (2024-08-11)
- homeassistant: use assembly version for mqtt device sw version (9c64973)
- Bridge events from Counter-Strike 2 Game State Integration to any MQTT broker
- Separate events from multiple providers into their own MQTT topics
- Keep track of the latest game state and emit the same data only once, using the MQTT retain flag
- Allow providers to limit and customize the data included in their payloads
- Maintain a system-wide availability topic
- Maintain separate availability topics for each type of game state component, for each provider
- Automatically detect when providers close their game/stop sending data and emit availability status for them
- Utilize the HomeAssistant MQTT device discovery protocol to automatically create a
cs2mqttdevice for each provider, with all data exposed as sensors - Expose data on REST API endpoints
- Optionally use pre-shared key (token) auth from CS2 Game State Integration on HTTP ingestion endpoint
- Optionally use TLS, custom client ID and credentials for MQTT broker