Upgrade pylutron-caseta to 0.5.0 to reestablish connections

[rohankapoorcom]

Description:

Something changed on the lutron end of things and pylutron_caseta was unable to connect to the caseta bridge. This was fixed upstream in (see links below) but the library was not upgraded in home assistant.

• New method no longer working? gurumitts/pylutron-caseta#22
• Support Spring 2018 protocol gurumitts/pylutron-caseta#23

No configuration changes were needed in home assistant to make this work.

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass

[mhofman]

Since the new caseta protocol seems to change the previously reported entity_id, wouldn't this be a good opportunity to add support for the entity registry, and avoid future break of entity names?

[pvizeli]

We can do this in a future PR @mhofman

[cgarwood]

Since its reported to change entity_id's should it be marked as a breaking change?

[rohankapoorcom]

@mhofman any documentation on integrating components onto the component registry? Happy to give it a shot for this one.

[mdonoughe]

Apparently the name change is actually due to gurumitts/pylutron-caseta#20. The component registry will fix it anyway. Unfortunately, it looks like we will need to change pylutron-caseta again to include more device information including the serial numbers so we have something to match against in the registry.

[mdonoughe]

I opened #14037 which will hopefully get the entity registry working once gurumitts/pylutron-caseta#25 is available.

[mdonoughe]

Do we still need to update the documentation? The old script to get the certificates still gets the certificates but reports an error at the end when it tries to verify the connection. There's an updated version in the pylutron-caseta repo.