Announcement

Collapse
No announcement yet.

Gateway showing as 'Unauthorised'

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

    Gateway showing as 'Unauthorised'

    Plug-in now loading successfully.

    I’ve changed the IP Address, and entered the ‘Security Code’ from the bottom of the Gateway (should be this as opposed to the Homekit code, right?), but now just getting this in Devices.

    Click image for larger version  Name:	Screenshot 2020-04-04 at 17.07.15.png Views:	0 Size:	11.1 KB ID:	1375046

    And this in the device config:

    Click image for larger version  Name:	Screenshot 2020-04-04 at 17.14.20.png Views:	0 Size:	38.2 KB ID:	1375047

    Here's what the Log has to say:
    Code:
     
    Apr-04 16:41:10 AK Ikea Warning [163]: [newIkea] New Receiver (127.0.0.1): Setting new IP address: 192.168.1.97:80
    Apr-04 16:40:58 AK Ikea [0]: * Set Ikea [newIkea] New Receiver (127.0.0.1) (HSPI_AKIkea.DeviceIkeaBridge) Same: False
    Apr-04 16:40:58 AK Ikea Saved device: newIkea (newIkea), id: Unknown, url: 127.0.0.1:80
    Apr-04 16:40:55 AK Ikea Warning Running on 'linux' - using Locator.MonoZeroconf.DeviceLocator
    Apr-04 16:40:55 AK Ikea ERROR Locator.MonoZeroconf.DeviceLocator: FATAL CreateListener: No Zeroconf providers could be found or initialized. Necessary daemon may not be running.
    Apr-04 16:40:54 Plug-In Finished initializing plug-in AK Ikea
    Apr-04 16:40:54 Starting Plug-In AK Ikea loaded in 2718 milliseconds
    Apr-04 16:40:54 Starting Plug-In Plugin AK Ikea started successfully in 833 milliseconds
    Apr-04 16:40:54 AK Ikea UpdateConfiguration: scheduled
    Apr-04 16:40:53 Starting Plug-In Initializing plugin AK Ikea ...
    Apr-04 16:40:53 Info Plugin AK Ikea has connected. IP:127.0.0.1:59203
    Broadly know what Zeroconf is, but not sure what this means...

    Thanks,

    R.

    #2
    Originally posted by rahaaas View Post
    Plug-in now loading successfully.

    I’ve changed the IP Address, and entered the ‘Security Code’ from the bottom of the Gateway (should be this as opposed to the Homekit code, right?), but now just getting this in Devices.

    Click image for larger version  Name:	Screenshot 2020-04-04 at 17.07.15.png Views:	14 Size:	11.1 KB ID:	1375046
    Code:
     
    Apr-04 16:41:10 AK Ikea Warning [163]: [newIkea] New Receiver (127.0.0.1): Setting new IP address: 192.168.1.97:80
    Apr-04 16:40:58 AK Ikea [0]: * Set Ikea [newIkea] New Receiver (127.0.0.1) (HSPI_AKIkea.DeviceIkeaBridge) Same: False
    Apr-04 16:40:58 AK Ikea Saved device: newIkea (newIkea), id: Unknown, url: 127.0.0.1:80
    Apr-04 16:40:55 AK Ikea Warning Running on 'linux' - using Locator.MonoZeroconf.DeviceLocator
    Apr-04 16:40:55 AK Ikea ERROR Locator.MonoZeroconf.DeviceLocator: FATAL CreateListener: No Zeroconf providers could be found or initialized. Necessary daemon may not be running.
    Zeroconf id discovering devices on the network. If it's not working, that's still fine if you know the IP address end enter it manually.

    On Linux it's using Avahi service which is usually part of Linux distro. You can check if you have Mono.Zeroconf.Providers.AvahiDBus.dll in bin\AKIkea folder. Or if there are still any initialisation errors in the console window.

    But again, it shouldn't be related to the authorisation issue.

    Comment


      #3
      Ver 3.0.0.20 - added more logging

      Comment


        #4
        Interestingly, I can’t seem to find a bin\AKIkea folder at all. My Linux navigation may be letting me down. Will work out how to do a proper search when I get some time later.

        *EDIT: it IS there - see below*

        The new logging says:
        Apr-05 11:39:50 AK Ikea [163]: Not ok: hubkey '', app '', appkey: ''
        Apr-05 11:39:49 AK Ikea Warning [163]: [newIkea] New Receiver (127.0.0.1): Setting new IP address: 192.168.1.97:80
        Apr-05 11:39:28 AK Ikea [0]: * Set Ikea [newIkea] New Receiver (127.0.0.1) (HSPI_AKIkea.DeviceIkeaBridge) Same: False
        Apr-05 11:39:28 AK Ikea Saved device: newIkea (newIkea), id: Unknown, url: 127.0.0.1:80
        Apr-05 11:38:56 AK Ikea Warning Running on 'linux' - using Locator.MonoZeroconf.DeviceLocator
        Apr-05 11:38:56 AK Ikea ERROR Locator.MonoZeroconf.DeviceLocator: FATAL CreateListener: No Zeroconf providers could be found or initialized. Necessary daemon may not be running.
        Apr-05 11:38:55 Plug-In Finished initializing plug-in AK Ikea
        Apr-05 11:38:55 Starting Plug-In AK Ikea loaded in 2842 milliseconds
        Apr-05 11:38:55 Starting Plug-In Plugin AK Ikea started successfully in 840 milliseconds
        Apr-05 11:38:55 AK Ikea UpdateConfiguration: scheduled
        Apr-05 11:38:54 Starting Plug-In Initializing plugin AK Ikea ...
        Apr-05 11:38:54 Info Plugin AK Ikea has connected. IP:127.0.0.1:45073
        Then, once the key is entered:
        Apr-05 11:40:33 AK Ikea [163]: Not ok: hubkey ‘XXXXXXXXXXXXXXXX', app '', appkey: ‘’
        (obvs the XXXX is the Security Key)

        Have tried multiple variations (0/O etc), case sensitive, but same error. Will keep trying to see if I’m just being an idiot.

        Thanks,

        R.

        Comment


          #5
          It looks like you do have the hubkey, but there's no appname or appkey.

          appname should be generated by the plugin, appkey obtained from the gateway for the generated appname

          I'll check why you may be missing the appname - that's pretty strange. Can you also check for any errors in the console window?

          Comment


            #6
            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:	73
Size:	29.4 KB
ID:	1375203

            Comment


              #7
              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.

              Comment


                #8
                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.

                Comment


                  #9
                  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)

                  Comment


                    #10
                    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.

                    Comment


                      #11
                      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

                      Comment


                        #12
                        Or you can you try to configure from PLUG-INS -> AK IKEA -> Config Page

                        Comment


                          #13
                          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..?)

                          Comment


                            #14
                            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

                            Comment


                              #15
                              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

                              Comment

                              Working...
                              X