Mr-JR
(James R)
January 28, 2022, 5:02pm
1
Suddenly Google Home is not able to talk to Openhab … everything had been working fine and no changes were made … symptoms are:
when I log into https://home.myopenhab.org/ I get a blank screen
When I attempt a sync (Hey Google, Sync Openhab) I get a sorry can’t connect …
When I attempt to access a device directly from google home app, it times out
There is nothing recorded in the log at these times.
Before I reboot the system (to see if that solves the problem) is there anything I can look for to determine what is wrong?
Any hints as to how to repair this?
Mr-JR
(James R)
January 28, 2022, 5:11pm
2
Well sorry … I forgot I just stopped openhab before I submitted this comment … after restarting openhab, the google service works fine … so not able to debug this.
If this happens again, what should I look for before restarting Openhab?
rpwong
(Russ)
January 28, 2022, 9:59pm
3
This may be related to the recent myopenhab outage. Yesterday, my system thought it was connected, but didn’t work until I restarted the cloud connector.
You don’t need to restart openHAB, just go into Main UI, click on “openHAB Cloud”, and click the “Save” button without changing anything. Saving restarts the connector, and you’ll see that in your log.
After doing that, I asked Google to sync my devices and they started working again.
If you’ve changed nothing and GA stops working, you should generally start by checking the community to see if myopenhab is down. See my post from the recent outage for some tips.
To answer some of the questions above:
If your log shows your server repeatedly trying to connect to myopenhab and you haven’t made any changes, you can assume the server is down.
Outages don’t always show up on status.openhab.org . Sometimes, the issues are in between the myopenhab server and individual OH servers. This means that the server is up, but we can’t reach it.
Anything that’s reliant upon myopenhab (Alexa, Google Assistant, mobile apps, etc.) will not work until myopenhab is back on…
3 Likes
Mr-JR
(James R)
March 7, 2022, 3:52pm
4
rpwong:
You don’t need to restart openHAB, just go into Main UI, click on “openHAB Cloud”, and click the “Save” button without changing anything. Saving restarts the connector, and you’ll see that in your log.
Bingo. The problem occurred again today and this worked. Thanks Russ.
1 Like
rpwong
(Russ)
March 7, 2022, 5:29pm
5
If this is happening regularly to you, there’s now another thread discussing it, along with a troubleshooting binding in the marketplace.
2 Likes
MDAR
(Stuart Hanlon, UK importer of Velbus hardware)
August 11, 2022, 7:16pm
6
rpwong:
You don’t need to restart openHAB, just go into Main UI, click on “openHAB Cloud”, and click the “Save” button without changing anything. Saving restarts the connector, and you’ll see that in your log.
You happen wouldn’t know of a way we could trigger this from a simple UI element?
As in, from HabPanel / BasicUI etc
(Something for the Non-tech user)
rpwong
(Russ)
August 11, 2022, 8:07pm
7
You’d need a rule to restart the binding using Karaf. I’ve never done that, but this looks like it should work.
All,
I currently struggle with my Netatmo binding. After a few hours it stops getting updates from the Netatmo station.
So I implemented a solution to restart the binding from within a rule.
I hope this helps someone for solving similar issues with specific bindings:
First generate the key (as an alternative to sshpass) to enable you to start karaf without beeing asked for your password
sudo -u openhab ssh-keygen -t rsa -f openhab.id_rsa (no passphrase)
Next, put the result (key only of co…
2 Likes