Chris

Does my card config look right? I didn't rename any of my entities they're all the defaults.

So I came up with something like this: ```yaml type: custom:charger-card entity: sensor.openevse_charging_status brand: openevse details: status: entity_id: sensor.openevse_charging_status substatus: entity_id: sensor.openevse_station_status currentlimits: - 0 - 10 - 12 -...

I've made a few tweaks that may work as defaults: ```yaml type: custom:charger-card entity: sensor.openevse_charging_status brand: openevse customCardTheme: theme_custom details: status: entity_id: sensor.openevse_charging_status substatus: entity_id: sensor.openevse_station_status currentlimits: - 6 -...

@tmjo I couldn't get the "disconnected" state using the "not connected" sensor state to work it always used "default" for some reason.

When `sensor.openevse_charging_status` state was `not connected` the card was using the `default` entry for the `stats` section, which is why I removed the `disconnected` entry from `statetext`. I hope this...

That would be a bug in the `zwave_js` integration then as setting and clearing codes should also enable/disable the slot.

> @firstof9 will you create a ticket in the integration github pages? Or should I do it? You're going to need driver logs to prove this is what's occurring, my...

> for manual install if i just `custom_components/keymaster` dir to `ha_conf_dir/custom_compoents`? Yes > If there are other channels please let me know. There's an extensive thread on the HA forums.

HACS is the perfered method as it 1) easier to use and 2) makes updating simple with handy notifications when updates are published.

Thank you! I'll update the link.