v2.2.1.2 Beta: Advanced Display Options v2

What's Changed

• Advanced display options v2 by @Snuffy2 in #126

See updated documentation at:

https://github.com/custom-components/places/blob/adv_display_opt/README.md

Full Changelog: v2.2.1....v2.2.1.2

Beta: Advanced Display Options

What's Changed

• Advanced display options by @Snuffy2 in #125

See updated documentation at:

https://github.com/custom-components/places/blob/adv_display_opt/README.md

Full Changelog: v2.2.1...v2.2.1.1

v2.2.1 - Add Option to use GPS Accuracy

What's Changed

• Make GPS Accuracy an Option in #119
  The new option defaults to True and the places sensor will only update if GPS Accuracy is >0. If you have a devicetracker_id that has a GPS Accuracy (gps_accuracy) attribute that is always 0 but the Latitude and Longitude are updating and accurate, set this option to False.

Full Changelog: v2.2.0...v2.2.1

v2.2.0 - Add Icon, Miles. Improve Dropdowns. Save state on reboot.

New Features and behind the scenes rework

• It was becoming very hard to manage all of the attributes with their internal and external names. It was redesigned to use a Dictionary to store the attributes so that there is only one name for each attribute. I've tried to ensure that this change is essentially invisible to everyone but makes it much easier to manage going forward. I also updated the class of the places sensor to be a Sensor class.

• Sensor state and attributes will persist through a Home Assistant reboot.

  • This should "fail gracefully" if it is unable to write or read the sensor status file, but please open an issue if it isn't working and especially if it is crashing the places sensor.

• Updated formatted_place to show the route number (but only if it contains a number) for highways instead of the official name if it exists.

  • Please open an issue if you find any roads that display weirdly. Please provide the OpenStreetMap URL from the Debug Logs.
  • I could make this an option for the display options and/or for formatted_place instead of always on for formatted_place if desired.

Changelog

• Add Default Icon for the sensor in #104
• Change from Entity to SensorEntity Class in #105
• Simplify code to use a dict for attributes instead of separate variables in #109
  • Move code into functions in Snuffy2#162
• Store sensor states in JSON files to keep state on reboot by in #106
  • Update JSON Import to identify not-imported attributes for debugging in #107
• Add GPS accuracy as attribute and only update the sensor if GPS accuracy is >0 if it exists in #108
  • If there are devicetracker_ids that work but have GPS Accuracy as 0, this could become an option.
• Add miles attributes for measurements in #110
• Show friendly name and entity id in config dropdowns in #111
• Add last_updated as attribute in #114
• Use highway number (ex. I 95) in formatted place for highways if it exists in #115
• Fix place_name to populate even if places is not in display options and ignore it it in formatted_place if it duplicates other attributes in #116

Full Changelog: v2.1.0...v2.2.0

v2.1.0 - Time in state is back, Update sensor after changing options, and more

Breaking Changes

• If you were using the state of 'Initializing...' that was set on load for any automations or other logic, the state will now be unknown like other sensors

What's Changed

• Add map_zoom into Google Maps URLs by @Snuffy2 in #89
• Add time to state as an option by @Snuffy2 in #82
• Update sensor after config options updates by @Snuffy2 in #96
• Deleted sensors still updating by @Snuffy2 in #81
• Change startup state from Initializing to unknown by @Snuffy2 in #90
• Catch JSON None Error by @Snuffy2 in #100
• Don't update if GPS Accuracy exists in devicetracker_id and is 0 by @Snuffy2 in #101
• Downgrade and refactor some logger alerts by @Snuffy2 in #103

Full Changelog: v2.0.5...v2.1.0

v2.0.5 - Bugfixes

What's Changed

• Fix casting errors to str by @Snuffy2 in #93
• Check if self._place_type is not none before trying to convert case to lower by @pippyn in #92

Full Changelog: v2.0.4...v2.0.5

v2.0.4 - Delay import validation and support HA <2022.9

What's Changed

• Only use issue_registry if it exists in Home Assistant version by @Snuffy2 in #86
• Move import validation until after ha is loaded by @Snuffy2 in #88

Full Changelog: v2.0.3.1...v2.0.4

v2.0.3 - More bugfixes and exception catching

Be sure to note the significant and breaking changes in v2.0.0

What's Changed

• Expanded Exception catching for Web connection issues by @Snuffy2 in #74
• If zone_name is lowercase, make it Title case by @Snuffy2 in #72
• Declare new_latitude and new_longitude to prevent errors by @Snuffy2 in #69
• Fallback to the old issue_registry import location by @Snuffy2 in #70
• Re-enable some logging to debug duplicate entities by @Snuffy2 in #75
• Fix more devicetracker_id selector issues by @Snuffy2 in #71
• New sensors stuck at initializing and don't ever update by @Snuffy2 in #79
• Validate home_zone on YAML import by @Snuffy2 in #77
• Fix some errors on changing options by @Snuffy2 in #78

Full Changelog: v2.0.2...v2.0.3

v2.0.3.2 - Only use issue_registry if it exists

What's Changed

• Only use issue_registry if it exists by @Snuffy2 in #87

Beta Release:
Only use issue_registry if it exists (issue_registry was only added in Home Assistant 2022.8 and then moved into its current location in 2022.9). With this change, the issue_registry will likely only work with versions $\geq$ 2022.9 but should not fail on earlier versions.

Full Changelog: v2.0.3...v2.0.3.2

v2.0.2 - Bugfixes and Handling Web Timeouts Gracefully

Be sure to note the significant and breaking changes in v2.0.0

What's Changed

• Code cleanup by @Snuffy2 in #60
• Fix is_float error by checking for none by @Snuffy2 in #63
• Remove | operand from async_setup_platform by @Snuffy2 in #66
• Gracefully handle Web request timeouts by @Snuffy2 in #65

Full Changelog: 2.0.1...2.0.2