To be used for setting the Name in the discovery payload.

Store Name in Case as Entered by User

Adds the basic functionality for reading discovery settings from
the config.yaml file.  Lightly implemented in Dimmer.

Still does not publish anything yet, need to monitor the
homeassistant/status topic

Monitors a defined topic looking for a message indicating that
HomeAssistant was restarted and triggers a re-publish of
discovery entities if that happens.

Publish discovery entities on startup.

Device information is likely to be the same structure across all
devices.  Or at least most devices.  This adds a variable that
is defined in yaml and useable in the jinja templates.

Add basic dimmer discovery entities.

Add additional information about the device model and such.
This is all primarily cosmetic, but it might aid with support
requests if a user can see their device info in a nice GUI.

This way it is only processed once, seems more streamlined.

Skeleton of Discovery Implementation

JSON is quite unforgiving.

Discovery Documentation; Additional Variables and Tweaks

Can't use default discovery class name for selecting the config
section, it will cause the wrong inheritance with things like
fan_linc inheritting dimmer settings.

Rename some variables and add better descriptions to try and make
them more clear.

Rather than extending a method, I think it is more concise and
makes more sense to load this data into the rendered topics
map on load.

Primarily to support KPL.  But other devices may need this as
well.

Add Discovery Support to All Devices

Need to broaden the range of jinja exceptions that are caught.

Adds unit tests for discoveryTopic.load_discovery_data and
_get_unique_id

Man this test file is not well written, who did this? .... oh yeah
it was me.

entries was a very generic name , disc_templates does a better
job describing what it is.

Pass a copy of a dict.  Passing the actual dict seemed to work
fine, but on the off chance that publish somehow happens async
need to pass a copy since we alter data immediately after passing
it.

It is replaced by discovery_publish() but still best not to
leave this around.

Add Unit Tests to Discovery Platform

Squelches a bunch of potential discovery log messages that are
unnecessary.

Necessary because the modem only uses a single template with
an indeterminate, until run time, number of topics generated

The HA implementation of the discovery protocol only allows a
very small subset of characters for use in the node_id and
the object_id.  This replaces all un-allowed characters with an
underscore.

Also removed the ability to set the topic via yaml.  This never
really worked anyways and would create potential problems.

Reverted changing the periods in the address to underscores,
periods are still fine in the unique_id, just not in the topic
string.

Discovery Tweaks After Initial Usage

Discovery Tweaks and Fixes