Any progress out there on controlling wifi stuff? I don’t think I’m alone in having use for this, it’s perfect for a more distributed system than z-wave…
If there still is no plug in, can anyone tell me how to command On and Off to a tp link HS100 in Lua?
[quote=“Forzaalfa, post:1, topic:199174”]Any progress out there on controlling wifi stuff? I don’t think I’m alone in having use for this, it’s perfect for a more distributed system than z-wave…
If there still is no plug in, can anyone tell me how to command On and Off to a tp link HS100 in Lua?[/quote]
There used to be a plugin but it was pulled…
There’s a semi working remake out there on git hub.
The best I came up with was use Node-Red in the middle and using Lua with http commands and virtual switches and scenes to call the Lua to interface to Node-Red which has a interface in their repo to talk with tp-link plugs.
How do I find the remake? Link?
I have a beagle board xm Tha should run node red just fine, so I think I’ll do it like you… So silly that this functionality isn’t in Vera yet!
[quote=“Forzaalfa, post:3, topic:199174”]How do I find the remake? Link?
I have a beagle board xm Tha should run node red just fine, so I think I’ll do it like you… So silly that this functionality isn’t in Vera yet![/quote]
Not in Vera yet? Umm…
To do the integration you will need to have a virtual switch for each plug. Install the virtual switch from the app store. Then create a virtual switch for how ever many plugs you want to setup. Then create a Scene. 2 per plug. 1 for ON and one for OFF. In each of those scenes you will have some Lua code that calls out to an OS or to a Luup function to perform the action that you want. That will be the starting point. Then on your beagle bone or pi you will need to have node-red running. You will then have to create a flow for each plug with an entry point (probably http) a service you are expecting, the input/outputs translate to boolean and have the flow send that to the plug handler which will then send out a message to the plug translating to on or off. Then have a response handler waiting for the status to then return back to your Lua code (if you want a response).
Or you can say never mind and go buy some z-wave plugs.
Another alternative is to set up a secondary automation system for things not supported on Vera. I happen to use openHAB, but there are other choices such as Home Assistant. openHAB does have a binding for TP Link (I have not personally used it). I set up some simple bridge commands between openHAB and the Vera. openHAB has a binding for the Xiaomi gateway that I will be using soon that isn’t available on Vera. A secondary automation system gives you some insight into the pros and cons of Vera and helps build out a more complete automation system. But it’s not trivial to do this.
What I mean by “Not in Vera” is that the functionality in Cybrmages old plugin should be native. They list wifi as a sensor interface, so it should have more of the popular devices supported as standard.
The reason why im looking in to these is that i have a VeraPlus at our cabin, which is one of 3 buildings with about 60 meters between them. I want to control some stuff in the other buildings as well, and as they are all connected to the same network (long ethernet cables), a wifi switch or two seemed to be the best solution.
Z-Wave works well within a certain range, but i’d need several repeaters to cover all buildings, and that seems excessive for just a few switches in the other buildings.
I have looked into other controllers like openHab and Domoticz, and may still end up with that, but i would prefer one interface to the total system, and one logging system as well.
I think i’ll try the Node-red path first, if there is no simpler solution. thanks for all the input!
It sounds like you need an additional Vera in each building.
I have a similar configuratio?n at my camp, and connected the two locations via wired ethernet. The extra Vera is also the access point for wifi at the workshop.
It’s not well documented, but I have the 2 Vera’s and the router all using the same SSID and password.
[quote=“Forzaalfa, post:6, topic:199174”]What I mean by “Not in Vera” is that the functionality in Cybrmages old plugin should be native. They list wifi as a sensor interface, so it should have more of the popular devices supported as standard.
The reason why im looking in to these is that i have a VeraPlus at our cabin, which is one of 3 buildings with about 60 meters between them. I want to control some stuff in the other buildings as well, and as they are all connected to the same network (long ethernet cables), a wifi switch or two seemed to be the best solution.
Z-Wave works well within a certain range, but i’d need several repeaters to cover all buildings, and that seems excessive for just a few switches in the other buildings.
I have looked into other controllers like openHab and Domoticz, and may still end up with that, but i would prefer one interface to the total system, and one logging system as well.
I think i’ll try the Node-red path first, if there is no simpler solution. thanks for all the input![/quote]
If you have network between the two locations I would use another vera plus and bridge them. The primary would see and control all devices in both locations.
As you have posted you are aware that Vera is very limited. Just because it was advertised doesn’t mean it actually works or is usable. Take bluetooth for example. Yeah Wifi devices and some basic features would be nice. For those use something else and bridge to Vera. I always ran a Home Assistant setup along with Vera for Wifi type devices. Home Assistant is very easy to setup, has a lot of native support for newer wifi and network devices. I still keep a pi with Home Assistant and Node-Red running for those odd things that I want to toy with.
A second vera would definately solve it, but as i only need a few env. sensors and 2 or 3 switches, a Vera/Z-Wave setup would end up costing about 10 times more than a few wifi switches and some ESP based sensors (i.e. mysensors)…
I will try to make the stuff i have work first, i’ll let you know how it works. ![]()