I am receiving the topic error in the log of OPENHAB, but i am not entirely sure why ? the device should support that value. In the log you can see the value change from OPEN to CLOSED…
If logs where generated please post these here using code fences:
2018-12-23 13:17:04.031 [vent.ItemStateChangedEvent] - DeviceLocked_Living changed from OPEN to CLOSED
2018-12-23 13:08:20.775 [WARN ] [rest.core.internal.item.ItemResource] - Received HTTP POST request at 'items/DeviceLocked_Living' with an invalid status value 'CLOSED'.
2018-12-23 13:09:14.071 [WARN ] [rest.core.internal.item.ItemResource] - Received HTTP POST request at 'items/DeviceLocked_Living' with an invalid status value 'OPEN'.
Hmm, i think i didnt ask the question precisely… The Problem doesnt occur with the Visibility, that works fine and i also tested Exchanging OPEN for CLOSED and it works the other way around.
But setting the state to OPEN or CLOSED fails, so something must be wrong with the mapping statement at the end, although from the first line in the log you can see that both values exist and are used by the fritz.box interface when i use the setting there. Also in the documentation those values are stated.
Also the visibility option works with both values without quotes, so it must be without quotes. I tried it with quotes and it postet the same problem, looking exactly the same with the syntax.
Are you trying to command the item through basicui? A POST request to the rest API is for sending commands to items, and contact items don’t support commands, only state updates.
Contact items in basicui is supposed to be read-only, since toggling them sends a command.
hmm, i am not instructing to use the map file, or is that automatically used in mappings[]
it looks like this :
CLOSED=gesperrt
OPEN=offen
NULL=???
actually i am trying to set a status, yes change it from OPEN to CLOSED and back. but how can i switch that state then, do i have to change the Item config itself to switch ?
I know you can switch the state in the fritz box menu… and it got by default inserted as a contact…
the binding docu documents it as a contact as well…
device_locked Contact Device is locked for switching manually (OPEN/CLOSE) - FRITZ!DECT 301,
the state seems to be CLOSED though, since that works for the visibility option…
In the item file your using the MAP transformation and in the site map your also using mappings.
If this is an item that can be switched, then your correct, change the item from a contact to a switch. As @pacive mentioned contact items are read only.
After changing to a switch check the logs to verify everything is correct.
