Conbee III

[HarryT]

Hi

Has anybody already experiences with Conbee III ?

Thanks
{HT}

[MadMax-FHEM]

Has anybody already experiences with Conbee III ?

A quick search lead me to here: https://forum.fhem.de/index.php?topic=117470.msg1292637#msg1292637
(sorry German only)

So it seems (at least) one had tried but moved back to Conbee II...

Regards, Joachim

[HarryT]

Thanks MadMax

Somebody more experiences?

Ps. My german ready skills are good. Writing not.

{HT}

[Jamo]

Hi Harry,
as described, my experiences are when migrating from ConBee II -> ConBee III. The migration failed as existing devices (except one) showed as non-reachable, and I did not want to add all devices again as new to the ConBee III / Phoscon GW. When moving back to the ConBee II, three Osram Plugs showed as non-reachable, so these three I had to reset and re-register with the ConBee II again.
Other than that I would expect that the ConBee III just works as smooth as the ConBee II. In general I'm more than happy with the ConBee.

I will try again when the next FW / stable Deconz release will be released.   

[Jamo]

Hi Harry,
According to Phoscon support, the release of deCONZ addon 2.24.x is a prerequisite for the ConBee III stick.
With this, I just completed successfully the migration from Conbee II -> ConBee III as follows:
- Deconz update to v2.24.2 (See https://github.com/dresden-elektronik/deconz-rest-plugin/releases)
- Update von ConBee II to ConBee II as per https://phoscon.de/de/conbee3/upgrade
With this, all my devices have been recognized, except the OSRAM plugs. For those OSRAM plugs you do not have to delete any OSRAM plug in FhEM nor in Phoscon, just press the "add new Plug" in Phoscon, and then press the button on the OSRAM plug for more then 10 seconds until the relais switches 2 times.

Hope that helps.

Regards, Jamo

[HarryT]

Thanks to all of you for the answers.

The new ConBeeIII is delivered with formware 2.42.2

I am absolutely new to Zigbee and ConBee. So I have no upgrade issues. But everything is new for me.

I used the installation instructions on https://phoscon.de/en/conbee3/install#raspbian
 and succeeded in installing deCONZ and using the Phoscon App to add a Tuya TS0203 "Zigbee Door Window Sensor". In the Phoscon App I see the status changing I open or close the sensor.

I added "define ConBeeIII_HUEGroup0 HUEDevice group 0  IODev=ConBeeIII" and FHEM added the other lines. 
However I seem not to be able to add the Tuya sensor to FHEM.

In fhem.cfg I have:

Code Auswählen Erweitern

define ConBeeIII HUEBridge localhost 60
setuuid ConBeeIII 65623eea-f33f-58d0-6574-fd97df012557f54f
attr ConBeeIII key 82fe496d35efaecdaee7c5cd8b55be20
attr ConBeeIII room Hardware
#
define ConBeeIII_HUEGroup0 HUEDevice group 0  IODev=ConBeeIII
setuuid ConBeeIII_HUEGroup0 65623f42-f33f-58d0-21a3-0a6a0abba438bbea
attr ConBeeIII_HUEGroup0 userattr createActionReadings:1,0 createGroupReadings:1,0
attr ConBeeIII_HUEGroup0 IODev ConbeeIII
attr ConBeeIII_HUEGroup0 alias Lightset 0
attr ConBeeIII_HUEGroup0 color-icons 2
attr ConBeeIII_HUEGroup0 delayedUpdate 1
attr ConBeeIII_HUEGroup0 devStateIcon {(HUEDevice_devStateIcon($name),"toggle")}
attr ConBeeIII_HUEGroup0 group HUEGroup
attr ConBeeIII_HUEGroup0 room Hardware


"get ConBeeIII devices" gives me an empty list. 
"set ConBeeIII autocreate sensors"  gives me 0/0/0

I guess I made a silly mistake somewhere. Any Ideas what can be wrong?
 
Thanks for any answer.
{HT}

[HarryT]

Probably this is part of the problem:

023.11.26 11:48:20 1: HUEBridge_HTTP_Request http://localhost/api/82fe496d35efaecdaee7c5cd8b55be20/config: Select timeout/error:
2023.11.26 11:48:20 3: HUEBridge_Call: failed, retrying
2023.11.26 11:48:24 1: HUEBridge_HTTP_Request http://localhost/api/82fe496d35efaecdaee7c5cd8b55be20/config: Select timeout/error:
2023.11.26 11:48:24 3: HUEBridge_Call: failed, retrying
2023.11.26 11:48:24 3: HUEBridge_Call: failed
2023.11.26 11:48:24 2: HUEBridge_OpenDev: got empty config
2023.11.26 11:48:29 1: usb create starting
2023.11.26 11:48:30 3: Probing TCM_ESP3 device /dev/ttyUSB0
2023.11.26 11:48:30 1: TCM_ESP3: Can't open /dev/ttyUSB0: Device or resource busy
2023.11.26 11:48:30 1: usb create end

[Jamo]

Hi Harry,
you need to look up the ID of your Sensor, by using "get ConBeeIII sensors" in fhem. The ID is the leftmost value in the popop table.
Then you can define the sensor in FHEM :

Code Auswählen Erweitern

defmod Tuyasensor HUEDevice sensor <ID> IODev=ConBeeIII

[HarryT]

Hi Jamo

Unfortunately  "get ConBeeIII sensors" returns an empty list with just an OK button.

Maybe it has something to do with the error in my logging. See my posting of 15:25


Greetings
{HT}
 

                                                   

[Jamo]

Hi Harry,
according to https://forum.fhem.de/index.php?topic=116933.0 (German), pls set the attr httpUtils followed by set active, that should fix the issue

Code Auswählen Erweitern

attr ConBeeIII httpUtils 1
set ConBeeIII active

[HarryT]

Hi Jamo

it didn't work.

In the thread you mentioned I also found noShutdown, but that also didn't work.

In my fhem log I now have:

2: ConBeeIII: invalid json detected for http://localhost/api/xxxxxxxxxxxxxxxxx/config:
 and
HUEBridge_OpenDev: got empty config

So I guess there is an installation issue. You have idea how to solve this?

Thanks
{HT}

 

[Jamo]

Hi Harry,
not sure how I can help here. Did you have a look at https://phoscon.de/en/support#conbee2-connection-issues, and there the section ,,Troubleshooting for ConBee II with Linux"

I would recommend to look at that and check all items mentioned.

[HarryT]

Hi Jamo

You helped me a lot. Thanks for that.

I found out what was wrong.
  define ConBeeIII HUEBridge localhost
should be
  define ConBeeIII HUEBridge localhost:8080

I used the default installation and can remember this was mandatory. Maybe this is new for ConBeeIII stick. 

Anyway, the stick and the sensor seem to is work smooth now.

I will repeat the whole Zigbee installation on a fresh fhem installation and publish the steps here. Maybe it can help someone.

{HT} 

   

 

[Jamo]

Hi Harry,
the wrong port was my first guess as well, but as you mentioned that you opened the Phoscon WebGui, I was under the impression that your installation was using the default port and that is not the issue. However, you can open the following file e.g. with the vi editor "sudo vi /lib/systemd/system/deconz.service"
Then you can check the port used, the matching line should read in your case

Code Auswählen Erweitern

ExecStart=/usr/bin/deCONZ -platform minimal --http-port=8080
Otherwise you need to change that specific line to match the port used (and the the fhem define accordingly.

[HarryT]

Hi all

Thanks for all the help. It took my some time to get the info together to make it work.

For any starter, attached is my script/notes how to install ConBeeIII and integrate it in FHEM

Have fun with it

Mfg
Harry
Du darfst diesen Dateianhang nicht ansehen.