I have same problem with my monoprice motion sensor thought it was just broken I will hope to hear of fix mine seems to stay stuck active but never goes back to inactive so never sends motion back to hub
@bobbyD why are all the official integrations not here? I cant find the August Lock Pro, the CT101 thermostat, and many official devices, but I see some official integrations, such as IFTTT and ecobee?
I'm having the exact same problem. Has anyone gotten the Monoprice Motion/Temperature Z-Wave 15271 working with Hubitat C7? Are there any custom drivers for it?
If you can live with just Motion sensing, I was able to get it to work with hub firmware 2.2.2 and the Generic Motion Sensor driver (the one without Temperature). I was never able to get it to work using the dual Motion / Temperature driver. Also, I had tons of problems with 2.2.3, and I don't recall if any version worked on 2.2.3. Hopefully when 2.2.4 is released, the driver problems will be fixed and it can work for both Motion & Temperature.
Does anyone know of a custom driver for the GE ZWave Dual Plug Plug-in Outlet (ZW4015). The built-in "Generic Z-Wave Outlet" provides the basic controls (controlling on/off for both the left and right plugs simultaneously), but doesn't have the ability to control them independently.
Just a short question. I've seen the IKEA Trådfri Driver for wireless control 10w as compatible device on this list. So that there is no link to a community driver, I suppose, that it works with an existing driver. Question is, which one? Generic Zigbee Bulb?
I have some drivers to be released. When I checked the list, I found that parts of the products supported by the drivers have been released (I don't know who released them and there is no previous driver). I think that new products information should be directly added to the original driver. Which administrator should I contact? What should I do?
You can always manually change to the driver (hit configure after doing so) even if it doesn't contain the fingerprint. Fingerprint is more for the automatic matching of drivers to devices at initial pairing than anything else.
I understand what you mean, but for non-professional users, it is more inclined to automatically match the drive. Therefore, it would be better if these fingerprints can be added to the most suitable driver.
I’m still a little unclear. Are you asking if it’s possible to add device fingerprints to a hub built-in driver so that they are automatically assigned to the device upon pairing?
@mike.maxwell has added fingerprints to the drivers based on user input in the past.