aderusha / mqttcarpresence Goto Github PK

I skimmed the .ino code as well as the yaml file and don't see a close delay programmed into the logic.

For my setup the processing time of the MQTT messages seems to result in about a 1.5 min lag, which is pretty good, but wanted to know if there was a setting somewhere I didn't see that would allow extending it for people that wanted a longer window of time.

I'm trying to get this set up, and it sorta works, but I think it could be done better but I haven't been able to wrap my head around how LWT and Retain works with Tasmota. I use the signal sensor to determine if my car is in the garage, driveway or away and this doesn't work if its unavailable. Do you know of a way to make the tasmota sensor not go unavailable when the car is off and the esp is powered off? Ideally it would show the switch as off as the LWT and the sensor data would be retained. Also I would like to be able to set the keepalive to something shorter as I like to have the delay set in my automation so the door shuts if the switch is off for 15 seconds instead of having the timeout set on the esp8266 itself.

The main reason I'm trying to use tasmota is because

1. the arduino method doesn't create a device in HA and
2. This is the only arduino code I use, and would like to consolidate everything in Tasmota or ESPHome for my dev boards.

Has this blueprint been tested? I suspect as written it will not work...

name: Garage Door Cover
...
name: Car Presence Sensor

These are the names assigned in the top of the blueprint, however in the action section these are referred to as:

entity_id: !input car_presence
...
entity_id: !input garage_door

I believe the names have to match the !input tag, so this should not work as-is. I don't have a cover I can connect this to, so I cannot test it as you have presented it here.
That is why I am sending an issue like this instead of giving you an edit to merge.

If an edit would be helpful, let me know, I will send you one.

Hi!
My D1 Mini is on a hard to reach spot, can it be accessed over the air?
I have to make changes on two devices, one I have to clear the credencials as the car will be sold and the other a have to change the node name. Can it be done over the air?
Thanks!

Is there a way to make the displayed as disconnected earlier?

It takes sometime after I am disconnected from the wifi network to turn the binary sensor to off.

It does not happen the same when I am connected.

Hi there,

I've followed the steps in the readme and double checked the wifi settings that I entered into the sketch but after I've finished setting everything up and get to the stage for testing, nothing happens.

The LED does not blink like crazy, I can't ping the device from a local computer (destination host unreachable) and no new entity shows up in Home Assistant. I know the MAC address of the board so I have assigned it an IP in my router. Using the MQTTCarPresence sketch, it's not showing up as connected at all.

I double checked that the board was actually working on Wifi OK using another sketch and was able to successfully ping the device using this so it's not the board: https://techtutorialsx.com/2017/06/29/esp32-arduino-getting-started-with-wifi/

When compiling and uploading using ArduinoIDE, I don't receive any errors.

Please advise on how I can resolve this issue as I'd really like to give this project a go, it looks great! If you need any extra info, just let me know :)

Many thanks

Hi Thanks for your great work

The car presence module isn't shown in the Mosquito integration.
I get data into MQTT. I can see data in MQTT Explorer, so everything is working ok.

But why can't I see this module in the auto discovered list on Mosquito

/Lars

Hello,

I have this set up and working and LOVE it, it works great. The only issue I have is that when I restart HA the sensor state goes into unknown until I start the car again. How would I go about setting the retain flag or similar to make HA remember its last state upon a restart?

Hi,

Love the solution - Thanks for making it available!

I'm new to HA and moving from Homeseer.

How can I add two additional conditions to the initial car starting-up sequence?

1—Test that a light is on in the garage (I have a motion-activated light in the garage). This will confirm that I am in the garage, as the car wakes up at times to report its state of charge, and this wake-up activates the USB port.

2- Test that the car is in the garage (open-garage distance sensor) as the car is often left on the driveway and is driven away.

Huge thanks for any assistance!

Philip

I get this error when trying to upload this sketch to a D1 Mini Pro:

`Arduino: 1.8.10 (Mac OS X), Board: "LOLIN(WEMOS) D1 mini Pro, 80 MHz, Flash, Disabled, All SSL ciphers (most compatible), 16M (15M SPIFFS), v2 Lower Memory, Disabled, None, Only Sketch, 115200"

Sketch uses 312248 bytes (29%) of program storage space. Maximum is 1044464 bytes.
Global variables use 29952 bytes (36%) of dynamic memory, leaving 51968 bytes for local variables. Maximum is 81920 bytes.
esptool.py v2.6
2.6
esptool.py v2.6
Serial port /dev/cu.usbserial-01849A42
Connecting......................................____Traceback (most recent call last):
File "/Users/biiiink/Library/Arduino15/packages/esp8266/hardware/esp8266/2.5.2/tools/upload.py", line 25, in
esptool.main(fakeargs)
File "/Users/biiiink/Library/Arduino15/packages/esp8266/hardware/esp8266/2.5.2/tools/esptool/esptool.py", line 2653, in main
esp.connect(args.before)
File "/Users/biiiink/Library/Arduino15/packages/esp8266/hardware/esp8266/2.5.2/tools/esptool/esptool.py", line 468, in connect
raise FatalError('Failed to connect to %s: %s' % (self.CHIP_NAME, last_error))
esptool.FatalError: Failed to connect to ESP8266: Timed out waiting for packet header
esptool.FatalError: Failed to connect to ESP8266: Timed out waiting for packet header`

I have tried using a D1 Mini and it worked fine. I've also tried a different D1 Mini Pro
These are the settings im using for the D1 Mini Pro

Any help would be greatly appreciated

How can we get the devices to show up as Devices instead of just multiple Entities and also have them published with unique_id values such that HA doesn't complain about them not being unique?

My wife typically comes home and she is on the phone in her car and pops her trunk. She can sit in the car this way for more than a few minutes. I dont want the garage door to ever close automatically, even when leaving the house or garage. Is there a simple way to disable all those variations that work with the door closing?

If you watched the DrZzs stream today, we found a bug in the Tasmota code...
I didn't find this in testing or think of it, but the relay needs to be ON for this to work correctly.
It monitors the switch for ON or unavailable...
Just need to add this to the config on the car D1 Mini. I can't fix the repo until i get back home because my GitHub editing computer is there, but add this to the car's Tasmota set-up and it will always be started up in the on state when the device turns on.

PowerOnState 4
so63 1

I will be able to update this at the end of October, until then, this is a note to make sure this problem gets fixed.

I will be happy to fix it then.

In the mean time, leave the relay set to on and it will continue to work as shown in the repo.

Sorry I'm not smart enough to do this on my own...
I'd like to monitor ignition on/off by reading a gpio high/low (say gpio 14) and sending that to the broker with the rest of the information. Could you add that please?

Is there any chance you could rewrite a portion of this that would NOT utilize the automatic discovery of HASS? I want to be able to test the MQTT functionality without having to rely on HASS to pick up the device in order to be used and simply using the MQTT broker, in my case mosquitto, instead.

My garage doors will close on their own using the timer in the 'smart' opener from the manuf.
I have ratgdo setup to provide state and control to HA. Can someone confirm if the blueprint automation is smart enough to not try to close an already closed door? I am guessing by the way the logic looks to my untrained eyes that it should ignore trying to close an already closed door, but I'd like a second opinion.

I guess same would go for not trying to open an already open door.

Works like a charm!! Thank you!

Assigning a static IP address to the ESP helps to connect to the wireless network faster

Hi,
Love this project. I just tried it today and so far haven't been able to get it working. I'm using a non-pro D1 mini. I wouldn't expect that to be the problem.
I modified the values at the top of the sketch with my info. The max packet size is 512. The sketch loads up fine without any errors.
In Home Assistant I added the automation. Changed the entity_id to match the mqttNode (I assumed that was necessary, maybe it isn't). When I power up the D1 mini, I don't see a new binary_sensor appear.
Most concerning is that when I plug the D1 into the computer, I don't see anything coming up in the Serial Monitor.

Any ideas of something else I can try?
Thanks!

Hello Aderusha and all. I love this idea and would really like to get this one working. I saw Dr. ZzS video and write up, which led me to this Github page.
I followed Aderusha's instructions with some help from Dr. ZzS more detailed steps and managed to set up Home assistant MQTT discovery and load Aderusha's sketch onto a D1 mini. The trouble starts when I plug the D1 mini into power and it connects to my wifi. I can see it in HA MQTT log as connected, however it is not adding itself as a binary sensor to configuration.yaml

1538340853: New connection from 192.168.1.160 on port 1883.
1538340853: New client connected from 192.168.1.160 as CarPresence (c1, k15, u'').

Specifically, in Dr. ZzS writeup (here: http://drzzs.com/mqtt-car-presence/) I’m stuck at the following step:

After that, restart Home Assistant and plug in your D1 Mini. After a few seconds the blue LED will start flashing like crazy. This sketch is genius. It adds itself as an entity to Home Assistant. Go to your states page and you should see a new “binary_sensor.CarPresence”. Once you see that, you’re ready for the next step.

However the binary_sensor never shows up, either in configuration.yaml or in the states. Any tips on what I can do?

Hello, do you know if anyone has converted this to esp32 based or if it is even possible?

I’m using this Aideepen WEMOS D1 Mini Pro - 16M Bytes External Antenna Connector ESP8266 WIFI IoT Board but Home Assistant is not discovering it. I know it’s connecting to my WiFi, because my router shows it and I can ping it.

What can I do to debug this?

Hi, is there a way to modify the code in order to connect to multiple wifi?
for example I have wi-fi A and wifi B, but I can configure it only for one of them.
tnx

hey there, I just got everything setup and it works with the tasmota variation, except when the d1 mini goes offline, HA reports the state as unknown and the garage door never closes. Is there a way to fix that?

Thanks
Jason