Describe the bug
After installing/updating the adapter, ioBroker logs the following warning repeatedly:
vw-connect.0
warn State "vw-connect.0.<VIN>.remote.access" has no existing object, this might lead to an error in future versions
The state remote.access is being written by the adapter (setState, ack: true) but there is no corresponding object created for it. All the other states under remote.* (e.g. charging, refresh, climatisation, windowheating, chargeMinLimit, maxChargeCurrent, forceRefresh, climatisationv2, climatisationv3) do have proper objects, so access appears to be the only one missing.
To Reproduce
- Install/run the adapter with
type: id (Volkswagen We Connect ID).
- Let it log in and poll vehicle data / rights.
- Check the ioBroker log — the warning above appears for
<vin>.remote.access.
- Deleting the orphaned state via
iobroker state del "vw-connect.0.<VIN>.remote.access" and restarting the adapter does not fix it — the state reappears without an object on every restart.
Expected behavior
The adapter should call setObjectNotExists/extendObject (with appropriate common metadata, e.g. type: boolean, role: indicator, read: true, write: false) before or together with setState for remote.access, the same way it does for the other remote.* states.
Workaround used
Manually created the missing object:
iobroker object set "vw-connect.0.<VIN>.remote.access" '{"type":"state","common":{"name":"Remote Access","type":"boolean","role":"indicator","read":true,"write":false},"native":{}}'This suppressed the warning after a restart.
Versions
- Adapter: vw-connect 0.9.7
- JS-Controller / Admin: 7.2.2 / 8.0.4
- Node.js: 22.23.2
- ioBroker host OS: Debian Trixie
Additional context
remote.access seems related to the vehicle-rights/remote-access-permission check (getVehicleRights) rather than being a user-triggered button like the other remote.* states, since its value is set by the adapter itself (ack: true) rather than via user interaction.
Describe the bug
After installing/updating the adapter, ioBroker logs the following warning repeatedly:
The state
remote.accessis being written by the adapter (setState,ack: true) but there is no corresponding object created for it. All the other states underremote.*(e.g.charging,refresh,climatisation,windowheating,chargeMinLimit,maxChargeCurrent,forceRefresh,climatisationv2,climatisationv3) do have proper objects, soaccessappears to be the only one missing.To Reproduce
type: id(Volkswagen We Connect ID).<vin>.remote.access.iobroker state del "vw-connect.0.<VIN>.remote.access"and restarting the adapter does not fix it — the state reappears without an object on every restart.Expected behavior
The adapter should call
setObjectNotExists/extendObject(with appropriatecommonmetadata, e.g.type: boolean,role: indicator,read: true,write: false) before or together withsetStateforremote.access, the same way it does for the otherremote.*states.Workaround used
Manually created the missing object:
This suppressed the warning after a restart.
Versions
Additional context
remote.accessseems related to the vehicle-rights/remote-access-permission check (getVehicleRights) rather than being a user-triggered button like the otherremote.*states, since its value is set by the adapter itself (ack: true) rather than via user interaction.