[homematic] Only percentages from 0 to 100 are accepted - homematic needs -1 too #6360
Comments
henrydiesner
added
the
bug
kaikreuzer
changed the title
That's definitely not the right solution, see also jens-maus/RaspberryMatic#737 (comment). |
|
Always the same Error: |
|
I will try to solve this problem in the next days. Are only the "DutyCycle" variables affected or did you get this with other devices, too? In my environment, I have never seen this message. |
|
@MHerbst: I think the "DutyCycle" variables are the only one. In RaspberryMatic all other percent system variables are in the range 0 to 100: Many thanks and stay healthy! |
|
Sorry, false button :-( |
|
@henrydiesner I have added support for a duty cycle value of -1 and the bridge state will be set to offline while the value is -1. I have uploaded a test jar here: https://github.com/MHerbst/openhab-addons-test |
|
Sorry for my late replay! What's getting wrong on my openHAB? |
|
@henrydiesner I seems that my fix was not sufficient. There seems to be another data point that causes this problem. Can you enable Trace mode and test whether it produces some relevant output? |
|
@MHerbst: I made a file with a homematic TRACE: |
|
@henrydiesner Unfortunately the log does not contain the exception. I have created a new test version (https://github.com/MHerbst/openhab-addons-test) that catches the exception and prints an error message with additional information instead. You can set the log level back to INFO or a higher value. After some time please check the log for error messages starting with: "Invalid value" and post the message. |
|
@MHerbst Here is the message: 2020-08-11 19:47:48.813 [ERROR] [ternal.handler.HomematicThingHandler] - Invalid Value: Value must be between 0 and 100::HmDatapoint[name=COLOR,value=103,defaultValue=0,type=INTEGER,minValue=0,maxValue=255,step=,options=,readOnly=false,readable=true,unit=,description=COLOR,info=,paramsetType=VALUES,virtual=false,trigger=false] A data point with the name "COLOR" ?? |
|
@henrydiesner This is interesting. Do you have any HM LEDs where you can set the color? I have searched the HmIP device doc for data points named COLOR. I have found e.g. BSL_V1. But is weird that a percent type is used for this data point. Maybe I can enhance tomorrow the message to get more information about the device that has got this data point. |
|
@MHerbst May be I found it: |
|
@henrydiesner The definiton of a "PercentType" for this data point is definitely wrong. I have to investigate why this happens. Please create a new issue for this problem because it has a different cause than the original issue. |
…openhab#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support type Int64 for messages from Homegear * Correct support of UP/DOWN for rollershutter devices - Important: UP command must send 1.0 to the device instead of the maximum value returned by Homematic which is 1.01 and does not work. * Correct max data point value of certain HmIP devices - Some data points of HmIP are returning 1.01d as max value instead of the correct value of 1.0. * HM channel "Blind Transmitter" also indicates a rollershutter * Reduced log level for certain datapoints to avoid flooding the logs - HmIP devices introduced new channel configuration datapoints that can't currently be detected automatically, but the CCU sometimes sends events and the logs were flooded with warnings. * CuxD interface apparently does not support the rssiInfo method * equals method call not necessary because of enum usage * HM method does not return any data if HmIP only is used Fixes openhab#6360 Fixes openhab#6145 Fixes openhab#5042 Fixes openhab#5674 Fixes openhab#8081 Fixes openhab#6688 Fixes openhab#5048 Fixes openhab#6743 Fixes openhab#5062 Signed-off-by: Martin Herbst <[email protected]>
…openhab#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support type Int64 for messages from Homegear * Correct support of UP/DOWN for rollershutter devices - Important: UP command must send 1.0 to the device instead of the maximum value returned by Homematic which is 1.01 and does not work. * Correct max data point value of certain HmIP devices - Some data points of HmIP are returning 1.01d as max value instead of the correct value of 1.0. * HM channel "Blind Transmitter" also indicates a rollershutter * Reduced log level for certain datapoints to avoid flooding the logs - HmIP devices introduced new channel configuration datapoints that can't currently be detected automatically, but the CCU sometimes sends events and the logs were flooded with warnings. * CuxD interface apparently does not support the rssiInfo method * equals method call not necessary because of enum usage * HM method does not return any data if HmIP only is used Fixes openhab#6360 Fixes openhab#6145 Fixes openhab#5042 Fixes openhab#5674 Fixes openhab#8081 Fixes openhab#6688 Fixes openhab#5048 Fixes openhab#6743 Fixes openhab#5062 Signed-off-by: Martin Herbst <[email protected]>
…openhab#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support type Int64 for messages from Homegear * Correct support of UP/DOWN for rollershutter devices - Important: UP command must send 1.0 to the device instead of the maximum value returned by Homematic which is 1.01 and does not work. * Correct max data point value of certain HmIP devices - Some data points of HmIP are returning 1.01d as max value instead of the correct value of 1.0. * HM channel "Blind Transmitter" also indicates a rollershutter * Reduced log level for certain datapoints to avoid flooding the logs - HmIP devices introduced new channel configuration datapoints that can't currently be detected automatically, but the CCU sometimes sends events and the logs were flooded with warnings. * CuxD interface apparently does not support the rssiInfo method * equals method call not necessary because of enum usage * HM method does not return any data if HmIP only is used Fixes openhab#6360 Fixes openhab#6145 Fixes openhab#5042 Fixes openhab#5674 Fixes openhab#8081 Fixes openhab#6688 Fixes openhab#5048 Fixes openhab#6743 Fixes openhab#5062 Signed-off-by: Martin Herbst <[email protected]>
…openhab#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support type Int64 for messages from Homegear * Correct support of UP/DOWN for rollershutter devices - Important: UP command must send 1.0 to the device instead of the maximum value returned by Homematic which is 1.01 and does not work. * Correct max data point value of certain HmIP devices - Some data points of HmIP are returning 1.01d as max value instead of the correct value of 1.0. * HM channel "Blind Transmitter" also indicates a rollershutter * Reduced log level for certain datapoints to avoid flooding the logs - HmIP devices introduced new channel configuration datapoints that can't currently be detected automatically, but the CCU sometimes sends events and the logs were flooded with warnings. * CuxD interface apparently does not support the rssiInfo method * equals method call not necessary because of enum usage * HM method does not return any data if HmIP only is used Fixes openhab#6360 Fixes openhab#6145 Fixes openhab#5042 Fixes openhab#5674 Fixes openhab#8081 Fixes openhab#6688 Fixes openhab#5048 Fixes openhab#6743 Fixes openhab#5062 Signed-off-by: Martin Herbst <[email protected]>
…openhab#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support type Int64 for messages from Homegear * Correct support of UP/DOWN for rollershutter devices - Important: UP command must send 1.0 to the device instead of the maximum value returned by Homematic which is 1.01 and does not work. * Correct max data point value of certain HmIP devices - Some data points of HmIP are returning 1.01d as max value instead of the correct value of 1.0. * HM channel "Blind Transmitter" also indicates a rollershutter * Reduced log level for certain datapoints to avoid flooding the logs - HmIP devices introduced new channel configuration datapoints that can't currently be detected automatically, but the CCU sometimes sends events and the logs were flooded with warnings. * CuxD interface apparently does not support the rssiInfo method * equals method call not necessary because of enum usage * HM method does not return any data if HmIP only is used Fixes openhab#6360 Fixes openhab#6145 Fixes openhab#5042 Fixes openhab#5674 Fixes openhab#8081 Fixes openhab#6688 Fixes openhab#5048 Fixes openhab#6743 Fixes openhab#5062 Signed-off-by: Martin Herbst <[email protected]> Signed-off-by: Daan Meijer <[email protected]>
…openhab#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support type Int64 for messages from Homegear * Correct support of UP/DOWN for rollershutter devices - Important: UP command must send 1.0 to the device instead of the maximum value returned by Homematic which is 1.01 and does not work. * Correct max data point value of certain HmIP devices - Some data points of HmIP are returning 1.01d as max value instead of the correct value of 1.0. * HM channel "Blind Transmitter" also indicates a rollershutter * Reduced log level for certain datapoints to avoid flooding the logs - HmIP devices introduced new channel configuration datapoints that can't currently be detected automatically, but the CCU sometimes sends events and the logs were flooded with warnings. * CuxD interface apparently does not support the rssiInfo method * equals method call not necessary because of enum usage * HM method does not return any data if HmIP only is used Fixes openhab#6360 Fixes openhab#6145 Fixes openhab#5042 Fixes openhab#5674 Fixes openhab#8081 Fixes openhab#6688 Fixes openhab#5048 Fixes openhab#6743 Fixes openhab#5062 Signed-off-by: Martin Herbst <[email protected]>
…openhab#8242) * Set bridge state to offline for duty cycle = -1 * Use correct type Contact for state channel of tilt sensor * Support type Int64 for messages from Homegear * Correct support of UP/DOWN for rollershutter devices - Important: UP command must send 1.0 to the device instead of the maximum value returned by Homematic which is 1.01 and does not work. * Correct max data point value of certain HmIP devices - Some data points of HmIP are returning 1.01d as max value instead of the correct value of 1.0. * HM channel "Blind Transmitter" also indicates a rollershutter * Reduced log level for certain datapoints to avoid flooding the logs - HmIP devices introduced new channel configuration datapoints that can't currently be detected automatically, but the CCU sometimes sends events and the logs were flooded with warnings. * CuxD interface apparently does not support the rssiInfo method * equals method call not necessary because of enum usage * HM method does not return any data if HmIP only is used Fixes openhab#6360 Fixes openhab#6145 Fixes openhab#5042 Fixes openhab#5674 Fixes openhab#8081 Fixes openhab#6688 Fixes openhab#5048 Fixes openhab#6743 Fixes openhab#5062 Signed-off-by: Martin Herbst <[email protected]>
Expected Behavior
openHAB accept percent values only between 0 and 100. But from homematic came percentages from -1 to 100:
Current Behavior
No error in the log file in this case.
Possible Solution
Do not limit percentages.
Context
See the issue in homematic: https://github.com/jens-maus/RaspberryMatic/issues/737
Your Environment
Newest stable openHAB on NUC with Debian 10
RaspberryMatic
The text was updated successfully, but these errors were encountered: