ZitatIst das angegebene Reading (im Beispiel "automatic") im Shelly.shellyplug3 nicht vorhanden, wird es vom Modul automatisch mit dem Wert "1" angelegt.
attr Forecast consumer01 SP.LaderHolger type=charger power=200 icon=electric_car_charger mintime=SunPath on=on off=off etotal=energy:Wh pcurr=power:W mode=can auto=automatic
Zitat von: RatisBow am 26 April 2024, 10:14:48Das beantwortet aber nicht mein Problem.
Hier ein einfaches Besipiel, das schon nicht funktioniert!([08:00-21:00|AT])
(set DOIF_Dum1 "Arbeitstag")
DOELSE
(set DOIF_Dum1 "Wochenende")
Das Listing:Internals:
DEF ([08:00-21:00|AT])
(set DOIF_Dum1 "Arbeitstag")
DOELSE
(set DOIF_Dum1 "Wochenende")
FUUID 5dbefce6-f33f-7b43-092f-2810cd773123eff5
MODEL FHEM
NAME DOIF_Dummy
NOTIFYDEV global
NR 380
NTFY_ORDER 50-DOIF_Dummy
STATE cmd_2
TYPE DOIF
VERSION 28546 2024-02-23 20:11:05
eventCount 6
READINGS:
2024-04-26 10:10:49 cmd 2
2024-04-26 10:10:49 cmd_event DOIF_Dummy
2024-04-26 10:10:49 cmd_nr 2
2024-04-26 10:10:37 mode enabled
2024-04-26 10:10:49 state cmd_2
2024-04-26 10:10:37 timer_01_c01 27.04.2024 08:00:00|AT
2024-04-26 10:10:37 timer_02_c01 26.04.2024 21:00:00|AT
Regex:
accu:
bar:
barAvg:
collect:
attr:
cmdState:
wait:
waitdel:
condition:
0 ::DOIF_time($hash,0,1,$wday,$hms,"AT")
days:
0 AT
1 AT
do:
0:
0 set DOIF_Dum1 "Arbeitstag"
1:
0 set DOIF_Dum1 "Wochenende"
helper:
NOTIFYDEV global
globalinit 1
last_timer 2
sleeptimer -1
timerdev
timerevent
timerevents
timereventsState
triggerDev
DOIF_eventa:
cmd_nr: 2
cmd: 2
cmd_event: DOIF_Dummy
cmd_2
DOIF_eventas:
cmd_nr: 2
cmd: 2
cmd_event: DOIF_Dummy
state: cmd_2
interval:
0 -1
1 0
intervalfunc:
localtime:
0 1714197600
1 1714158000
realtime:
0 08:00:00
1 21:00:00
time:
0 08:00:00
1 21:00:00
timeCond:
0 0
1 0
timer:
0 0
1 0
timers:
0 0 1
triggertime:
1714158000:
localtime 1714158000
hash:
1714197600:
localtime 1714197600
hash:
uiState:
uiTable:
Attributes:
room Testraum
Das sollte doch heute als Arbeitstag funktionieren!
RatisBow
Zitat von: Allgaeuer am 28 April 2024, 19:24:43use Time::Piece verwende ich bei ein paar selbst erstellten Modulen. Soll ich diese Einträge löschen / auskommentieren?
Zitatdefmod MQTT2_CLIENT_general_bridge MQTT2_DEVICE f2f
attr MQTT2_CLIENT_general_bridge autocreate 1
attr MQTT2_CLIENT_general_bridge bridgeRegexp (tele|stat|shellies|valetudo|Advantech)/([^/]+)/.*:.* "$2"\
(shellyp(lus|ro4pm)[^/:_]{4,}+)/.*:.* "$1"\
zigbee2mqtt/bridge/.*:.* "zigbee2mqtt"\
sonos/connected.* "sonos"\
tvheadend/[^/:]+.* "tvheadend"\
milight/LWT:.* "milight"\
(ESPClient_[^/]+)/.*:.* "$1"\
(ebusd[^/]*)/global/.*:.* "$1"\
[^/]+/(ems-esp[^/]+)/start:.* "$1"\
(mygateway[\d]+)-(in|out)/.* "$1"\
(wallpanel|wled|instar)/([^/]+)/.*:.* "$1_$2"\
(nuki)/[^/]+/.* "$1"\
go-eCharger/([^/]+)/.*:.* "go_eCharger_$1"\
owntracks/[^/]+/([^/:]+).* "owntracks_$1"\
home/(O[^/]*M[^/]*G[^/]*)/LWT:.* "$1"\
homeassistant/.*/config:.* ""\
tasmota/discovery/[^/:]+/(config|sensors):.* ""\
mqttGenericBridge/([^/]+)/.*:.* "$1"\
mqttGenericBridge/set/.*/.*:.* ""
attr MQTT2_CLIENT_general_bridge comment Do not use very open bridgeRegexp expressions! This might lead to irritating results... Especially make sure to not have two regexpes that may both match!
attr MQTT2_CLIENT_general_bridge icon mqtt_bridge_2
attr MQTT2_CLIENT_general_bridge model MQTT2_CLIENT_general_bridge
attr MQTT2_CLIENT_general_bridge room MQTT2_DEVICE
attr MQTT2_CLIENT_general_bridge setList clear_all:noArg {fhem("deleteattr $NAME readingList;; deletereading -q $NAME (?!associatedWith|IODev).*");;return undef}
attr MQTT2_CLIENT_general_bridge setStateList on off
mqttGenericBridge/d/alexaName:.* alexaName
in MQTT2_d automatisch ergänzt wird. So entsteht das "Attribut-Reading".19:18:50.848 RCVD mqttGenericBridge/d/state on
19:19:06.512 RCVD mqttGenericBridge/d/state off
19:19:44.116 RCVD mqttGenericBridge/d/alexaName \0 #kommt wenn man im entfernten System alexaName löscht
19:19:55.898 RCVD mqttGenericBridge/d/alexaName sonne #aleaName ergänzt
{"Air_Quality_Analytic":{"noModel":1},"CUL":{"noModel":1},"CUL_HM":{"CCU-FHEM":1,"HM-CC-RT-DN":3,"HM-ES-PMSW1-PL":2,"HM-MOD-RE-8":1},"DOIF":{"FHEM":9},"DWD_OpenData":{"noModel":1},"EnOcean":{"TF":1,"noModel":4},"Energy_Forecast":{"noModel":1},"Energy_Forecast_Analytic":{"noModel":1},"FHEMWEB":{"noModel":1},"FileLog":{"noModel":5},"HMCCU":{"noModel":1},"HMCCUDEV":{"noModel":2},"HMCCURPCPROC":{"noModel":1},"I2C_BME680":{"noModel":1},"JeeLink":{"LaCrosseITPlusReader.10.1h":1},"LaCrosse":{"noModel":3},"Landroid_DWD":{"noModel":1},"MQTT2_CLIENT":{"noModel":2},"MQTT2_DEVICE":{"noModel":2,"worx_landroid_mover":1},"ModbusRegister":{"noModel":76},"ModbusTCPServer":{"noModel":3},"OWTHERM":{"DS18B20":20},"OWX":{"noModel":1},"RPII2C":{"noModel":1},"SVG":{"noModel":2},"SYSSTAT":{"noModel":1},"TCM":{"ESP3":1},"at":{"noModel":15},"autocreate":{"noModel":1},"average":{"noModel":12},"dummy":{"noModel":10},"eventTypes":{"noModel":1},"logProxy":{"noModel":1},"notify":{"noModel":9},"statistics":{"noModel":42},"system":{"configType":"configFile","os":"linux","perl":"5.28.1","revision":"28499","uniqueID":"fab..."},"telnet":{"noModel":1}}
Zitat von: fabian_niesen am 21 April 2024, 19:54:12Was ich suche, ist ein ReadingList das mir immer das "label" als Namen des Reading mit "state" als Wert ausgibt.
attr <deviceName> readingList multi(jsonPath('$.[*]'),property('label'), property('state'))
Zitat von: fabian_niesen am 21 April 2024, 19:54:12Bonus wäre wenn über das Feld "stateDescription.pattern" die Einheit bereinigt werden könnte.