-
-
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] Error: rssiInfo method not found #6743
Comments
Same problem here with 2.5.1. I'll try to get a debug log. |
I started openhab using "openhab-cli start --debug", but there seem to be no DEBUG entries in the log file. Is this correct? See the attached file below anyways: If I enable DEBUG logging with "log:set DEBUG" the following log results in the timespan from switching on the ReloadRssi switch and receiving the error message (please note that I replaced IP addresses with <device_IPv*_Address> instead, so you can identify the devices behind those addresses. |
I have never tried to use this --debug option. For the debug log it would be sufficient to enable debug only for the Homematic binding. It's now a bit too much information :-). |
Is there already a solution available? I still get that error in the log file and hometaic bridge is still not able to connect to my CCU3 (COMMUNICATION_ERROR). Thx in advance. |
@keepinslow This problem is already open. I will try to work on it next. But I am not sure that the rssiInfo problem prevents communication with the CCU3. Are you sure that all necessary ports are open (like described in the binding's documentation)? Do you have CUxD installed? If all ports are open please enable DEBUG mode, restart openHAB and post the content of openhab.log until the message regarding rssiInfo appears. |
Yes, CUxD is installed, ports are open. Any idea how to enable DEBUG mode on a synology disk station... |
@keepinslow Unfortunately I don't have any experience with OH on Synology but I can remember that there have been several problems regarding ports. It is possible that the firewall on the disk station blocks the communication from the CCU to openHAB. Maybe you can find some information in the forum.
The normal way to set the the log level is to connect to the openHAB Karaf console via ssh. The console uses port 8101. From the command line (Linux or Windows 10) you can use the following command |
…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 <develop@mherbst.de>
…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 <develop@mherbst.de>
…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 <develop@mherbst.de>
…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 <develop@mherbst.de>
…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 <develop@mherbst.de> Signed-off-by: Daan Meijer <daan@studioseptember.nl>
…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 <develop@mherbst.de>
…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 <develop@mherbst.de>
This problem was first filed here:
#3153
Then moved to Eclipse:
eclipse-archived/smarthome#5790
Then it was forgotten, I guess. ;-)
The text was updated successfully, but these errors were encountered: