Installation completely fails

Support und Bugs Hörmann BiSecur
1

Adding a Hörmann VersaMatic P Gate door worked without any issues.

I could successfully program all codes in.

However, programming in a Hörmann SupraMatic E3 failed.

It’s state is singular: Opening, and persistent.

No other states are reported.

Malfunction Alarm says a lot (cynically): Malfunction!

However, the icon and the actions do actually a) show the correct door configuration (shows a picture being open or being closed, and a the right times), and the buttons do send a pulse also. It seems the programming cannot determine and just throws a Malfunction!. Since I am not allowed further diagnosis on the OS, I cannot diagnose the issue further.

That is one problem.

The 2nd problem is that Apple HomeKit integration does not work: de bridge can be seen and added. This adds 1 out of two devices, and is displayed as a window blind that can open and close. However, opening the blind does not change either state of Garage Door or Gate Door. Also, since the name and the icon are completely not related to the Garage Door or Gate, I cannot tell which device might have been attempted to add.

The 3rd problem is that Matter support does not work. When I try to enable it, a little circle just keeps turning. I waited a long time (like 30 minutes at least, but after a refresh it was clear nothing had been done.

So, Hörmann SupraMatic E3 is not working, HomeBridge is not working and Matter support is not working.

This little cube cost me 300 euro, so I would really appreciate an answer.

As a unix engineer, I am very much ready to assist further in any queries you may have. Also, feel free to access my cube remotely (at the condition I can do the same).

However, I have so ssh access, so I cannot diagnose much further.

Thank you for your patience, and if you read all the way to here: I’m very honored.

Sincerely,

Diederik CABRI

dcabri@gmail.com

2

Core Version: 2.40.2 (268ae103)
Web App Version: 2.40.1 (34403884)

„Send a message to support“ fails with a simple „could not send message“

Internet connected.
Remote access: connected
No Homeegrams, Plans or Scenario’s
No Groups.

3

@Steffen @Hoermann_KG_AST your turn.

2 „Gefällt mir“
4

In case you don’t get answer here next few days - write to
smarthome@hoermann.de

2 „Gefällt mir“
5

Meanwhile, I have done some troubleshooting at home, and at my neighbor’s.
Findings:

  • /etc/resolv.conf is having as default 127.0.0.1 for DNS resolving. That, obviously fails, but the logs are complaining and using the „good one“ anyway.
  • Doorways (both Gate and Garage) work well at my neighbor’s.
  • Only Garage doorway does not work for me:
    • goes always into alarm
    • I noticed some anomalies (I think) through the API :
      „id“: 46,
      „type“: 304, # CAAttributeTypeImpulse
      „state“: 3, # CANodeStateUpdateInProgress
      „id“: 50,
      „minimum“: 0,
      „maximum“: 4,
      „current_value“: 3.0,
      „type“: 135, # CAAttributeTypeUpDown
      „state“: 1, # CANodeStateAvailable
      „id“: 51,
      „current_value“: 1.0,
      „type“: 70, # CAAttributeTypeMalfunctionAlarm
      (I added the field descriptions)
  • My Garage door always goes into alarm, even when sending a simple pulse for „light“

So, I am inclined to think this has to do with the „weight“ the engine puts on the garage door.
You see: when you hold a garage door from closing, it displays an error - great!
When I don’t do that, the garage door still goes into error. I though this is reasonable deduction of mine, that maybe the engine would like the door to be „even closerder“ :wink:

Hoever, I am still wondering why the status stays „Opening“ (and never changes, whatever the door does, opening or closing), but the image and % statuses are updated correctly.
I also don’t understand what is keeping it in ‚Opening‘, when everywhere else one can see the status being updated. I should expect that after a few times going between 0 and 100%, open and closed, that status would eventually update also - but no.

The Apple Home app integration fails big time. But at least I gotten the API working (that was not easy), and the device is now connected to my HomeBridge system via this API. So, my server runs the HomeBridge doorways, and it receives and sends commands through the API that exists on the Homee Brain Cube.

A good enough solution for me (as my HomeBridge does not go into any alarm because there really is none - except maybe that the door „unexpectedly stopped“ when it could close no further. okay.

It was a difficult 72 hours, but now a working solution exists, yeey :wink:

Sincerely,

Diederik