[homematic] remote problem

MrPatHome commented 7 years ago

Hio all,

gat a problem with my remote since i switched to openhab 2. Cant get it workin

Items: Switch RC_7 "Remote Control Button 7" {homematic="address=MEQ0601774, channel=7, parameter=PRESS_SHORT"} Switch RC_8 "Remote Control Button 8" {homematic="address=MEQ0601774, channel=8, parameter=PRESS_SHORT"}

rule rule "Test vitrine an" when Item RC_8 received update ON

then sendCommand(VitrineRechts_1_State, ON) end

MHerbst commented 7 years ago

The item definitions format has changed for OH2: http://docs.openhab.org/addons/bindings/homematic/readme.html

MrPatHome commented 7 years ago

Thanks M,

now changed to: // Fernsteuerung

Switch RC_7 "Remote Control Button 7" { channel="homematic:HM-RC-8:ccu:MEQ0601774:7#PRESS_SHORT" } Switch RC_8 "Remote Control Button 7" { channel="homematic:HM-RC-8:ccu:MEQ0601774:8#PRESS_SHORT" }

Still not workin. Maybe it´s the name of the Bridge. Tried "ccu" like in the example and 8a90db01 wihch ist the Number of the Homematic bridhe in Paper UI. BTW: Is it a Problem, to have the same Item defined in Paper UI and items file?

Greetings

Christian

MrPatHome commented 7 years ago

P.S.: Using Homegear

MHerbst commented 7 years ago

BTW: Is it a Problem, to have the same Item defined in Paper UI and items file?

Hmm I am not sure what happens if both have the same ID. Maybe its better to move the items file for a test to a different place.

P.S.: Using Homegear

Here are two important hints regarding Homegear:

MrPatHome commented 7 years ago

Tried both,

Swiches defined in the items file (They appear instantly in Paper UI too) and only in Paper UI.

Still doesn´t work :-(

Is "recieve update" still the right way in Openhab 2 or is a new syntax required?

MHerbst commented 7 years ago

Can you activate the trace with

log:set TRACE org.openhab.binding.homematic

and attach the log file?

MrPatHome commented 7 years ago

Sorry, but i don´t know where to activate the trace

MHerbst commented 7 years ago

The documentation contains some information http://docs.openhab.org/administration/logging.html and http://docs.openhab.org/administration/console.html. Instead of using a ssh client to access the console you can also execute ./runtime/bin/client on your RasPi.

MrPatHome commented 7 years ago

This is what the log says, when i press the buttons:

2017-02-03 19:56:52.702 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Integer) value '-58' for 'MEQ0601774:0#RSSI_DEVICE' from gateway with id '8a90db01' 2017-02-03 19:56:54.955 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Integer) value '-42' for 'MEQ0192561:0#RSSI_DEVICE' from gateway with id '8a90db01' 2017-02-03 19:56:55.048 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Boolean) value 'false' for 'MEQ0192561:1#STATE' from gateway with id '8a90db01' 2017-02-03 19:56:55.051 [TRACE] [ng.homematic.converter.TypeConverter] - Converting BOOL value 'false' with OnOffTypeConverter for 'MEQ0192561:1#STATE' 2017-02-03 19:56:55.058 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Boolean) value 'false' for 'MEQ0192561:1#WORKING' from gateway with id '8a90db01' 2017-02-03 19:56:58.547 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Integer) value '-52' for 'LEQ0928823:0#RSSI_DEVICE' from gateway with id '8a90db01' 2017-02-03 19:56:58.560 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Double) value '375.0' for 'LEQ0928823:2#CURRENT' from gateway with id '8a90db01' 2017-02-03 19:56:58.571 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Double) value '6614.099998' for 'LEQ0928823:2#ENERGY_COUNTER' from gateway with id '8a90db01' 2017-02-03 19:56:58.576 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Double) value '50.03' for 'LEQ0928823:2#FREQUENCY' from gateway with id '8a90db01' 2017-02-03 19:56:58.582 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Double) value '51.83' for 'LEQ0928823:2#POWER' from gateway with id '8a90db01' 2017-02-03 19:56:58.586 [TRACE] [ng.homematic.converter.TypeConverter] - Converting FLOAT value '51.83' with DecimalTypeConverter for 'LEQ0928823:2#POWER' 2017-02-03 19:56:58.593 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Double) value '230.6' for 'LEQ0928823:2#VOLTAGE' from gateway with id '8a90db01' 2017-02-03 19:57:03.325 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Integer) value '-58' for 'MEQ0601774:0#RSSI_DEVICE' from gateway with id '8a90db01' 2017-02-03 19:57:05.263 [TRACE] [al.communicator.client.SocketHandler] - Returning socket for port 2001 2017-02-03 19:57:05.956 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Integer) value '-45' for 'MEQ0192561:0#RSSI_DEVICE' from gateway with id '8a90db01' 2017-02-03 19:57:06.049 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Boolean) value 'true' for 'MEQ0192561:1#STATE' from gateway with id '8a90db01' 2017-02-03 19:57:06.058 [TRACE] [ng.homematic.converter.TypeConverter] - Converting BOOL value 'true' with OnOffTypeConverter for 'MEQ0192561:1#STATE' 2017-02-03 19:57:06.072 [DEBUG] [ternal.communicator.HomematicGateway] - Received new (Boolean) value 'false' for 'MEQ0192561:1#WORKING' from gateway with id '8a90db01'

MrPatHome commented 7 years ago

Here´s the complete log:

openhab.log.txt

(The Remote is MEQ0601774)

MHerbst commented 7 years ago

Your log file is very large and contains entries from last year. You should delete it and then restart openHAB.

Then there are some messages regarding parsing problems in phome.things, demo.rules, p-home.rules. You should either check and correct them or move them to a different directory to start OH without errors.

Here is another message that may explan your problems: 2017-02-03 18:30:35.740 [INFO ] [atic.type.HomematicTypeGeneratorImpl] - Multiple firmware versions for device type 'HM-LC-Sw1PBU-FM' found (2.3, 2.8). Make sure, all devices of the same type have the same firmware version, otherwise you MAY have channel and/or datapoint errors in the logfile

According you the log file the device is correctly detected and the add-on receives some datapoint values (like RSSI).

MrPatHome commented 7 years ago

Thanks for the Help

Deleted The Logfile
Still can´t update the firmware of one the switches. But this couses no problem to any other rule. The switches work correctly by triggerin from homegear diretly or with cron based rules. I only got the problem that my rules dont work on my romote and on the astro binding (see other post)

Any other Idea what could be wrong?

MHerbst commented 7 years ago

@gerrieg Do you have an idea?

gerrieg commented 7 years ago

First of all the correct bridgeId is 8a90db01, so you have to map the channels like this:

{ channel="homematic:HM-RC-8:8a90db01:MEQ0601774:7#PRESS_SHORT" }

It's hard to say what's wrong, because the logfile has so many errors that are not related to homematic and there is no TRACE information. Please cleanup the errors and then switch the Homematic binding into DEBUG mode and press a button on the remote control. There should be a event in the logfile that shows you the correct mapping.

If it still does not work, please post a TRACE log

Please use the latest snapshot build, it includes many fixes and optimizations based on user feedback.

MHerbst commented 7 years ago

@MrPatHome Is this issue still open? If no please close this issue.

MrPatHome commented 7 years ago

Don´t get it working yet but i think it´s a problem with the remote. Homematic Konfigurator permanently has Data to transfer to the remote and will not finish. So i think it´s a problem with the device. Think i should close it here.

openhab / openhab-addons

[homematic] remote problem #1748