Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee) Topic is solved

[Thorgal789]

@Thorgal789, It is the ikea remote with 5 buttons.
Ikea Tradfri and DeConz support the long press of the light intensity button.
It is only now not visible in Domoticz if you hold down the button for a long time.

Ok so you are right.
Do you need it for "<>" or "color" or both ? I can add both but for that I need 4 mores button on the device ...
Or you just want the same button activated on device for short press and log press ?

[bitjeverkeerd]

For <> it would be great if that is possible.

[bitjeverkeerd]

It would be nice if you can see the difference between long and short pressing the brightness up / down button.

[Thorgal789]

For <> it would be great if that is possible.

It would be nice if you can see the difference between long and short pressing the brightness up / down button.

Lol, Ok, so for all ?

Try theses files > https://github.com/Smanar/Domoticz-deCONZ/tree/beta
Delete your remote sensor and reload it (setting/hadware/deconz/update), the device have now 9 buttons.

[Harald777]

Ok so it's that.
The device 199 is the remote device, with the same buton than the remote itself.
The device 200 is the group associed to the remote (the special group for "group" command)

The first one is an transmitter, you can only see wich one button are pressed.
The second one is a receiver, you can only send order to this group (don't use it to check a state, not reliable)

Okay, perhaps I had better not assign the remotes to a group then.
On the other hand I believe this is the only option to get the remote to operate the light, key assignment only showed up once I added the remote to the group.
I think the remote did not operate when only assigned to the light bulb but don't know for sure.

Is there a way to totally clear the Phoscon / deConz database to start over again???

[Thorgal789]

Nope, if you add a bulb in the remote group, you will use the "special feature" without configuration, on/off and luminosity will work as it.
But you can too select a group bulb, then press "edit" then "switch editor" and link the remote without adding it in the group.
You can too use domoticz for your scene and don't use group at all (or use domticz scenario)
You can to make a group in phosocn and use domoticz to trigger the group according to the remote (it s the solution Im using, better control)

There is lot of solution possible.

Okay, perhaps I had better not assign the remotes to a group then.

Yep, for me it's not a good way, the remote have it own group and you don't need to put it in a group to use it to trigger an event (and you will have more options using this way)
Other switch like xiaomi one don't have the special group like the ikea one, but they work too.

And yes, there is some "reset features", but reset is realy a reset ^^. You can too delete group in phosocn, it will delete group/scenerio/associed event, ect ..., less dangerous.

[bitjeverkeerd]

Thank you very much Thorgal789. The ikea remote works perfectly now.

[Harald777]

Nope, if you add a bulb in the remote group, you will use the "special feature" without configuration, on/off and luminosity will work as it.
But you can too select a group bulb, then press "edit" then "switch editor" and link the remote without adding it in the group.
You can too use domoticz for your scene and don't use group at all (or use domticz scenario)
You can to make a group in phosocn and use domoticz to trigger the group according to the remote (it s the solution Im using, better control)

There is lot of solution possible.

Okay, perhaps I had better not assign the remotes to a group then.

Yep, for me it's not a good way, the remote have it own group and you don't need to put it in a group to use it to trigger an event (and you will have more options using this way)
Other switch like xiaomi one don't have the special group like the ikea one, but they work too.

And yes, there is some "reset features", but reset is realy a reset ^^. You can too delete group in phosocn, it will delete group/scenerio/associed event, ect ..., less dangerous.

Thanks again for your support,

Deleted the groups but now I know why I added the groups.
Without the groups you cannot alter the ikea remote switch commanded.
Now without groups only the on/off and dim/bright work.
Cool / warm arrows now not working.

When you delete the groups in Phoscon and Domoticz the show up in Domoticz again after reboot.
I believe this is by design and I have to add them to the deCONZ banned device list???

Greetings, Harald

[Thorgal789]

Without the groups you cannot alter the ikea remote switch commanded.

I have just make try, it works. have selected a group, edit, switch editor, link ikea remote. Then "key assignement", i select the up button "long press for warmer", I select the bottom button "long press for colder'. And it works, the remote is still alone in his group.

Now without groups only the on/off and dim/bright work.
Cool / warm arrows now not working.

This is the "special feature", it 's zigbee direct link that can work without deconz, and in this mode color can't work because it's a zigbee scene. And if on/off and dimmer are working, it mean you have bulb in same group than remote somewhere.

When you delete the groups in Phoscon and Domoticz the show up in Domoticz again after reboot.

If the group is deleted in phoscon the plugin will not add it in domoticz, but if you already have the group in domoticz, it will be not deleted (to prevent broken script), when you restart the plugin, on log you will have the list of dead device that are in domoticz and not in phoscon, you can delete them if you want, they will not be re-added.
If after a restart, a device group is re-created in domoticz it mean it still exist in phoscon.

[Harald777]

I have just make try, it works. have selected a group, edit, switch editor, link ikea remote. Then "key assignement", i select the up button "long press for warmer", I select the bottom button "long press for colder'. And it works, the remote is still alone in his group.

Just exactly done that and ended up with again duplicated switches.

Switches.png (19.9 KiB) Viewed 1701 times

This is the "special feature", it 's zigbee direct link that can work without deconz, and in this mode color can't work because it's a zigbee scene. And if on/off and dimmer are working, it mean you have bulb in same group than remote somewhere.

After editing the switches as mentioned above assigned the warm and cool function to the remote, working than.

If the group is deleted in phoscon the plugin will not add it in domoticz, but if you already have the group in domoticz, it will be not deleted (to prevent broken script), when you restart the plugin, on log you will have the list of dead device that are in domoticz and not in phoscon, you can delete them if you want, they will not be re-added.
If after a restart, a device group is re-created in domoticz it mean it still exist in phoscon.

Reset gateway and used old (saved) Domoticz database with empty deCONZ devices. Setup all over again and working again but with duplicated remotes.
But all is working fine.

Harald

[Thorgal789]

Hello again ^^

It's not duplicate switches. You have
1 - 1 device switch for each remote
2 - 1 device swith for all group created by remotes, all ikea remote create a group (for the special feature) just don't use them if you don't need them.

[Harald777]

Hello again ^^

It's not duplicate switches. You have
1 - 1 device switch for each remote
2 - 1 device swith for all group created by remotes, all ikea remote create a group (for the special feature) just don't use them if you don't need them.

I am not using them in Domoticz, only created them to control the Ikea bulbs directly from the remote.
All okay.

[Harald777]

Unfortunately I have another question:

After every reboot of the Raspberry PI I observe the following error:

2019-10-28 20:47:46.240 (deCONZ) onMessage called
2019-10-28 20:47:46.241 (deCONZ) ### WebSocket Data : {'id': '65520', 'e': 'changed', 'state': {'all_on': False, 'any_on': False}, 'r': 'groups', 't': 'event'}
2019-10-28 20:47:46.241 Error: (deCONZ) Websocket error, unknow device > 65520 (groups)
2019-10-28 20:47:46.241 (deCONZ) Send Command /api/0899D2ADF8/groups/65520 with None (0 in buffer)

Once rebooted all seems to be working okay, no issues after that.
Something to worry about??

[Thorgal789]

Nope ^^, I know there is so much useless error displayed, but I prefer that, easier for me to repair and check for error.

So, on the version you are using, the plugin detect itself new device when it see the information in websocket.
Since 2/3 version deconz use an hidden group that group ALL your devices, but this group is hidden.
When you start the plugin, it synchronise with deconz, but it can't see this hidden group, so the plugin don't memorise it. So later, during you use, you will trigger this group, and the plugin detect it, add it in the device list, and never ask you again, up to the next restart/reboot.
For information, you can see this group in your device list too, it's called "GROUP_All"

I know, I can avoid this message, but deconz is a "moving project", this hidden group is new, and can disapear soon, so for the moment I use the lazy way and let the message.
You can have this message everytime you are adding a new device in phoscon after having loading the plugin. It just mean the plugin have find a new device and add it in the device list, nothing important if all is working, but usefull if you have bugs.

[Harald777]

Nope ^^, I know there is so much useless error displayed, but I prefer that, easier for me to repair and check for error.

So, on the version you are using, the plugin detect itself new device when it see the information in websocket.
Since 2/3 version deconz use an hidden group that group ALL your devices, but this group is hidden.
When you start the plugin, it synchronise with deconz, but it can't see this hidden group, so the plugin don't memorise it. So later, during you use, you will trigger this group, and the plugin detect it, add it in the device list, and never ask you again, up to the next restart/reboot.
For information, you can see this group in your device list too, it's called "GROUP_All"

I know, I can avoid this message, but deconz is a "moving project", this hidden group is new, and can disapear soon, so for the moment I use the lazy way and let the message.
You can have this message everytime you are adding a new device in phoscon after having loading the plugin. It just mean the plugin have find a new device and add it in the device list, nothing important if all is working, but usefull if you have bugs.

Tanks for the clarification on that and thanks again for you help.
I really appreciate you answering the "beginners" questions i have.

The deCONZ plugin is really (working) great for Domoticz on the Raspberry PI (with a little learning curve).
It is great to have a RFLink and Raspbee (zigbee) working on the same device.

This morning I replaced some unreliable "Klik aan Klik uit" and "Kerui" switches with some Xiaomi Aqara ones.
All working great.
In the near future I will replace more old RFLink stuff for zigbee items including Yeelight bulbs (replacing my KAKU home light switching).

Greetings, Harald

[Thorgal789]

NP, I have some xiaomi stuff too, because realy cheaper, but for me they are the worst zigbee devices, it's incredible the amout of problem you can have with theses devices.

[Harald777]

NP, I have some xiaomi stuff too, because realy cheaper, but for me they are the worst zigbee devices, it's incredible the amout of problem you can have with theses devices.

What is a better alternative?

Harald

[Thorgal789]

Philips ^^. But not the same price.
Take Xiaomi, it's not expensive, you can change for another manufacturer later if you have problems (I have 2 xiaomi presence sensor working since 1 year, I haven't only problems ofc )

[Harald777]

Hi there,

This time I am in big trouble.
Last evening a bad Domoticz update corrupted my installation.
Fixed today with a new Domoticz update but the deCONZ plugin is giving big troubles.

Domoticz is starting but the web interface / domoticz sever stops 1 or 2 minutes after boot.
Found following messages:

2019-11-03 18:35:10.881 Error: Domoticz(pid:862, tid:1150('WebServer_8443')) received fatal signal 11 (Segmentation fault) while backtracing
2019-11-03 18:35:10.881 Error: siginfo address=0x194, address=0x80000001

Deactivated all my plugins one by one (removed directly from the plugin folder) and found out that as soon as the deCONZ plugin folder is removed Domoticz is running fine again.
So removed the deCONZ folder from plugins folder and reinstalled the plugin again, same result, Domoticz crashing right after boot.
Phoscon is running fine, I can use all my zigbee devices.
So something went really wrong with the deCONZ plugin.

Any thoughts on this?
Hope to solve this without a complete re-installation.

Greetings, Harald

[Thorgal789]

I have make a search on "Fatal signal 11" and it's something realy frequent, hard to find a special procedure.
https://www.domoticz.com/forum/viewtopi ... 11#p227513
https://www.domoticz.com/forum/viewtopi ... 11#p222058
https://www.domoticz.com/forum/viewtopic.php?t=27921

Wich one domoticz version are you using ATM ?
Have you try an older version ?

You haven't change your python version ?

You can too make a backup, reinstall a clean install of domoticz an restore the backup.

Or easier, if the problem is a right problem, just delete the plugin folder and reinstal it, you will loosse nothing (all the config is in deconz), you can just have device name problem (if you have changed device name in domoticz). But I don't think the problem was from here.