-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[homematic] HM-Sec-TiS implemented as Switch instead of Contact #5674
Labels
bug
An unexpected problem or unintended behavior of an add-on
Comments
andrewfg
pushed a commit
to andrewfg/openhab-addons
that referenced
this issue
Aug 31, 2020
…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]>
andrewfg
pushed a commit
to andrewfg/openhab-addons
that referenced
this issue
Aug 31, 2020
…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]>
andrewfg
pushed a commit
to andrewfg/openhab-addons
that referenced
this issue
Aug 31, 2020
…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]>
andrewfg
pushed a commit
to andrewfg/openhab-addons
that referenced
this issue
Aug 31, 2020
…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]>
DaanMeijer
pushed a commit
to DaanMeijer/openhab-addons
that referenced
this issue
Sep 1, 2020
…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]>
CSchlipp
pushed a commit
to CSchlipp/openhab-addons
that referenced
this issue
Sep 12, 2020
…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]>
markus7017
pushed a commit
to markus7017/openhab-addons
that referenced
this issue
Sep 19, 2020
…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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Homematic Tilt Sensor (HM-Sec-TiS) is implemented as a Switch instead of a Contact (as Door/Window Sensors).
Could you please use a Contact item?
Details: https://community.openhab.org/t/hm-sec-tis-undefined/18229
The text was updated successfully, but these errors were encountered: