You can install the beta driver through the ST beta channel if you are wanting to migrate the device now. Otherwise, the fingerprint should be uncommented in the production version by the time the automatic migration happens.
If it is listed as “Placeholder” in the IDE you are good to go.
I still have a few Zooz items that I’m waiting for Edge drivers for, but at this point with 9/30 approaching, my biggest concern is: How will I reboot my hub once ide/groovy is gone?
Plug your hub into a cheap WiFi plug and remove the batteries if it is a v2 hub.
I never put batteries back in it after the first set leaked and it is not easily accessible (in my attic), and yes that will work if you are home but does not work when not connected to the wifi.
That depends on the outlet. I’m using a cheap one that works through the Alexa app from anywhere. My only complaint is that it doesn’t automatically turn back on after a power failure.
Excellent question, but offtopic for this thread. Please start a new thread for this. Thanks!
Can you add this driver?
Metrics * Received Messages From Device: 32
- Received Messages From Device (Duplicates): 0
- Messages Transmitted to Device: 32
- Messages Transmitted to Device (Failures): 0
- Updated Time: 2022-08-19 6:26 PM WEST
Data * networkSecurityLevel: ZWAVE_LEGACY_NON_SECURE
Raw Description zw:F type:1005 mfr:0258 prod:0003 model:1088 ver:2.94 zwv:4.38 lib:06 cc:5E,86,72,5A,73,70,85,59,25,71,87,80
Current States * alarm: off
- tamper: clear
- battery: 100 %
- switch: off
checkInterval: 7320 s
Preferences (edit) Name Type Value
alarmLEDflash bool false
tamper bool false
I don’t know what device this is and I don’t think I could add it
If you want to get more answers it is better to offer all the possible details of the device and if possible the DTH you are currently using
It’s a Neo Coolcam Z-wave Siren
Since you have a z-wave siren driver I thought you could do it!
The driver is the stock one with some changes for ecolink sound firefighter
I’ll look at it tomorrow, if adding the fingerprints is enough I’ll do it and let you know
This device is the stock driver Z-Wave Siren
Link to GitHub to search in fingerprints.yml file of the driver you need:
- open file
- click on search in Page
- write manufacturer number 0258
- get all devices with this manufacturer in the file
- id: 0258/0003/1088 deviceLabel: NEO Coolcam Siren manufacturerId: 0x0258 productType: 0x0003 productId: 0x1088 deviceProfileName: alarm-battery
Will be migranted automatically when groovy end
So something is going on because I added it, but it doesn’t work… I simulated triggering the alarm and the siren didn’t go off…
It won’t let me control the siren… On and off…
That’s why I thought I didn’t have the correct driver and asked you!
Just like the Neo Coolcam socket I asked you above… It adds like a Switch, but it doesn’t give me the power consumption which is important…
Request for Edge drivers for Secure SRT323 and Secure SRT321 (I have one of each).
I currently use Aonghus-Mor’s custom Groovy driver.
I am nervous now that the end-date for the Groovy is set for September.
Here is the Raw description from ‘Show device’:
zw:S type:0806 mfr:0000 prod:0000 model:0000 ver:4.00 zwv:3.67 lib:06 cc:72,86,80,84,31,43,85,70,42,40
Edit: I believe mfr should be 0059, prod should be 0001, and model should be 0004 and 0003 respectively.
Edit 2: Unfortunately, while attempting to install my own Edge driver I have confirmed that ‘my’ SRT323 reports: mfr:0000 prod:0000 model:0000
The good news is I am able to associate the driver with the SRT323. The bad news is the driver is not functional. I need to add more logging tomorrow.
Apologies if this is covered elsewhere.
Update: I now have a functioning Secure SRT323 Edge driver. It seems to do everything that the custom groovy driver but runs locally.
I also have an semi-functioning Secure SRT321 Edge driver. The SRT321 receives set point vaues send from the SmartThings during wake up handling (normal behavior)
Unlike the SRT323, SmartThings does not receive unsolicited temperature, operating state (binary switch), or set point changes from the SRT321. Instead, I have included a Get in the wake up handler to trigger temperature reporting.
In future I might add a Get for set point but I would much prefer configure the SRT321 to send such changes.
Update 2: With help from @philh30 and other folk, I now have a working Edge driver for both Secure SRT323 and SRT321 thermostats based on, but not integrated into (yet) the community Zwave Thermistat Edge driver. They are not the prettiest, but are functional. I will be uploading to GitHub soon (another learning objective
All devices that are on the stock beta drivers should work when the migration is done.
If you have tried this driver and it doesn’t work, you should open a new thread to tell what is happening and have it fixed before it goes into production driver.
If you mean where to write the zwave siren driver problem? here or in a new one that you open
Assuming one doesn’t exist, can one be made for Remotec zxt-600?
Is there a way to look at the fingerprint at large to see if you driver already cover our existing device ?
Could save a lot of question / request
please can the SONOFF ZBMINI-L be added to a driver , thanks