Looking for a simple solution that doesn't require running wire (replacing a switch receptacle is fine)
The problem: the only light switch in my garage is not near a door. So have to walk into the garage to turn the lights on.
Ideal Solution: physical remote I can stick on the wall next to the door to toggle a switch. Is there a product that is a toggle switch to replace the basic switch in the receptacle that I can also operate with a remote?
Is anyone actively developing anything on these IoT chips?
In particular, using NodeMCU for Lua programmability?
Just got a development board to play with myself...
After a fruitless search for WiFI pulse utility meter readers (can't believe I couldn't find anything suitable) and also having resolved a while ago not to include any homebrew hardware in my HA configuration, I've decided in the end to try this out, after all.
Having cut my teeth on Lua, thanks to Vera, it seems promising to use it for development, rather than Arduino programming, and the hardware is SO much cheaper, smaller, and neater than a RPi or the like.
Any experiences welcomed!
Shelly i3 is an unbelievably cheap (9,99 EUR/USD) WiFi device that’s part of the fantastic Shelly family. It supports REST API, MQTT and much more.Shelly i3 Shelly i3
Downloads Manuals App Guide User and Safety Guide Certificates & Declarations Declaration of conformity Declaration of conformity - DE What is Shel...10
It’s just L,N and 3 inputs. No relays, so it’s a scene controller with bonus point to the fact that you can use your own buttons and keep the aesthetics of your house. Bonus points for WAF. It’s very small, so it will fit in your standard wall box easily.
While I built my own Scene Controller Virtual Device and I’m using MQTT for other devices of the family, Shelly can call your HTTP endpoints on button presses and in this case is more than enough.
The buttons support different actions (press, long press, double/triple press) and you can just call a service endpoint, or update a variable:
Go get it if you need a very cheap, very reliable scene controller for your home.
Finally, I’ve found an adequate replacement for my beloved MiniMote four-button remotes (I’ve had nine of them for the last 10 years or so!). I should have realised this earlier, but with four buttons and approximately the same form factor, the Philips Hue remotes are viable replacements…
…however, they are, of course, Zigbee and not Zwave, but this doesn’t matter in my HA environment, which has now completely ditched Zwave and Vera for all lighting and control functions, and replaced them with Hue and Shelly devices. These are all brought together with a Homebridge installation running under Docker on Synology NAS with the Apple Home app as the UI. This gives, of course, both secure remote access and voice control.
The MiniMote buttons I had configured as scene triggers to do whatever I needed, most usually toggling lights. The same functionality is easily achieved within the Home app by appropriate shortcuts.
I’m still using openLuup as a secondary hub which mimics all the various devices using MQTT and the ALTHUE plug-in and logs all device and sensor data using the built-in Historian and viewed through Grafana.
Works for me!
After a long wait for an updated version of the rather crude and unfinished Z-Way integration to HASS, i'm now looking (reluctantly) in to replacing Z-Way with Z-wave JS..
Mind you this is a big existing network, not a new controller stick..
I threw up a docker for z-wave JS UI, and tried to connect it to the UZB stick.. It loads the whole network from the stick, but the driver keeps restarting?
Looking at the logs, I see a lot of Dropping message because the driver is not ready to handle it yet.
It seems like the stick just keeps talking like z-way was still listening? This ends up in the driver crashing repeatedly.. Any ideas to how I can get them talking?
In the code snippet below, you see the driver restarting with the graphic letters, seemingly while the stick is mid-sentence, or because of ACK timeout...2022-10-02T19:19:59.664Z CNTRLR received additional controller information: Z-Wave API version: 6 (legacy) Z-Wave chip type: ZW050x node type Controller controller role: primary controller is the SIS: true controller supports timers: false nodes in the network: 1, 5, 6, 10, 11, 12, 13, 14, 17, 18, 21, 22, 23, 24, 25, 26, 27, 28, 29, 32, 33, 34, 36, 37, 38, 39, 41, 42, 43, 44, 45, 46, 4 7, 48, 52, 55, 69, 70, 71, 73, 74, 75, 77, 78, 79, 81, 82, 83 2022-10-02T19:19:59.765Z CNTRLR [Node 001] [Manufacturer Specific] manufacturerId: metadata updated 2022-10-02T19:19:59.766Z CNTRLR [Node 001] [Manufacturer Specific] productType: metadata updated 2022-10-02T19:19:59.767Z CNTRLR [Node 001] [Manufacturer Specific] productId: metadata updated 2022-10-02T19:19:59.768Z CNTRLR [Node 001] [+] [Manufacturer Specific] manufacturerId: 277 2022-10-02T19:19:59.769Z CNTRLR [Node 001] [+] [Manufacturer Specific] productType: 1024 2022-10-02T19:19:59.770Z CNTRLR [Node 001] [+] [Manufacturer Specific] productId: 1 2022-10-02T19:19:59.770Z CNTRLR [Node 001] [Version] firmwareVersions: metadata updated 2022-10-02T19:19:59.771Z CNTRLR [Node 001] [+] [Version] firmwareVersions: 5.39 2022-10-02T19:19:59.772Z CNTRLR [Node 001] [Version] sdkVersion: metadata updated 2022-10-02T19:19:59.772Z CNTRLR [Node 001] [+] [Version] sdkVersion: "6.9.0" 2022-10-02T19:19:59.772Z CNTRLR setting serial API timeouts: ack = 1000 ms, byte = 150 ms 2022-10-02T19:19:59.792Z SERIAL » 0x01050006640f97 (7 bytes) 2022-10-02T19:19:59.792Z DRIVER » [REQ] [SetSerialApiTimeouts] payload: 0x640f 2022-10-02T19:19:59.815Z SERIAL « [ACK] (0x06) 2022-10-02T19:19:59.816Z SERIAL « 0x01050106640f96 (7 bytes) 2022-10-02T19:19:59.817Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:03.177Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗ ╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝ ███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗ ███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║ ███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║ ╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝ 2022-10-02T19:21:03.178Z DRIVER version 10.2.0 2022-10-02T19:21:03.179Z DRIVER 2022-10-02T19:21:03.179Z DRIVER starting driver... 2022-10-02T19:21:03.199Z DRIVER opening serial port /dev/zwave 2022-10-02T19:21:03.212Z DRIVER serial port opened 2022-10-02T19:21:03.213Z SERIAL » [NAK] (0x15) 2022-10-02T19:21:03.229Z SERIAL « 0x01090141d39601020201f3 (11 bytes) 2022-10-02T19:21:03.232Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:03.233Z SERIAL « 0x01090141d39601020201f3 (11 bytes) 2022-10-02T19:21:03.234Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:03.234Z SERIAL « 0x01090141d39601020201f3 (11 bytes) 2022-10-02T19:21:03.234Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:03.261Z DRIVER « [RES] [GetNodeProtocolInfo] payload: 0xd39601020201 2022-10-02T19:21:03.268Z DRIVER « [RES] [GetNodeProtocolInfo] [unexpected] payload: 0xd39601020201 2022-10-02T19:21:03.268Z DRIVER unexpected response, discarding... 2022-10-02T19:21:03.268Z DRIVER « [RES] [GetNodeProtocolInfo] payload: 0xd39601020201 2022-10-02T19:21:03.271Z DRIVER « [RES] [GetNodeProtocolInfo] [unexpected] payload: 0xd39601020201 2022-10-02T19:21:03.271Z DRIVER unexpected response, discarding... 2022-10-02T19:21:03.271Z DRIVER « [RES] [GetNodeProtocolInfo] payload: 0xd39601020201 2022-10-02T19:21:03.273Z DRIVER « [RES] [GetNodeProtocolInfo] [unexpected] payload: 0xd39601020201 2022-10-02T19:21:03.274Z DRIVER unexpected response, discarding... 2022-10-02T19:21:03.274Z DRIVER loading configuration... 2022-10-02T19:21:03.298Z CONFIG Using external configuration dir /usr/src/app/store/.config-db 2022-10-02T19:21:03.298Z CONFIG version 10.2.0 2022-10-02T19:21:04.284Z DRIVER beginning interview... 2022-10-02T19:21:04.286Z DRIVER added request handler for AddNodeToNetwork (0x4a)... 1 registered 2022-10-02T19:21:04.286Z DRIVER added request handler for RemoveNodeFromNetwork (0x4b)... 1 registered 2022-10-02T19:21:04.286Z DRIVER added request handler for ReplaceFailedNode (0x63)... 1 registered 2022-10-02T19:21:04.287Z CNTRLR querying controller IDs... 2022-10-02T19:21:04.484Z SERIAL » 0x01030020dc (5 bytes) 2022-10-02T19:21:04.485Z DRIVER » [REQ] [GetControllerId] 2022-10-02T19:21:04.487Z SERIAL « 0x0123000400511a9f039900b834787d066515a4b79c45bb3af55ea7f6203006010 (37 bytes) 80120c84d 2022-10-02T19:21:04.489Z SERIAL « [DISCARDED] invalid data 0x9ef4 (2 bytes) 2022-10-02T19:21:04.490Z DRIVER Dropping message because it contains invalid data 2022-10-02T19:21:04.490Z SERIAL » [NAK] (0x15) 2022-10-02T19:21:05.488Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i n 100 ms. 2022-10-02T19:21:05.591Z SERIAL » 0x01030020dc (5 bytes) 2022-10-02T19:21:05.592Z DRIVER » [REQ] [GetControllerId] 2022-10-02T19:21:06.596Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i n 1100 ms. 2022-10-02T19:21:07.698Z SERIAL » 0x01030020dc (5 bytes) 2022-10-02T19:21:07.699Z DRIVER » [REQ] [GetControllerId] 2022-10-02T19:21:08.717Z DRIVER Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/D river.ts:3980:23) at ZWaveController.identify (/usr/src/app/node_modules/zwave-js/src/lib/co ntroller/Controller.ts:713:33) at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js /src/lib/driver/Driver.ts:1207:26) at Immediate.<anonymous> (/usr/src/app/node_modules/zwave-js/src/lib/drive r/Driver.ts:1014:16) 2022-10-02T19:21:08.723Z DRIVER destroying driver instance... 2022-10-02T19:21:08.728Z DRIVER driver instance destroyed 2022-10-02T19:21:08.739Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗ ╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝ ███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗ ███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║ ███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║ ╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝ 2022-10-02T19:21:08.740Z DRIVER version 10.2.0 2022-10-02T19:21:08.740Z DRIVER 2022-10-02T19:21:08.740Z DRIVER starting driver... 2022-10-02T19:21:08.745Z DRIVER opening serial port /dev/zwave 2022-10-02T19:21:08.751Z DRIVER serial port opened 2022-10-02T19:21:08.752Z SERIAL » [NAK] (0x15) 2022-10-02T19:21:08.754Z DRIVER loading configuration... 2022-10-02T19:21:08.755Z SERIAL « 0x01080120c84d9ef40138 (10 bytes) 2022-10-02T19:21:08.757Z SERIAL » [ACK] (0x06) 2022-10-02T19:21:08.758Z DRIVER « [RES] [GetControllerId]
I have an old analog intercom (Golmar) that has this horrible buzz sound when someone rings my apartment from the buildings front gate. This becomes very annoying at night so I need to make this buzz silent from 10:00pm till 7:00am
I have a "Shelly Plus 1" connected to the intercom. (wire #0 and wire #3 are responsible for closing the circuit for the buzzer).
I have set Webhooks and Scenes, but my wiring does not work. Can anyone tell me what i have done wrong?
Well with all that has been going on with Vera/eZlo, many people are abandoning the Vera hubs and moving on to other solutions, such as Hubitat (my case), HASS, HA, and many other controllers.
In the past, I had already been informed that when the migration was over, my Vera would go to the incinerator, or under the wheel of my car, and of course, I did not comply.
So I wanted to open a debate, for those who have not yet sold their Vera on eBay, are with the equipment idle, what destination could be given?
I see many saying that it has become a laboratory, I don't see much sense, since it is becoming obsolete and without a drive. But it can be a destiny. Has anyone thought about whether it is feasible to change the hub's SO so that it becomes a host for MSR, for example? Or even Home Assistance? I have no knowledge, but it seems to me that processor and memory have to do something like that, already has embedded wifi and network.
Does anyone have any idea if it is possible to give this equipment a destination other than a box?
I just started [uncloud] forum to gather in one central place all smart devices working without the cloud, since this is not information easily available on the Internet.
I thought this might interest some users of this forum and any feedback are welcome.
And let me know if you know more devices that I should add to the list!
I didn't see an existing Topic for heating-ventilation-air conditioning, so here goes...
Is anyone successfully controlling a "mini split" (i.e. ductless) A/C or heat pump system at home? I will be adding such a system soon to new construction, and wondered if certain brands/models interface better via Z-Wave or WiFi than others in a HA setting.
I know a bunch of these "splits" come with handheld remotes, but having robust Home Automation control (preferably without a dedicated plug-in needed on the Vera side) would be idea.
Happy to hear suggestions. Thanks!Libra
I have a legacy Vera system that in my home and I need to add a few devices to a cottage on my property. The Vera zwave won't see devices that far away. Both the house and cottage are on the same LAN. Can I bridged an Ezlo Plus to my existing Vera plus and if so are there instructions?
Is it just me or the GE/Jasco switch or very sensible to power outage ?
Almost each time we have a power outage, I need to replace at least 1 switch to replace.
Each time, same behaviour, the blue led is flashing rapidely and nothing works.
Last power outage, I got 3 switches. 95% of our switch and dimmer are GE/Jasco.
About one month ago I got a new electrical meter in the house. The new meter is a "smart" meter equipped with a data port. It is more or less the same type of meter that is used in a number of European countries, e.g. The Netherlands, Belgium, Sweden etc.
Norway has selected a different version with a RJ45 port with another protocol.
The dataport is a serial "P1" port in the form of a RJ12 contact that sends quite a lot of data every 10 seconds:
The data will show both consumption and production if you e.g. have solar panels at home.
My initial though was to use the Tasmota P1 Smart Meter with Mqtt. I tried this and it works, but unfortunately I got some serial data errors every 5-10th message for some reason so I decided to try another solution.
I found a few other alternatives and tested one of them. The upside with this version is that it is adapted to the Swedish data fomat that differs from the Dutch a bit and that it delivers the data in Mqtt form:
The hardware is pretty simple. For the Tasmota variant and most of the other solutions you need a ESP8266, e.g. a Wemos mini and then a transistor and two resistors (image below). The version I use is even simpler since it does not need the transistor.
For a lot of the meters delivered (DSMR 5 versions if I am right) you can power the ESP from the 5V provided in the RJ12 port, very handy.
It is also possible to buy a readymade P1 meter, this one looks quite nice, although I have not tested it.
In order to get a good overview of the data from the meter I have started creating a dashboard in Grafana that gets data from Historian in OpenLuup. It is quite useful to be able to see the load over time per phase etc.
I also managed to grab the hourly prices in json format and display that in the dashboard via some lua code in a scene.
At the moment I have built no logic around this, but it opens up posibilities for sure. In Sweden the electrical tarrifs will change from daily rates to being higher when demand is higher, perhaps then this can be used.
All in all a fun DIY project that provides some useful data out of the electrical meter. 🙂
I am new to this forum. I have been building an Alexa-based smart home for a few years. Overall, works well. I have a curious problem with a smart light. I set up a Kasa smart bulb in a ceiling can fixture. It worked well for at least 2 years. Then it began turning on randomly. Eventually, it began turning off randomly.I swapped out an identical bulb from another fixture and the problem persisted. I just replaced the ceiling fixture with a new one, properly installed, and the problem remained.
I replaced the Kasa bulb with a PlusMinus bulb. I can control it correctly, but the replacement bulb behaves in the same random on/off way.
Any ideas? I am at a loss!
So, I’m searching for something to send SkyQ’s infrared remote IR from a different room. I have a Logitech Harmony box, but it’s out of sight, so I’m just using the app, but a remote is definitely better, since the tv is in the master bedroom and the skyq box is downstairs.
I’ve searched for something like an IR device capturing and sending the codes via network to the box, but I’m not finding anything. I’m not 100% sure a wireless transmitter will work, since my house is all concrete and signals from other floors are usually blocked.
Not 100% home automation, I know, but is there anything I could do? Thanks.
Besides having integrated the xiaomi vacuum cleaner robot to my system, I have actually also integrated a large number of air filters to my automation system (homeassistant -> bridged into openLuup) for quite sometime. I have been using them mostly to monitor the air quality in different rooms. All of these devices are wifi but are communicating through a local API. I was looking today at replacing also my foobot which is my very last cloud dependent devices (and a non critical one) and found/ordered this:134.36C$ |Xiaomi Mijia Air Quality Tester 3.97" HD Touch Screen Remote Monitoring PM2.5 Temperature Humidity Measurement For Smart Home|Smart Remote Control| - AliExpress 134.36C$ |Xiaomi Mijia Air Quality Tester 3.97" HD Touch Screen Remote Monitoring PM2.5 Temperature Humidity Measurement For Smart Home|Smart Remote Control| - AliExpress
Smarter Shopping, Better Living! Aliexpress.com
It can very likely be integrated into home-assistant and then openLuup the same way I have with my filters but what I found particularly interesting is its low cost and the fact that it can also serve as a BT gateway! Why is this getting me excited? Because I have long regretted the loss of Plantlink which was a zigbee platform for soil/plant monitoring which unfortunately was cloud dependent and went belly up. I have since been automating my garden watering based on predictive algorithm only, without sensors. (yes still with openLuup). I am now looking forward to see how this will workout as my better half is very invested in gardening these days...
So my house only has 2 wire lighting and due to the way it's been installed, plus our flooring options, conversion to 3 wire is not practicable in any case that I want (hope I got those the right way around!)
So it's only dimmer units for me (boo hiss!) even though I'm only ever using them as on and off.
So what's going to happen if I put a non-dimmable LED bulb on a dimmer? is the dimmer going to get upset or will the bulb just come on at 100%? I'm never going to ask the bulb to actually dim, I only want on or off.
Quite a number of years ago I set up a few Arduino sensors that reported temperature to my VeraLite running UI5. I did this with MySensors, a quite nice community based platform.
I discontinued this mostly because that the combination of a rather flaky Vera and that the Vera when rebooting lost the USB connected gateway.
Some time ago I started to look at this again, but this time using ESP8266’s and Tasmota. I think the credit for this partially is the plugin for Shelly and Tasmota that @therealdb has written, even though I have still to use the plugin. The other reason for reentering into this area is that my electrical supplier is replacing the electrical meters for a new smart meter. Today I use a blink meter from Effergy, but the new meter will have a port for reading out data. This also led me to Tasmota, there seems to be a functioning solution for this.
I must say that Tasmota is brilliant! Support for all kind of devices and sensors and super easy to use, also for multi-sensors, OTA update, good documentation etc. You can get parts on ebay etc quite cheap. It has also so far been very stable. You can also very easily adjust the sensors readout, e.g. TempOffset -1.5 gives an offset of -1.5 degrees.
I have put together sensors for temperature and humidity for use in the garage, the outhouse, on the attic etc. I have tested DHT22, DS1820B, BME280 and BH1750 so far and they all work without issues. The latter two I installed in an outdoor enclosure to use as a simple weather station reporting temperature, humidity, air pressure and light level.
I also got a MH-Z19B CO2 meter for testing to monitor the indoor CO2 levels. The initial feeling is that it does what it should.
In general I have pretty good wifi coverage with a few Unifi access points. One of the sensors is in a building some 25 meters from the house where the wifi is not that strong, but the NodeMCU has no problem with this. Quite impressive and a good addition to Z-wave for that kind of location.
Not owning a 3D printer I have had to resort to purchased enclosures and the old Dremel. 😊
For the CO2 sensor I put it in an old smoke detector enclosure for now.
I am sure that there are a lot of talent here that can do much better with a 3D printer!
You can get the data from the Tasmota devices into OpenLuup in a number of ways. The obvious way is via MQTT. I have still to set this up at some point in time. The second way is to use the excellent SiteSensor plugin. I tested this but had some problems with reporting stopping after a few days for some reason. I probably got something wrong in the setup. The third option, that I currently use is via adding rules to each sensor. You can quite easily add rules for reporting data to a virtual sensor in OpenLuup, e.g:
Rule1 ON tele-AM2301#Temperature DO Var1 %value% ENDON ON tele-AM2301#Temperature DO WebSend [IP_adress:3480]/data_request?id=lu_action&DeviceNum=65&id=variableset&serviceId=urn:upnp-org:serviceId:TemperatureSensor1&Variable=CurrentTemperature&Value=%Var1% ENDON
With TelePeriod you can change the polling interval as required.
This method I think could be super useful for reporting back e.g. switch status from a Tasmota node much like I understand Shelly can do.
Some resources and notes I made on the way:
Using Tazmotizer to flash the ESP’s is very easy
List of supported sensors including how to connect, commands etc
A good pinout reference for ESP8266 variants
Tasmota rules documentation
Most sensors are either “Generic (0)” or “Generic (18)”, check for each sensor type what to use
For I2C sensors e.g. BME280 one must use tasmota-sensors.bin
For the MH-Z19B I had to flash the ESP before attaching the sensor, this could be a good practice always
Use the following url for the query in SiteSensor:
This became a rather long post but hopefully it can be of some use.
So, I'm at the 4th Z-wave devices and I still have trouble in getting my Vera operate my door gate, and getting the input from the doorbell. It's already all 220v, because I have an external modulo meant for integration.
So, last night I had an idea: why not use a Shelly 1 as both sensor and opener?
If you need instructions on wiring, here's an image:
Shelly 1 can operate the output independently from the input. So, I prototyped this:I attached to the doorbell sensor O attached to the gate opener
It seems to work on my bench, because I can call the endpoints when the button is pressed or the input is triggered, so I can update virtual devices and execute all the logic I want. I usually integrate these devices with MQTT, but it's not necessary in this case, since I can live with a doorbell buzz being missed.
Bonus point: you can run it at 12v if you want.
Next in my TODO list, the Shelly Universal, a 9 EUR universal binary inputs, with separated inputs and outputs (so, you can get 2 inputs and operate 2 outputs independently), that I'll probably use in my weather sensors project, where I'm using two Shelly 1 at the moment, just the get the inputs.
Using a Shelly Button1 as car presence sensor
therealdb last edited by
Caveat: I'm still bored, so I'm building a lot of things lately (I used to travel a lot, so the last year has been really different - but I digress).
Last week I built two car sensors using a Shelly Button1 in each. It's a new device, with a battery and USB charging (see https://shelly.cloud/products/shelly-button-1-smart-home-automation-device/)
I've placed one in each car under the leg rest. I'm parking outside (my house is modern architecture, I have a covered terrace that's my open space, so cars are outside the garage, but covered), but WiFi is still reachable.
When plugged via USB, the device is sending a new MQTT message upon boot, and that's great for leaving home. It usually takes less than 10 seconds from when I open the car. This action will open my car gate unless party mode is on or the gate is already opened. It will automatically close it after 40 secs.
When coming back, it will reconnect in seconds (less than 10) and send a new online MQTT message. The trick here is to get the uptime via an HTTP call to /status (I've asked them to add to the MQTT message) and if more than 10 seconds are passed from the last boot, I'm assuming the car is coming back and the gate needs to be opened, and then closed automatically after 40 secs (again, if no party mode is enabled and if the gate is closed upon arrival).
It's a very simple thing to do, but I'm loving it. Obiously, my wife was like "you're really lazy", but I know she will love this eventually. Saving me from 10 clicks to a remote is what home automation really is
rafale77 last edited by
I am doing something similar but a bit differently. I am using video recognition to detect a car and then read the license plate. If it recognizes the car, it triggers some actions in openLuup. Similar idea as facial recognition to unlock the door when it detects that my phone just came back home.
@rafale77 so no copy of the key, just the plate
rafale77 last edited by
It's a bit smarter than that... it requires other conditions to be met... like having broken geofence within a certain time and not having open any door yet.