Gledopto GL-FL-004TZ - not supported - update the zigbee-herdsman-converters dependency

[volker73]

Hello,

I had a question within another forum.
You can find the whole conversation at the link below.

Koenkk/zigbee2mqtt#13680 (reply in thread)

or the summary here:

---

My question/ issue:

I am unfortunately a beginner in this area, although already have a few ZigBee devices in operation and all work with On / Off, color change etc..

I have now bought a LED floodlight "Gledopto GL-FL-004TZ", for which there is also a device sheet on your site.
There are apparently also several who have this spotlight successfully in operation.

The teach-in (connect) was no problem, it was also recognized.
I tried to switch the light on and off in different ways (JSON {"state: "on"}) but without success.

It appears constantly the message:
"Device with modelID 'GL-FL-004P' is not supported."

After the factory setting, there is a green light in the center of the emitter, but have not found any posts as to what this means.

I have also found the "Support new device" page. But this is beyond my capabilities!

I have a "RED MATIC 7.1.2" running on a RaspberryMatic.
I use "Z-Stack/ ZigBee Shepard"

What am I doing wrong?

---

Answer and solution by "Koenkk:

You are probably using an old z2m version, this device is supported in zigbee2mqtt 1.27.0

---

My answer:

I use RED NODE
and the ZigBee Node

• node-red-contrib-zigbee 0.20.0

Which Node should I use?

• node-red-contrib-zigbee2mqtt 2.6.3 for example?
  There are are lot of dependencies which I have to install before
  Or am I on the wrong track?

---

Answer and solution by "Koenkk:

node-red-contrib-zigbee is a different project, it does not use Zigbee2MQTT. I suggest to create an issue in this repo: https://github.com/hobbyquaker/node-red-contrib-zigbee and ask if he can update the zigbee-herdsman-converters dependency.

[Sineos]

This node here is probably abandoned.
I'd suggest to use pure zigbee2mqtt and work with mqtt messages in Node Red. This is the most flexible way with the least dependencies.

[volker73]

You mean "node-red-contrib-zigbee2mqtt 2.6.3" for example? Or is there another way? Am So., 28. Aug. 2022 um 17:57 Uhr schrieb Sineos ***@***.***

…

: This node here is probably abandoned. I'd suggest to use pure zigbee2mqtt and work with mqtt messages in Node Red. This is the most flexible way with the least dependencies. — Reply to this email directly, view it on GitHub <#171 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHBXCNVCDZWTBQTWM7IGJDV3OEADANCNFSM573IFMCQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Sineos]

Install zigbee2mqtt as per https://www.zigbee2mqtt.io/. Use standard MQTT nodes in NR to communicate with the devices. Nothing extra needed.

[volker73]

My first problem, I could not start "sudo or apt.." My login is "root" ***@***.***:~# sudo curl -fsSL https://deb.nodesource.com/setup_16.x | sudo -E bash - sh: sudo: not found I have found everything possible on the Internet but no solution for " sh: sudo: not found" Am So., 28. Aug. 2022 um 21:06 Uhr schrieb Sineos ***@***.***

…

: Install zigbee2mqtt as per https://www.zigbee2mqtt.io/. Use standard MQTT nodes in NR to communicate with the devices. Nothing extra needed. — Reply to this email directly, view it on GitHub <#171 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHBXCLHZK45HP7ZCE2HUXTV3O2EZANCNFSM573IFMCQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Sineos]

This will not work as integration in Raspberrymatic. Raspberrymatic is not a full Linux and this brings various issues with integrations.
I suggest to us a Node Red instance outside of Raspberrymatic and run things like zigbee2mqtt etc there. This will save you a lot of trouble in the long run.

[volker73]

Hello, just for my understanding and my last question. These LED emitters are not supported in this node "node-red-contrib-zigbee" although this LED emitter is listed in the official list at "Zigbee2Mqtt"? The teach-in worked without any problems But since a new version 0.21 of this node is already worked out the node can't be "This node here is probably abandoned" as you described. I can not delete all my other ZigBee devices and look for another possibility what costs me as a beginner very, very much time. I have even implemented a current stick (ZigBee 3.0 CC2652R) which runs without problems. If it's just that someone needs to implement this LED emitter in the node, *who should I contact?* kind regards Volker Am Mo., 29. Aug. 2022 um 11:58 Uhr schrieb Sineos ***@***.***

…

: This will not work as integration in Raspberrymatic. Raspberrymatic is not a full Linux and this brings various issues with integrations. I suggest to us a Node Red instance outside of Raspberrymatic and run things like zigbee2mqtt etc there. This will save you a lot of trouble in the long run. — Reply to this email directly, view it on GitHub <#171 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHBXCOA3SNQ7YNXZ6KZLHDV3SCSXANCNFSM573IFMCQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Sineos]

These LED emitters are not supported in this node "node-red-contrib-zigbee" although this LED emitter is listed in the official list at "Zigbee2Mqtt"? The teach-in worked without any problems

node-red-contrib-zigbee integrates parts of zigbee2mqtt. When zigbee2mqtt is updated, someone needs to update node-red-contrib-zigbee as well. If there is no one to update node-red-contrib-zigbee then you are stuck with an old zigbee2mqtt integration.

If it's just that someone needs to implement this LED emitter in the node, who should I contact?

As the maintainer is no longer active, there is nobody to contact.

My opinion:

• You will be stuck in this situation on every new device
• Sooner or later all might break because the environment is no longer actively updated
• Invest the work once and have a future proof setup

My personal lesson learned (not necessarily only from this topic):

• Do not use 3rd party integration if there is another way
• Use the original system (e.g. zigbee2mqtt) and interface to it with standard tools, e.g. mqtt etc
• Avoid 3rd party stuff that has not been updated for more than 6 months at all cost
• Especially node-red: Use as few 3rd contrib nodes as possible. In most cases you can reach the same goal with standard nodes

Since a few years my entire home automation is largely based on node red with around 30 flows and some hundreds of nodes. I have gone through such obsolescence topics a few times already and whenever possible I now use separate instances, avoid deep integrations and use as much standard as possible.

[volker73]

Thanks for your support and information. That means I have to search a new possibility for my ZigBee devices. Volker Sineos ***@***.***> schrieb am So., 18. Sept. 2022, 11:34:

…

These LED emitters are not supported in this node "node-red-contrib-zigbee" although this LED emitter is listed in the official list at "Zigbee2Mqtt"? The teach-in worked without any problems node-red-contrib-zigbee integrates parts of zigbee2mqtt. When zigbee2mqtt is updated, someone needs to update node-red-contrib-zigbee as well. If there is no one to update node-red-contrib-zigbee then you are stuck with an old zigbee2mqtt integration. If it's just that someone needs to implement this LED emitter in the node, *who should I contact?* As the maintainer is no longer active, there is nobody to contact. My opinion: - You will be stuck in this situation on every new device - Sooner or later all might break because the environment is no longer actively updated - Invest the work once and have a future proof setup My personal lesson learned (not necessarily only from this topic): - Do not use 3rd party integration if there is another way - Use the original system (e.g. zigbee2mqtt) and interface to it with standard tools, e.g. mqtt etc - Avoid 3rd party stuff that has not been updated for more than 6 months at all cost - Especially node-red: Use as few 3rd contrib nodes as possible. In most cases you can reach the same goal with standard nodes Since a few years my entire home automation is largely based on node red with around 30 flows and some hundreds of nodes. I have gone through such obsolescence topics a few times already and whenever possible I now use separate instances, avoid deep integrations and use as much standard as possible. — Reply to this email directly, view it on GitHub <#171 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHBXCLKQQPCRNORMF57NLDV63O3PANCNFSM573IFMCQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Sineos]

That means I have to search a new possibility for my ZigBee devices.

My proposal:

• Get a small Linux box, RPi 3 and above, Orange Pi, Old NUC, whatever. You do not need much power
• Install mosquitto
• Install zigbee2mqtt
• Work in node-red with mqtt in and out nodes