unverständniss ignoreregex

Begonnen von brain666, 19 Mai 2022, 15:02:10

Vorheriges Thema - Nächstes Thema

brain666

servus zusammen,

ich steige nicht wirklich durch wie ich diese state meldungen und discovery meldungen ignorieren kann :(

könnte evtl. mir jemand was dazu erklären ?


ignoreRegexp     fhem/(?!set/)|milight/0x[0-9a-fA-F]{1,4}/.*/[0-8]|shellies/[^/]+/command|cmnd/[^/]+/|homeassistant/.*/config



DVES_F3F9BC

tele/tasmota_006588/STATE

{"Time":"2022-05-19T13:56:48","Uptime":"8T20:29:41","UptimeSec":764981,"Heap":31,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":85,"POWER1":"off","Wifi":{"AP":1,"SSId":"EM WLAN","BSSId":"CC:CE:1E:D2:8D:D3","Channel":1,"RSSI":48,"Signal":-76,"LinkCount":242,"Downtime":"0T00:56:47"}}
DVES_F3F9BC

tele/tasmota_006588/SENSOR

{"Time":"2022-05-19T13:56:48","ENERGY":{"TotalStartTime":"2022-03-18T09:07:55","Total":6.120,"Yesterday":0.000,"Today":0.000,"Period":0,"Power":0,"ApparentPower":0,"ReactivePower":0,"Factor":0.00,"Voltage":0,"Current":0.000}}
DVES_B52640

tele/tasmota_em_wz/STATE

{"Time":"2022-05-19T13:56:49","Uptime":"23T08:09:16","UptimeSec":2016556,"Heap":30,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":213,"POWER1":"off","Wifi":{"AP":1,"SSId":"EM WLAN","BSSId":"CC:CE:1E:D2:8D:D3","Channel":1,"RSSI":100,"Signal":-48,"LinkCount":522,"Downtime":"0T02:01:05"}}
DVES_B52640

tele/tasmota_em_wz/SENSOR

{"Time":"2022-05-19T13:56:49","ENERGY":{"TotalStartTime":"2022-03-15T00:00:00","Total":13.386,"Yesterday":0.000,"Today":0.000,"Period":0,"Power":0,"ApparentPower":0,"ReactivePower":0,"Factor":0.00,"Voltage":0,"Current":0.000}}
DVES_519BB5

tele/tasmota/STATE

{"Time":"2022-05-19T13:56:50","Uptime":"44T22:21:01","UptimeSec":3882061,"Heap":30,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":101,"POWER1":"on","Wifi":{"AP":1,"SSId":"EM WLAN","BSSId":"E0:28:6D:95:7F:8C","Channel":1,"RSSI":68,"Signal":-66,"LinkCount":7,"Downtime":"0T00:00:24"}}
DVES_519BB5

tele/tasmota/SENSOR

{"Time":"2022-05-19T13:56:50","ENERGY":{"TotalStartTime":"2022-03-21T21:17:03","Total":22.952,"Yesterday":0.213,"Today":0.084,"Period":0,"Power":12,"ApparentPower":25,"ReactivePower":22,"Factor":0.49,"Voltage":249,"Current":0.101}}
DVES_F443FD

tele/tasmota_F443FD/STATE

{"Time":"2022-05-19T13:56:50","Uptime":"60T03:33:05","UptimeSec":5196785,"Heap":27,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":252,"POWER1":"off","Wifi":{"AP":1,"SSId":"EM WLAN","BSSId":"CC:CE:1E:D2:8D:D3","Channel":1,"Mode":"11n","RSSI":74,"Signal":-63,"LinkCount":16,"Downtime":"0T00:02:06"}}
DVES_F443FD

tele/tasmota_F443FD/SENSOR

{"Time":"2022-05-19T13:56:50","ENERGY":{"TotalStartTime":"2022-03-18T09:07:24","Total":20.721,"Yesterday":0.000,"Today":0.000,"Period": 0,"Power": 0,"ApparentPower": 0,"ReactivePower": 0,"Factor":0.00,"Voltage": 0,"Current":0.000}}
DVES_8FFB3A

tele/tasmota_8FFB3A/STATE

{"Time":"2022-05-19T13:56:56","Uptime":"22T23:18:14","UptimeSec":1984694,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":72,"POWER1":"off","Wifi":{"AP":1,"SSId":"EM WLAN","BSSId":"E0:28:6D:95:7F:8C","Channel":1,"Mode":"11n","RSSI":92,"Signal":-54,"LinkCount":7,"Downtime":"0T00:00:55"}}
DVES_8FFB3A

tele/tasmota_8FFB3A/SENSOR

{"Time":"2022-05-19T13:56:56","ENERGY":{"TotalStartTime":"2022-04-03T13:10:03","Total":71.496,"Yesterday":0.000,"Today":0.000,"Period": 0,"Power": 0,"ApparentPower": 0,"ReactivePower": 0,"Factor":0.00,"Voltage": 0,"Current":0.000}}
DVES_99048E

tele/tasmota_99048E/STATE

{"Time":"2022-05-19T13:56:55","Uptime":"6T10:07:30","UptimeSec":554850,"Heap":28,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":183,"POWER1":"off","Wifi":{"AP":1,"SSId":"EM WLAN","BSSId":"E0:28:6D:95:7F:8C","Channel":1,"Mode":"11n","RSSI":40,"Signal":-80,"LinkCount":24,"Downtime":"0T00:58:27"}}
DVES_99048E

tele/tasmota_99048E/SENSOR

Beta-User

Ich verstehe die Frage nicht so richtig...

ignoreRegexp am MQTT2_(SERVER|CLIENT) ist dazu da, bestimmte Messages nicht in FHEM weiter zu verarbeiten, sondern direkt zu ignorieren. Das was du gezeigt hast, entspricht zum großen Teil einem von mir empfolenen Standard, der wohl zu einem MQTT2_CLIENT gehört und
- zum einen bestimmte Messages rausfiltert, die als Infos an jemanden anderes (verm. von einer MQTT_GENERIC_BRIDGE) an einen externen MQTT-Server gesendet werden (fhem/(?!set/);
- rausfischen, was als Befehl an einen milight-Hub ("Sidoh-Bridge") geht
- HomeAssistant-Auto-discovery-Meldungen verwirft (sowas sendet ein Haufen Geräte, eigentlich sollte neuerdings auch die tastmota-discovery noch dazu)
- und eben Kommando-Topics für Tasmota und Shelly.

Was das mit den gezeigten STATE und SENSOR-Topics zu tun hat, verstehe ich nicht so ganz, das sind Nutzdaten, die man potentiell haben will. Wenn nicht, kann man die ignoreRegexp entsprechend ergänzen.

Server: HP-elitedesk@Debian 12, aktuelles FHEM@ConfigDB | CUL_HM (VCCU) | MQTT2: MiLight@ESP-GW, BT@OpenMQTTGw | MySensors: seriell, v.a. 2.3.1@RS485 | ZWave | ZigBee@deCONZ | SIGNALduino | MapleCUN | RHASSPY
svn: u.a MySensors, Weekday-&RandomTimer, Twilight,  div. attrTemplate-files

brain666

Danke

ich möchte direkt an meinen mqtt2 server
folgendes filtern

DVES_994CED:tasmota/discovery/A4E57C994CED/config:.*
DVES_994CED:tasmota/discovery/A4E57C994CED/sensors:.*
FHEM:homeassistant/sensor/4db094de-a292-415d-a224-7a910a30faf5/54e019a977f5_wireless/config:.*

ich denke es müsste dann so sein


ignoreRegexp    .*:./discovery/.*/.*|FHEM:homeassistant/.*/.*/.*


Beta-User

Zitat von: brain666 am 20 Mai 2022, 09:06:15
ich möchte direkt an meinen mqtt2 server
folgendes filtern

DVES_994CED:tasmota/discovery/A4E57C994CED/config:.*
DVES_994CED:tasmota/discovery/A4E57C994CED/sensors:.*   
FHEM:homeassistant/sensor/4db094de-a292-415d-a224-7a910a30faf5/54e019a977f5_wireless/config:.*

:) Guter Plan!

Meine ignoreRegexp sieht grade so aus:milight/0x[0-9a-fA-F]{1,4}/.*/[0-8]|shellies/[^/]+/command|cmnd/[^/]+/|homeassistant/.*/config|tasmota/discovery/

Prinzipiell wird vorne und hinten automatisch ".*" ergänzt, so dass es ausreicht, den passenden "Zwischenschnipsel" reinzunehmen. Aber sinnvollerweise nimmt man das, was einen stört, zusätzlich zu den "allgemeinen Standards" dazu ;) (der milight-Teil kann raus, wenn man das nicht hat).
Server: HP-elitedesk@Debian 12, aktuelles FHEM@ConfigDB | CUL_HM (VCCU) | MQTT2: MiLight@ESP-GW, BT@OpenMQTTGw | MySensors: seriell, v.a. 2.3.1@RS485 | ZWave | ZigBee@deCONZ | SIGNALduino | MapleCUN | RHASSPY
svn: u.a MySensors, Weekday-&RandomTimer, Twilight,  div. attrTemplate-files

brain666