Update iobroker.yaml

[Chris685]

remove /rest-api

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="templates/definition/vehicle/iobroker.yaml" line_range="144" />
<code_context>
     source: http
     headers:
       - accept: text/plain;charset=UTF-8
-    uri: {{ .uri }}/rest-api/v1/state/{{ .soc }}/plain?extraPlain=true
+    uri: {{ .uri }}/v1/state/{{ .soc }}/plain?extraPlain=true
     cache: {{ .cache }}
</code_context>
<issue_to_address>
**issue (bug_risk):** With the documented `rest-api` adapter setup and the documented host-only `.uri`, every vehicle request is sent to `/v1/state/...` instead of the adapter's `/rest-api/v1/state/...` mount, so reads and writes fail with an unavailable endpoint rather than accessing the configured datapoints.

**Triggers:** When `.uri` is a host URI as shown in the template example and the ioBroker `rest-api` adapter is mounted under `/rest-api`.

**Suggested fix:** Retain the `/rest-api` prefix, or update the adapter/URI contract consistently and migrate the charger and meter ioBroker templates as well.
</issue_to_address>

Sourcery assessment

Approval pending. 1 finding to address first.

Blocking findings: templates/definition/vehicle/iobroker.yaml:144

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (bug_risk): With the documented rest-api adapter setup and the documented host-only .uri, every vehicle request is sent to /v1/state/... instead of the adapter's /rest-api/v1/state/... mount, so reads and writes fail with an unavailable endpoint rather than accessing the configured datapoints.

Triggers: When .uri is a host URI as shown in the template example and the ioBroker rest-api adapter is mounted under /rest-api.

Suggested fix: Retain the /rest-api prefix, or update the adapter/URI contract consistently and migrate the charger and meter ioBroker templates as well.

[github-actions]

Code review

Bug risk: removing /rest-api from all 10 endpoint URIs in this template (templates/definition/vehicle/iobroker.yaml, e.g.

evcc/templates/definition/vehicle/iobroker.yaml

Lines 143 to 145 in 0695aaf

	- accept: text/plain;charset=UTF-8
	uri: {{ .uri }}/v1/state/{{ .soc }}/plain?extraPlain=true
	cache: {{ .cache }}

) likely breaks every read/write for this vehicle integration.

The ioBroker rest-api adapter (distinct from simple-api) is documented to be mounted at /rest-api. The sibling templates using the same adapter still keep the prefix with a bare-host .uri:

• evcc/templates/definition/charger/iobroker.yaml

  Lines 77 to 79 in 0695aaf

  	- accept: text/plain;charset=UTF-8
  	uri: {{ .uri }}/rest-api/v1/state/{{ .status }}/plain?extraPlain=true
  	cache: {{ .cache }}

• evcc/templates/definition/meter/iobroker.yaml

  Lines 84 to 86 in 0695aaf

  	- accept: text/plain;charset=UTF-8
  	uri: {{ .uri }}/rest-api/v1/state/{{ .power }}/plain
  	{{- if .user }}

Both explicitly document: "The rest-api adapter (not simple-api) must be installed... configured as an extension of a web adapter." Since this vehicle template uses the identical adapter/URI convention, stripping /rest-api sends requests to a path the adapter doesn't serve, so soc, range, status, limitSoc, odometer, climater, finishTime, chargeEnable, setMaxCurrent, and wakeup would all fail — unless .uri was intentionally redefined elsewhere to already include /rest-api (not evident from this diff). Sourcery AI's automated review independently flagged this same line as a blocking issue.

Suggest reverting the prefix removal, or if the adapter's mount path genuinely changed, confirming that and updating the charger/meter templates to match for consistency.