Goal is to get SmartThings zigbee button working with Home Assistant first. Then, Wyze Sense sensors. Conbee II will be the zigbee coordinator (aka gateway, aka hub).

Use Windows PC to update firmware and set 2.4GHz channel. Download GCFFlasher and deConz.

Android CH340 USB to Serial Driver: Link 1: CH340/CH341 USB to serial port Android free drive app library, used for Android Host 3.1 & above USB Host mode, no need to load Android kernel driver, no root privileges. Contains apk installer, lib library file (Java Driver), App Demo routine (USB to UART Demo project SDK). Starting from Windows ® 10, the STSW-STM32102 driver is no more adequate and the usage of the native inbox driver is recommended. Key Features Virtual COM port driver installation package for Windows ® operating systems: 98SE, 2000, XP, Vista ®, 7, and 8.x.

This Qualcomm QDLoader Driver helps in detecting the device when it is connected to PC in EDL Mode or Download Mode. This Qualcomm HS-USB Driver package is for 64-bit OS, you can download the 32-bit version of the driver here. If you would like to install the drivers manually, download these Qualcomm Drivers.

GCFFlasher.exe install error:

Diversified power management company and global technology leader in electrical systems for power quality, distribution and control; hydraulics components, systems and services for industrial and mobile equipment; aerospace fuel, hydraulics and pneumatic systems for commercial and military use; and truck and automotive drivetrain and powertrain systems for performance, fuel economy and safety. Select “Let me pick from a list of available drivers on my computer” 7. First select “Show compatible hardware” and then select “Prolific USB-to-Serial Comm Port Version 3.3.2.105 27/10/208” from the list. The driver is now installed successfully and is even maintained after a reboot.

So skip for now and install deConz for Win. Connect Conbee II. deConz app says frequency band is 2400 – 2483.5MHz.

Ensure status is “Not in Network”, else click “Leave”. Click icon for “Network Preferences”, top-center. Device type = Coordinator with Channel Mask 15.

Metageek diagram:

Don’t untick current channel, but rather tick channel 20 checkbox then “Save”, “Done”. Close deConz. Restart deConz. Verify channel is 20.

Download firmware deCONZ_ConbeeII_0x26580700.bin.GCF

Ad100 Pro Channel (com3) Driver Download 32-bit

Download D2XX drivers 2.12.28 (x64). Copy ftd2xx.dll from “i386” folder of drivers to same folder as GCFFlasher.exe.

Open powershell shell, navigate to folder with GCFFlasher.

List devices:

Shows “path” is COM3, but no firmware version info. Firmware ver is displayed when flashing.

Copy firmware file to same folder as GCFFlasher.exe. Flash:

Ran same command again to see expected version:

Move conbee II from Windows pc to ubuntu Home Assistant server.

Dresden Elektronik:

This adds /dev/ttyACM0

But, may be wiser to use /dev/serial/by-id/… device path (in case future usb devices cause ttyACM* to change):

dmesg:

Add user to ‘dialout’ group:

Web-ui: Configuration > Intergrations > “+” icon. Search for “ZHA”. See & install “Zigbee Home Automation”.

Unable to connect error:

Abort integration. Use Portainer to map device into the Home Assistant container.

“Duplicate/Edit”.

Then “Runtime & Resources” > “add device”:

Map the long device path (host) to /dev/ttyACM0 within the container:

Scroll up and “Deploy the container”. Confirm that you want to “Replace” the existing container. Wait for HA to restart. Try again to install the ZHA integration, but use /dev/ttyACM0 as the device path this time.

It’ll find it right away because we mapped the host’s device path to inside the container as /dev/ttyACM0:

This is HA 0.110.7

Saw a bunch of sensible “zha” logs in home-assistant.log

‘docker inspect’ output:

Was not prompted for zha database path; kinda expected it. Later, I found it in /config:

From the docs:

“To add new devices to the network, call the permit service on the zha domain. Do this by clicking the Service icon in Developer tools and typing zha.permit in the Service dropdown box. Next, follow the device instructions for adding, scanning or factory reset.”

Seen in home-assistant.log when I called the permit service:

Power ON SmartThings button and tap the button a few times:

“samjin” button.

Entities:

HA web-ui > Configuration > Zigbee Home Automation. Click the device.

Button press event: Developer Tools > Events. Listen to “zha_event”.

Single-tap:

Double-tap:

Ad100 Pro Channel (com3) Driver Download Windows 10

Long-press event:

Check-in event. Might be useful as a heartbeat signal to ensure the button is really alive; and indirectly, the the quality of the zigbee network. The following is the value for msg.payload as displayed in Node Red:

Use [events: all] node:

AD100 Pro Channel (COM3) Driver Download

But filter to “zha_event”:

Ad100 Pro Channel (com3) Driver Download Windows 7

See the data using [debug] node:

Ad100 Pro Channel (com3) Driver Download 64-bit

Grafana query, because SmartThings button has a temperature sensor inside:

According to grafana/influxdb, the SmartThings button is reporting its battery level (%) every 3 hours. But next day, changed to every 10 hours.

#