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

[Thorgal789]

Try


For the headless mode

Code: Select all

     sudo systemctl disable deconz-gui
     sudo systemctl stop deconz-gui
     sudo systemctl enable deconz

For the desktop mode

Code: Select all

     sudo systemctl disable deconz
     sudo systemctl stop deconz
     sudo systemctl enable deconz-gui

[EdwinK]

sudo systemctl enable deconz

The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.

Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.

[EdwinK]

Oooops.... Let's hope Dresden Elektronik is not pulling support on this. Would it be possible to create the API key on a Windows machine?

Code: Select all

Ga dan naar C:\Program Files\Domoticz\plugins\deCONZ
En draai: “api_key.py 127.0.0.1:80 create”
De aangemaakte API key moet ingevuld worden in de deCONZ plugin configuratie

I'm sure they wouldn't pull the plug on this

[Thorgal789]

I'm sure they wouldn't pull the plug on this

No Their API is "free to use", it s possible too making domoticz create the key itself, but I don't remember the issue when making that.
it s possible too just with this command

Code: Select all

curl http://127.0.0.1:80/api/ -X POST -d '{"devicetype": "TestKey"}'

The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.

Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.

You have edited the file, to change the port ? probably a typo in the file ? Try with removing your changes.

[EdwinK]

Possible, but.. what file. I thought I had removed everything and installed again.

[Thorgal789]

I finally had it set to another port (8090)

Its not you that have changed the setting ? a systemd file ? Probably that https://github.com/dresden-elektronik/p ... /issues/26

[EdwinK]

Yes. but I forgot to take note of what file I did change. No matter, because in the last few hours my Domoticz Pi died on me, and I had to start all over again.

[EdwinK]

After reinstalling everything finally works as it should, I think.

Sent from my SM-A505FN using Tapatalk

[Thorgal789]

my Domoticz Pi died on me

Arf, RIP, I m with you.

[Sjonnie2017]

I bought a Zigbee remote to be able to control devices without the need for a phone or tablet. With help of Thorgal I have been able to add the "switch" to Domoticz but the behavior is unexpected.

The facts:
MOES Scene Remote - 4 button remote with three modes per button (https://www.moeshouse.com/collections/z ... nt-control)
Conbee2 stick with DeCONZ bridge by Thargal

The findings:
The Domoticz logs shows two sets of data depending on how I look at it. If I filter on the "MAC address" I get predictable results. If I filter on the device name (Scene Remote as I called it) the results are less logical (that's the Vulcan in me )

Results based on MAC address:

Code: Select all

2021-05-22 12:49:52.491 Status: ConBee2: (ConBee2) ### Device 60:a4:23:ff:fe:d2:23:2e-02-0006(ConBee2 - Switch 54) Not in deCONZ ATM, the device is deleted or not ready.
2021-05-22 12:52:39.985 ConBee2: (ConBee2) ### WebSocket Data : {'e': 'changed', 'id': '57', 'r': 'sensors', 'state': {'buttonevent': 1002, 'lastupdated': '2021-05-22T10:52:39.943'}, 't': 'event', 'uniqueid': '60:a4:23:ff:fe:d2:23:2e-01-0006'} (button 1 - single press)
2021-05-22 12:52:46.271 ConBee2: (ConBee2) ### WebSocket Data : {'e': 'changed', 'id': '57', 'r': 'sensors', 'state': {'buttonevent': 2002, 'lastupdated': '2021-05-22T10:52:46.261'}, 't': 'event', 'uniqueid': '60:a4:23:ff:fe:d2:23:2e-01-0006'} (button 2 - single press)
2021-05-22 12:52:50.806 ConBee2: (ConBee2) ### WebSocket Data : {'e': 'changed', 'id': '57', 'r': 'sensors', 'state': {'buttonevent': 3002, 'lastupdated': '2021-05-22T10:52:50.779'}, 't': 'event', 'uniqueid': '60:a4:23:ff:fe:d2:23:2e-01-0006'} (button 3 - single press)
2021-05-22 12:52:54.647 ConBee2: (ConBee2) ### WebSocket Data : {'e': 'changed', 'id': '57', 'r': 'sensors', 'state': {'buttonevent': 4002, 'lastupdated': '2021-05-22T10:52:54.612'}, 't': 'event', 'uniqueid': '60:a4:23:ff:fe:d2:23:2e-01-0006'} (button 4 - single press)
2021-05-22 12:54:32.335 ConBee2: (ConBee2) ### WebSocket Data : {'e': 'changed', 'id': '57', 'r': 'sensors', 'state': {'buttonevent': 1004, 'lastupdated': '2021-05-22T10:54:32.299'}, 't': 'event', 'uniqueid': '60:a4:23:ff:fe:d2:23:2e-01-0006'} (button 1 - double press)
2021-05-22 12:54:36.169 ConBee2: (ConBee2) ### WebSocket Data : {'e': 'changed', 'id': '57', 'r': 'sensors', 'state': {'buttonevent': 2004, 'lastupdated': '2021-05-22T10:54:36.160'}, 't': 'event', 'uniqueid': '60:a4:23:ff:fe:d2:23:2e-01-0006'} (button 2 - double press)
2021-05-22 12:54:40.605 ConBee2: (ConBee2) ### WebSocket Data : {'e': 'changed', 'id': '57', 'r': 'sensors', 'state': {'buttonevent': 3004, 'lastupdated': '2021-05-22T10:54:40.575'}, 't': 'event', 'uniqueid': '60:a4:23:ff:fe:d2:23:2e-01-0006'} (button 3 - double press)
2021-05-22 12:54:45.757 ConBee2: (ConBee2) ### WebSocket Data : {'e': 'changed', 'id': '57', 'r': 'sensors', 'state': {'buttonevent': 4004, 'lastupdated': '2021-05-22T10:54:45.733'}, 't': 'event', 'uniqueid': '60:a4:23:ff:fe:d2:23:2e-01-0006'} (button 4 - double press)
2021-05-22 12:55:05.787 ConBee2: (ConBee2) ### WebSocket Data : {'e': 'changed', 'id': '57', 'r': 'sensors', 'state': {'buttonevent': 1003, 'lastupdated': '2021-05-22T10:55:05.771'}, 't': 'event', 'uniqueid': '60:a4:23:ff:fe:d2:23:2e-01-0006'} (button 1 - long press)
2021-05-22 12:55:13.259 ConBee2: (ConBee2) ### WebSocket Data : {'e': 'changed', 'id': '57', 'r': 'sensors', 'state': {'buttonevent': 2003, 'lastupdated': '2021-05-22T10:55:13.222'}, 't': 'event', 'uniqueid': '60:a4:23:ff:fe:d2:23:2e-01-0006'} (button 2 - long press)
2021-05-22 12:55:20.584 ConBee2: (ConBee2) ### WebSocket Data : {'e': 'changed', 'id': '57', 'r': 'sensors', 'state': {'buttonevent': 3003, 'lastupdated': '2021-05-22T10:55:20.527'}, 't': 'event', 'uniqueid': '60:a4:23:ff:fe:d2:23:2e-01-0006'} (button 3 - long press)
2021-05-22 12:55:28.617 ConBee2: (ConBee2) ### WebSocket Data : {'e': 'changed', 'id': '57', 'r': 'sensors', 'state': {'buttonevent': 4003, 'lastupdated': '2021-05-22T10:55:28.571'}, 't': 'event', 'uniqueid': '60:a4:23:ff:fe:d2:23:2e-01-0006'} (button 4 - long press)

Results based on device:

Code: Select all

2021-05-22 13:29:53.277 ConBee2: (ConBee2) ### Update device (Scene Remote) : {'nValue': 10, 'sValue': '10'} (button 1 - single press)
2021-05-22 13:29:57.453 ConBee2: (ConBee2) ### Update device (Scene Remote) : {'nValue': 20, 'sValue': '20'} (button 2 - single press) *
2021-05-22 13:30:02.032 ConBee2: (ConBee2) ### Update device (Scene Remote) : {'nValue': 30, 'sValue': '30'} (button 3 - single press) *
2021-05-22 13:30:06.252 ConBee2: (ConBee2) ### Update device (Scene Remote) : {'nValue': 40, 'sValue': '40'} (button 4 - single press) *
2021-05-22 13:30:09.294 ConBee2: (ConBee2) ### Update device (Scene Remote) : {'nValue': 30, 'sValue': '30'} (button 1 - double press) *
2021-05-22 13:30:12.092 ConBee2: (ConBee2) ### Update device (Scene Remote) : {'nValue': 60, 'sValue': '60'} (button 2 - double press) *
2021-05-22 13:30:14.992 ConBee2: (ConBee2) ### Update device (Scene Remote) : {'nValue': 90, 'sValue': '90'} (button 3 - double press)
2021-05-22 13:30:18.217 ConBee2: (ConBee2) ### Update device (Scene Remote) : {'nValue': 120, 'sValue': '120'} (button 4 - double press)
2021-05-22 13:30:25.497 ConBee2: (ConBee2) ### Update device (Scene Remote) : {'nValue': 20, 'sValue': '20'} (button 1 - long press) *
2021-05-22 13:30:30.785 ConBee2: (ConBee2) ### Update device (Scene Remote) : {'nValue': 40, 'sValue': '40'} (button 2 - long press) *
2021-05-22 13:30:36.139 ConBee2: (ConBee2) ### Update device (Scene Remote) : {'nValue': 60, 'sValue': '60'} (button 3 - long press) *
2021-05-22 13:30:41.075 ConBee2: (ConBee2) ### Update device (Scene Remote) : {'nValue': 80, 'sValue': '80'} (button 4 - long press)

I have added an * behind every duplicated nValue/sValue.

The question:
If I can assign lights to the remote using ID combined with button event, that would be fine. Otherwise I would need to find a way to assign unique nValues/sValues to the device.

Any help greatly appreciated!

[Thorgal789]

Hello, again

@Sjonnie2017 have updated the beta plugin, to handle tuya switch, now it will be a new device just for them.
Just delete the domoticz entry (in the device pannel) and restart the plugin (hardware/deconz/update)
The device will be re-created with a new widget.

Do you need help to install the Beta ?

[Sjonnie2017]

Hi Thorgal,

Help would be appreciated. I have the stable installed and have an update script (topgrade) to keep it up to date. I can handle topgrade but I am not sure how to replace the stable with the beta without loosing my devices in Domoticz.

Looking forward to your reply and invaluable help!

[Thorgal789]

Hu ? Sorry I realy don't know how work toupgrade ....

There is an easy way, you can just replace your 2 files plugin.py and fonctions.py from this branch https://github.com/Smanar/Domoticz-deCONZ/tree/beta
Can use just copy/paste or download files (there is a link in green)
But you will have error message later if you use the git command.

Else if you already use git command, with command line, go to the plugin directory (domoticz/plugin/Domoticz-deCONZ)

Code: Select all

git pull
git checkout beta
git pull

To re switch to stable

Code: Select all

git pull
git checkout master
git pull

But don't worry, you will not loose zigbee device, the zigbee installation is managed by deconz, totally independent from domoticz.
And there is no change between version, you can switch versions without problem.

To loose something you need to delete a domoticz device in the device panel, else at every restart the plugin resynchronise deconz and domoticz, all missing device will be re-added, and if it s the reverse (entry present in domoticz but not deconz) you will just have a message, the plugin never delete something in domoticz.

[Sjonnie2017]

Hi Thorgal,

I don't see any changes or anything happening when I try to switch from stable to beta. This is the output from the terminal:

Code: Select all

pi@RPi4:~/domoticz/plugins/Domoticz-deCONZ $ git pull
remote: Enumerating objects: 6, done.
remote: Counting objects: 100% (6/6), done.
remote: Compressing objects: 100% (6/6), done.
remote: Total 6 (delta 1), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (6/6), done.
From https://github.com/Smanar/Domoticz-deCONZ
   6b5d8a6..17f021d  beta       -> origin/beta
Already up to date.
pi@RPi4:~/domoticz/plugins/Domoticz-deCONZ $ git checkout beta
Branch 'beta' set up to track remote branch 'beta' from 'origin'.
Switched to a new branch 'beta'
pi@RPi4:~/domoticz/plugins/Domoticz-deCONZ $ git pull
Already up to date.
pi@RPi4:~/domoticz/plugins/Domoticz-deCONZ $ git pull
Already up to date.
pi@RPi4:~/domoticz/plugins/Domoticz-deCONZ $ git pull master
fatal: 'master' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
pi@RPi4:~/domoticz/plugins/Domoticz-deCONZ $ git checkout master
Switched to branch 'master'
Your branch is up to date with 'origin/master'.
pi@RPi4:~/domoticz/plugins/Domoticz-deCONZ $ git pull
Already up to date.
pi@RPi4:~/domoticz/plugins/Domoticz-deCONZ $ git pull
Already up to date.
pi@RPi4:~/domoticz/plugins/Domoticz-deCONZ $ git checkout beta
Switched to branch 'beta'
Your branch is up to date with 'origin/beta'.
pi@RPi4:~/domoticz/plugins/Domoticz-deCONZ $ git pull
Already up to date.
pi@RPi4:~/domoticz/plugins/Domoticz-deCONZ $ 

I must be doing something wrong but can; t figure out what mistake I made

[Thorgal789]

Code: Select all

Switched to a new branch 'beta'
pi@RPi4:~/domoticz/plugins/Domoticz-deCONZ $ git pull
Already up to date.

This is good, it mean you have switched and all is in date.
After that you just need to delete the bad swich device in domoticz (from the "device" panel)
And restart the plugin with the "hardware" panel deconz / update

The widget will be re-created but with the new widget with B1,D1,L1,B2,D2,L2, ......

[Sjonnie2017]

Deleted the switch, restarted the plugin and recreated the device. Still B1, B2, B3 etc. Removed switch again, restarted the plugin and restarted Domoticz. Recreated the device but no B1, D1 etc. Checked the filedates voor fonctions.py and plugin.py. Both are from 05/22/2021@18:27 so they seem to be correct. The device data from the Custom -> Deconz panel:

Code: Select all

{
  "config": {
    "battery": 100,
    "on": true,
    "reachable": true
  },
  "ep": 1,
  "etag": "4d51a8a8cd699da524f3f06049733947",
  "lastseen": "2021-05-23T09:18Z",
  "manufacturername": "_TZ3000_abci1hiu",
  "mode": 1,
  "modelid": "TS0044",
  "name": "Scene Remote",
  "state": {
    "buttonevent": 1003,
    "lastupdated": "2021-05-23T09:10:48.464"
  },
  "type": "ZHASwitch",
  "uniqueid": "60:a4:23:ff:fe:d2:23:2e-01-0006",
  "id": "57",
  "deviceclass": "sensors"
}

I am open to out of the box thinking

EDIT: Don't know if it is related but I have a lot of problems with my Xiaomi Zigbee 2 gang wall switches. They don't work anymore. I can see them in DeCONZ but they don't seem to be able to command the roller shutter switches I have (done in Domoticz with a DzVents script). One of those roller shutter switches has gone offline somewhere between yesterday end of the afternoon and this morning. That could be a coincidence of course.

[Thorgal789]

Ok so have find the problem.
I was checking model id starting by "_TZ3" but it s the manufacture name, ahve corrected the code to check for "TS004"

If you are un beta branch, just use "git pull" to update files.

For the roller shutter switches, it s probably a connection issue. Are you using the GUI to check mesh ? if yes look at the parents. Else can use log to check connexion issues.
The device don't work at all, or it leave regulary ?
If you can see it in deconz, check if the device is still on the network (name is grayed or black).
If the device is in deconz and not the API, it s another problem, you think it can be deleted in the API by error with ours tests ?

[Sjonnie2017]

Hi Thorgal,

The update fixed the Scene Remote which now has 12 levels (plus "Off") and the buttons work as expected. Kodus!

Most Xiaomi wall switches are working again. Only one won't work. It's name is in gray in DeCONZ. Same for one roller shutter switch. Also gray. I have power cycled the roller shutter switch twice but no effect. I have removed the battery form the wall switch, left it there for a few minutes and returned the battery. No change. The battery is newly placed this morning (just to make sure). Should I report these issues on deCONZ github?

Note that all devices in deCONZ/Phoscon are still present in Domoticz. So no problems as a result of our tests.

EDIT: Somehow the roller shutter switch came back online so that issue seems to be resolved for now. The wall switch however is as stubborn as it can be I have removed the node from deCONZ and re-added it. It is available (in black) but that's it. Will experiment a bit more and if it does not cooperate I will open an issue on deCONZ github.

EDIT2: Thanks for your invaluable help so far

EDIT3: Wall switch miraculously came back online this morning.

[Thorgal789]

For information have just repaired the frontend, it s now possible again to configure sensors using Domoticz
Remember this tab can be disabled by defaut on domoticz.

domo.jpg (66.4 KiB) Viewed 1898 times

[Patricen]

Hello,
My plugin is up to date, I have added a sensor on Phoscon app, I can see the sensor on Domoticz' deCONZ custom panel, but how do I populate Domoticz devices with this new sensor so that I can use it?

Thanks!

Patrice
I'm running Domoticz last stable version 2021.1