First, I'm too ignorant to know how to install an app like this to work. I can only assume you are referring to the last post where it states how to add an app that refreshes the status of switches I guess on a pretty frequent basis. As another poster commented, it didn't work. I did read that and tried the first suggestion of changing the few commands. But that thread describes both the issue and ways to address it. So it takes some finessing to do what you’d like to. ![]() Please read the thread I linked to above.Įdit: The Tapt doesn’t conform to the ZHA1.2 standard. Does anyone know what the the trick is to accomplish this? The HUB would need to know what the status of the TAPT light is to trigger the other lights accordingly. If you turn it off at the light, the HUB doesn't receive that information and thinks it is still on. That is, the status of what the TAPT light is in does not go back to the HUB. I'm sure I can setup a rule to do that, but there is one major problem. However, the whole reason for having a Tapt light where I do is to turn on and off two other lights that are in close proximity. ![]() I can turn it ON and OFF from the hub, which is great. Anyway, I leveraged the driver code and added it to the Developer Tools accordingly, repaired the Tapt light using Zigbee and then selected the new driver code and it does work. I've had some success, but surprised how complicated this has gotten for a consumer product. ![]() You need to reset it, and re-pair it as a regular Zigbee device. Switched to the "nue zigbee switch" driver. I've used virtual motion sensors to test automations (easier than waiting for a real one to switch between active and inactive). For example, I have a "Virtual Vacation" switch that I turn on (manually or via voice/Alexa) when I want some of my automations to work differently-e.g., don't turn this smart outlet off at 8 AM like it would if the "vacation switch" were not on. Virtual devices have several uses, but in no case would you use a virtual driver for a "real" device-virtual devices exist only in Hubitat, and you can use them for either testing, working around things that don't work with "real" devices (often no longer needed but once useful for multichannel devices before Hubitat or ST supported child devices), or storing information like using the state of a virtual switch for an automation that can be restricted based on switch state (for example). The DTH linked to in the above post might work if ported to Hubitat (from looking at it, it looks like it might work verbatim, but no guarantees).Īs for virtual devices, they will not help you here. From the post below yours and above this one, it sounds like this might not actually work anyway since the Quirky switch is.quirky and might not work like most other Zigbee switches do. The only thing you'd need to do afterwards is try and see if it works. ![]() Nothing is supposed to visibly happen when you hit "Configure" the driver just sends some information to the device that it may need to work properly after a driver change. Yeah, nothing happens when I hit "Configure" I tried using the Type "Virtual switch" and it turns it on and office via the device and I see it's on/off via the dashboard but it's still not working, when I look at the light, nothing is turning on or off also TBH i'm not sure why or what's the point of the virtual devices.
0 Comments
Leave a Reply. |