-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update {Match} regex for Hideki Module #1071
Conversation
- Prüfung ergänzt, welche dmsg gegen den Match eintrag verifiziert
- Match Regex angepasst - Subs als Coderef hinterlegt
- ParseData Test mit Testdaten hinterlegt
- Weitere Testdaten ergänzt
Modul {Match} als Regex und nicht als string scalar speichern.
Codecov Report
@@ Coverage Diff @@
## master #1071 +/- ##
==========================================
+ Coverage 62.18% 63.56% +1.38%
==========================================
Files 126 128 +2
Lines 9340 9363 +23
Branches 1476 1477 +1
==========================================
+ Hits 5808 5952 +144
+ Misses 2431 2280 -151
- Partials 1101 1131 +30
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Warte auf #1065 |
Attributname angepasst
(You can also link to an open issue here, if this describes the current behavior)
Sensors with less data like temperature only, are not matched by the {Match} regex.
As from FHEM Revision @25489 upwards, the .clientArray is no longer used for dispatch if a module is already loaded.
The {Match} regex accepts messages with less data, so the data will also be dispatched after the module has been loaded.
No
The {Match} regex is complied once the module is initalized and not for every check it's used by fhem