-
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
new protocol TCM 218943 #696
Conversation
Definition protocol for weather station TCM 218943 replaces protocol 6 (Eurochron was under development). Protocol 6 removed from file 90_SIGNALduino_un.pm. Evaluation protocol 15 removed from file 90_SIGNALduino_un.pm. Protocol 15 has been processed for some time in module SD_BELL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Als nächstes bitte hier https://github.com/RFD-FHEM/SIGNALduino_TOOL/blob/pre-release/FHEM/lib/SD_Device_ProtocolList.json noch ergänzen :-)
Ich weiß nicht, ob das schon sinnvoll ist. |
Doch kann man machen. Der Test gegen pre-release läuft ohne einen Fehler zu produzieren und RMSG/DMSG ist vom TCM Modul unabhängig. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Warten auf Erweiterung der JSON Datei
Was soll ich dann dort für Werte eintragen?
|
Ich hattw an dmsg Wert und die Anzahl an wiederholen gedacht |
DMSG ist klar, die Anzahl der Wiederholungen nicht. |
Dann ist der Wert 1 vermutlich der richtige |
Aus meiner Sicht passt das Ergebnis :
|
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature
What is the current behavior? (You can also link to an open issue here)
no evaluation, see new Sensor TCM218943 #692
What is the new behavior (if this is a feature change)?
new protocol for weather station TCM 218943 replaces protocol 6 (Eurochron was under development)
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
no
Other information: