Feedback pyhomematic + EQ3 eco switch

Configuration
1

Hi all,
Hi @danielperna84,

First of: great job with pyhomematic! It works really good!

I configured the homematic component to connect to homegear on localhost on my rpi.

I paired some heating valves and an EQ3 eco switch (BC-PB-2-WM) to homegear which works well now.

In the HASS automation trigger, I had to do two things, differing from the homematic documentation:

  1. The switches device name (no name resolving) had to be in upper case! That’s not especially noted in the documentation. This is a bit confusing, because for the valves, lower case works fine.

  2. The event is “PRESS”, not “PRESS_SHORT”. I tried PRESS_SHORT with no success. Here is the homegear log:
    12/12/17 18:07:17.748 MAX packet received (My-MAX-CUL, RSSI: 0x2B): 0C0902500A2F5FFD3DBC001001 12/12/17 18:07:17.749 Module MAX: Info: PRESS on channel 2 of peer 1 with serial number KEQ0687158 was set to 0x10. 12/12/17 18:07:17.787 Module MAX: CUL "My-MAX-CUL": Info: Sending (My-MAX-CUL, WOR: no): 0B090202FD3DBC0A2F5F0000

Can you please verify these issues?

Best regards

2

Hi,

thanks for the kind words. :slight_smile:

Regarding your issues:

  1. In the documentation it says: The name depends on if you chose to resolve names or not. If not, it will be the device ID (e.g. LEQ1234657). This example is upper case. :wink:
  2. As the documentation says: Be aware, that there are devices which don’t provide all of these events. But in general: if you can press it, it usually at least has PRESS_SHORT. Where usually leaves room for things being different. There are devices that use just PRESS as the event. But that’s rather rare. Most (wireless) devices do have PRESS_SHORT. There is no “one fits all” documentation, and with HomeMatic IP eq3 will probably sooner or later even add more variants. When working with events, it’s best to monitor the log and just take exactly that data. :slight_smile:
3

OK, thanks for the clarification!