![]() Updated device_state_attributes to extra_state_attributes.V2.2.1 (includes v2.1.4 Pre Release changes) Fix distance and pressure deprecated to use unit_conversion. ![]() Fix deprecation issue of async_get_registry #74.Fix usage of deprecated device class constant #84.To enable logging of the attributes and status data in the debug log, set the debug data option in config options with debugging turned on as above.To enable debug logging for this component, add the following to your configuration.yaml.A big thanks for all the work you have done on this. This integration uses the jlrpy api written by ardevd. Please raise an issue for any functionality you would like to see. I am looking for suggestions to improve this integration and make it useful for many people. The recipes page is a collection of ideas contributed by the community to help you get the most out of using this integration. The master branch is the current release. It will also be updated regularly as new fixes/functions are developed, so please check you have the latest update before raising an issue. Please note that there maybe issues with new functions or fixes that have not been fully tested. Configure via the integrations page in the UI.Īs of v1.0.0, the dev branch is now where the very latest version is held.Copy the jlrincontrol folder to the custom_components directory of your Home Assistant installation.On your server clone the github repository into a suitable directory using the git clone command.Installing via HACS and configuring via the UI is the recommended method. You do not need to restart HA to enable or disable this sensor, but you may need to add it into your Lovelace UI after enabling it. Configuration -> Integrations -> Select Options on the JLR Incontrol integration. NOTE: By default this sensor is not created and must be enabled in the config options. The recipes document gives an example of a template sensor that uses this data and shows how to extract the values from the all info sensor. This sensor displays the attribute, status and position information being received from the JLR servers and allows the creation of custom sensors and use of any of this data in scripts and automations. ![]() Creating Custom SensorsĪs all use cases cannot be covered and to allow the best benefit to all of this integration, version 2.1.0 introduced and 'All Info' sensor. on EV vehicles you could only call it if the vehicle is charging, or on all vehicles, only call it during the day and it was more than x period since the last update. Recommended 120 mins.Īlternatively, you can make a more intelligent health update request automation using the service call available in this integration and the output of some sensors. I would certainly not set it to too low an interval. ![]() I do not know the impact on either vehicle battery or JLRs view on running this often, so please use at your own risk. Setting the interval and your pin in the config options will enable this. This integration has the ability to perform a scheduled health status update request from your vehicle. It is recommended to remove them after this has happened, otherwise changes via the UI can be reverted by the entries in configuration.yaml. The new config flow will import your settings from configuration.yaml.
0 Comments
Leave a Reply. |