search

eclipse-archived / smarthome

Eclipse SmartHome™ project
https://www.eclipse.org/smarthome/
Eclipse Public License 2.0
862 stars 783 forks source link

[Homematic] Error: rssiInfo method not found #5790

Open mdicke2s opened 6 years ago

mdicke2s commented 6 years ago

From @lampi87 on January 21, 2018 16:6

Hello,

after OpenHAB2 restart I get an error in my logfiles

[WARN ] [matic.handler.HomematicBridgeHandler] - Unable to load RSSI values from bridge 'ccu'
[ERROR] [matic.handler.HomematicBridgeHandler] - -1 rssiInfo: unknown.method name (sending rssiInfo()
)
java.io.IOException: -1 rssiInfo: unknown.method name (sending rssiInfo()
)

Expected Behavior

Error should not appear

Current Behavior

Error shown in logfiles. Is something missing in my installation?

Steps to Reproduce (for Bugs)

  1. CCU2 is setup on RPI using YAHM
  2. Add CCU2 to OpenHAB
  3. Restart OpenHAB and watch logfile

Your Environment

Copied from original issue: openhab/openhab2-addons#3153

mdicke2s commented 6 years ago

From @MHerbst on January 24, 2018 18:45

On a first look it seems that the message "unknown.method" is returned by CCU. But I need to have a closer look into the sources to be sure. You could try to enable the trace for the Homematic binding and restart openHAB. With the enabled trace the log file will contain more detailed information from the communication between openHAB and the CCU.

mdicke2s commented 6 years ago

From @ne0h on January 31, 2018 14:19

I have the same issue. Where exactly do I have to set logging to trace to provide more information?

mdicke2s commented 6 years ago

From @maxx92 on April 24, 2018 11:56

Same here... no solution?

mdicke2s commented 6 years ago

From @maxx92 on May 13, 2018 9:38

Still no one?

mdicke2s commented 6 years ago

From @MHerbst on May 13, 2018 11:57

Are you also using YAHM? Can you provide some more information (like a trace output)?

Maybe there is a general problem with YAHM and RSSI information. I found this entry on the Homematic forum: https://homematic-forum.de/forum/viewtopic.php?f=37&t=33522#p316388

mdicke2s commented 6 years ago

From @s0170071 on May 14, 2018 8:3

Same here. I use: RPi 3B+ (stretch) with piVCCU (lxc version of CCU) OH 2.2 stable Mosquitto, influxDB, Telegraf, grafana.

mdicke2s commented 6 years ago

From @gerrieg on June 11, 2018 13:56

Issue still valid? I have tested it with a CCU and RaspberryMatic, works as expected.

mdicke2s commented 6 years ago

From @maxx92 on June 11, 2018 14:44

Unfortunately: yes. Now I use pivccu but no improvement.

2018-06-09 15:16:05.382 [WARN ] [matic.handler.HomematicBridgeHandler] - Unable to load RSSI values from bridge 'PEQ0175517' 2018-06-09 15:16:05.384 [ERROR] [matic.handler.HomematicBridgeHandler] - -1 rssiInfo: unknown.method name (sending rssiInfo() java.io.IOException: -1 rssiInfo: unknown.method name (sending rssiInfo() at org.openhab.binding.homematic.internal.communicator.client.RpcClient.loadRssiInfo(RpcClient.java:385) ~[?:?] at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.loadRssiValues(AbstractHomematicGateway.java:520) ~[?:?]

mdicke2s commented 6 years ago

From @gerrieg on June 11, 2018 14:59

Then i think it is a pivccu issue.

mdicke2s commented 6 years ago

From @s0170071 on June 11, 2018 16:43

Probably not as pivccu runs the original CCU binary.

mdicke2s commented 6 years ago

From @maxx92 on June 11, 2018 19:42

.. I had it on a CCU2 when I originally posted..

mdicke2s commented 6 years ago

From @gerrieg on June 12, 2018 16:10

On a CCU2? I tried it yesterday on my CCU2. Hmmm, currently no idea why the gateway does not know the RPC method.

Can you please install Homematic Manager, then click on RPC Konsole, select BidCos-RF and send the rssiInfo command.

mdicke2s commented 6 years ago

From @maxx92 on June 12, 2018 16:19

Hi Gerhard

As said, I changed from CCU2 to pivCCU about two weeks ago. However, I must add (maybe this has some importance) I use 95% Homematic IP components.. I only have 2 components that are NOT HmIP...

I installed Homematic Manager and sent the rssiInfo > send command. Here’s the output: '{ "OEQ0800785": { "PEQ0175517": [ 65536, -59 ] }, "OEQ0902127": { "PEQ0175517": [ 65536, -59 ] }, "PEQ0175517": { "OEQ0800785": [ -59, 65536 ], "OEQ0902127": [ -59, 65536 ] } } '

Am 12.06.2018 um 18:10 schrieb Gerhard Riegler notifications@github.com:

On a CCU2? I tried it yesterday on my CCU2. Hmmm, currently no idea why the gateway does not know the RPC method.

Can you please install Homematic Manager https://github.com/hobbyquaker/homematic-manager/releases, then click on RPC Konsole, select BidCos-RF and send the rssiInfo command.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/openhab/openhab2-addons/issues/3153#issuecomment-396646624, or mute the thread https://github.com/notifications/unsubscribe-auth/AkHQ3elkXuirXRrVV0Hv02zl2eLzKOKgks5t7-f6gaJpZM4Rl3d1.

mdicke2s commented 6 years ago

From @gerrieg on June 12, 2018 16:26

OK, so that's a good hint with the HMIP devices. There is another issue with a HMIP only installation. As soon as i receive my new RPI-RF-MOD, i have one Raspi free and i will setup a HMIP only system to test.

fanavity commented 5 years ago

is there a solution to the problem in the meantime?

itn3rd77 commented 5 years ago

Hi,

I have seen the same error in openHAB 2.4 with RaspberryMatic 3.41.11.20181222.

2019-01-08 08:25:32.542 [WARN ] [matic.handler.HomematicBridgeHandler] - Unable to load RSSI values from bridge 'homematic'
2019-01-08 08:25:32.543 [ERROR] [matic.handler.HomematicBridgeHandler] - -1 rssiInfo: unknown.method name (sending rssiInfo()
)
java.io.IOException: -1 rssiInfo: unknown.method name (sending rssiInfo()
)
    at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:51) ~[?:?]
    at org.eclipse.smarthome.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:82) ~[?:?]
    at org.eclipse.smarthome.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:94) ~[?:?]
    at org.eclipse.smarthome.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:70) ~[?:?]
    at org.eclipse.smarthome.binding.homematic.internal.communicator.client.RpcClient.loadRssiInfo(RpcClient.java:448) ~[?:?]
    at org.eclipse.smarthome.binding.homematic.internal.communicator.AbstractHomematicGateway.loadRssiValues(AbstractHomematicGateway.java:534) ~[?:?]
    at org.eclipse.smarthome.binding.homematic.handler.HomematicBridgeHandler.initializeInternal(HomematicBridgeHandler.java:118) ~[?:?]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
    at java.lang.Thread.run(Thread.java:748) [?:?]

This is what I have seen on the RaspberryMatic side:

Jan  8 08:25:25 homematic-raspi daemon.warn cuxd[571]: 192.168.100.2 called unknown request method 'rssiInfo'
Jan  8 08:25:25 homematic-raspi daemon.warn cuxd[571]: 192.168.100.2 called unknown request method 'rssiInfo'
Alestrix commented 5 years ago

Same here using a CCU2 and OH v2.4. It shows up in the logs at openhab startup. When I set the "Reload Rssi" switch of Gateway-extras to on I see a somewhat longer exception:

2019-01-30 00:44:22.222 [ERROR] [ematic.handler.HomematicThingHandler] - -1 rssiInfo: unknown.method name (sending rssiInfo()
)
java.io.IOException: -1 rssiInfo: unknown.method name (sending rssiInfo()
)
        at org.eclipse.smarthome.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:51) ~[251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at org.eclipse.smarthome.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:82) ~[251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at org.eclipse.smarthome.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:94) ~[251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at org.eclipse.smarthome.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:70) ~[251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at org.eclipse.smarthome.binding.homematic.internal.communicator.client.RpcClient.loadRssiInfo(RpcClient.java:448) ~[251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at org.eclipse.smarthome.binding.homematic.internal.communicator.AbstractHomematicGateway.loadRssiValues(AbstractHomematicGateway.java:534) ~[251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at org.eclipse.smarthome.binding.homematic.internal.communicator.virtual.ReloadRssiVirtualDatapointHandler.handleCommand(ReloadRssiVirtualDatapointHandler.java:56) ~[251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at org.eclipse.smarthome.binding.homematic.internal.communicator.AbstractHomematicGateway$1.execute(AbstractHomematicGateway.java:673) ~[251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at org.eclipse.smarthome.binding.homematic.internal.misc.DelayedExecuter.start(DelayedExecuter.java:65) ~[251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at org.eclipse.smarthome.binding.homematic.internal.communicator.AbstractHomematicGateway.sendDatapoint(AbstractHomematicGateway.java:665) ~[251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at org.eclipse.smarthome.binding.homematic.internal.communicator.AbstractHomematicGateway.sendDatapoint(AbstractHomematicGateway.java:644) ~[251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at org.eclipse.smarthome.binding.homematic.handler.HomematicThingHandler.sendDatapoint(HomematicThingHandler.java:307) ~[251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at org.eclipse.smarthome.binding.homematic.handler.HomematicThingHandler.handleCommand(HomematicThingHandler.java:283) [251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source) ~[?:?]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
        at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [102:org.eclipse.smarthome.core:0.10.0.oh240]
        at org.eclipse.smarthome.core.internal.common.InvocationHandlerSync.invoke(InvocationHandlerSync.java:59) [102:org.eclipse.smarthome.core:0.10.0.oh240]
        at com.sun.proxy.$Proxy134.handleCommand(Unknown Source) [251:org.eclipse.smarthome.binding.homematic:0.10.0.oh240]
        at org.eclipse.smarthome.core.thing.internal.profiles.ProfileCallbackImpl.handleCommand(ProfileCallbackImpl.java:75) [109:org.eclipse.smarthome.core.thing:0.10.0.oh240]
        at org.eclipse.smarthome.core.thing.internal.profiles.SystemDefaultProfile.onCommandFromItem(SystemDefaultProfile.java:49) [109:org.eclipse.smarthome.core.thing:0.10.0.oh240]
        at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source) ~[?:?]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
        at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [102:org.eclipse.smarthome.core:0.10.0.oh240]
        at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [102:org.eclipse.smarthome.core:0.10.0.oh240]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
        at java.lang.Thread.run(Thread.java:748) [?:?]
regnets commented 4 years ago

I still got the same issue with the current 2.5 Release. It is a clean install with RaspberryMatic as CCU device.

2020-01-01 16:57:03.611 [ERROR] [ernal.handler.HomematicBridgeHandler] - -1 rssiInfo: unknown.method name (sending rssiInfo()
)
java.io.IOException: -1 rssiInfo: unknown.method name (sending rssiInfo()
)
    at org.openhab.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:51) ~[?:?]
    at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:82) ~[?:?]
    at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:94) ~[?:?]
    at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:70) ~[?:?]
    at org.openhab.binding.homematic.internal.communicator.client.RpcClient.loadRssiInfo(RpcClient.java:447) ~[?:?]
    at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.loadRssiValues(AbstractHomematicGateway.java:534) ~[?:?]
    at org.openhab.binding.homematic.internal.handler.HomematicBridgeHandler.initializeInternal(HomematicBridgeHandler.java:120) ~[?:?]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_232]
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_232]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_232]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_232]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_232]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_232]
    at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]

Here is my log. if you need any further information, just ask for it.

I configured everything through textual based configuration. Here is an excerpt from my thing file.

Bridge homematic:bridge:RaspberryMatic "Bridge: RaspberryMatic" [gatewayAddress="10.0.0.210", callbackHost="10.0.0.220"] {
    Thing GATEWAY-EXTRAS-RASPBERRYMATIC GWE00000000  "Homematic: Gateway Extras" @ "Allgemein"
}
sidamos commented 4 years ago

Migrated to: https://github.com/openhab/openhab-addons/issues/6743

Alestrix commented 4 years ago

Just revisiting this issue as I still have the same error in OH 2.5.1-2.

2020-01-19 22:01:04.264 [INFO ] [ommunicator.AbstractHomematicGateway] - HmGatewayInfo[id=CCU,type=CCU2,firmware=2.47.12,address=LEQ0643921,rf=true,wired=false,hmip=true,cuxd=true,group=true]
...
2020-01-19 22:01:29.312 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name '${sysVarAlarmZone1}' contains invalid characters, new Datapoint name '__sysVarAlarmZone1_'
2020-01-19 22:01:29.316 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Datum_MM.TT' contains invalid characters, new Datapoint name 'Datum_MM_TT'
2020-01-19 22:01:29.326 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Tageszeit_hh.mm' contains invalid characters, new Datapoint name 'Tageszeit_hh_mm'
2020-01-19 22:01:29.342 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Rollo Tag/Nacht EG.Rolladen.EsszimmerSued' contains invalid characters, new Datapoint name 'Rollo_Tag_Nacht_EG_Rolladen_EsszimmerSued'
2020-01-19 22:01:29.343 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Rollo Tag/Nacht EG.Rolladen.EsszimmerTerrasse' contains invalid characters, new Datapoint name 'Rollo_Tag_Nacht_EG_Rolladen_EsszimmerTerrasse'
2020-01-19 22:01:29.343 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Rollo Tag/Nacht EG.Rolladen.WohnzimmerOst' contains invalid characters, new Datapoint name 'Rollo_Tag_Nacht_EG_Rolladen_WohnzimmerOst'
2020-01-19 22:01:29.344 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Rollo Tag/Nacht EG.Rolladen.WohnzimmerSued' contains invalid characters, new Datapoint name 'Rollo_Tag_Nacht_EG_Rolladen_WohnzimmerSued'
2020-01-19 22:01:29.344 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Tag/Nacht Definition Mo-Fr' contains invalid characters, new Datapoint name 'Tag_Nacht_Definition_Mo-Fr'
2020-01-19 22:01:29.345 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Tag/Nacht Definition Sa-So' contains invalid characters, new Datapoint name 'Tag_Nacht_Definition_Sa-So'
2020-01-19 22:01:29.626 [WARN ] [ernal.handler.HomematicBridgeHandler] - Unable to load RSSI values from bridge 'ccu'
2020-01-19 22:01:29.627 [ERROR] [ernal.handler.HomematicBridgeHandler] - -1 rssiInfo: unknown.method name (sending rssiInfo()
)
java.io.IOException: -1 rssiInfo: unknown.method name (sending rssiInfo()
)
        at org.openhab.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:51) ~[?:?]
        at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:82) ~[?:?]
        at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:94) ~[?:?]
        at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:70) ~[?:?]
        at org.openhab.binding.homematic.internal.communicator.client.RpcClient.loadRssiInfo(RpcClient.java:447) ~[?:?]
        at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.loadRssiValues(AbstractHomematicGateway.java:534) ~[?:?]
        at org.openhab.binding.homematic.internal.handler.HomematicBridgeHandler.initializeInternal(HomematicBridgeHandler.java:120) ~[?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_232]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_232]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_232]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_232]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_232]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_232]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]
MHerbst commented 4 years ago

Can you please copy or move your post to this issue: https://github.com/openhab/openhab-addons/issues/6743 . The binding has moved back to the openHAB repo.