-
Notifications
You must be signed in to change notification settings - Fork 503
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
2.10.00-Beta: Lidl/Silvercrest TS0211 not recognized as button #4450
Comments
Ok there is probably an issue (perhaps the device is missing in button_maps.json), but the device is clearly a switch from the JSON. |
If the device missing from button_maps.json could be the reason for the switch not being usable as a switch perhaps @jurriaan has these changes at the ready based on the original PR. |
Not sure how this is supposed to work, I just listen to the button events and that works fine here. Should a pushbutton even be registered as a switch? |
Yes, that indeed seems to be the case. |
ist there any solution for that? |
I have been trying to get a button_maps.json entry going for this one. But as its my first time trying, no clue if/when I will figure out what the contents should be. So if anyone has a manual or list of logs he/she needs from me feel free to comment/ask. |
I have the same problem in FHEM, the readings always stay at "zero", but the timestamp is rewritten. So it does not really work unfortunately. |
Just had a look at the PR, the implementation is wrong and it should have never exposed as a switch. Correct would have been to expose it as alarm sensor. |
@SwoopX What would be the next steps? |
The resource type should just be changed from ZHASwitch to ZHAAlarm so the I guess I can do that somewhere next week. |
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
This issue is currently waiting for the Merge of the fix #4652. |
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
Can someone please check with debug enabled if such an event gets generated on press and release (and please also share the lines)?
|
Hi @SwoopX , Have started deconz with
|
Hi @Kane610, Do think that also for the Lidl TS0211 support is required within HA? Here we encounter the issue as with the Ikea Shortcut Button, were the device registered without any further option within HA. Thanks for your help! |
Yeah it's not supported today. Supported units can be seen here https://github.com/home-assistant/core/blob/eb687b733233c8aa97b7963b9b522808ed65d711/homeassistant/components/deconz/device_trigger.py#L525 Open an issue and be as detailed as possible. But not deconz logs but events from within hass |
I see in logs the follow messages when I push the (single) button on this device ; Deconz;
HA;
Is this implementation correct enough for HA @Kane610 ? I just started with HA, so I have not yet an idea of the design principes 😅 |
The HA event is what I need, but it needs to contain "buttonpress": 100x in them to be relevant, I need a mapping between that event and what you did to generate it e.g. short press -> 1001, release after short press -> 1002, etc. I also need a modelid |
@SwoopX can you help out here ? 😅 Can you make a device mapping somehow? Some HA logs already;
Some extra deconz logs, not sure of this needed;
|
I'll unsubscribe to this issue. Create an issue on https://github.com/Kane610/deconz once deCONZ support is verified to work. |
Please note: The device here is named either ts0211_4, ts0211_5 or ts0211_6. That is due to re-pairing, after deleting the device through the rest-api.
Describe the bug
The Lidl/Silvercrest TS0211 should now in deconz (not Phoscon) be supported after Pull Request #4282.
It connects to the network, and is named as expected. If I then understand how a device that is not yet supported by Phoscon should work, is that it should be working in 3rd party apps as just a button in this case. That it does not.
Steps to reproduce the behavior
ps. Instead of using HA, the rest-api can also be used. This will not directly list the battery status and will list buttonevent as "null"
listening to the deconz_event in HA lists a button event on button press:
Expected behavior
Phoscon should see the device as pairing as a Switch device, it does see it if pairing as a sensor device. (not in the UI just the pairing action)
Step 7 & 8 should have battery status & button options
Screenshots
Screenshot of device info in Deconz:
Screenshot of Home-Assistant reading the device:
Note there is no battery level listed. Nor in HA is the fact it should be a button recognized.
Rest-API sensor read (after waiting for the battery status to show):
Environment
deCONZ Logs
Click on button event:
Additional context
Other devices in the network:
The text was updated successfully, but these errors were encountered: