Nur Text | Text mit Bildern

FHEM Forum

FHEM - Hausautomations-Systeme => Homematic => Thema gestartet von: buliwyf am 30 Oktober 2019, 19:35:36

Titel: Ebenfalls Probleme mit Raspmatic CCU3 und sich nicht aktualisierenden Werten.
Beitrag von: buliwyf am 30 Oktober 2019, 19:35:36
Hallo zusammen,

ich habe das gleiche Problem das einige hier schon hatten.
Ich habe meine CCU via HMCCU in FHEM integriert.
Es funktioniert auch alles soweit bis auf die regelmäßige Aktualisierung durch den RPC Server.
Ich habe Homematic und Homematic IP Geräte an meiner CCU
Ein "set d_ccu update" funktioniert immer und aktualisiert die Geräte.

Hier der Auszug vom start des RPC Servers.
Code Auswählen

2019.10.30 18:57:00 5: Cmd: >define d_rpc203045BidCos_RF HMCCURPCPROC http://192.168.203.45 BidCos-RF<
2019.10.30 18:57:00 5: Loading ./FHEM/88_HMCCURPCPROC.pm
2019.10.30 18:57:00 1: HMCCURPCPROC: [d_rpc203045BidCos_RF] Initialized version 1.8 for interface BidCos-RF with I/O device d_ccu
2019.10.30 18:57:00 4: HMCCURPCPROC: [d_rpc203045BidCos_RF] Reset RPC state
2019.10.30 18:57:00 4: HMCCURPCPROC: [d_rpc203045BidCos_RF] Set rpcstate to inactive
2019.10.30 18:57:00 4: HMCCURPCPROC: [d_rpc203045BidCos_RF] Set state to Initialized
2019.10.30 18:57:00 5: Cmd: >attr d_rpc203045BidCos_RF alias CCU RPC BidCos-RF<
2019.10.30 18:57:00 5: Cmd: >define d_rpc203045HmIP_RF HMCCURPCPROC http://192.168.203.45 HmIP-RF<
2019.10.30 18:57:00 1: HMCCURPCPROC: [d_rpc203045HmIP_RF] Initialized version 1.8 for interface HmIP-RF with I/O device d_ccu
2019.10.30 18:57:00 4: HMCCURPCPROC: [d_rpc203045HmIP_RF] Reset RPC state
2019.10.30 18:57:00 4: HMCCURPCPROC: [d_rpc203045HmIP_RF] Set rpcstate to inactive
2019.10.30 18:57:00 4: HMCCURPCPROC: [d_rpc203045HmIP_RF] Set state to Initialized
2019.10.30 18:57:00 5: Cmd: >attr d_rpc203045HmIP_RF alias CCU RPC HmIP-RF<
2019.10.30 18:57:02 0: HMCCU: Start of RPC server after FHEM initialization in 12 seconds
2019.10.30 18:57:14 2: HMCCU: [d_ccu] Get RPC device for interface BidCos-RF
2019.10.30 18:57:14 2: HMCCU: [d_ccu] Get RPC device for interface HmIP-RF
2019.10.30 18:57:14 2: HMCCURPCPROC: [d_rpc203045BidCos_RF] RPC server process started for interface BidCos-RF with PID=4058
2019.10.30 18:57:14 2: CCURPC: [d_rpc203045BidCos_RF] Initializing RPC server CB2001203050203045 for interface BidCos-RF
2019.10.30 18:57:14 1: HMCCURPCPROC: [d_rpc203045BidCos_RF] RPC server starting
2019.10.30 18:57:14 5: Starting notify loop for d_rpc203045BidCos_RF, 1 event(s), first is RPC server starting
2019.10.30 18:57:14 2: HMCCURPCPROC: [d_rpc203045HmIP_RF] RPC server process started for interface HmIP-RF with PID=4059
2019.10.30 18:57:14 2: CCURPC: [d_rpc203045HmIP_RF] Initializing RPC server CB2010203050203045 for interface HmIP-RF
2019.10.30 18:57:14 1: HMCCURPCPROC: [d_rpc203045HmIP_RF] RPC server starting
2019.10.30 18:57:14 5: Starting notify loop for d_rpc203045HmIP_RF, 1 event(s), first is RPC server starting
2019.10.30 18:57:14 2: HMCCURPCPROC: [d_rpc203045BidCos_RF] Callback server CB2001203050203045 created. Listening on port 7411
2019.10.30 18:57:14 2: CCURPC: [d_rpc203045BidCos_RF] CB2001203050203045 accepting connections. PID=4058
2019.10.30 18:57:14 2: HMCCURPCPROC: [d_rpc203045BidCos_RF] RPC server CB2001203050203045 enters server loop
2019.10.30 18:57:14 2: HMCCURPCPROC: [d_rpc203045BidCos_RF] Registering callback http://192.168.203.50:7411/fh2001 of type A with ID CB2001203050203045 at http://192.168.203.45:2001
2019.10.30 18:57:14 2: HMCCURPCPROC: [d_rpc203045HmIP_RF] Callback server CB2010203050203045 created. Listening on port 7420
2019.10.30 18:57:14 2: CCURPC: [d_rpc203045HmIP_RF] CB2010203050203045 accepting connections. PID=4059
2019.10.30 18:57:14 1: HMCCURPCPROC: [d_rpc203045BidCos_RF] RPC server CB2001203050203045 running
2019.10.30 18:57:14 1: HMCCURPCPROC: [d_rpc203045BidCos_RF] Scheduled CCU ping every 300 seconds
2019.10.30 18:57:14 5: Starting notify loop for d_rpc203045BidCos_RF, 1 event(s), first is RPC server CB2001203050203045 running
2019.10.30 18:57:14 2: HMCCURPCPROC: [d_rpc203045HmIP_RF] RPC server CB2010203050203045 enters server loop
2019.10.30 18:57:14 2: HMCCURPCPROC: [d_rpc203045HmIP_RF] Registering callback http://192.168.203.50:7420/fh2010 of type A with ID CB2010203050203045 at http://192.168.203.45:2010
2019.10.30 18:57:15 1: HMCCURPCPROC: [d_rpc203045HmIP_RF] RPC server CB2010203050203045 running
2019.10.30 18:57:15 1: HMCCU: [d_ccu] All RPC servers running
2019.10.30 18:57:15 5: Starting notify loop for d_ccu, 1 event(s), first is RPC server running
2019.10.30 18:57:15 5: Starting notify loop for d_rpc203045HmIP_RF, 1 event(s), first is RPC server CB2010203050203045 running
2019.10.30 18:57:15 2: CCURPC: [d_rpc203045BidCos_RF] CB2001203050203045 NewDevice received 146 device and channel specifications
2019.10.30 18:57:15 2: CCURPC: [d_rpc203045HmIP_RF] CB2010203050203045 NewDevice received 88 device and channel specifications


Ich freue mich über jede Idee.

Hier der Code für das Device Setup.
Code Auswählen

defmod d_ccu HMCCU 192.168.203.45
attr d_ccu ccuflags procrpc
attr d_ccu room Homematic-IP
attr d_ccu rpcinterfaces BidCos-RF,HmIP-RF
attr d_ccu rpcport 2001,2010
attr d_ccu rpcserver on
attr d_ccu stateFormat rpcstate/state

setstate d_ccu running/OK
setstate d_ccu 2019-10-31 09:05:51 count_channels 197
setstate d_ccu 2019-10-31 09:05:51 count_devices 20
setstate d_ccu 2019-10-31 09:05:51 count_groups 0
setstate d_ccu 2019-10-31 09:05:51 count_interfaces 4
setstate d_ccu 2019-10-31 09:05:51 count_programs 5
setstate d_ccu 2019-10-30 22:07:13 iface_addr_1 PEQ0625013
setstate d_ccu 2019-10-30 22:07:13 iface_addr_2 3014F711A0001F58A992F175
setstate d_ccu 2019-10-30 22:07:13 iface_conn_1 1
setstate d_ccu 2019-10-30 22:07:13 iface_conn_2 1
setstate d_ccu 2019-10-30 22:07:13 iface_ducy_1 7
setstate d_ccu 2019-10-30 22:07:13 iface_ducy_2 8
setstate d_ccu 2019-10-30 22:07:13 iface_type_1 CCU2
setstate d_ccu 2019-10-30 22:07:13 iface_type_2 HMIP_CCU2
setstate d_ccu 2019-10-31 09:06:06 rpcstate running
setstate d_ccu 2019-10-31 09:06:06 state OK


Ich habe mir vorerst mit einem at geholfen.
Code Auswählen

defmod updateCCU at +*00:05:00 get d_ccu update
attr updateCCU room Homematic-IP
Titel: Antw:Ebenfalls Probleme mit Raspmatic CCU3 und sich nicht aktualisierenden Werten.
Beitrag von: zap am 31 Oktober 2019, 18:02:04
Hast Du einen Logauszug vom FHEM Start für die HMCCU und HMCCURPCPROC Einträge?
Titel: Antw:Ebenfalls Probleme mit Raspmatic CCU3 und sich nicht aktualisierenden Werten.
Beitrag von: buliwyf am 31 Oktober 2019, 20:59:13
Danke für die Antwort.

Bitteschön.

Code Auswählen

2019.10.31 20:57:00 1: HMCCU: [d_ccu] Initialized version 4.3.019
2019.10.31 20:57:00 1: HMCCU: [d_ccu] HMCCU: Initializing device
2019.10.31 20:57:00 1: HMCCU: [d_ccu] HMCCU: Read 20 devices with 197 channels from CCU 192.168.203.45
2019.10.31 20:57:00 1: HMCCU: [d_ccu] HMCCU: Read 4 interfaces from CCU 192.168.203.45
2019.10.31 20:57:00 1: HMCCU: [d_ccu] HMCCU: Read 5 programs from CCU 192.168.203.45
2019.10.31 20:57:00 1: HMCCU: [d_ccu] HMCCU: Read 0 virtual groups from CCU 192.168.203.45
2019.10.31 20:57:01 1: HMCCURPCPROC: [d_rpc203045BidCos_RF] Initialized version 1.8 for interface BidCos-RF with I/O device d_ccu
2019.10.31 20:57:01 1: HMCCURPCPROC: [d_rpc203045HmIP_RF] Initialized version 1.8 for interface HmIP-RF with I/O device d_ccu
2019.10.31 20:57:01 1: HMCCURPCPROC: [d_rpc203045CUxD] Initialized version 1.8 for interface CUxD with I/O device d_ccu
2019.10.31 20:57:01 0: HMCCU: Start of RPC server after FHEM initialization in 12 seconds
2019.10.31 20:57:13 2: HMCCU: [d_ccu] Get RPC device for interface BidCos-RF
2019.10.31 20:57:13 2: HMCCU: [d_ccu] Get RPC device for interface HmIP-RF
2019.10.31 20:57:13 2: HMCCURPCPROC: [d_rpc203045BidCos_RF] RPC server process started for interface BidCos-RF with PID=13272
2019.10.31 20:57:13 2: CCURPC: [d_rpc203045BidCos_RF] Initializing RPC server CB2001203050203045 for interface BidCos-RF
2019.10.31 20:57:13 1: HMCCURPCPROC: [d_rpc203045BidCos_RF] RPC server starting
2019.10.31 20:57:13 2: CCURPC: [d_rpc203045HmIP_RF] Initializing RPC server CB2010203050203045 for interface HmIP-RF
2019.10.31 20:57:13 2: HMCCURPCPROC: [d_rpc203045HmIP_RF] RPC server process started for interface HmIP-RF with PID=13273
2019.10.31 20:57:13 1: HMCCURPCPROC: [d_rpc203045HmIP_RF] RPC server starting
2019.10.31 20:57:14 2: HMCCURPCPROC: [d_rpc203045BidCos_RF] Callback server CB2001203050203045 created. Listening on port 7411
2019.10.31 20:57:14 2: CCURPC: [d_rpc203045BidCos_RF] CB2001203050203045 accepting connections. PID=13272
2019.10.31 20:57:14 2: HMCCURPCPROC: [d_rpc203045HmIP_RF] Callback server CB2010203050203045 created. Listening on port 7420
2019.10.31 20:57:14 2: CCURPC: [d_rpc203045HmIP_RF] CB2010203050203045 accepting connections. PID=13273
2019.10.31 20:57:14 2: HMCCURPCPROC: [d_rpc203045BidCos_RF] RPC server CB2001203050203045 enters server loop
2019.10.31 20:57:14 2: HMCCURPCPROC: [d_rpc203045BidCos_RF] Registering callback http://192.168.203.50:7411/fh2001 of type A with ID CB2001203050203045 at http://192.168.203.45:2001
2019.10.31 20:57:14 1: HMCCURPCPROC: [d_rpc203045BidCos_RF] RPC server CB2001203050203045 running
2019.10.31 20:57:14 1: HMCCURPCPROC: [d_rpc203045BidCos_RF] Scheduled CCU ping every 300 seconds
2019.10.31 20:57:14 2: HMCCURPCPROC: [d_rpc203045HmIP_RF] RPC server CB2010203050203045 enters server loop
2019.10.31 20:57:14 2: HMCCURPCPROC: [d_rpc203045HmIP_RF] Registering callback http://192.168.203.50:7420/fh2010 of type A with ID CB2010203050203045 at http://192.168.203.45:2010
2019.10.31 20:57:14 1: HMCCURPCPROC: [d_rpc203045HmIP_RF] RPC server CB2010203050203045 running
2019.10.31 20:57:14 1: HMCCU: [d_ccu] All RPC servers running
2019.10.31 20:57:15 2: HMCCU: [d_ccu] Updating 3 of 3 client devices matching devexp=.* filter=ccudevstate=active,ccuif=BidCos-RF|HmIP-RF
2019.10.31 20:57:15 2: CCURPC: [d_rpc203045BidCos_RF] CB2001203050203045 NewDevice received 126 device and channel specifications
2019.10.31 20:57:15 2: HMCCU: [d_ccu] Update success=3 failed=0
2019.10.31 20:57:15 2: CCURPC: [d_rpc203045HmIP_RF] CB2010203050203045 NewDevice received 88 device and channel specifications


Zusätzliche Infos kann ich jederzeit besorgen.
Titel: Antw:Ebenfalls Probleme mit Raspmatic CCU3 und sich nicht aktualisierenden Werten.
Beitrag von: zap am 31 Oktober 2019, 21:44:25
Wenn du eine Weile wartest nach dem Start und dann

get d_ccu rpcevents

ausführst, was wird dann bei den EV Einträgen angezeigt?
Titel: Antw:Ebenfalls Probleme mit Raspmatic CCU3 und sich nicht aktualisierenden Werten.
Beitrag von: buliwyf am 31 Oktober 2019, 22:51:45
Das hier?

Code Auswählen

Event statistics for server CB2001203050203045
Average event delay = 0.0571361054353608
========================================
ET Sent by RPC server   Received by FHEM
----------------------------------------
EV                  0                271

ND                  0                126

DD                  0                  0

RD                  0                  0

RA                  0                  0

UD                  0                  0

IN                  0                  0

EX                  0                  0

SL                  0                  1

TO                  0                  0

Event statistics for server CB2010203050203045
Average event delay = 0.00217715176669034
========================================
ET Sent by RPC server   Received by FHEM
----------------------------------------
EV                  0                 22

ND                  0                 88

DD                  0                  0

RD                  0                  0

RA                  0                  0

UD                  0                  0

IN                  0                  0

EX                  0                  0

SL                  0                  1

TO                  0                  0


Titel: Antw:Ebenfalls Probleme mit Raspmatic CCU3 und sich nicht aktualisierenden Werten.
Beitrag von: zap am 01 November 2019, 12:39:23
Ja. Anhand der EV Einträge kannst Du sehen, dass Events von der CCU in FHEM angekommen sind.
Wenn die Readings nicht aktualisiert werden, kann das auch an einer falschen ccureadingfilter Konfiguration im HMCCUDEV/HMCCUCHN Device liegen
Titel: Antw:Ebenfalls Probleme mit Raspmatic CCU3 und sich nicht aktualisierenden Werten.
Beitrag von: buliwyf am 01 November 2019, 13:08:24
Danke für die Info.

Ich habe es mir eben mal angesehen.

als ccureadingfilter war im Device .* eingetragen.
Im ioDev bei ccudef-readingfilters nichts.
Jetzt habe ich es mal überall gelöscht.
Die Situation hat sich nicht geändert.

Code Auswählen

defmod Wandthermostat_Buero HMCCUDEV 000A9A49993DCC
attr Wandthermostat_Buero IODev d_ccu
attr Wandthermostat_Buero controldatapoint 1.SET_POINT_TEMPERATURE
attr Wandthermostat_Buero eventMap /datapoint 1.BOOST_MODE true:Boost/datapoint 1.CONTROL_MODE 0:Auto/datapoint 1.CONTROL_MODE 1:Manual/datapoint 1.CONTROL_MODE 2:Holiday/datapoint 1.SET_POINT_TEMPERATURE 4.5:off/datapoint 1.SET_POINT_TEMPERATURE 30.5:on/
attr Wandthermostat_Buero genericDeviceType thermostat
attr Wandthermostat_Buero icon max_wandthermostat
attr Wandthermostat_Buero room Buero,Homematic-IP
attr Wandthermostat_Buero statedatapoint 1.SET_POINT_TEMPERATURE
attr Wandthermostat_Buero stripnumber 1
attr Wandthermostat_Buero substexcl control
attr Wandthermostat_Buero substitute SET_POINT_TEMPERATURE!#0-4.5:off,#30.5-40:on;;WINDOW_STATE!(0|false):closed,(1|true):open
attr Wandthermostat_Buero webCmd control:Boost:Auto:Manual:Holiday:on:off
attr Wandthermostat_Buero widgetOverride control:slider,4.5,0.5,30.5,1

setstate Wandthermostat_Buero 24.0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.CONFIG_PENDING false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.DUTY_CYCLE false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.INSTALL_TEST true
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.LOW_BAT false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.OPERATING_VOLTAGE 3.0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.OPERATING_VOLTAGE_STATUS 0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.RSSI_DEVICE 193
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.RSSI_PEER 200
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.UNREACH false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.UPDATE_PENDING false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.ACTIVE_PROFILE 1
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.ACTUAL_TEMPERATURE 24.4
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.ACTUAL_TEMPERATURE_STATUS 0
setstate Wandthermostat_Buero 2019-11-01 11:32:24 1.BOOST_MODE 0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.BOOST_TIME 0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.FROST_PROTECTION false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.HEATING_COOLING 0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.HUMIDITY 37
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.HUMIDITY_STATUS 0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.PARTY_MODE false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.PARTY_SET_POINT_TEMPERATURE 0.0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.PARTY_TIME_END
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.PARTY_TIME_START
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.QUICK_VETO_TIME 0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.SET_POINT_MODE 1
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.SET_POINT_TEMPERATURE 24.0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.SWITCH_POINT_OCCURED false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.WINDOW_STATE closed
setstate Wandthermostat_Buero 2019-11-01 12:55:49 control 24.0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 hmstate 24.0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 state 24.0


Hier der jeweilige Raw State:
Code Auswählen

defmod Wandthermostat_Buero HMCCUDEV 000A9A49993DCC
attr Wandthermostat_Buero IODev d_ccu
attr Wandthermostat_Buero controldatapoint 1.SET_POINT_TEMPERATURE
attr Wandthermostat_Buero eventMap /datapoint 1.BOOST_MODE true:Boost/datapoint 1.CONTROL_MODE 0:Auto/datapoint 1.CONTROL_MODE 1:Manual/datapoint 1.CONTROL_MODE 2:Holiday/datapoint 1.SET_POINT_TEMPERATURE 4.5:off/datapoint 1.SET_POINT_TEMPERATURE 30.5:on/
attr Wandthermostat_Buero genericDeviceType thermostat
attr Wandthermostat_Buero icon max_wandthermostat
attr Wandthermostat_Buero room Buero,Homematic-IP
attr Wandthermostat_Buero statedatapoint 1.SET_POINT_TEMPERATURE
attr Wandthermostat_Buero stripnumber 1
attr Wandthermostat_Buero substexcl control
attr Wandthermostat_Buero substitute SET_POINT_TEMPERATURE!#0-4.5:off,#30.5-40:on;;WINDOW_STATE!(0|false):closed,(1|true):open
attr Wandthermostat_Buero webCmd control:Boost:Auto:Manual:Holiday:on:off
attr Wandthermostat_Buero widgetOverride control:slider,4.5,0.5,30.5,1

setstate Wandthermostat_Buero 24.0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.CONFIG_PENDING false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.DUTY_CYCLE false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.INSTALL_TEST true
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.LOW_BAT false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.OPERATING_VOLTAGE 3.0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.OPERATING_VOLTAGE_STATUS 0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.RSSI_DEVICE 193
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.RSSI_PEER 200
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.UNREACH false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 0.UPDATE_PENDING false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.ACTIVE_PROFILE 1
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.ACTUAL_TEMPERATURE 24.4
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.ACTUAL_TEMPERATURE_STATUS 0
setstate Wandthermostat_Buero 2019-11-01 11:32:24 1.BOOST_MODE 0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.BOOST_TIME 0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.FROST_PROTECTION false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.HEATING_COOLING 0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.HUMIDITY 37
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.HUMIDITY_STATUS 0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.PARTY_MODE false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.PARTY_SET_POINT_TEMPERATURE 0.0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.PARTY_TIME_END
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.PARTY_TIME_START
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.QUICK_VETO_TIME 0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.SET_POINT_MODE 1
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.SET_POINT_TEMPERATURE 24.0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.SWITCH_POINT_OCCURED false
setstate Wandthermostat_Buero 2019-11-01 12:55:49 1.WINDOW_STATE closed
setstate Wandthermostat_Buero 2019-11-01 12:55:49 control 24.0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 hmstate 24.0
setstate Wandthermostat_Buero 2019-11-01 12:55:49 state 24.0




Code Auswählen

defmod Wandthermostat_Wohnzimmer HMCCUDEV 000A9A4999461B
attr Wandthermostat_Wohnzimmer IODev d_ccu
attr Wandthermostat_Wohnzimmer controldatapoint 1.SET_POINT_TEMPERATURE
attr Wandthermostat_Wohnzimmer eventMap /datapoint 1.BOOST_MODE true:Boost/datapoint 1.CONTROL_MODE 0:Auto/datapoint 1.CONTROL_MODE 1:Manual/datapoint 1.CONTROL_MODE 2:Holiday/datapoint 1.SET_POINT_TEMPERATURE 4.5:off/datapoint 1.SET_POINT_TEMPERATURE 30.5:on/
attr Wandthermostat_Wohnzimmer genericDeviceType thermostat
attr Wandthermostat_Wohnzimmer icon max_wandthermostat
attr Wandthermostat_Wohnzimmer room Homematic-IP,Wohnzimmer
attr Wandthermostat_Wohnzimmer statedatapoint 1.SET_POINT_TEMPERATURE
attr Wandthermostat_Wohnzimmer stripnumber 1
attr Wandthermostat_Wohnzimmer substexcl control
attr Wandthermostat_Wohnzimmer substitute SET_POINT_TEMPERATURE!#0-4.5:off,#30.5-40:on;;WINDOW_STATE!(0|false):closed,(1|true):open
attr Wandthermostat_Wohnzimmer webCmd control:Boost:Auto:Manual:Holiday:on:off
attr Wandthermostat_Wohnzimmer widgetOverride control:slider,4.5,0.5,30.5,1

setstate Wandthermostat_Wohnzimmer 24.0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 0.CONFIG_PENDING 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 0.DUTY_CYCLE 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 12:55:49 0.INSTALL_TEST true
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 0.LOW_BAT 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 0.OPERATING_VOLTAGE 3.0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 0.OPERATING_VOLTAGE_STATUS 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 0.RSSI_DEVICE -74
setstate Wandthermostat_Wohnzimmer 2019-11-01 12:55:49 0.RSSI_PEER 176
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 0.UNREACH 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 12:55:49 0.UPDATE_PENDING false
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.ACTIVE_PROFILE 1
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.ACTUAL_TEMPERATURE 24.7
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.ACTUAL_TEMPERATURE_STATUS 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.BOOST_MODE 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.BOOST_TIME 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.FROST_PROTECTION 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.HEATING_COOLING 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.HUMIDITY 44
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.HUMIDITY_STATUS 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.PARTY_MODE 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 12:55:49 1.PARTY_SET_POINT_TEMPERATURE 0.0
setstate Wandthermostat_Wohnzimmer 2019-11-01 12:55:49 1.PARTY_TIME_END
setstate Wandthermostat_Wohnzimmer 2019-11-01 12:55:49 1.PARTY_TIME_START
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.QUICK_VETO_TIME 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.SET_POINT_MODE 1
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.SET_POINT_TEMPERATURE 24.0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.SWITCH_POINT_OCCURED 0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 1.WINDOW_STATE closed
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 control 24.0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 hmstate 24.0
setstate Wandthermostat_Wohnzimmer 2019-11-01 13:02:51 state 24.0


Hier sind auch jede Menge seltsame Werte im device. Hier ist der Logauszug dazu :
Code Auswählen

2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 0.DUTY_CYCLE: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 0.UNREACH: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 0.OPERATING_VOLTAGE: 3.0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 0.CONFIG_PENDING: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 0.RSSI_DEVICE: -74
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 0.LOW_BAT: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 0.OPERATING_VOLTAGE_STATUS: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer hmstate: 24.0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.ACTUAL_TEMPERATURE: 24.7
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.FROST_PROTECTION: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.HUMIDITY: 44
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.HUMIDITY_STATUS: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.ACTUAL_TEMPERATURE_STATUS: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.SET_POINT_TEMPERATURE: 24.0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer control: 24.0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 24.0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.PARTY_MODE: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.SWITCH_POINT_OCCURED: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.WINDOW_STATE: closed
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.QUICK_VETO_TIME: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.BOOST_TIME: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.SET_POINT_MODE: 1
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.BOOST_MODE: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.ACTIVE_PROFILE: 1
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer 1.HEATING_COOLING: 0
2019-11-01_13:02:51 Wandthermostat_Wohnzimmer hmstate: 24.0


z.B. 0 statt false. Das sollte doch so auch nicht sein oder?

nach einem get d_ccu update waren wieder alle Werte normal.

Danke für deine Hilfe.
VG
Titel: Antw:Ebenfalls Probleme mit Raspmatic CCU3 und sich nicht aktualisierenden Werten.
Beitrag von: buliwyf am 01 November 2019, 15:13:43
Ich habe eben noch etwas getüftelt.

wird der RPC Call im fhem.log mit

Code Auswählen

2019.11.01 14:57:44 2: HMCCU: [d_ccu] Updating 3 of 3 client devices matching devexp=.* filter=ccudevstate=active
2019.11.01 14:57:44 2: HMCCU: [d_ccu] Update success=3 failed=0

gelogged?

Dann sollte der Eintrag doch alle 5 Minuten dort stehen?
Oder steht der Eintrag nur drin wenn ich manuel über das ioDEV aktualisiere?
Titel: Antw:Ebenfalls Probleme mit Raspmatic CCU3 und sich nicht aktualisierenden Werten.
Beitrag von: zap am 01 November 2019, 17:59:55
Diese Logeinträge sollten bei jedem get update im IO Device kommen.

Steigen die EV Werte bei get rpcevents an ?
Titel: Antw:Ebenfalls Probleme mit Raspmatic CCU3 und sich nicht aktualisierenden Werten.
Beitrag von: buliwyf am 02 November 2019, 08:08:12
Das kann ich bestätigen:

Code Auswählen

Event statistics for server CB2001203050203045
Average event delay = 0.0591939002529022
========================================
ET Sent by RPC server   Received by FHEM
----------------------------------------
EV              32373              32793

ND                126                126

DD                  0                  0

RD                  0                  0

RA                  0                  0

UD                  0                  0

IN                  0                  0

EX                  0                  0

SL                  1                  1

TO                  0                  0

Event statistics for server CB2010203050203045
Average event delay = 0.0192531293479159
========================================
ET Sent by RPC server   Received by FHEM
----------------------------------------
EV               2411               2637

ND                 88                 88

DD                  0                  0

RD                  0                  0

RA                  0                  0

UD                  0                  0

IN                  0                  0

EX                  0                  0

SL                  1                  1

TO                  0                  0
Nur Text | Text mit Bildern