HmIP-RC8 no fhem PRESS events - dummy CCU3 prog exist

Begonnen von Mario, 10 Januar 2020, 13:53:20

Vorheriges Thema - Nächstes Thema

Mario

Hello,

I have problem with HmIP-RC8, SHORT/LONG_PRESS are not seen by fhem but from another device WRC6 are.
I tried dummy programs also variables scripts and even connection with other device but press events are not seen in fhem events
(via "inform on" only alike UNREACH false/0 events)

Similar configuration from another HmIP-WRC6 pass events to fhem and set device state correctly

What is strange I see minor difference from get  deviceinfo result after RC8 key press:

- after restart I observe deviceinfo with SHORT_PRESS have empty value
- after RC8 press SHORT_PRESS values changes  to "false" value
- => so some events are coming to fhem (maybe only releases not presses, is this possibile ? or some filtering-out in fhem occurs ?)

any hints, how can I fix or trace this further ?
FHEM since 2013, mixed FS20, HmIP, HM,
own modules for heater, garden & wheater station,
sun intensity, rain ratio & soil humidity sensors for inteligent watering.

zap

Is the configuration in CCU correct? Is it possible to change the behavior in CCU, when to send an event (when pressing or releasing a button)?

Please provide a "list" of the device.
2xCCU3 mit ca. 100 Aktoren, Sensoren
Entwicklung: FHEM auf Proxmox Debian VM
Produktiv inzwischen auf Home Assistant gewechselt.
Maintainer: HMCCU, (Fully, AndroidDB)

Mario

I didn't identionally modify CCU config in aspect of RC*, this is 2 week install with very few modification from defaults

Below goes list on RC device

DEF        000XXXXXXX57A
   FUUID      5e159778-f33f-16b6-2a01-6a630fdb11912371
   IODev      iCCU3
   NAME       HmIP_RC8_000XXXXXXX57A
   NR         1053
   STATE      Initialized
   TYPE       HMCCUDEV
   ccuaddr    000XXXXXXX57A
   ccudevstate active
   ccuif      HmIP-RF
   ccuname    HmIP-RC8 000XXXXXXX57A
   ccutype    HmIP-RC8
   channels   9
   firmware   1.0.19
   statevals  devstate
   READINGS:
     2020-01-10 20:11:05   0.UNREACH       0
     2020-01-10 20:11:05   battery         0
     2020-01-10 20:11:05   hmstate         Initialized
     2020-01-08 09:48:56   state           Initialized
   hmccu:
     devspec    000B15699AE57A
     dp:
       0.CONFIG_PENDING:
         OVAL       0
         VAL        0
       0.DUTY_CYCLE:
         OVAL       0
         VAL        0
       0.LOW_BAT:
         OSVAL      0
         OVAL       0
         SVAL       0
         VAL        0
       0.OPERATING_VOLTAGE:
         OVAL       2.6
         VAL        2.6
       0.OPERATING_VOLTAGE_STATUS:
         OVAL       0
         VAL        0
       0.RSSI_DEVICE:
         OVAL       -44
         VAL        -48
       0.UNREACH:
         OSVAL      0
         OVAL       0
         SVAL       0
         VAL        0
       1.PRESS_SHORT:
         OVAL       1
         VAL        1
       2.PRESS_SHORT:
         OVAL       1
         VAL        1
       3.PRESS_SHORT:
         OVAL       1
         VAL        1
       4.PRESS_SHORT:
         OVAL       1
         VAL        1
       5.PRESS_SHORT:
         OVAL       1
         VAL        1
       7.PRESS_SHORT:
         OVAL       1
         VAL        1
       8.PRESS_SHORT:
         OVAL       1
         VAL        1
Attributes:
   IODev      iCCU3
   room       HmIP
FHEM since 2013, mixed FS20, HmIP, HM,
own modules for heater, garden & wheater station,
sun intensity, rain ratio & soil humidity sensors for inteligent watering.

Mario

OK, thank you for hint, I already found reason,
it was missing ccureadingfilter for my RC8 (due missing defaults for RC8 in fhem)  AND with not empty ccudef-readingfilter (my entry was based on wiki HMCCU best practice)
FHEM since 2013, mixed FS20, HmIP, HM,
own modules for heater, garden & wheater station,
sun intensity, rain ratio & soil humidity sensors for inteligent watering.

zap

Many users have problems with the behavior of ccureadingfilter. It works without this attribute, if no ccudef-readingfilter ist set in IO Device. I will change this in the next version and remove the default attribute in Io device.

For a multi switch it makes more sense to define a HMCCUCHN device for each channel. Otherwise it's not possible to assign a unique statedatapoint because of the multiple PRESS datapoints.
And don't forget to set attribute event-on-update-reading to PRESS or .*
PRESS... will never be false. Without this attribute FHEM will recognize only the first button press.
2xCCU3 mit ca. 100 Aktoren, Sensoren
Entwicklung: FHEM auf Proxmox Debian VM
Produktiv inzwischen auf Home Assistant gewechselt.
Maintainer: HMCCU, (Fully, AndroidDB)