-
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
Device support Bticino Living Now #2707
Comments
Hello, was my question here ^^ #2674 (comment) How are you using deconz for this device ? And it doesn't report status because this device is not in whitelist for binding. I can add it in the code (just one line to add). To activate the reporting, waiting for code modification, you can use deconz First make the bind
Then enable attribute reporting
Or if you can compile the code, I can make modification now, but I need to understand how it work, because there is no real "on" and "off", if you use the output 2 it will be "off" but if you use the output 1 it will be "on". And if you are using a not connected deviator on the same circuit, it can be on and off without action on the device. |
Ok, so if the value stay false, it will be a problem, I will check z2m to see If I found more information But can you use the device ATM with the API (phoscon or HA) ? There is no toogle command on it, how are you using the device ? If you seend multiple "on" command it toogle the output ? |
Ok so I have found something
But
So I think the device can check the consumption or current presence, are you making try with a bulb or other thing that consumme current ? |
Update: I connected the device with a bulb and another deviator and actually works correctly. Now the ON/OFF status changes between true and false, so it must have a kind of consumption meter inside. |
Realy nice hardware, seriously, was a good idea to use something hardware to guess if it's on or off for this kind of situation. So, nothing to change ? I just need to enable the binding/report automaticly ? |
I think so, anyway I connected all the 4 deviators that were previously connected to the Bticino gateway and everything is working great with Home Assistant, the trick was to connect a load in order to change the on/off flag. |
All is already working ? |
No need for manual binding |
Ok thx, so I let the code as it. |
It seems this issue is inactive / resolved. If it is not, please re-open or create another issue! |
Hi all, I have a strange problem with a BTicino connected deviator (N4003C) and Conbee II. I have a fresh installation of deCONZ (last version V2_05_86). Once configured to use the channel 11 and reset the deviator to default factory I can see inot the zigbee network, connected t the Conbee II, but after a few minutes the binding is lost and it's not anymore possible to add it. let me underline between the automatic adding into the network and the lost of bidning I didn't perform any action...just waiting for the lost of bidnding. Any ideas ? thx |
Yep, probably a bad inclusion. What if your inclusion procedure ? remember you need to use the hidden button not the deviator itself. |
mmmmm.....maybe I missed something...I'm very rookie on this topic. Could you please remember which is the proper procedure ? Personally I just pressed the reset button in order to restore default factory settings into the deviator, but nothing else. It has been joined to the Zigbee network. thx |
I have only Legrand device on my side, not Bticino but for me it's Long press to reset, ignoring the first blink, , release, then short press. |
ok thx I will try. Just a quick question. Do you have the original gateway in place ? Currently I'm trying such kind of test without the Legrand/Bticino gateway. thx |
I have it, but in a box, not connected. You don't need the long press on it, for deconz, you need the red led fixe (at least for legrand) |
unfortunately with BTicino if I take pressed button for reset I have the first blink, but after that if I release and repress the button nothing else happen. I need someone else who have already integrated a BTicino component. |
Hi, can I kindly ask you your help ? thx |
You need to ignore the first blink, and keep pressed. If @zinoalex have another procedure ? |
Hi lambu, |
But it works too without the gateway ? |
Hi dear,
All of them are visible into HomeAssistant (Hass.IO distribution) and I was able to integrate them in Google Home. All of them works fine by switching on and off what is connected to, except the shutter. If I press UP /Open and Down / Close Exec button in "Cluster info" windows within deConz interface the shutter motor rotate clockwise and anti clock wise properly, as when I press the shutter itself, but when I click UP arrow and Down arrow within Home Assistant the rotation happen always in the same direction. Do you know whihc could be the reason ? thx |
Yeah ^^, I m already on it > #3532 By hazard can you compile the code to test it ? The other user don't have unix machine. |
unfortunately I installed deconz on Windows and Hass.IO as virtual appliance by downloading a VHDX virtual disk. I took a look to the post mentioend by you, but I'm not getting if you are mentioning my same identical problem or something else. thx P.S. user: lambu76 |
Ha yep sorry, the discution have started on discord, but it s a similar issue, if you want to make it working you need to use the "open" command, HA use "bri" and this command is buggy witht his device. I will make the PR in blind mode, but I think it will be enought, I have mimic the other shutter device. |
I'm a little bit lost but happy to know that can work...could you please support me in order to instruct HA to send the proper command? Thx a lot |
I don't know at all HA. You need to change the command done by the app to make try with the not corrected version, or use direclty the API with Curl for exemple. |
Where did you find that the reason for this bug is a wrong command send by HA ? Maybe I could find someone else in some community to help me with HA, since unfortuantely you are not using it. thx |
Hi guys, did it with a K4003C, all good so far and it's connected correctly to my home assistant. I'd like to use the led inside (the blue one) so that, when light is off led is on. I've found something that can work but it's based on mqtt. there's a way to "traslate" it natively to deconz? Thank you |
Yes it's probably already in the XML file. Its on the Legrand cluster, it s called "option 2" or "option 3", |
oh, thank you! this run perfect! :) |
Hi all guys, since a couple of month the Bticino DIN power consumption module always stop working after 24h from the host restart. I'm on HA (core-2022.3.8, supervisor-2022.05.0, Home Assistant OS 7.6) with Phoscon/ Deconz (2.15.03 / 21/4/2022 - 26720700) |
And other zigbee module still working ? Only this one stop working ? |
Yes, every other zigbee device works fine. As soon as it stops again i’ll post the json (i still need to wait few hours) |
Here the json in phoscon as "switch":
And here as sensor:
The sensor says it is not reachable, but in the stream tab I can see the event sent. |
Ha yes, we can see the "lastupdated" in date but only the ZHASwitch have "reachable" to true.
"lastseen" is not updated, It remember me an old issue. BTW do you know how to edit a file on your OS ? (to try to create a DDF for this device) |
Now I see the point of your question. On HA I can't find the folder where the DDF device are, but I can access to the visual editor of deconz, where I saved the DDF as a new file, and I guess/home I can edit it from there. If it helps I may restart HA too just to get the same info in the 24h window when everything works. |
No, it s ok. Will see after if a DDF can help or not. |
Should I open a new issue rather than monitoring this closed one? |
I'll reopen. |
Your issue is almost the same than here https://forum.phoscon.de/t/since-migrating-deconz-plugin-from-2-14-1-to-2-15-3-heiman-hs2wd-e-siren-sensors-become-note-reachable-after-a-few-hours/1951 Manup have updated the firwmare since, but I don't think he had enought time to check the issue. |
Your issue is probably solved with this PR #6106 |
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. |
Has anyone been able to solve the problem of the open / close percentage not recognized by the k4027c device? |
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. |
As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again. |
Did you? I have been struggling with this today. I have successfully added the device on Deconz\Phoson but I can only open or closed it. Thanks! |
Are you sure your device support it ? If yes, pls open a new issue with all the needed information to make a new DDF. |
Yes, using the GUI it works. I opened the issue thanks! |
does it mean you are able to open cover to a specific percentage ? |
Yes, it’s working as expected. |
I think the next will be here #7390 (comment) |
Hi guys, would be possible to expand the support to the Bticino Living Now devices?
I was able to include (only on channel 11 and after device's firmware upgrade) and use:
K4027C shutter controller (light in Phoscon)
F20T60A: DIN energy monitor mistakenly called Legrand DIN power consumption module (not visible in phoscon)
K4531C: power consumption module (light in Phoscon)
K4027CW: wireless shutter command (not visible in phoscon)
In all those devices the manufacturer is wrong reporting Legrand.
Unable to use:
K4003C: connected deviator
This one is recognized and included in the network after FW upgrade to v22 and channel 11 but it doesn't report the actual status. Toggle mode in deconz works. Any ideas to do that? I read a post about zigbee2mqtt and they were able to control this device.
Device
Screenshots
The text was updated successfully, but these errors were encountered: