New Add-on for HomeMatic/homematicIP support - Action Required

Merc · March 14, 2022, 9:20pm

Success.
I can find the devices. But they do not get their clear name. I can only find them by their serial number. Is this intended or what would I have to do in order for the clear name to show up?

Thanks,

Merc

danielperna84 · March 14, 2022, 10:19pm

The username and password are relevant for the names to work. I assume 1234 is not your real password. Sadly the integration does not allow fancy passwords. So if yours has any special characters, change it to something with only a-z and 0-9.

Merc · March 14, 2022, 10:29pm

Actually 1234 is the password at the moment. But still the names did not get picked up.

danielperna84 · March 15, 2022, 5:38pm

As many others had similar problems with resolving names, please use the search-function to find further topics that cover that problem. I’m fairly sure you’ll find answers there that will help you. Configuration-support is out of scope for a topic that actually announced changes in a very different part of Home Assistant.

Merc · March 15, 2022, 6:25pm

Understood. Sorry for the off topic question and thanks for the help and of course for the great integration.

Herr.Vorragend · March 20, 2022, 4:17pm

Hello Daniel, I’ve been following your developments for many weeks and I’m already looking forward to a release. You are really busy.
What bothers me about the current integration is that I can’t control devices with “Servicemeldungen” messages" (Plz see Fixing Homematic Servicemeldungen?)

Is that solved differently with your integration?

Your opinion is important for me.

Danke.

danielperna84 · March 20, 2022, 4:42pm

I don’t encounter that problem that often, so I can’t give a reliable answer to your question. I suggest to just give the new integration a try. It’s possible to have it running in parallel. Here are the instructions for installation.

Herr.Vorragend · March 20, 2022, 4:55pm

Thank you, I just did it and installed your integration. I am now waiting for the next HM error message.

Herr.Vorragend · March 20, 2022, 6:00pm

Unfortunately, I was able to test it directly when all my blinds went down.
The behavior is identical. The entities are grayed out.

When I start the device in RaspberryMatic, the messages always disappear. For this reason, I hoped that the devices could simply be triggered again through HA.

I’ve used BidCos-Homematic in FHEM for years and haven’t had any problems. There I used different HM-MOD-UART.

Now I am using just real eq3-Gateways:

Flashed CCU2GW0001 so that i can use it like a HomeMatic RF-LAN Gateway.
Real HomeMatic RF-LAN Gateway

Just as a side note: I already have a delay between all commands to avoid radio collisions.

Sorry for offtopic.

arganto · March 20, 2022, 6:02pm

But how should a integration switch a device, which is not switchable in CCU because of whatever reasons. I have this as well, with my shutters, one here one there sometimes, but then it is not switchable in CCU either.

arganto · March 20, 2022, 6:04pm

Then open an issue in New integration. Perhaps there is a chance of improvements or root cause analysis.

Merc · April 2, 2022, 5:54pm

Hi @danielperna84,
great to see that the new add-on has reached a stable v1 and is now going to be migrated to Home Assistant, at some point.
Do you have an idea at this point how this is going to interact with the existing inbuilt HomeMatic integration?
At this moment I am still running my TRVs with the old integration, although I have your new one installed, but disabled right now.
Would you recommend to leave everything as it is or install your new one and then move all the entities from the “old” one to your new one?

Or will this switch happen at some point when the new one gets fully integrated?

Thanks for the great work!

Cheers,

Merc

danielperna84 · April 2, 2022, 11:58pm

There actually has been some debate on how this should be handled. The process I initially thought of seems not to be practical / acceptable from the perspective of other users. So right now I literally have no idea on what to recommend. You can follow the discussion here: Planung für Integration im HA Core · Discussion #381 · danielperna84/hahomematic · GitHub

Merc · April 3, 2022, 9:26am

Thanks Daniel,
I had a look and I see that this might be turning into quite a big issue for some people. Luckily I am not that far down the route with my TRVs and reconfiguring them and some templates will be pretty straight forward.

I have one additional comment and observation.

After installing your new HACS addon again (and previously deleting everything in the custom folder) I managed to install the integration and connect it to RaspberryMatic. However it did not show any entities so I thought that I had done something wrong again. I checked my configuration.yaml, all the firewall settings, everything I could think of that might have an impact and could not find any mistakes. So I decided to just let it sit since everything is still working with the core-based HomeMatic integration. After maybe 5 to 10 minutes suddenly the entities appeared with their clear names. Maybe it would be good to mention somewhere that this can take some considerable time, or is there a method to trigger this a bit quicker. It can be pretty misleading I found.

And one more question: I think, when I had used the climate cards in Lovelace before, based on the HAHM addon, I could see 3 buttons for the presets. In the old HM integration they are not visible and it seems that in the new HMIP integration they are not there either. Is this correct?

Thanks again and regards,
Merc

danielperna84 · April 3, 2022, 3:42pm

That’s not unusual. Normally you could have just reloaded the Integration via UI. That should have triggered the Init-Process immediately.
What you install now as a custom component (it’s not an add-on) is the same as what was previously using the domain hahm. We just renamed it from hahm to homematicip_local. Besides from minor issues that have been fixed meanwhile nothing has changed.

Merc · April 3, 2022, 7:42pm

Sorry for the addon confusion… I know it is not an addon per se.
Strange that the button configuration changed though…

EDIT: ok. Button issue solved as well. The presets become visible once switching to AUTO. This is not happening in the old integration.

EDIT 2: Don’t know if you have experienced that but switching from MANUAL to AUTO mode (in Lovelace) regularly leads to a connection drop and the TRV becoming unavailable.

arganto · April 4, 2022, 5:17pm

Can you open corresponding issues here?

Merc · April 4, 2022, 8:21pm

Done

Cheers,
Merc

bobic · April 14, 2022, 1:53pm

Hi, thanks for this great add-on.

That addon made me to transfer my old FHEM instance to HA.

Now i am struggeling since a few days with my 6-Button Homatic device.
But first some info on my setup.
I have a rasperrymatic with the RPI-RF-MOD installed.
On a other raspberry is HA running with the custom homematic integration.
All devices are created via auto create in HA.

My problem is, that i cannot use the “long_press” button as continuously pressed in order to dimm up or dimm down, or change the volume of my speakers.

I tried to create a programm in my raspberrymatic for the device, but this didn’t help.
I tried to change the min duration for “long press”, didn’t help.

I figured out, while using the listening function on homematic.keypress that the no events arrive if is press the button. The “long_press” and the “press_long_release” arrive at the time, doesn’t matter how long i press the button. I assumed a “long_press” event every seconds to arrive until I release the button.

Here are the two events which arrive:

Event 1 fired 3:49 PM:
{
    "event_type": "homematic.keypress",
    "data": {
        "interface_id": "RaspberryMatic-BidCos-RF",
        "address": "PEQ1590823",
        "type": "press_long_release",
        "subtype": 2,
        "device_id": "254415a1ed493ef48c86f4ed99dd6796"
    },
    "origin": "LOCAL",
    "time_fired": "2022-04-14T13:49:20.940049+00:00",
    "context": {
        "id": "8e8637beebf0a129db4d1b5ab5971e89",
        "parent_id": null,
        "user_id": null
    }
}
Event 0 fired 3:49 PM:
{
    "event_type": "homematic.keypress",
    "data": {
        "interface_id": "RaspberryMatic-BidCos-RF",
        "address": "PEQ1590823",
        "type": "press_long",
        "subtype": 2,
        "device_id": "254415a1ed493ef48c86f4ed99dd6796"
    },
    "origin": "LOCAL",
    "time_fired": "2022-04-14T13:49:20.939567+00:00",
    "context": {
        "id": "5d433dce586f8fc09d2101c76ed1b6a1",
        "parent_id": null,
        "user_id": null
    }
}

I hope someone can help me I need this function, took me a long time to teach my girlfriend how to use the buttons.

Thanks Lukas

bobic · April 14, 2022, 2:05pm

i found my solution. i had to change the communication from secure to standard in my raspberrymatic instance.

Is there a way to adapt the blueprint for 6 button for “continuously pressed”?

alias: SW55_2Press
description: ''
trigger:
  - platform: device
    domain: homematicip_local
    device_id: deviceid
    event_type: homematic.keypress
    interface_id: RaspberryMatic-BidCos-RF
    address: address
    type: press_cont
    subtype: 2
condition: []
action:
  - device_id: deviceid
    domain: light
    entity_id: light.badezimmer
    type: brightness_increase
mode: single

Br, Lukas