Hi.
And doesn't the coordinator detect directly through the ZHA?
If not then there are two solutions:
1. move everything to zigbee2mqtt
2. buy a second coordinator and upload the zigbee2mqtt add-on
What kind of coordinator do you have? Sonoff dongle P? HA on a virtual machine?
If you choose the second point, i.e. the second coordinator (sonoff P) then in the serial in the zigbee2mqtt configuration you punch in:
I have a Home Assis os and a Sonoff dongle 3+. The zha detects the thermostat but there is no way to adjust the temperature and other functions and the zigbee2mqqt so average it wants to work.
Zha detects thermostat but has no ability to adjust temperature and other functions
.
You need to enter:
Settings > Devices and services > ZHA (devices) > you select the device > you have control and configuration > add to dashboard
If you don't have this then apparently it doesn't work with ZHA yet.
I personally use ZHA and zigbee2mqtt at the same time having two coordinators.
hkielp745 wrote:
zigbee2mqqt so moderately wants to work.
.
Meaning? If you have ZHA then on a single coordinator it definitely won't run zigbee2mqtt for you, even if you disable ZHA it still makes problems.
So should I uninstall zha first and then install zigbee2mqtt?
.
1.The first is to make a backup.
2.First try to remove the coordinator from the device list in ZHA and disable ZHA
3.Create a new user in HA - MQTT User
4.Now install and configure Mosquitto broker
5. install and configure before running Zigbee2MQTT
Added after 2 [minutes]:
Pct 2 - physically disconnect the coordinator so it doesn't reinstall itself into ZHA
How to do all this you have in detail on YouTube - look for videos from this year, just making sure that in the serial next to sonoff zigbee 3.0 + is entered
And what did I write above?
In the zigbee2MQQT configuration in the add-on
adapter: zstack
As you can attach a screen shot of what you have in the config - obscure the password.
Added after 5 [minutes]: .
Have you done the configuration with the video I sent? .
If you mess up too much you will have to uninstall the add-ons, delete the user and reinstall haha .
Use the same passwords and usernames in the Mosquitto broker and Zigbee2MQTT configuration.
.
I have this now, but there is still a problem:
[18:15:10] INFO: Preparing to start....
[18:15:12] INFO: Socat not enabled
[18:15:20] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-10-23 18:15:47] info: z2m: Logging to console, file (filename: log.log)
[2024-10-23 18:15:48] info: z2m: Starting Zigbee2MQTT version 1.40.2 (commit #unknown)
[2024-10-23 18:15:48] info: z2m: Starting zigbee-herdsman (2.1.3)
[2024-10-23 18:15:50] error: zh:zstack:znp: Failed to determine if path is valid: 'Error: spawn udevadm ENOENT'.
[2024-10-23 18:15:50] info: zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyACM0", "baudRate":115200, "rtscts":false, "autoOpen":false}
[2024-10-23 18:15:50] info: zh:zstack:znp: Serialport opened
[2024-10-23 18:15:50] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2024-10-23 18:15:51] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2024-10-23 18:15:51] error: z2m: Error while starting zigbee-herdsman
[2024-10-23 18:15:51] error: z2m: Failed to start zigbee
[2024-10-23 18:15:51] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-10-23 18:15:51] error: z2m: Exiting...
[2024-10-23 18:15:51] error: z2m: Error: Error: Not supported, cannot set
/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:264
var er = new ERR_STREAM_WRITE_AFTER_END();
^
Error: write after end
at writeAfterEnd (/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:264:12)
at DerivedLogger.Writable.write (/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:300:21)
at DerivedLogger.log (/app/node_modules/winston/lib/winston/logger.js:231:12)
at Logger.log (/app/lib/util/logger.ts:198:25)
at Logger.info (/app/lib/util/logger.ts:211:14)
at Znp.onPortClose (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:96:16)
at Object.onceWrapper (node:events:632:26)
at SerialPort.emit (node:events:529:35)
at port.close.then.closing (/app/node_modules/@serialport/stream/dist/index.js:242:18)
The username cannot be mqqt-user only mqqt_user there was a problem with hyphens at least with me.
Do the whole configuration from scratch. And I beg to God follow the steps with the video I posted .
Uninstall these add-ons, reload HA and start again with mqqt_user. Remove ZHA
.
Added after 2 [minutes]: .
As long as you have copies then don't worry.
You can't run Z2MQQT before the step-by-step configuration.
Later if you do we will worry about the coordinator path and "adpater" in the serial .
It is with mqtt_user and still the same: [18:39:10] INFO: Preparing to start.... [18:39:12] INFO: Socat not enabled [18:39:19] INFO: Starting Zigbee2MQTT... Starting Zigbee2MQTT without watchdog. [2024-10-23 18:39:46] info: z2m: Logging to console, file (filename: log.log) [2024-10-23 18:39:46] info: z2m: Starting Zigbee2MQTT version 1.40.2 (commit #unknown) [2024-10-23 18:39:46] info: z2m: Starting zigbee-herdsman (2.1.3) [2024-10-23 18:39:48] error: zh:zstack:znp: Failed to determine if path is valid: 'Error: spawn udevadm ENOENT'. [2024-10-23 18:39:48] info: zh:zstack:znp: Opening SerialPort with {"path":"/dev/ttyACM0", "baudRate":115200, "rtscts":false, "autoOpen":false} [2024-10-23 18:39:48] info: zh:zstack:znp: Serialport opened [2024-10-23 18:39:48] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload [2024-10-23 18:39:50] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352 [2024-10-23 18:39:50] error: z2m: Error while starting zigbee-herdsman [2024-10-23 18:39:50] error: z2m: Failed to start zigbee [2024-10-23 18:39:50] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions [2024-10-23 18:39:50] error: z2m: Exiting... [2024-10-23 18:39:50] error: z2m: Error: Error: Not supported, cannot set
/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:264 var er = new ERR_STREAM_WRITE_AFTER_END(); ^ Error: write after end at writeAfterEnd (/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:264:12) at DerivedLogger.Writable.write (/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:300:21) at DerivedLogger.log (/app/node_modules/winston/lib/winston/logger.js:231:12) at Logger.log (/app/lib/util/logger.ts:198:25) at Logger.info (/app/lib/util/logger.ts:211:14) at Znp.onPortClose (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:96:16) at Object.onceWrapper (node:events:632:26) at SerialPort.emit (node:events:529:35) at port.close.then.closing (/app/node_modules/@serialport/stream/dist/index.js:242:18)
Did you do everything from the beginning as I asked? .
Use the ID of the one under the path I marked for you earlier and show what logs pop up for you
Added after 2 [minutes]:
Failed to determine if path is valid - It appears that Zigbee2MQTT cannot verify that the specified path to the device (/dev/ttyACM0) is valid. This could be a problem with the configuration of the Zigbee device you are trying to connect to.
spawn udevadm ENOENT - This error indicates that udevadm (the command responsible for managing devices) was not found. This could be a problem with missing software or tools that are required for proper operation.
Error while starting zigbee-herdsman - Error starting zigbee-herdsman, which means that something in the Zigbee hardware control has gone wrong.
write after end - Attempting to write to a stream after it has been closed, which is an error in the code.
Same:
[19:05:51] INFO: Preparing to start....
[19:05:54] INFO: Socat not enabled
[19:06:02] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-10-23 19:06:28] info: z2m: Logging to console, file (filename: log.log)
[2024-10-23 19:06:28] info: z2m: Starting Zigbee2MQTT version 1.40.2 (commit #unknown)
[2024-10-23 19:06:28] info: z2m: Starting zigbee-herdsman (2.1.3)
[2024-10-23 19:06:30] error: zh:zstack:znp: Failed to determine if path is valid: 'Error: spawn udevadm ENOENT'.
[2024-10-23 19:06:30] info: zh:zstack:znp: Opening SerialPort with {"path":"/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20231220134520-if00","baudRate":115200,"rtscts":false,"autoOpen":false}
[2024-10-23 19:06:30] info: zh:zstack:znp: Serialport opened
[2024-10-23 19:06:31] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2024-10-23 19:06:32] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2024-10-23 19:06:32] error: z2m: Error while starting zigbee-herdsman
[2024-10-23 19:06:32] error: z2m: Failed to start zigbee
[2024-10-23 19:06:32] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-10-23 19:06:32] error: z2m: Exiting...
[2024-10-23 19:06:32] error: z2m: Error: Error: Not supported, cannot set
/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:264
var er = new ERR_STREAM_WRITE_AFTER_END();
^
Error: write after end
at writeAfterEnd (/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:264:12)
at DerivedLogger.Writable.write (/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:300:21)
at DerivedLogger.log (/app/node_modules/winston/lib/winston/logger.js:231:12)
at Logger.log (/app/lib/util/logger.ts:198:25)
at Logger.info (/app/lib/util/logger.ts:211:14)
at Znp.onPortClose (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:96:16)
at Object.onceWrapper (node:events:632:26)
at SerialPort.emit (node:events:529:35)
at port.close.then.closing (/app/node_modules/@serialport/stream/dist/index.js:242:18)
Without a reboot it will not happen
You know what, try using any address from the coordinator in the configuration, by the way if it was throwing up logs then use ezsp with zstack interchangeably.
Added after 3 [minutes]: .
Connect to usb 2.0 not 3.0.
Turn the whole machine off and on.
20-30 minutes of play.
The discussion addresses the integration of the AVATTO Tuya ZigBee 3.0 smart actuator and TRV thermostat with Home Assistant (HA) using the ZHA integration versus Zigbee2MQTT. The thermostat is detected by ZHA but lacks full control functionality, prompting recommendations to switch to Zigbee2MQTT for better device support. Users suggest running both ZHA and Zigbee2MQTT simultaneously with separate coordinators, preferably Sonoff Zigbee 3.0 USB Dongle Plus (non-V2) for compatibility. Detailed guidance is provided on configuring Zigbee2MQTT, including disabling ZHA, creating a dedicated MQTT user in HA, installing and configuring the Mosquitto broker, and correctly setting the serial port path and adapter type in Zigbee2MQTT configuration. The importance of matching MQTT credentials and avoiding special characters in passwords is emphasized to resolve authorization errors. Troubleshooting logs reveal common errors such as invalid serial port paths, missing udevadm utility, and adapter driver mismatches (zstack vs. ezsp vs. ember). The Sonoff Dongle Plus V2 requires specifying the 'ezsp' or 'ember' adapter due to different hardware. Users report persistent issues with Zigbee2MQTT startup and MQTT connection refusals, despite following step-by-step video tutorials and configuration advice. The discussion concludes with encouragement to persist, consider a second coordinator for stability, and verify all configuration steps carefully to achieve successful integration. Summary generated by the language model.
.
.
.
.
.
.
