Koen Kanters

Added it! Changes will be available in the [dev branch](https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) in a few hours from now.

TuYa uses non-standard commands, you will need to sniff the traffic with the original gateway and follow https://medium.com/@dzegarra/zigbee2mqtt-how-to-add-support-for-a-new-tuya-based-device-part-2-5492707e882d

@MUzair030 I don't have knowledge about TuYa devices, all I know is that they use a custom protocol (which makes integration very hard and time consuming). There are some people...

Pushed a fix, let me know if it works. Changes will be available in the [dev branch](https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) in a few hours from now.

I will probably do a hotfix release in the coming days, but good that this is fixed now! Changes will be available in the [dev branch](https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) in a few hours...

> Payload is not supported (e.g. open, closed, opening, closing, stopped): pause When is this logged?

@asan84 can you provide me your z2m configuration.yaml?

I think it's because of the `log_syslog`, can you remove it from your `configuration.yaml` and see if that fixes the problem?

@asan84 can you SSH into your system, execute the following and see if the issue is fixed? ``` docker exec -it $(docker ps | grep zigbee2mqtt | cut -d" "...

But it looks like the `/app/node_modules/winston-transport/node_modules/readable-stream/lib/_stream_writable.js:264 var er = new ERR_STREAM_WRITE_AFTER_END();` is gone now?