8 Commits (7d9c8fdfa09323eef42a73dca295ab5fabe1d833)

Author	SHA1	Message	Date
Joe Gross	3b4c3e6e17	Fix prometheus component to fully sanitize Unicode characters (#31037) ... * Fix prometheus component to fully santize Unicode characters. Sanitization used isdigit() to match numerics but that also matches Unicode "digit" characters that require special handling, like superscripts. Failures would look like this: ValueError: Invalid metric name: sensor_unit_u0x23_per_m³ Changed sanitize to use string.digits, which matches only ascii digits, and added test. See https://stackoverflow.com/questions/44891070/whats-the-difference-between-str-isdigit-isnumeric-and-isdecimal-in-python for discussion. https://docs.python.org/3/library/stdtypes.html#str.isdigit https://docs.python.org/3.7/library/string.html#string.digits * fix formatting to comply with black	2020-01-22 01:03:42 +01:00
Franck Nijhof	e642d95d0f	Migrate collection of component tests from coroutine to async/await (#30504)	2020-01-06 01:22:22 +01:00
Bas Nijholt	21816eeed4	Sort imports according to PEP8 for components starting with "P" (#29775)	2019-12-09 14:29:39 +01:00
Bram Kragten	15e6278a2e	Add config entry and device support to Demo (#28702) ... * Add config entry and device support to Demo * Some more devices * Fix tests using demo * Review comments * Update config_flow.py * Revert * Disable pylint	2019-11-13 16:37:31 +01:00
Andrew Rowson	770eeaf82f	Encode prometheus metric names per the prom spec (#26639) ... Referencing issue #26418. Prometheus metric names can only contain chars a-zA-Z0-9, : and _ (https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels). HA currently generates invalid prometheus names, e.g. if the unit for a sensor is a non-ASCII character containing ° or μ. To resolve, we need to sanitize the name before creating, replacing non-valid characters with a valid representation. In this case, I've used "u{unicode-hex-code}". Also updated the test case to make sure that the ° case is handled.	2019-09-19 12:51:49 +02:00
Per Osbäck	e9705af055	Prometheus metrics naming based on device_class and unit_of_measurement (#24103) ... * - Change how we extract the metrics for sensors - Add component filtering as seen in influxdb - Add metric override as seen in influxdb - Add more unit tests with actual device data * Extract sensor metric logic to separate handlers * Update prometheus dependency * Format using black * Format using black * Fix flake8 * Move sensor metric handler list to init * Use f strings instead of .format	2019-08-10 14:35:04 +02:00
Paulus Schoutsen	4de97abc3a	Black	2019-07-31 12:25:30 -07:00
Paulus Schoutsen	b8cc547fa3	Move components to folders (#20774) ... * Move all components into folders * Move component tests into folders * Fix init moving * Move tests * Lint * Update coverage * Fix service descriptions * Update CODEOWNERS	2019-02-05 19:31:15 -08:00