The curious is. That FP is based on thing edition to ZIGBEE VALVE stock device handler, but in this case Amazon Alexa will NOT get as new device, so… does not exist at the platform.
Then i tried changing to average ZIGBEE SWITCH DH and… Bingo! Alexa ready!
Do you think adding the fingerprint to your Zigbee Valve MC will allow alexa to find it? if not, what´s the best solution? Add to any average switch like that or find the “alexa issue” on Valve driver?
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Valve Mc │
│ Version │ 2022-03-16T21:54:51.044256 │
└─────────────┴──────────────────────────────────────┘
I do not know.
If not works could try adding it to the zigbee switch driver
Firstly I would like to send a big thank you to @Mariano_Colmenarejo!
I have a Lidl Silvercrest 3-gang power strip and your edge driver works like a charm. It’s so great to have people like you here providing all of us with drivers for free.
I have two minor things to ask for, maybe it’s possible to support this:
Firstly, with the old DTH I used formerly I saw the three outlets as separate devices. I found I can change the setting to show all three plugs in the SmartThings app, but sadly only the “main plug” is showing up in Alexa devices. I have some Echo routines where it would be great to also again make use of the 2nd and 3rd outlet.
Secondly, would it be possible to let the user customize the name of the three outlets? With the old groovy DTH I could name each “device”, which would of course be great if that would also work with the new edge driver.
Again, thanks a lot for your work and cheers from Germany,
Christoph
These are two requests that have been made to smartthings by various users.
Hopefully they can give us a solution.
Currently the only thing that can be done is to use 2 virtual switches and with automations to synchronize the state and actions of switch2 and switch3 with the virtual devices.
Also to facilitate the control of the three switches without opening it, you can choose in preferences a multiple mosaic with the 3 switches and the all switches
Thanks a lot for clearing things up for me. So we have to hope the SmartThings team will adress this in the future. In the meantime the work-around with virtual devices will be sufficient for me for scenarios where local execution is not the goal anyway (ie Echo routines).
Best regards!
Ikea’s CWS color bulbs don’t work in my driver or stock as they use the currentX and currentY attributes.
In the driver that smartthings will be updated shortly, I hope, there will already be the ikea CWS bulbs and from what I have seen in the code, it seems that they will use default utils libraries to convert standard Saturation and Hue to X, Y values.
I don’t know if the default libraries to handle those colorControl attributes will be updated in the last beta 42.5 firmware.
We’ll have to wait a bit, I don’t want to waste time doing something, what are they supposed to do
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Light Multifunction Mc │
│ Version │ 2022-03-28T11:14:02.827217 │
└─────────────┴──────────────────────────────────────┘
Thanks for that info, makes perfect sense.
I work in IT was my day job, so I’m all to familiar with this type of thing; no sense spending time on something until the base drivers handle it.
I’ve been debating signing up for the beta firmware.
I have 3 eWeLink MS01 motion sensors connected with the Zigbee Motion Sensor Mc driver that keep going offline. Sometimes they come back with a motion event but they have been offline since yesterday afternoon.
I saw another post regarding issues with another zigbee edge drivers after driver updates and am wondering if this related or a seperate issue.
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Multi Switch Mc │
│ Version │ 2022-04-02T11:47:02.045555 │
└─────────────┴──────────────────────────────────────┘
(NEW RELEASE) Version 4 of the Edge Beta Driver: Zigbee Motion Sensor Mc Improvements:
Application of the specific formula for calculating the percentage of remaining battery for Smartthings (Samjin) motion sensors:
1.1. The driver used the standard zigbee formula for calculating % of battery. (percentage = Raw_value.value / 2).
Observed that with 30% of battery, approximately, 2 sensors begin to give false warnings of detected movement.
1.2. The specific formula for Samjin is applied as the DTH stock and the next stock driver.
The value corresponding to that value 30% now is 0%.
local raw_percentage = raw_value.value - (200 - raw_value.value) / 2
local percentage = utils.clamp_value(utils.round(raw_percentage / 2), 0, 100)
1.3. Batteries are replaced and false motion detections are no longer sent. Batteries CR2 works fine for 2 years.
Because some users of the MS01 and ms01 eWelink sensors suffer from inactivity disconnections, similar to the aperture sensor eWelink, the same solution applies.@Terri_Baker
2.1. Run a timer to emit event with the last state of these sensors.
As the driver has a new subdrivers, the update will not be done automatically.
I have tried to update it without changing driver ID and the update does not work correctly. Don’t want anyone, at midnight, wake up due to the updated motion sensors
To facilitate the update, I am going to change driver version 3 to the name Zigbee Motion Sensor Mc-(OLD).
I will publish the new version 4 with the original name Zigbee Motion Sensor Mc
In this way, your driver installed will renamed with (OLD), indicating that there is a new version available and you can install the new version with a driver change whenever you want.
This is the new version
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Motion Sensor Mc │
│ Package Key │ zigbee-motion-sensor-v4 │
│ Version │ 2022-04-02T12:07:15.212298 │
└─────────────┴──────────────────────────────────────┘
