Hi guys, I am looking at https://www.home-assistant.io/components/gogogate2/ and trying to install it on my hass.io setup (raspberry pi4 with the 32bit image from the HASS website) but just can’t get it to show up, something must be wrong with my configuration.yaml can someone see anything wrong:
What does your log say?
Are you using the proper IP address for your actual controller? 192.168.0.200 is likely not the IP you need.
Actually turns out it did work, the IP is fine since I can get to the gate menu from Chrome.
Looks like it went to unused entities
Silly question, but if I want to add it to the main page what time of entity should I create to see it on the home page?
I would use an entity card
Great, thank you
Gosh - hate to bring this thread back up since you are up and running.
I keep getting the errors below:
Error while setting up gogogate2 platform for cover
10:57:21 AM – Cover (ERROR)
Gogogate2 - Login secirty token may have expired, will attempt relogin on next attempt
10:57:21 AM – components/gogogate2/cover.py (ERROR)
iSmartGate does not show anywhere.
The iSmartGate is hardwired with a static IP.
My configuration.yaml entry is essentially exactly the same as yours:
cover:
- platform: gogogate2
username: anon
password: anon
ip_address: 192.168.1.80
Can anyone help please? I also tried to open the original ticket on GitHub.
Many thanks.
I tried to get the new direct integration by @difeta in HA 0.111 and still no luck. Cannot get it to work. I upgraded to iSmartGate from GoGoGate original hardware, if that makes a difference.
Any ideas?
I actually followed advice on here and use it as a HomeKit device, but this means I cannot pair it with my HomePod or other hub in the house also.
Thanks 
Gogogate2 devices only allow the admin user to use the API. That’s the most common factor in getting it to work.
I stand corrected, non admin users you work on my devices. I submitted all pull request to fix the issue. The fix will be in home assistant 0.112.1.
Hi. Gogogate2 integration has been working flawlessly until last HA update.
Can access via ismartgate web interface and app and HomeKit.
User is admin.
Error is “Retrying setup: Error communicating with API: ‘AsyncConnectionPool’ object has no attribute ‘handle_async_request’”
I searched for hours. I tried to log an issue via the GitHub page but it was all core HA stuff not gogogate2 specific.
I can use it via the HomeKit to HA integration but it doesn’t get the battery and temp sensors and there is a little more delay.
Any pointers greatly appreciated. @difeta
Hi, is it possible to add cover stop support to the ismart gate mini. Need a method to stop the garage door if it is closing. Also, I find there is a 5 second delay between pressing the button and the door opening.
Many thanks
Hi, I have a GoGoGate2 that randomly stopped connecting with Home Assistant. I updated to the most recent version of HA, uninstalled and reinstalled the GoGoGate and I’m still having the issue.
I can access my GoGoGate from a browser, and ping it from the machine HA is installed on. The errors from the log were:
WARNING (MainThread) [homeassistant.config_entries] Config entry ‘GoGoGate’ for gogogate2 integration not ready yet: Error communicating with API: ; Retrying in background
Now, when trying to re-add the integration, I get: Failed to connect
If anyone could help me sort this out, I’d be very appreciative.
Thanks.
I’m having the same issue - error communicating with API
For posterity in case someone else searches for a similar problem for the API issue. It seems (in my case) that the admin userid is no longer working properly for API connections. I was able to log in directly to the Ismartgate device and create a new userid / password (10 are “free!”) that i now use to log in from the home assistant integration. That works great.
long shot, but here goes
stumbled across your post as GoGoGate had a wobbletoday and APi communication seemed to be broken, removed it to re-access and then it’s getting the “Failed to connect”.
Tried a new user, as per your post, with Total access, bust still same issue
Can you remember if you did anything specific