Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

6221-Sensor is not detected correctley #183

Open
Spartacus68 opened this issue Apr 17, 2024 · 4 comments
Open

6221-Sensor is not detected correctley #183

Spartacus68 opened this issue Apr 17, 2024 · 4 comments

Comments

@Spartacus68
Copy link

Hi all,
I have installed a free@Home SYSAP with a Sensor 6221/2.0-WL. The integration is setup and the Sensor is online in SYSAP.

Homeassistant detetcs the sensor only with the left Channel and on/off events are generated.
Nothing happens if I click on the right channel.

image

Also long-press will not be sent out. Is this technically not possible? I only use free@home with sensor. No actuators

@jheling
Copy link
Owner

jheling commented Apr 19, 2024

Hello, the integration works by intercepting the messages of a sensor when a sensor is paired with an acuator. You can test this under home assistant as described as point 2 of the debugging section of the homepage of this integration. Then you should see the messages of the left button and maybe the right button

@Spartacus68
Copy link
Author

Hi,

does this mean, that a sensor only works, if an actuator is paired with the sensor in free@home directley? And does this also mean, that a setup with only sensor in free@home and actuators in HA does not work?

Sorry for my stupid questions but I am totally new in freee@home and in close contact with Busch-Jäger in order to test the szenarios with HA. BJ provided me only sensors for testing the connection to HA. Only to understand the situation: Is it a technical limitation of freeqhome that the communication only works if sensor and actuator are paired in the SysAP or is this the current functionallity within your integration?

@jheling
Copy link
Owner

jheling commented Apr 20, 2024

Hello, When I started with this integration there had to be a link from the sensor to the actuator if you wanted to see a button press of the sensor in home assistant. The integration intercepts the messages that are on the free@home bus wire. This bus wire also makes it possible to use the sensors and actuators without a sysap.

If you want to use a free@home sensor in combination with a home assistant actuator you can use the Emulated Hue integration. This will make a home assistant actuator look like a philips hue bulb. The free@home will see the emulated hue and you can connect a sensor to this bulb.

Using the free@home only for the switches/sensors looks a bit expensive as there are also zigbee of wifi switches that are a bit cheaper.

@Spartacus68
Copy link
Author

Hello

I'll explain the background:

I hve bought BJ Zigbee switches 2 years ago. As it turned out, they just don't work in big Zigbee networks and are no longer usable for me. Since I spent a lot of money on the BJ wall switch program and use the design throughout the house, I didn't want to accept this circumstance and complained to BJ. On a Zigbee basis, BJ can't offer anything because they will no longer support Zigbee products in future. Instead, the company will focus on Matter and free@home in the future. I would like to continue using BJ in future and BJ promised to replace the Zigbee sensors. But this only makes sense if I can connect them to HA. I now understand that your free@home integration currently only works if actuators are installed on the bus or in the SysAP. For me, this means that a pure solution with sensors will not work.
BJ also has a keen interest in connecting the free@home with HA. I'm not a programmer and don't trust myself to develop it further, but I could make contacts to make the sensors and actuators transparent. It would be great if they could help!Just let me know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants