I found that model really interesting, so, I might get one of those soon = P.
I added the fingerprint at the button-battery-v1.3.1 from the @erickv Shared Drivers channel, but I’m not sure that every feature will work as expected, especially the built-in dimmer, but I have high hopes that the button will report acordingly.
However, it would be great if you could share with me in a PM a set of logs while interacting with the device (dimmer and button), just to check if reports button events as expected and how dimmer events are generated.
Logs can be tracked through the SmartThings CLI with this command:
That is great, thank you soooo much. I will install and have a look and share the logs with you. I think it is a really cool device too, so hopefully it will work
If you don’t have a Zigbee hub what would you propose to pair the Zigbee device to?
Smartthings can control wifi based devices that are connected to the cloud.
Zigbee devices need a local hub.
Nice =] I’m glad that main functionality is covered.
That’s understandable, because handling level events are not programmed at all.
In this context it would be important to track these dimmer events, so, let me collect some info for you so you can get started very quicky with the CLI.
Also… are you planning to use the device with a specific bulb?
Following up, let me share with you basically the most essential requirements to get started with the CLI:
NodeJS(during installation, make sure to white list any option that points Node being available at your PATH).
Once you install it, you’re ready to install the SmartThings CLI through your terminal:
npm install --global @smartthings/cli
and then:
smartthings edge:drivers
This last command may prompt you to the SmartThings Login, but is a one-time process to set up permission.
After this, you’ll be able to query basically everything regarding your SmartThings environment and, of course the edge:drivers:logcat command I shared before, i.e.:
* You can get the IP Address of your Hub at your Hub details in the Groovy IDE or DHCP server ** To avoid cluttering this thread, you can send me the logs through a PM
At this point I’m quite confident that my driver can handle the 4 Moes models so, if you’re able to share the fingerprint at this thread, I can add support for it and will notify you as soon as posible =]
Thank Erick. I live in the UK and can only find the Moes Wifi single gang switch (not the zigbee one) so before I can order the Wifi switch, can you let me know what a fingerprint is? I am not a developer so excuse my ignorance.
Hi,
this thread is about “scene switch” remote controls , i.e. things that look like this or similar (see below).
I think you are referring to a wired wall switch, which is different?
In general terms, the fingerprint is device metadata to identify it across the Zigbee network and the platform (this is only a raw description tho, I’m sure theres a better description for it =P). For example:
And to be able to match a device with an edge driver, we only need the manufacturer and model values.
These can be tracked from the Groovy IDE once you’ve paired the device without having drivers or dth that match with it.
Try looking for it at the MOES AliExpress store (link here), that where I got my zigbee scene switches.
Many thanks Erick, clear on what a fingerprint is. I have an Yagusmart 2-gang zigbee switch so if I provide the manufacturer and model, would you be able to add it to your Edge driver and provide it to me?
An edge driver can only handle one protocol as far as I know. So it will be for Zigbee or Z wave or Wi-Fi LAN but you can’t use a Zigbee edge driver with a Wi-Fi switch even if they physically look exactly the same on the outside.
The First rule of home automation still applies to edge drivers: “the model number matters.“