Lutron Caseta Integration with new instance of Hassio

New to Hassio and have a Caseta Pro system and attempting to interface with Hassio and I am having a challenge finding the problem.
Starting with a fresh image Hassio (99.2) on my RPi3, i ran the Lutron_Caseta addon to create the needed certificate files, made the required changes to the configuration.yaml file. When i re-boot, i receive a notification that the lutron_caseta config is invalid.
The log from the Developer Tools reports the following:

Error during setup of component lutron_caseta

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 168, in _async_setup_component hass, processed_config
File "/usr/src/homeassistant/homeassistant/components/lutron_caseta/__init__.py", line 53, in async_setup await bridge.connect()
File "/usr/local/lib/python3.7/site-packages/pylutron_caseta/smartbridge.py", line 40, in connect yield from self._login()
File "/usr/local/lib/python3.7/site-packages/pylutron_caseta/smartbridge.py", line 285, in _login yield from self._load_scenes()
File "/usr/local/lib/python3.7/site-packages/pylutron_caseta/smartbridge.py", line 351, in _load_scenes scene_name = scene['Name']
KeyError: 'Name'

The needed certificate files are in the /ssl/lutron/ directory and the configuration.yaml includes the following:
lutron_caseta:
host: 192.168.1.xx
keyfile: /ssl/lutron/caseta.key
certfile: /ssl/lutron/caseta.crt
ca_certs: /ssl/lutron/caseta-bridge.crt

Any suggestions would be most appreciated.

Thanks in advance.
Dave

Still having no luck sorting this out. Have reinstalled hassio/ha, recreated the certificates, all with the same result. In trying to track down the code throwing the error, i cannot find the scripts on the drive. Hidden directories maybe?

The hub is found as a homekit device, but that is not the route I would like to go.

Regards
David

I am having same issue, with existing config after upgrade to .100.2. Regenerated the certs, no difference.

I ended up using the Caseta Pro addon. Also found a bug in the integration report, reported to Lutron, they acknowledged but not fixed. Has to do with deleted scenes showing up in the integration report.