Did you follow the instructions in the manual. This device doesn’t even have a battery so it only has the power to transmit and receive when you press a button.
The instruction manual has a combination of long and short presses you need to do while the coordinator is in scanning mode to make it join a network.
Yes I follow the user guide carefully, but it’s not very easy and could lead to some issues.
This is the reason why I’ve bought and tested today another similar switch:
I have not seen many tuya that are true zigbee standard most are tuya nonstandard ZigBee and have issues with the standard OpenHAB Zigbee binding.
From your link it states this
“Control your smart devices such as lighting, roller shutters and more using Tuya Zigbee scenarios with the MOES wireless, battery-free switch.”
Anyway, because I can’t pairing none of these devices with piezo effect, I was wondering if there was something specific in the Zigbee protocol, related to green power, that could prevent to support them ?
Are you aware about something ?
I’ve already requested Nodon support that answered me that they didn’t try on OpenHab.
Do you know where I could ask my question ? Maybe something is wrong with the Dongle or with the coordinator ?
just reading what you posted says a lot.
Does not work with
Home Assistant strike 1
Jeedom strike 2
Zigbee2MQTT strike 3
and you are out!.
Nonstandard!
Normally when I have a Tuya branded Zigbee device that the standard OpenHAB binding did not work with I was quickly able to pair it up and use it in Zigbee2MQTT but your device is clearly even more nonstandard since it does not support Zigbee2MQTT or even HA so it must be Tuya proprietary. Or so new that no one in any of the “big 3” communities have looked at creating the device profile. I do not think it is a dongle or a OpenHAB configuration issue. I think your device just has such a nonstandard implementation of the Zigbee protocol and very little market penetration at this point no one has reverse engineered its nuances to make it work on any of the main platforms. You may have some luck reaching out to the Zigbee2MQTT community to see if someone there has looked at it or is attempting to create a device profile Heck, they may even be able to guide you to running through some debug efforts to get it working in Zigbee2MQTT. They are very receptive and love adding new devices to their supported list.
Thanks for your answer.
I will send back MOES device, I agree with you it was the bad choice.
However the first device for which I created this thread, the nodon device, should work right ?
I have other nodon devices that work.
By reading your answer, I understand that it’s maybe better to add Zigbee devices through Zigbee2MQTT instead of the Open Hab Zigbee binding. Is it true ?
Do you know if I can have the both way to do at the same time ? So that I could setup Zigbee2MQTT, test if my nodon switch is working, without removing the existing Zigbee binding.
You would need 2 coordinators for that and you have to decide for each device to which mesh it should belong. This means you would have two completely separated zigbee networks (which doesn’t make much sense imho).
Both solutions have advantages and disadvantages actually. So, no it would not be a true statement to say that use of ZigBee2MQTT over the OpenHAB Zigbee binding is better or preferred. If all the devices you have are all fully Zigbee compliant and the OPenHAB Zigbee Binding is able to discover and control them then from a user perspective, you might find it is easier to configure items and such using the binding.
However, if you have a need to have MQTT devices and support then having a broker and the Zigbee2 MQTT solution might be a good way to expand your home automation solutions flexibility. Since a MQTT broker (such as Mosquito) Can handle other MQTT events and present them for OpenHAB to consume it does increase versatility.
Of course, it means you have 2 other applications outside of OpenHAB you have to maintain and insure they are functional regardless of whether you are running them on the same hardware as OpenHAB.
It is also important to point out you mentioned you are running on a Raspberry Pi 3 That could present resource limitations as you expand your home automation solution and as you upgrade to later versions of OpenHAB so you should consider that as well when you make your choices.
As was mentioned already only one coordinator can be used at a time for each Zigbee solution OpenHAB Zigbee binding is one Zigbee solution and Zigbee2MQTT is a separate Zigbee Solution. And yes, you can run both solutions at same time with 2 different coordinators. As for if it makes sense that is a personal preference really. Just keep in mind a device can only be paired with one coordinator at a time. Additionally, you will need to make sure that each Coordinator is on a separate channel Ideally as far apart a channel number as you can define them (i.e. one on channel 11 and say other on channel 22) Also keep in mind some Zigbee channels overlap with Wireless and that too can cause some interference on either ZigBee or wireless spectrums in use so should you go that route to help prevent interference do a little googling and read about RF spectrums and coexistence of ZigBee and Wireless it will help you understand the nuances.. Other than that, there really is no other major challenges to consider.
Hope that helps answer your questions.
