Need help - Fibaro FGPB101 button & POPP 012501 strike

Configuration Z-Wave
1

Hi all,

I’m having a rough time setting up what I thought would be a simple configuration.
I’m not new to using Linux either, so I thought this would be easier…

I have 2 products:
FIBARO System FGPB101 Button (Aka “The Button”)
Popp 012501 Strike Lock Control (Electric Strike Controller)

My intention was to have a ‘simple automation’ to press/hold the button and have the door buzzer activate. This, however, seems like a lot to ask for. :sweat:

Firstly:
-Running a Raspberry Pi 1, works well. :slight_smile:
-Setup HA using the HASS Image
-Interfacing Z-Wave using Aeotec Z-Stick Gen5
-I have paired both the devices to my Pi
-All are reporting in HA/OZW.

This is where I am having trouble…

The Button:
I am confused as to how to interpret the Fibaro Button commands to an action (And I’m very new to Home Assistant, so please bear with me).

The 4 button entities shows up in HA as:

sensor.fibaro_system_fgpb101_button_alarm_type_2_0
sensor.fibaro_system_fgpb101_button_alarm_level_2_1
sensor.fibaro_system_fgpb101_button_sourcenodeid_2_2
sensor.fibaro_system_fgpb101_button_burglar_2_10

The Fibaro Button reports into OpenZwave when I click it and I get the following in my OZW_Log.txt:

Detail, Node002,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x02, 0x05, 0x5b, 0x03, 0x20, 0x00, 0x01, 0x8e
Info, Node002, Received Central Scene set from node 2: scene id=1 in 0 seconds. Sending event notification.
Warning, Node002, No ValueID created for Scene 1

I can also see the other functions in OZW.

2 clicks:

Detail, Node002,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x02, 0x05, 0x5b, 0x03, 0x21, 0x03, 0x01, 0x8c
Info, Node002, Received Central Scene set from node 2: scene id=1 in 3 seconds. Sending event notification.
Warning, Node002, No ValueID created for Scene 1

3 clicks:

Detail, Node002,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x02, 0x05, 0x5b, 0x03, 0x22, 0x04, 0x01, 0x88
Info, Node002, Received Central Scene set from node 2: scene id=1 in 4 seconds. Sending event notification.
Warning, Node002, No ValueID created for Scene 1

4 clicks (Initiates ‘Wake Up’ mode, so also lots of other ZW noise):

Detail, Node002,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x02, 0x05, 0x5b, 0x03, 0x48, 0x05, 0x01, 0xe3
Info, Node002, Received Central Scene set from node 2: scene id=1 in 5 seconds. Sending event notification.
Warning, Node002, No ValueID created for Scene 1

5 clicks:

Detail, Node002,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x02, 0x05, 0x5b, 0x03, 0x24, 0x06, 0x01, 0x8c
Info, Node002, Received Central Scene set from node 2: scene id=1 in 6 seconds. Sending event notification.
Warning, Node002, No ValueID created for Scene 1

Click & Hold: A whole lot of HEX functions get output.

The Strike Controller
The strike controller shows up and exposes 4 entities to my HA, but I’m also at a loss as how to interface to a strike/buzz action.

The 4 entities show up as:

sensor.popp_012501_strike_lock_control_alarm_type_5_0
sensor.popp_012501_strike_lock_control_alarm_level_5_1
sensor.popp_012501_strike_lock_control_sourcenodeid_5_2
sensor.popp_012501_strike_lock_control_access_control_5_9

I even contacted POPP support, who advised that I am supposed to have an on/off interface with the device, and the manual shows that there are 3 options that can be set (Parameter 0, 1 and 2), which I assume to be the “Alarm Type”, “Alarm Level” and Source Node ID" respectively.
I am quite sure that the “Access Control” (Aka sensor.popp_012501_strike_lock_control_access_control_5_9) is my on/off switch, but it only shows up in HA/OZW as a sensor with value 254. I cannot find any reference of how to translate this to an on/off, or force it.

So, here I am…
I’ve read through Home Assistant documentation for days and cant find how to interface this, the best I’ve been able to do is create groups and show the values of 0 on the front page. :sweat:

I fear that I’ve picked the 2 Z-Wave items that may be the hardest to get working.

I’ve tried to put details here of my setup and configuration, but I can post anything else that would be requested.

Is there anyone that can provide some pointers and/or help?

2

These are what you’re looking for (or based on the last comment in the issue, already found ;)) . Posting for others who stumble across this but haven’t found the open-zwave thread yet.


3

Thanks very much for this link, but I’ve already found this too, and posted in that same issue yesterday. :blush:

I also downloaded the CentralScene.cpp.zip linked into one of the last posts in that same thread.

I tried swapping this one over my existing CentralScene.cpp, and restarted HA, and nothing seemed to work. When looking into the updated file, I can see that they added some logic via additional if statements, to interpret the output.
I would be extremely grateful if someone could help me debug it. :innocent:

I’m hoping to get this working, and record the details here, and hopefully someone else will benefit.

Maybe this could become the thread to workaround this issue. :grin:

4

Eagerly awaiting updates :slight_smile:

5

i’m still trying to get this to work.

very lost.

Does anyone have any advice on how to manipulate the POPP 012501 strike?

6

Hi,

I only used the popp in homeseer, but had issues with zwave pairing needs to bedste secure. Try to unpair and repair where you have the popp right next to the controller. That gave med the correct pairing, and more child objects to the popp.

7

Home Assistant is still resisting to resist show any useful control over the POPP 012501 controller.

So I shut down HA, went to the OZWCP did a secure pairing there.
It appears to have worked as desired, but in HA States, I still only see 4 items:

Pasted image918×257 30.2 KB

I’m stumped, as everything seems to show up fine in OZWCP.
I copied the .xml configs over to the HA directory as required also.

If I close HA, and go back to the OZW CP I see that the device is listed:

Pasted image1434×55 6.81 KB

Current Values are available:

Pasted image720×375 13.2 KB

Configuration Values are also available:

The information is available:

Pasted image641×890 30.3 KB

Am I missing something?

8

Did you solved the problem with the Fibaro Button?

9

Honestly, no, I still have a useless Fibaro button and Popp Strike.

It’s very frustrating, as I monitor the threads here here here (also here) daily for any progress on the root issues, but they seem to persist forever in a state of “almost committed”.

The consensus on various threads seems to be that theis might be released in OpenZWave 1.6, but I have doubts.
So I presume for this to work a few things need to happen:

  • openzwave needs to support Central Scene
  • python-openzwave needs support update?
  • home-assistant needs support update?

Maybe someone can confirm if Central Scene support is already integrated into Home-Assistant, as presumably that also needs to be in the chain for this to work…

You might see my inputs in threads as happy to test being ignored.

And so I wait…

Open Source sucks sometimes.

10

Ok, thanks for your answear and good luck in the future!

11

We need support for COMMAND_CLASS_CENTRAL_SCENE for this to work. Please vote and maybe some of the brilliant developers will look into it. It looks like it requires a rewrite of some core systems: Add support for zwave COMMAND_CLASS_CENTRAL_SCENE

12

Any luck with this? Just bought a Fibaro FGPB-101-1 and now feel like a dummy for not checking here first…!

1 Like
13

Are there any news to this. I have the same issue with HA not showing the on/off switch for the POPP strike lock control.

Since i do not need command_class_scene I’m wondering why there isn’t the on/off switch. If I look at the screenshots shown for OZW CP the switch is there.
I tried to remove and readd the node but without any improvment.

Has anyone had luck with the popp strike control ?

14

I’m sorry to say, but I gave up trying to get this thing to work with HA z-wave, as it has been well over a year of headache.

I’ve since started moving all my z-wave devices to an external VeraPlus controller, which works EXCELLENTLY. I use HA still for all my automations, and the VeraPlus is basically the replacement for my Aeotec stick, as it integrates with HA and exposes all devices transparently.

For the record, both the FGPB101 and Popp012501 both work perfectly with the VeraPlus using this setup, and my z-wave network has never been faster.

If you’re interested in learning more, I have a thread over here. :smile: :+1:

15

Thanks for the reply. I was afraid of that. My goal was to not use a hub since for every system needing a hub you end up having 10 different hubs at the end (I’m exagerating on purpose here)

I have filled an issue on github both on homeassistant and open-zwave repository. Lets see if some cares about this.

2 Likes
16

Same problem here. My popp strike lock is not working because it’s not showing a switch entity. Could you please solve this issue or let us know when may it be solved?? Thanks.

17

I have contacted Popp support and they have told me this:

Blockquote Have you tried to “switch” the device via the DoorLock CC? This class must be supported by the gateway. You can only control the StrikeLock via this CC.

No idea what they are referring to, I guess CC means command class but don’t know how to do this. Any clue??

18

As you can the in the issue that i opened, openzwave does already recognize all the Command Classes for the POPP Strike Lock.

The propblem is that they are not shown in HA. Other Home-Automation solution like OpenHAB or FHEM do not have that problem with the POPP strike control and they are also using open-zwave. It must also be HA or python-openzwave.

https://github.com/home-assistant/home-assistant/issues/11938
Look at my attached zwcfg-file

1 Like
19

I know you’re exaggerating on purpose, and you’re free do do as you will but I think you may be kinda missing the point that what gives HA its strength is its integrations, not its buggy direct control over z-wave devices. I’m able to use HA as a single system (HA) that manages all devices, through their respective hubs/controllers.
HA doesn’t do direct control very well, like manage z-wave. Unfortunately the upstream path is not very good in my opinion: HA->python-open-zwave->open-zwave
HA also uses an older version of PyOZW, and PyOZW relies on upstream improvements from OZW.
What HA does do well is integrations with other systems and hubs that do z-wave better.

You need to go to the developers of HA and PyOZW and OZW to make sure its all in sync, and supported through the chain. I chased this for a year and got involved in pull requests and issues, so at this point I’ve moved on and I’m much happier.
It looks like there is another new issue logged, from the messages here, so thats good.

1 Like
20

Still having the issue.
I have not tried yet 0.63.1. Any luck with it??