Fivem integration (#65089)

* Initial fivem integration setup

* Use licenseKey for unique ID

* Create FiveMServer class

* Create FiveMStatusBinarySensor

* Fix platform loading

* Create sensor platform

* Remove config flow tests

* Update manifest.json

* Use attr_ instead or properties in sensors.py

* Use entry_id as unique_id

* Move device info to _attr instead of property

* Register callback in FiveMEntity

* Create config flow tests

* Add loggin to fivem

* Use FiveM in config_flow

* Use update_coordinator instead of dispatcher

* Bump fivem-api to 0.1.2

* Remove leftovers

* More tests for config flow

* Add component files to .coveragerc

* Fix simple comments

* Add gamename check to config flow

* Use entity descriptions for sensors

* Move extra attributes to init

* Use [] instead of get() for server info

* Fix error in gamename test
This commit is contained in:
Sander Jochems 2022-02-08 10:27:11 +01:00 committed by GitHub
parent 8b38fa58aa
commit 0ea82bdbfb
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
15 changed files with 627 additions and 0 deletions

View file

@ -95,6 +95,7 @@ FLOWS = [
"ezviz",
"faa_delays",
"fireservicerota",
"fivem",
"fjaraskupan",
"flick_electric",
"flipr",