Setting up Garadget with Home Assistant

home-assistant
howto
home-automation
Tags: #<Tag:0x00007fe3b7711810> #<Tag:0x00007fe3b77116a8> #<Tag:0x00007fe3b7711568>

#1

Video is courtesy of BRUH Automation:


#2

First post here!

Let me start by saying that this product is really fantastic. I was able to retrofit my Linear garage with the outstanding support of Denis.

My question to you on integration with Hassio/Home Assistant:

I was able to successfully install and integrate Garadget with Hassio. I’m getting a weird behaviour though: A sporadic “garage open” alert followed a few seconds afterwards by a “garage closed” one tends to happen every few hours. I know the garage is NOT opening because the main Garadget application is not triggering an alert. So clearly something generating a false signal in the Hassio implementation.

Anyone seeing this behaviour?


#3

@Woody, thank you for your feedback.
The false alert is likely to do with the sensor and not specific to Hassio integration.
Please check out troubleshooting guide for false notifications.


#4

Hey Denis,

Thanks again for the prompt reply.

Would this be the case even if the main Garadget app is NOT triggering the same events?


#5

Do you receive app notifications for the factual door events?


#6

Yes. Everything is working perfectly well when the door opens and closes, I get the app’s alerts and 1-2 seconds later Hassio’s.

Those sporadic open/closed alerts only happen within Hassio and never appear in the Garadget app. They happen every few hours. Hence my assumption that it’s something that has to do with the hassio implementation.

Does hassio use the app configuration when it comes to various settings (reflection threshold, reads, etc?)


#7

Yes, same settings are used for all communication channels.
BTW: do you connect to hassio via cloud or locally via MQTT?


#8

Via cloud. Using the standard configuration.


#9

When you have a moment, check out MQTT support, it works with hassio directly over the local network.


#10

I’m currently not using MQTT as I was reading that there were some issues, particularly with memory leaks with the internal Hassio implementation.

In any case, I noticed that the following error messages appear in Hassio when the Open/Closed alert is triggered:

Update for cover.garage_door fails
October 24, 2018, 9:05 PM components/cover/garadget.py (ERROR)
Update of cover.garage_door is taking over 10 seconds
October 24, 2018, 9:05 PM util/async_.py (WARNING)
Unable to connect to server: HTTPSConnectionPool(host=‘api.particle.io’, port=443): Max retries exceeded with url: /v1/devices/MASKED/doorStatus?access_token=MASKED (Caused by NewConnectionError(’<urllib3.connection.VerifiedHTTPSConnection object at 0x6f9feef0>: Failed to establish a new connection: [Errno -3] Try again’,))
October 24, 2018, 8:59 PM components/cover/garadget.py (ERROR)
Unable to connect to server: HTTPSConnectionPool(host=‘api.particle.io’, port=443): Max retries exceeded with url: /v1/devices/MASKED/doorStatus?access_token=MASKED (Caused by NewConnectionError(’<urllib3.connection.VerifiedHTTPSConnection object at 0x6f9585b0>: Failed to establish a new connection: [Errno -3] Try again’,))
October 24, 2018, 8:57 PM components/cover/garadget.py (ERROR)

Is there a way to limit the number of calls in Hassio or define some timeout via the configuration?

Thanks a lot for all your help, Denis!


#11

This is something that Jason (the author of the integration) can probably comment on in the original post in Hassio community.

As for MQTT: if you have concerns about embedded broker, you can use a dedicated one like Mosquitto.


#12

I just posted a summary in the original post and waiting for Jason’s response.

Thanks a lot, Denis.


#13

No response from Jason, unfortunately. @garadget, I did also notice that many people were having the same problem with particle API connection timeouts while I continued investigating my issue.

I’ll try the MQTT approach now.