-
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 SD_Protocols for received Somfy telegrams (remove leading '0') #1112
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1112 +/- ##
==========================================
+ Coverage 67.53% 67.62% +0.09%
==========================================
Files 133 134 +1
Lines 9802 9830 +28
Branches 1570 1570
==========================================
+ Hits 6620 6648 +28
Misses 1887 1887
Partials 1295 1295
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
You have not provided out standard PR template. Can you explain the problem which this fixes in more detail? |
I got two Somfy RCs. |
Do you have some rawdata for all this sitiations? |
No, each RC has different raw data and each button on the RC sends also a different message. |
Here are the raw data from my 2 Somfy RCs. Here are the device settings:
READINGS:
INTERNALS:
|
There was a syntax error which i fixed. But there is a problem within the raw data The bitlengt and the real number of bits do not fit.
|
I just added the two lines code in Sd_protokol.pm and copied just this unit into my FHEM installation. The logs were created in FHEM wirh verbose=5. |
I had no luck to reconstruct your log output. :-( May you can double the Code check, because in your commited version, there was an perl syntax error caused massive malfunction. |
I'm sorry that I created so much trouble with my PR.
to
and added the comments on top of the file (file is attached as SD_Protocols.pm.txt)
I hope this will help. |
I'll try to check this. Thanks for support |
I took the changed code lines you send me:
But there is a syntax error, one bracket is missing in the elsif statement : Did you took this file from your fhem installation? |
I think i found the problem, was not on your side, was on my side :( |
extended tests reworked code slightly
00_SIGNALduino.pm - Frequency changed to 868.3 MHz for all Bresser protocols in documentation. 14_SD_WS.pm - Corrected protocol 115 battery bit, added batChange bit and corrected calculation for negative temperatures. SD_ProtocolData.pm - Changed frequency and register settings for all Bresser protocols to 868.3 MHz.
…ng '0' and add a '0' at the end
fix syntax
extended tests reworked code slightly
(You can also link to an open issue here, if this describes the current behavior)
Some Somfy RTS telegrams are not accepted because they seems invalid
Telegrams are accepted and dispatched
no
CHG: mcBit2SomfyRTS() remove leading '0' in any Somfy telegram if this bit it is not expected