The other red wire plugs into the “W” slot. Also, there are two red wires-the one next to the blue wire plugs into the “R” slot. Take note that the white wire doesn’t actually plug into the “W” slot, but rather the “V+” slot. Here’s a photo of what the connections look like so that you can match it with yours. To do this, use a pen or small screwdriver to press down on the terminal, slide the wire into its slot, and release the terminal to lock the wire in place. To start, take the six wires on the end of the LED light strip and plug them into their respective slots on the controller module. For the simple case of connecting a smart light switch to a light group, you wouldn’t notice a thing.There’s not a whole lot you need to do to get it all up and running, and it takes about five minutes to put together everything. If they keep hitting the driver, then the driver will keep making requests. It would really come down to the automations you setup. There isn’t really much additional traffic from the driver on its own. To separate them, you would need multiple hubs. The drivers all connect to the Hue hub and not the lights themselves. Hue hub updates state internally for other drivers to request in the future.Hue hub processes the request and send the zigbee commands out to the lights.Edge driver gets an event and sends a request to the Hue hub (https).It is the same for most LAN connected hubs. So to simplify it, here is what happens when you interact with the driver. This driver technically doesn’t need a hub object, but there will be one to make managing settings simpler and to streamline discovery. This driver would be an additional connection. Your Hue hub allows connections from many different clients (ST, Hue App, Hue add-ons, etc). The “hub” used by both this driver and the ST platform driver is really just a stand-in for a network connection to the actual hub. So this gets tagged as an Edge Driver and put in the “community created device types” section of the forum, at least for now. The “writing edge type drivers “ section, which did get split off, is for developer questions. (By the way, you don’t need to use Hue as a tag if it’s also in the title, it would come up in the same searches.) Assuming, of course, that it is an edge driver and not a new smartapp. Instead, we add one of the edge tags, in this case lighting, so that people can see what it is and find it more easily in a search. By convention, it goes in the “community created device types” subforum because they never split off a separate one for edge Drivers. I moved it in the “Community Apps” group. Just want a good group to test it out since there are a bunch of device types and ways to setup Hue.Įxcellent! That definitely fills a lot of gaps in the smartthings Hue implementation. Plan to post the alpha in a few days one the automation pieces are done. Get rid of the “popcorn” effect inherent in the ST lighting groups.Group support in automations (ST groups don’t allow automations).Switch and dimmer control of Hue groups.Here are the current goals of the driver: If you are interested in trying it out with those caveats, please let me know and I will send you an invite once I publish the driver this weekend. They should not interact at all other than increasing traffic to the Hue hub. This driver can run alongside the ST platform driver for the Hue. It will likely get updated (and broken) frequently. The goal of the alpha testing would be to try it out in a wider variety of systems and get some feedback on robustness and features. This alpha driver is not intended for continual use and support. This also sends out group commands rather than individual light commands, so the popcorn effect is reduced if not completely gone. This will enable group level control of rooms/zones defined in the Hue app, as well as any scenes that are used by those groups. I am looking for volunteers interested in alpha testing an Edge driver for the Philips Hue Hub.
0 Comments
Leave a Reply. |