-
Notifications
You must be signed in to change notification settings - Fork 1
add support for 'eco' switch and window sensor #2
Comments
Thanks! Sorry for keeping you waiting. Unfortunately I don't know to which existing messages the echo switch corresponds, but I added handling of shutter contact messages. Can you maybe try the |
using this here's the log of
and for the window sensor:
|
Thank you very much! I fixed the errors, can you please try again? Some of them where unnecessary mistakes, I'll start linting my files. |
sure, for the 'eco switch':
do you need log of the shutter for now, too? |
@maufl spring time is ahead... 🌸 |
Sorry, I was quite busy. Also I think the parsing of the status bits was wrong. I took a look at the FHEM code and tried to understand Perl, I think the parsing should be correct now. Could you try again with the latest code? Meanwhile I will continue implementing the switch component in Home Assistant. |
sure! same procedure as before:
i was using https://github.com/fbeek/pimatic-maxcul before - personally, i can read |
This is strange, I don't know what |
hmm, i'm using this particular firmware because it does ignore the crediting. has been working fine with new try:
|
I fixed the error with the logging string. But I still don't understand why the ACKs are not accepted. Do you know how pimatic-maxcul did ACK the PushButtonStateMessages? |
@maufl unfortunately not and i also lost all the logs.. i suggest marking the shutter support as experimental. guess i could test "better" when some integration with new try:
looks good to me, except that one |
I'm not satisfied that the ACK message seems not to be accepted by the push button. Do you think you could record messages exchanged between pymatic-maxcul and your push button (and shutter)? |
@maufl uh i was actually refering to the 'eco switch' but typed 'shutter' instead. sorry. |
Ah, I just assumed that you meant eco switch anyway. The shutter contact is supported by my home assistant fork now, at least if there are no grave bugs. I don't know as what kind of component the eco switch / push button should be added. It is also missing from the home assistant maxcube component. |
@maufl that's a good question. guess the switch can't be binary - it has two buttons ( |
@maufl getting back here from home-assistant/core#11454 👍 |
Sorry, I was a bit busy last week. We'll the problem isn't that we are resending many packets, there is already a limit to the number of ACKs I send and an increasing backoff. The problem is that the Eco Switch sends a message, seems to expect an ACK but does not accept our ACK and thus resends it's message two times. Do you think you could test and record the messages exchanged with another implementation like pymatic? |
@maufl i got rid of all the
in |
well, it seems to be even simpler:
but actually the
and keeping |
unfortunately and as you expected the
|
Hm, I took a look at the code of pimatic, but they don't seem to send ACKs. |
Btw, your budget is much higher than what I have ever seen. |
@maufl the button has a LED which blinks once when pressed, and three times when pressed and not paired. i noticed that besides the 'paired' messages in the log the LED has always been blinking three times for now. |
Well, looking at pimatic did not help. I compared the decoding of all messages but I found only a difference in decoding the rferror field of PushButtonMessages, and I think this might be their mistake as I compared it again against FHEM. The last idea I have is that maybe the flag field of the ACK must match that of the message to which it responds. I added this feature to the |
@maufl as you asked for at home-assistant/core#11454 (comment) here's the issue 😄
The text was updated successfully, but these errors were encountered: