What they did
The poster, u/Jackald1918, took delivery of a Rivian R2 and a 40 A charger that speaks OCPP, and wanted a wall-mounted Fire tablet in the garage showing the whole charging session at a glance. They connected Claude to their Home Assistant through the HA MCP server. Claude read the real entities from the unofficial Rivian integration and the OCPP integration, then wrote and edited the dashboards live. The poster reviewed screenshots of the tablet and fed notes back each round. The result is two dashboards: one for the charger with start and stop buttons styled like emergency stops, needle gauges, cost and energy readouts and a current slider, and one for the car with tire pressures, battery level and charge rate graphs. Two small custom JavaScript cards and a wake-on-motion automation tied to a Frigate camera finished the panel.
How it went
It took a couple of evenings. The poster published the full YAML, both custom cards, a session cost sensor and the automation as a gist so others can copy it. They list the snags they hit: OCPP caps current at 32 A until you raise it in the integration settings, the charger only reports its body temperature, and the Rivian integration can read the charge limit but cannot set it. One round of Claude's edits was silently lost when a stale dashboard editor tab was saved over it.
Worth knowing
Close any open dashboard editor while the agent is editing, or saving the old tab will overwrite its work. The poster also warns that a 40 A charger is a continuous load that needs a 50 A breaker and matching wire before you raise the limit. Entity names in the shared files are generic and need a find and replace.