I am using several homematic devices (thermostats, window contacts, …) which are connected to a homegear server.
All device are correctly recognized by home-assistant except the HM-PBI-4-FM and the HM-SECI-3-FM.
I cannot see them in the entities list. Am i doing something wrong?
Let me know if you have the same issue or know how get them recognized by home-assistant.
Hi,
the HM-SCI-3-FM is currently not implemented. Have a look at https://github.com/danielperna84/pyhomematic/issues/28 for devices which still need to be implemented. Feel free to contribute.
It is correct, that the HM-PBi-4-FM does not show up as an entity. Consider the device “stateless”, which is why no entity is created for it. Instead those devices only create events within Home Assistant. Please read the documentation for Homematic at https://home-assistant.io/components/homematic/
There’s the section “Devices with buttons”, which explains all of this.
Hi!
I also have problems with the HM-PBI-4-FM.
I finally understood what the section “Devices with buttons” wants to tell me, and when pressing buttons, it shows up in my hass terminal (can you say that? not too familiar with the correct terms…).
BUT:
It does not show the nice name that you can set on the CCU2-interface and I am not able to use the event as a trigger for automations.
As a comparison: I also have the HM-MOD-EM-8, and when pressing a button, the hass terminal gives three messages; the last one with:
Bus:Handling <Event homematic.keypress[L]: channel = 5, param=PRESS_SHORT, name=my_nice_name>
I can use my_nice_name and the PRESS_SHORT as well as the channel number to trigger automations without problems.
When pressing a button from HM-PBI-4-FM, the hass terminal does not show this message with “Bus:Handling”.
However, I do get the other two messages; this means, that in general the device works (somehow) and events do occur.
I am also not able to use the button event to trigger automations or sth. (which is the actual problem I have 
)
Does anyone else have this issue?
Is it a problem of homeassistant or rather one with my CCU2? In any case, do you have any idea on how to solve the matter?
As a side note: the battery is low on my HM-PBI-4-FM; might that in any way cause the issue? (I guess not, but who knows)
The low battery shouldn’t be the issue here. You get something in the logs, so the signal is processed. No problem for that matter.
The log message you have posted is exactly the one you need for your automations. I don’t know though why they are missing in your case. Could you please post the other two related messages you see in the log?
In general it doesn’t make sense that it’s not working, because a lot of working devices use exactly the same code. The only differency is that some devices have more channels than others. Another difference may be, that the HM-PBI-4-FM is not using PRESS_SHORT but some other form of the event. In that case the way it is implemented in pyhomematic would actually be wrong. But that shouldn’t be the case, because the device documentation which was used to implement this clearly says it’s PRESS_SHORT.
Hi,
thanks for your quick reponse, and sorry for my late one, busy evening yesterday
Anyways, the other two messages are:
2018-01-27 11:47:25 INFO (Thread-12) [pyhomematic.devicetypes.generic] HMGeneric.event: address=KEQ0184716:0, interface_id=homeassistant-CCU2, key=LOWBAT, value=True
2018-01-27 11:47:25 INFO (Thread-12) [pyhomematic.devicetypes.generic] HMGeneric.event: address=KEQ0184716:1, interface_id=homeassistant-CCU2, key=INSTALL_TEST, value=True
For comparison, all the messages when pressing a button from HM-MOD-EM-8:
2018-01-27 11:51:32 INFO (Thread-12) [pyhomematic.devicetypes.generic] HMGeneric.event: address=MEQ0046686:6, interface_id=homeassistant-CCU2, key=PRESS_SHORT, value=True
2018-01-27 11:51:32 INFO (MainThread) [homeassistant.core] Bus:Handling <Event homematic.keypress[L]: param=PRESS_SHORT, name=my_nice_name, channel=6>
2018-01-27 11:51:32 INFO (Thread-12) [pyhomematic.devicetypes.generic] HMGeneric.event: address=MEQ0046686:6, interface_id=homeassistant-CCU2, key=INSTALL_TEST, value=True
Looking at it, it actually seems to me that the low battery might indeed be the issue, as it says key=LOWBAT instead of key=PRESS_SHORT, thus maybe not triggering the system to handle the event as a pressed button.
I will get new batteries and try, just to make sure.
EDIT: found batteries at home; the new batteries only have the effect, that the first message (with key=LOWBAT) does not show up anymore.
Additional note:
in CCU2-GUI you can “imitate” pressing buttons. When doing this, it works just fine within Homeassistant.
The following messages appear in the hass terminal:
2018-01-27 12:06:06 INFO (Thread-12) [pyhomematic.devicetypes.generic] HMGeneric.event: address=KEQ0184716:2, interface_id=homeassistant-CCU2, key=PRESS_SHORT, value=True
2018-01-27 12:06:06 INFO (MainThread) [homeassistant.core] Bus:Handling <Event homematic.keypress[L]: name=my_nice_name2, param=PRESS_SHORT, channel=2>
Do you have any further ideas?
Best regards,
Christoph
Usually the LOWBAT event is sent additionally to the regular event. I haven’t seen any devices yet that stop reporting the initial event and just telling about the low battery. But since I don’t have every device it might be the case that your device behaves that way. Especially now that you are saying it is working when you fire the event via the UI, which indicates, that it’s generally working. So yes, please replace the batteries and check again.
Hi,
obviously my edit hasn’t made it to you before your response
“found batteries at home; the new batteries only have the effect, that the first message (with key=LOWBAT) does not show up anymore.”
I also posted the messages in hass terminal when pressing the button within CCU2-webinterface
2018-01-27 12:06:06 INFO (Thread-12) [pyhomematic.devicetypes.generic] HMGeneric.event: address=KEQ0184716:2, interface_id=homeassistant-CCU2, key=PRESS_SHORT, value=True
2018-01-27 12:06:06 INFO (MainThread) [homeassistant.core] Bus:Handling <Event homematic.keypress[L]: name=my_nice_name2, param=PRESS_SHORT, channel=2>
This is exactly as I would expect when pressing the “real” button.
If you have any further ideas, please let me know.
I will, of course, also look further into this matter myself. At the moment I think that I somehow set up the HM-PBI-4-FM in the CCU2 in a wrong way, somehow, for some weird reason.
I found the “problem”.
In the CCU2, the communication mode was set to secure
(Übertragungsmodus: gesichert)
I changed it to standard, and bam, it works.
Not sure though, if it is really meant to be that way - that you don’t get the proper signals when communication mode is secure. Maybe you might want to change that?
(for windows sensors the secure communication also works, and also for HM-RC-Sec4-2)
Anyways, many thanks for your help, and even more thanks that you and the other guys implemented all the stuff from homematic!
Happy regards
Great you found the solution. Now that you mention it I think I’ve heard that before, but forgot about it because I didn’t need that for myself. I guess that should be part of the documentation. If you want you could add a paragraph about that and how to change the settings. Thinking about it, it actually makes sense. Secured communication kind of implies, that such events should not be leaked or spoofed. Hence the CCU only provides basic data.
I wrote some lines for the documentation and created a pull request.
Hope it meets the standards
1 Like
Since yesterday I am playing the first time with Home Assistant (linked with a Homematic CCU2). But I also have problems connecting a Remote HM-RC-Sec4-3 with hassio. There is the XML-API installed on the CCU2. The config for homematic is:
homematic:
hosts:
ccu2:
host: 192.168.2.100
interfaces:
wireless:
host: 192.168.2.100
resolvenames: xml
With this config ALL other devices were found (with resolved names). I also tried to disable the secure transmission-mode (Übertragungsmodus) of the device, but without luck. I checked the device type and according to the Github-repo it is supported.
Like I said, I’m very new to Home Assistant. Can somebody help?
This type of device does generally not show up in the UI. Have a look at this section of the documentation.
Edit: You may have to change the log level of Home Assistant to be able to see those messages.
1 Like
Ohhh RTFM… and read it CAREFULLY! I went over this section without care obviously. Many thanks for the fast response. I found an answer of you in another topic, how to enable the debugging. Thank you once again.
Okay… now I found the events in the log:
2018-11-25 19:34:11 INFO (Thread-2) [pyhomematic.devicetypes.generic] HMGeneric.event: address=NEQ0391177:2, interface_id=homeassistant-wireless, key=PRESS_SHORT, value=True
2018-11-25 19:34:11 DEBUG (Thread-2) [homeassistant.components.homematic] Event PRESS_SHORT for Handsender Axel channel 2
But how can I use that now, e. g. in the automation? As far as I unterstood till now I need an entity (which this device in fact does not have).