The Zigbee profiles that smartthings uses only allow for one primary coordinator per network, so you will not be able to add another brand’s Zigbee hub to your smartthings network, regardless of brand.
oh right thanks
I would like to see a device driver for enphase envoy (solar).
Would like current power and total energy produced.
Would be nice to super cool/heat the house with excess solar or raise or lower hot water set point.
May I request an Edge Driver for Remotec ZXT-120. The ZXT-120 is a Z-Wave to air-conditioner (AC) IR Extender. I have recently excluded it, and upon inclusion, it doesn’t lock to any edge driver? Only the generic z-wave thermostat which doesn’t seem to any remote code capability.
- manufacturer: Remotec Technology Ltd
- networkSecurityLevel: ZWAVE_LEGACY_NON_SECURE
- productId: 33655
- productTypeId: 256
Raw Description zw:L type:0806 mfr:5254 prod:0100 model:8377 ver:1.20 zwv:3.42 lib:06 cc:20,27,31,40,43,44,70,72,80,86
Its not likely worth the time to support such an old device on Edge. Looking at the manual for the ZXT-120, the customization needed to enable the programming modes isn’t trivial. All for a 1 way IR integration on a Zwave (non plus) device.
For IR control of AC units on SmartThings, many people recommend the SwitchBot mini. Its cheap and you’d have plug and play solution. Its not local of course (requires the cloud) but its an easy solution.
This will likely pair as a standard zwave switch, once the stock Edge drivers are taken out of beta. They’ll enable the match by device class logic at that point instead of requiring an exact fingerprint.
This device requires HAIL support for the hub to see changes made to the switch at the device, which the stock Edge drivers no longer support. Using HAIL was Leviton’s Zwave (non plus) workaround for the Lutron patent that is now expired. You could also get around the patent by hubs polling the device, which also sucked for other reasons.
I don’t know why the on/off feature isn’t working as it should just be a regular binary zwave update. But the hail issue makes it not worth figuring out.
My suggestion is to replace it with a newer zwave plus device. You’ll get much better performance than trying to work around zwave 300 series implementation issues.
Thanks for the suggestion, will look into this
Thanks for the explanation. Part of the issue is that I utilize the dimmer with a magnetic low voltage dimmer appliance, and a lot of the Z wave dimmers available are triac dimmers that are not compatible. It looks like the Eaton RF9640-NDW works with magnetic low voltage dimmers so I’ll give that a shot.
Has anyone had any luck getting the Smarter Ikettle 3.0 working?
Their customer support said they would look into it years ago. It seem now however they have no interest in smartthings
I currently use Alexa Iftt and virtual switches but direct SmartThings would be great
I have the Hampton Bays Fan Controler (King of Fans Zigbee Fan Controller). They stopped responding although both appear online in both google home and smartthings. I see several requests for an edge driver, but couldn’t find that it has been handled. Sorry if this is a duplicate request for something resolved, but I would appreciate being pointed in the right direction. Thanks!
I was looking to see if someone with experience can update this groovy app for twinkly smart Christmas lights to the new edge drivers. Attached is the link to the form , and one of the last entries was a GitHub update for the current work. I did a message on that form but have not received any updates since October, and it’s finally Christmas time, and I wanted to see if I could get it updated. Thanks in advance for the help. Twinkly Christmas Lights
Will your driver also work with “Asus Z-Wave Smoke Detector SHRM10000”?
It’s AFAIK a rebranded “Heiman HS1SA-Z Smoke Sensor”.
Works in ST Hub with “Z-Wave Smoke Alarm” generic driver (had to choose manually in IDE).
Raw description is:
zw:Ss2 type:0701 mfr:0403 prod:0002 model:0003 ver:3.01 zwv:5.03 lib:06 cc:5E,6C,55,9F sec:86,85,8E,59,72,5A,73,80,71,84
Added to this driver version
Try if it works
─────────────────────────────────────────────────── Name Z-Wave Smoke Alarm-Mc Version 2022-11-26T15:55:09.731420425 ─────────────────────────────────────────────────── - id: 0403/0002/0003 deviceLabel: Asus Smoke SHRM10000 manufacturerId: 0x0403 productType: 0x0002 productId: 0x0003 deviceProfileName: smoke-battery
I have a Fibaro FGK-101 (product type 0x0700), which I use with an external temperature probe (I don’t use the open/close function). I have tried the various edge drivers, and can’t seem to find any that work correctly for the temperature function of the probe. Maybe I’m missing somethings?
If you install this driver it could works
Z-Wave Sensor and Child Thermostat Mc
thank you for the suggestion!
sadly, it doesn’t seem to work either (no temperature reading, and the contact sensor doesn’t register on/off status, also getting connecting error). When I then immediately switch back to the z-wave sensor (ST beta), the contact sensor is again functional, but obviously there is no option of a temperature reading, and no connecting error
I did try to take a picture of the error message, maybe that could provide a clue, hoping it’s a bug that can be fixed?
I don’t know how the device was paired with the driver.
If it was done with a driver change from the stock driver it is normal that it does not work.
To get it to work with the temperature profile you have to drop and re-pair directly with this driver.
In Zwave drivers, the configuration is not sent when changing from one driver to another driver to respect the custom configuration that could have been done with another driver. (zwave device config Mc, for example)
This has its advantages and disadvantages.
Try to exclude it and make it pair directly with this driver, there are other users who use it and it worked for them, that’s why there is this temperature option in the driver.
You may need to remove the stock driver from your hub.
These are things to polish in the new edge architecture.
Added preference and profile to show temperature in the tile in this driver version. Default option is open/close sensor
You need clear app memory cache the first time you change the profile
─────────────────────────────────────────────────── Name Z-Wave Sensor Mc Version 2022-10-29T19:03:15.341030072 ───────────────────────────────────────────────────
@makrisn You can try this driver that Mariano created. I use this with my Fibaro FGK-101 sensors with external temperature probes. I believe he has added prod code 0700 and 0701 to the driver.