This is not a binding issue. Some people reported it depends on IP address change, iirc. And somehow the innogy hotline can help. It could depend on the remote access service. I never had this error personally…
Thanks Olli!
I contacted innogy support and got the following answer, unfortunately in German:
Innogy support answer
Da Sie von Nutzung der API sprechen gehen wir davon aus, dass Sie u. U. diefalsche Anmeldeseite nutzen.
Der Einstieg über den Browser läuft über die Seite:
I think they misunderstood and the answer does not help. It seems like the subscription service could have something todo with it. However, I do not have it activated as far as I know but I never get this error.
You can PM me yout innogy username, the last date/timestamp when you got the error message and I can ask the developer team about it.
I got the hint from the innogy developers that the IP address is stored in the access token. I’ll try to implement an automatic token refresh when the “Remote access not allowed” error occurs.
I have since today the same problem. I installed (at least I tried) the Version 2.3.0 you provided with the link above.
When starting openhab the following error is logged:
2018-03-02 18:52:53.046 [ERROR] [org.openhab.binding.innogysmarthome ] - [binding.innogysmarthome] Cannot register Component
org.osgi.service.component.ComponentException: The component name 'binding.innogysmarthome' has already been registered by Bundle 230 (org.openhab.binding.innogysmarthome) as Component of Class org.openhab.binding.innogysmarthome.internal.InnogyHandlerFactory
at org.apache.felix.scr.impl.ComponentRegistry.checkComponentName(ComponentRegistry.java:222) [42:org.apache.felix.scr:2.0.12]
at org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:448) [42:org.apache.felix.scr:2.0.12]
at org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:315) [42:org.apache.felix.scr:2.0.12]
at org.apache.felix.scr.impl.BundleComponentActivator.<init>(BundleComponentActivator.java:268) [42:org.apache.felix.scr:2.0.12]
at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:388) [42:org.apache.felix.scr:2.0.12]
at org.apache.felix.scr.impl.Activator.access$200(Activator.java:54) [42:org.apache.felix.scr:2.0.12]
at org.apache.felix.scr.impl.Activator$ScrExtension.start(Activator.java:265) [42:org.apache.felix.scr:2.0.12]
at org.apache.felix.utils.extender.AbstractExtender.createExtension(AbstractExtender.java:254) [42:org.apache.felix.scr:2.0.12]
at org.apache.felix.utils.extender.AbstractExtender.modifiedBundle(AbstractExtender.java:227) [42:org.apache.felix.scr:2.0.12]
at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:482) [?:?]
at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:415) [?:?]
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:232) [?:?]
at org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:444) [?:?]
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:903) [?:?]
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [?:?]
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) [?:?]
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213) [?:?]
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120) [?:?]
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112) [?:?]
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:156) [?:?]
at org.eclipse.osgi.container.Module.publishEvent(Module.java:476) [?:?]
at org.eclipse.osgi.container.Module.start(Module.java:467) [?:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) [?:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1253) [8:org.apache.felix.fileinstall:3.5.8]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1225) [8:org.apache.felix.fileinstall:3.5.8]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:512) [8:org.apache.felix.fileinstall:3.5.8]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:361) [8:org.apache.felix.fileinstall:3.5.8]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:312) [8:org.apache.felix.fileinstall:3.5.8]
A view lines later, there is still the error:
2018-03-02 18:52:54.245 [hingStatusInfoChangedEvent] - 'innogysmarthome:bridge:SMARTHOME05' changed from INITIALIZING to OFFLINE (COMMUNICATION_ERROR): Remote access not allowed. Access is allowed only from the SHC device network.
Looking at the karaf console, their is only one bundle listed
I had the same problem here as well and it simply disappeared after some undefined time. I have no clue.
Can anyone say if the “remote access not allowed” error is gone now?
This error is also gone. But not with the update I installed on Friday. As I wrote, it just disappeared today. So I am not sure if the problem with my installations was even triggerd by the same reason as the problem of the initial thread owner.
Ah okay. Please have an eye on this. If I did it correctly, the binding should now restart and load a new access-token, which then should work and allow the remote access.
This problem still exists for me. Sometimes it works, but when my IP changes it stops working. Sometimes it starts working again after a couple of hours. In this example it tried from 5 am to connect but it didn’t suceed until 1:30 pm
