Todd, thanks as always for your amazing work and continued support. I think MQTT will indeed be the way I go.
I currently have a combo temperature and humidity sensor in my bathroom near my shower head. I’m trying to detect when the shower turns on by detecting a rate of humidity increase, and not rely on absolute numbers as the baseline humidity fluctuates throughout the year. I envision a rule that detects when the humidity has risen by greater than or equal to 5% relative humidity in the span on 10 minutes or less.
I guess a custom SmartApp could take care of this, but I’m not familiar with programming those and would much rather write something in Python running on my RPi4.
I envision utilizing your Web Req Multi Master device to trigger (every time the humidity changes) a script running on the Pi that grabs the humidity from the appropriate sensor and time stamps it. Then it looks back and identifies what the humidity was 10 minutes ago, and if it’s increased enough would then trigger the appropriate bathroom fan on, which I can do with your LAN Device Trigger, although I could probably also do it via MQTT.
Todd, are your vEdge and webrequestor drivers open source? I’m trying to write a driver for the Hunter Douglas PowerView generation 1 & 2 shades, and it’d be much easier to write it if I could borrow chunks of code rather than learn Lua from scratch. Thanks!
Many of my solutions are available as open source in my github repository. Should be plenty of things there you can lift from!
@TAustin I’m successfully using the Edgebridge, with LanMotion and wondered if you would consider creating a ‘LanContactSensor’ driver. I read you implemented the contact sensor capability in Shelly Motion but it was removed… I have tried myself by taking LanMotion and converting it to a contact sensor and everything works but I cannot get ‘open’/‘close’ to present in the dashboard, it just states ‘Connected’, I think its something to do with the metadata (vid) being the same as LanMotion, I’m happy to learn but I’m not a developer and think I’m not far off my technical limit. I see (and appreciate) you’ve got lots going on and I only ask as I think this would be a fairly quick thing (for you) to do.
I could probably knock this out within the next few days. Let me get back to you.
You may have already seen this, but this limit was just raised this week from 200 to 1000.
Smart Lighting (new plugin version) - #23 by vlad
Hi @TAustin, I’m looking to do the same sort of thing as @SlySi here and the contact sensor would be great to add to my smart home. Did this ever get created?
I will try to get to this within the next day or so.
You can now find a new LAN Contact driver on my shared projects channel.
It works just like the others: once you’ve enrolled in my channel, you choose to install LAN Contact Device Driver V1 from the list of available drivers. Once it is installed on your hub, the next time you do an Add device / Scan for nearby devices, you will get a new device created in your No room assigned room called LAN Contact Device.
This driver requires that you have edgebridge installed and running on a computer on your LAN.
Go into device Settings and configure the unique name, device/app address (IP:port), and edgebridge address (IP:port). It will register with your edgebridge server and then you can start sending it http requests from any device or app:
POST http://<edgebridge IP:port>/<unique name>/contact/[open | closed]
Let me know if you have any problems.
@TAustin That’s fantastic news, will get it tested and report back if I get any issues, really appreciate your time to add this.
Hi there. I’ve got a lantrigger driver that supports multiple triggers - up to 19, which is the maximum number of components I can define within a device (+1 for main). So now you can have a single device to handle multiple LAN triggers through edgebridge. You can also create additional devices, each with another 19 triggers.
I’ll put the driver on my test channel for now until you can try it out and make sure it meets your needs. Look for the driver named LAN Trigger Multi V1.0. Once installed on your hub, do an Add device / Scan for nearby devices and you’ll get your first device created which you can configure in device Settings for each trigger name/address combination, plus the edgebridge address (at the end). On the device Controls screen, you’ll see a list of all name/address combos that have been registered with edgebridge.
Let me know what you think.
@TAustin I’m getting the following from the Lan Contact Driver.
The Lan Contact Driver also picks up a motion sensor request but doesn’t like that either.
The LAN Motion Driver picks up the contact, although it cannot find a matching device there is no error.
The motion and contact sensors are both on the same ESP8266 and the http request is sent identically, it just replaces the device name and the value depending on what changes.
The contact driver expects a POST message, not a GET. Make sure your device is sending a POST message to edgebridge.
I can’t seem to find LAN Trigger Multi V1.0 driver, in the test channel
Sorry, missed the POST and assumed it was the same as the LAN Motion. All seems to be working well now, thanks for this, its really appreciated.
Can you check it again? Either I’m losing it or something flakey is going on, but it was not there. I just pushed it out (again??).
Yep, it’s there now, thanks
Are you familiar with Hubitat? Several users have migrated from SmartThings and we had a connector between the hubs until SmartThings ended groovy.
Just wonder if you could create some hooks between the hubs, Hubitat has a local API for devices but I don’t know enough about new SmartThings.
BTW: I have been using Edgebridge for a several weeks to monitor for offline status for the few devices I have on SmartThings that can’t be migrated. I really appreciate your work!