Announcement

Collapse
No announcement yet.

Gateway showing as 'Unauthorised'

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

  • alexbk66
    replied
    Originally posted by alexbk66 View Post
    I'll have to add more logging to trace the whole path....
    Ok, please try ver. 3.0.0.22 (BETA) - added more logging, also I generate the appKey earlier.

    If still doesn't work - please send me the logs.

    Leave a comment:


  • alexbk66
    replied
    Originally posted by rahaaas View Post
    Yep. Tried both config pages.

    HA runs on its own headless SEL box, and so the server starts automatically at boot.
    Do you mean HS? Yeah, for troubleshooting probably the easiest is to connect a display. You can try SSH and restart HS from the SSH window too.

    Leave a comment:


  • rahaaas
    replied
    Yep. Tried both config pages.

    HA runs on its own headless SEL box, and so the server starts automatically at boot.

    Leave a comment:


  • alexbk66
    replied
    Originally posted by rahaaas View Post
    Well, props for dedication! Lockdown in London, so pretty early nights to cope with home-schooling...

    Am running BETA 3.0.0.21.

    I'm SSHing into the SEL, so not seeing the boot / HS initialisation, if that's what we need?
    How do you start HS? Via SSH?

    When you enter the hub KEY - the plugin should generate the appName - then request the appKey from Gateway. Since you don't even have the appName - means there's some problem before trying to get the appKey.

    Did you try both config pages? I fixed the Device Config, may be you get more lucky.

    I'll have to add more logging to trace the whole path....

    Leave a comment:


  • rahaaas
    replied
    Well, props for dedication! Lockdown in London, so pretty early nights to cope with home-schooling...

    Am running BETA 3.0.0.21.

    I'm SSHing into the SEL, so not seeing the boot / HS initialisation, if that's what we need? Can get a monitor on it in a squeeze, but assuming there'll be a log the startup somewhere?

    In case you wanted to see my Plugin config page:

    Click image for larger version  Name:	Screenshot 2020-04-05 at 23.56.22.png Views:	0 Size:	28.6 KB ID:	1375336
    Also notice the Device config page now has 'App "key"' on it, if that's a thing.

    Click image for larger version  Name:	Screenshot 2020-04-05 at 23.56.02.png Views:	0 Size:	127.0 KB ID:	1375335
    Thanks for all so far.

    R.

    Leave a comment:


  • alexbk66
    replied
    Originally posted by rahaaas View Post
    Sorry - just to clarify, I have been using the Config Page on the Plug-ins menu, rather than the Device page.
    Still, I found the problem on the Device page

    Leave a comment:


  • alexbk66
    replied
    By "console" I mean the window where you start HS server - on Linux it's actually called "terminal" window.

    Are you using BETA 3.0.0.21?

    I will continue tomorrow as it's 2:22 am here in AU

    BTW, 163 & 164 are the HS device reference numbers

    Leave a comment:


  • rahaaas
    replied
    Sorry - just to clarify, I have been using the Config Page on the Plug-ins menu, rather than the Device page. That was just the screenshot.

    Hmmmn. If we’re talking usr/local/HomeSeer/Config, then I don’t have any AKIkea.ini files in there at all, which may be telling... All the other plug-ins I’m using do have files there.

    Tried an uninstall / reinstall of the plugin, and the status became:


    Click image for larger version  Name:	Screenshot 2020-04-05 at 16.47.40.png Views:	0 Size:	16.2 KB ID:	1375250

    A further uninstall / reinstall got it running again. But now with a 164 error (from 163). Still no .ini files in /Config. And nothing else in the main HomeSeer Log (by which I mean VIEW / LOG).
    Apr-05 17:11:32 AK Ikea [164]: Not ok: hubkey 'XiAsC85dOnm5JUMp', app '', appkey: ''
    Is there another ‘console' I’m missing somewhere (to look for these AvahiDBus.dll / other errors..?)

    Leave a comment:


  • alexbk66
    replied
    Or you can you try to configure from PLUG-INS -> AK IKEA -> Config Page

    Leave a comment:


  • alexbk66
    replied
    Originally posted by rahaaas View Post

    Exactly the same [163] error with 3.0.0.21, I’m afraid.
    Probably you need to remove Config\AKIkea.ini and Config\AKIkea.ini.bak (with the plugin stopped) and remove the Bridge device, then start from scratch

    Leave a comment:


  • rahaaas
    replied
    Originally posted by alexbk66 View Post
    Ok, I think I found the problem - the Bridge config page wasn't generating the appName, so fixed in ver. 3.0.0.21, please try.
    Exactly the same [163] error with 3.0.0.21, I’m afraid.

    Leave a comment:


  • alexbk66
    replied
    Originally posted by rahaaas View Post
    Right. So Mono.Zeroconf.Providers.AvahiDBus.dll IS present in bin/AKIkea.

    Will have a hunt round the logs to see if any more clues in there.
    That's a minor issue - if you enter IP address manually - you don't need the Zeroconf. It's nice to have if your Gateway IP address isn't static though. So Zeroconf will detect if IP changes.

    So there may be some errors loading AvahiDBus.dll - in the console window, not the logs.

    But for the authentication issue please try ver. 3.0.0.21 (BETA)

    Leave a comment:


  • rahaaas
    replied
    Right. So Mono.Zeroconf.Providers.AvahiDBus.dll IS present in bin/AKIkea.

    Will have a hunt round the logs to see if any more clues in there.

    Leave a comment:


  • alexbk66
    replied
    Ok, I think I found the problem - the Bridge config page wasn't generating the appName, so fixed in ver. 3.0.0.21, please try.

    Leave a comment:


  • alexbk66
    replied
    Actually, can you try to configure from PLUG-INS -> AK IKEA -> Config Page (see attached screenshot) - that's where the App Name is generated.

    I need to check the config page you are using...

    Click image for larger version

Name:	Start.png
Views:	79
Size:	29.4 KB
ID:	1375203

    Leave a comment:

Working...
X