openhab.log (194.6 KB) It doesn’t look very informative - I think there is some other element that perhaps needs tracing. It basically gives the same error message of:
2020-10-03 16:29:32.187 [WARN ] [rest.core.internal.item.ItemResource] - Received HTTP POST request at 'items/WallMasterMode' with an invalid status value 'SET_TEMPERATURE'.
Here’s the full log for that area:
2020-10-03 16:29:22.466 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (String) value 'ABDD5864-8959-5743-FE7A-8ADC71DCD01D' for 'CENTRAL:0#PONG' from gateway with id 'ABDD5864-8959-5743-FE7A-8ADC71DCD01D'
2020-10-03 16:29:22.460 [TRACE] [nal.communicator.client.BinRpcClient] - Client BinRpcResponse:
true
2020-10-03 16:29:22.472 [TRACE] [nal.communicator.client.BinRpcClient] - Client BinRpcRequest:
listBidcosInterfaces()
2020-10-03 16:29:22.474 [TRACE] [al.communicator.client.SocketHandler] - Returning socket for port 2001
2020-10-03 16:29:22.484 [TRACE] [nal.communicator.client.BinRpcClient] - Client BinRpcResponse:
[
{
ADDRESS=VBC8696336
CONNECTED=true
DEFAULT=true
DESCRIPTION=Homegear default BidCoS interface
}
]
2020-10-03 16:29:32.187 [WARN ] [rest.core.internal.item.ItemResource] - Received HTTP POST request at 'items/WallMasterMode' with an invalid status value 'SET_TEMPERATURE'.
2020-10-03 16:29:32.486 [TRACE] [nal.communicator.client.BinRpcClient] - Client BinRpcRequest:
ping()
4BCAAC30-44F5-BBDE-DF54-27D1B87DCE09
2020-10-03 16:29:32.491 [TRACE] [al.communicator.client.SocketHandler] - Returning socket for port 2001
2020-10-03 16:29:32.507 [TRACE] [nal.communicator.client.BinRpcClient] - Client BinRpcResponse:
true
2020-10-03 16:29:32.510 [TRACE] [nal.communicator.client.BinRpcClient] - Client BinRpcRequest:
listBidcosInterfaces()
2020-10-03 16:29:32.512 [TRACE] [nicator.server.BinRpcResponseHandler] - Event BinRpcMessage: system.multicall()
[
{
methodName=event
params=
[
RF-4BCAAC30-44F5-BBDE-DF54-27D1B87DCE09
CENTRAL
PONG
4BCAAC30-44F5-BBDE-DF54-27D1B87DCE09
]
}
]
2020-10-03 16:29:32.512 [TRACE] [al.communicator.client.SocketHandler] - Returning socket for port 2001
The startup log might tell us something, attached as well. There’s an enormous amount of stuff in there, things that looked interesting included:
2020-10-03 16:33:26.982 [TRACE] [omematic.internal.type.MetadataUtils] - Description not found for: CLIMATECONTROL_TRANSCEIVER|PARTY_STOP_MONTH, PARTY_STOP_MONTH
2020-10-03 16:33:26.983 [TRACE] [omematic.internal.type.MetadataUtils] - Description not found for: CLIMATECONTROL_TRANSCEIVER|PARTY_TEMPERATURE, PARTY_TEMPERATURE
2020-10-03 16:33:26.984 [TRACE] [omematic.internal.type.MetadataUtils] - Description not found for: CLIMATECONTROL_TRANSCEIVER|SHOW_SET_TEMPERATURE, SHOW_SET_TEMPERATURE
2020-10-03 16:33:26.986 [TRACE] [omematic.internal.type.MetadataUtils] - Description not found for: CLIMATECONTROL_TRANSCEIVER|PARTY_STOP_DAY, PARTY_STOP_DAY
2020-10-03 16:33:26.987 [TRACE] [omematic.internal.type.MetadataUtils] - Description not found for: CLIMATECONTROL_TRANSCEIVER|BOOST_TIME_PERIOD, BOOST_TIME_PERIOD
2020-10-03 16:33:26.988 [TRACE] [omematic.internal.type.MetadataUtils] - Description not found for: CLIMATECONTROL_TRANSCEIVER|BOOST_TIME_PERIOD|0 min, BOOST_TIME_PERIOD|0 min, 0 min
....
SHOW_SET_TEMPERATURE=
{
DEFAULT=0
FLAGS=1
ID=SHOW_SET_TEMPERATURE
MAX=1
MIN=0
OPERATIONS=7
TAB_ORDER=6
TYPE=ENUM
UNIT=
VALUE_LIST=
[
SET_TEMPERATURE
ACTUAL_TEMPERATURE
]
}
....
2020-10-03 16:33:27.514 [TRACE] [ommunicator.AbstractHomematicGateway] - HmDatapoint[name=SHOW_SET_TEMPERATURE,value=0,defaultValue=0,type=ENUM,minValue=0,maxValue=1,step=<null>
,options=SET_TEMPERATURE;ACTUAL_TEMPERATURE,readOnly=false,readable=true,unit=<null>,description=SHOW_SET_TEMPERATURE,info=<null>,paramsetType=VALUES,virtual=false,trigger=false]
....
2020-10-03 16:33:27.905 [TRACE] [converter.type.AbstractTypeConverter] - Converting datapoint 'MEQ0856945:1#SHOW_SET_TEMPERATURE' (dpType='ENUM', dpUnit='null', dpValue='0') with St
ringTypeConverter
Interestingly, I still couldn’t see any action when I tried any of toggling the switch (just got the HTTP error), or tried directly manipulating from the console:
openhab> smarthome:send WallLoungeMode ON
Command has been sent successfully.
openhab> smarthome:update WallLoungeMode ON
Update has been sent successfully.
openhab> smarthome:update WallLoungeMode OFF
Update has been sent successfully.
openhab> smarthome:update WallLoungeMode 1
Error: State '1' is not valid for item 'WallLoungeMode'
Valid data types are: ( OnOffType UnDefType )
openhab> smarthome:update WallLoungeMode (1 as NumberItem
sequence> )
Error executing command: Cannot coerce as(Token) to any of []
