HTTP or EXEC Binding for EDMIAX Smart Plug SP-1101W?

Add-ons Bindings
21

Hi,

Thank you for this binding, I believe everyone very much appreciates it!

I have one problem though: both with this latest version 1.9 and the previous 1.7.3 I have a lot of log entries in my openhab.log that "[ERROR] [.edimax.internal.EdimaxBinding] - Device with MAC: … not found/discovered."
I have 6 EDIMAX switches around my house, at least 3 of them are always in here, while through the EDIMAX mobile app they are accessible.
Would it be possible to change the logging level of the binding in the first place?
If you could look into the matter it would be nice as well. Some of the switches (SP1101W) are on a fix IP, others on DHCP, but there doesn’t seem to be a correlation.
Thank you!

22

At the moment I am trying to adopt the OH1 binding for OH2. I hope, that heinz did not have any problems with using his code.

23

Did you already had any luck here? Also I thought the second link was the OH2 Binding?

24

I am ongoning, but I have too less time. The first step is done.
The second link above is the current OH1 Plugin, that also works in compatibility mode with OH2.

25

An working version is out now, for 1101 and 2101. I did a pull request to the openhab2 repository. Maybe someone can review it and give feedback. At the moment you have to add the things by IP address. Discovery is not yet implemented, but it is the next step for me.

1 Like
26

I use EdimaxBinding20160729 from derHeinz and I get the following error

2017-05-11 00:48:05.914 [ERROR] [inding.edimax.internal.EdimaxBinding] - Error in communication with device. Device’s MAC: 74DA384AFE1F. Cannot get update from device.
java.io.IOException: Server returned HTTP response code: 401 for URL: http://192.168.1.11:10000/smartplug.cgi
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1876)[:1.8.0_121]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)[:1.8.0_121]
at org.openhab.binding.edimax.internal.HTTPSend.executePost(HTTPSend.java:176)[208:org.openhab.binding.edimax:1.9.0.201607291201]
at org.openhab.binding.edimax.internal.commands.AbstractCommand.executeCommand(AbstractCommand.java:216)[208:org.openhab.binding.edimax:1.9.0.201607291201]
at org.openhab.binding.edimax.internal.HTTPSend.getState(HTTPSend.java:89)[208:org.openhab.binding.edimax:1.9.0.201607291201]
at org.openhab.binding.edimax.internal.EdimaxBinding.execute(EdimaxBinding.java:98)[208:org.openhab.binding.edimax:1.9.0.201607291201]
at org.openhab.core.binding.AbstractActiveBinding$BindingActiveService.execute(AbstractActiveBinding.java:157)[197:org.openhab.core.compat1x:2.0.0]
at org.openhab.core.service.AbstractActiveService$RefreshThread.run(AbstractActiveService.java:173)[197:org.openhab.core.compat1x:2.0.0]

If I try to connect via browser, user admin and the configured password are working. Does someone have an idea? I am currently using firmware 2.08 (it was preinstalled)

Is there a .jar for https://github.com/fharni/openhab2-addons/tree/master/addons/binding/org.openhab.binding.edimax
from Falk Harnisch available so I can test this binding?

Thanks a lot!

27

Hello guys,

since plug firmware > 2.03 basic auth is not possible anymore.

I ordered a new plug yesterday with firmware 2.08. This plug only supports digest auth.
edimax changed the password length in the edilife app. The default password is 1234 but you must set a new one on initial setup procedure, which is minimum 8 chars long.

I checked it out with following modified shell command, after i could´nt get it work with the edimax binding:

curl --digest http://admin:12345678@http://<IPADRESS>:10000/snapshot.cgi

If you check it out without a xml post message, it should not answer anything. If the login fails you get a html response 401 Unauthorized.

So the binding has to be updated, so that it supports old basic auth and digest.

just my 2 cents

gl

28

Any chance to have the binding updated with the new authentication method? :smiley: I have some new adapters I can’t use because of this new feature.
Thanks!

29

I know this is an old thread but I have them working again!
I managed to downgrade the firmware to 2.02 and with success…
Follow this thread https://github.com/mwittig/edimax-smartplug/blob/master/Downgrade.md.