Announcement

Collapse
No announcement yet.

Sorry I couldn't reach HomeSeer...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • wkrasner
    replied
    just as an aside. if you have one bad voice command event or device checked the sync to GA will fail. you need to find the offending event or device on HS and uncheck voice command

    Leave a comment:


  • getmp3s
    replied
    Worked for a week and then offline again. I contacted HomeSeer support and they don't know what the problem is. I don't think I'm going to invest any further in this platform.

    Leave a comment:


  • MattL0
    replied
    This is certainly a problem with myhs side.

    I have events called diretly from amazon website (they bypass my hs cloud ( via a openhab binding)) , and they are processed really fast without any fail.

    but when i call devices linked with the myhs cloud , I experiment delays and ‘’ device could not be reach’’. That is very anoying .


    Leave a comment:


  • getmp3s
    replied
    Getting this issue in Toronto canada all day today .I wonder if its regional?

    Leave a comment:


  • MrMxyzptlk
    replied
    We get this randomly everyday.

    Leave a comment:


  • dotelpenguin
    replied
    Yeah I did a full reset, (which didn't fix it) and it was a mess. This time I'm just waiting.

    Leave a comment:


  • Bigmaxy
    replied
    Also been having an intermittent problem with this message. Made me very nervous as I lost all ability to sync with Google Home and Amazon Alexa before Christmas and ended up completely factory resetting homeseer to get it working again. Don't want to go through that again.

    Leave a comment:


  • JoeT
    replied
    Looks like it only lasted for a few hours. I've been good since at least 8:30am.

    Leave a comment:


  • HSAccord
    replied
    Originally posted by rmies1 View Post
    Same Issue with Log entries indicating Have Not heard from MyHS in over 3 Minutes - Very Inconsistent Can Homeseer folks advise us what causes this issue.
    This way we can prevent - troubleshoot and avoid on our own.
    I had this problem intermittently yesterday, though it seems to be working this morning.

    I'm nearly certain this is a Google problem, not a HS problem. I can always access HS contemporaneously when Google reports a problem.

    Leave a comment:


  • rmies1
    replied
    Same Issue with Log entries indicating Have Not heard from MyHS in over 3 Minutes - Very Inconsistent Can Homeseer folks advise us what causes this issue.
    This way we can prevent - troubleshoot and avoid on our own.

    Leave a comment:


  • JoeT
    replied
    Having problems this morning as well. From the HS log:
    Feb-17 6:29:35 AM Info System connected to MyHS Service successfully with license ID XXXXXXX.
    Feb-17 6:29:35 AM Info System connected to MyHS Service, waiting for acknowledge...
    Feb-17 6:29:24 AM Warning Have not heard from MyHS in over 3 minutes, disconnecting for re-connection.
    These messages are repeating. First one:
    Feb-17 6:22:04 AM Warning Have not heard from MyHS in over 3 minutes, disconnecting for re-connection.
    All times Eastern time.

    Leave a comment:


  • Almighty
    replied
    It worked for a brief moment about three hours ago (it even seemed faster than usuallly), but now it's again "unable to reach Homeseer".

    Leave a comment:


  • weaslyd
    replied
    Same issue here all day today. Google reports as "unable to reach Homeseer". MyHS login is working in the HomeSeer app, so it doesn't seem to be a MyHS problem. Going to submit a bug report now.

    Leave a comment:


  • dannieboiz
    replied
    Was working for a day then back again for me. I emailed support to report a bug and they told me it's not a wide spread issue so they are not looking into it. Suggest everyone with the issue report it to HS so they know this is an issue.

    Leave a comment:


  • Almighty
    replied
    Same here, I get this reply for most of the day today

    Leave a comment:

Working...
X