Energenie Binding Issues

Add-ons Bindings
1

Used Version: OpenHab 2.5.9 and Energenie Binding
No Problem with Energenie 1.X Binding
Devices: EG-PMS-LAN and EG PM2-LAN Ports both on 5000 with specific set ip

I uninstall Binding 1.x and install Binding 2.x. I created new Items and Things via Paper UI. I use the same Names as before for each switch that i can use my switch items on site.map as before.

All Bindings and Things are online. On site map via Basic UI no refresh of switch state. I can switch on a socket but nothing but software switch via site maps jumps immediately off and stay off.

After set all items, restart openhab service twice. But no luck. All switches stay red and off.

What can i do now to fix this issue?

@hmerk

2

Please enable trace log and send the log. Also, please post your thing and item config.

3

Thanks for reply. How can i send you thing and item config? I’ve created all via Paper Ui. Normal log there are no anomalys. Will take a look to make trace log enable.

4

In that case, please post a screenshot

5 
2020-10-14 20:27:03.826 [TRACE] [nie.internal.handler.EnergenieSocket] - Start Condition '[17]' send to EG
2020-10-14 20:27:03.829 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with task (int) '[-111, 126, 119, -98]' (hex) '917E779E'
2020-10-14 20:27:03.833 [TRACE] [nie.internal.handler.EnergenieSocket] - Solution '[1, 5, 30, 49]' send to EG
2020-10-14 20:27:03.836 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with statcryp (int) '[18, -43, 18, 18]' (hex) '12D51212'
2020-10-14 20:27:03.838 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with status (int) '[65, 65, -126, 65]' (hex) '41418241'
2020-10-14 20:27:03.877 [TRACE] [nie.internal.handler.EnergenieSocket] - Start Condition '[17]' send to EG
2020-10-14 20:27:03.880 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with task (int) '[-101, 25, -128, -88]' (hex) '9B1980A8'
2020-10-14 20:27:03.884 [TRACE] [nie.internal.handler.EnergenieSocket] - Solution '[27, 0, -16, 44]' send to EG
2020-10-14 20:27:03.887 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with statcryp (int) '[-112, -112, -112, -112]' (hex) '90909090'
2020-10-14 20:27:03.890 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with status (int) '[65, 65, 65, 65]' (hex) '41414141'
2020-10-14 20:27:18.711 [TRACE] [nie.internal.handler.EnergenieSocket] - Start Condition '[17]' send to EG
2020-10-14 20:27:18.713 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with task (int) '[70, 53, 11, 83]' (hex) '46350B53'
2020-10-14 20:27:18.717 [TRACE] [nie.internal.handler.EnergenieSocket] - Solution '[-81, 53, -125, 35]' send to EG
2020-10-14 20:27:18.722 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with statcryp (int) '[-37, 26, -37, -37]' (hex) 'DB1ADBDB'
2020-10-14 20:27:18.725 [TRACE] [nie.internal.handler.EnergenieSocket] - Control message send to EG (int) '[4, 4, 4, 1]' (hex)'04040401'
2020-10-14 20:27:18.831 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with statcryp (int) '[-37, 26, -37, -37]' (hex) 'DB1ADBDB'
2020-10-14 20:27:18.834 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with status (int) '[65, 65, -126, 65]' (hex) '41418241'
2020-10-14 20:27:44.431 [TRACE] [nie.internal.handler.EnergenieSocket] - Start Condition '[17]' send to EG
2020-10-14 20:27:44.437 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with task (int) '[14, -36, 77, 27]' (hex) '0EDC4D1B'
2020-10-14 20:27:44.441 [TRACE] [nie.internal.handler.EnergenieSocket] - Solution '[-77, 43, 27, 23]' send to EG
2020-10-14 20:27:44.445 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with statcryp (int) '[78, 78, 78, 78]' (hex) '4E4E4E4E'
2020-10-14 20:27:44.448 [TRACE] [nie.internal.handler.EnergenieSocket] - Control message send to EG (int) '[4, 1, 4, 4]' (hex)'04010404'
2020-10-14 20:27:44.551 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with statcryp (int) '[78, 78, 78, 78]' (hex) '4E4E4E4E'
2020-10-14 20:27:44.553 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with status (int) '[65, 65, 65, 65]' (hex) '41414141'
2020-10-14 20:27:53.621 [TRACE] [nie.internal.handler.EnergenieSocket] - Start Condition '[17]' send to EG
2020-10-14 20:27:53.624 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with task (int) '[8, 7, 38, 21]' (hex) '08072615'
2020-10-14 20:27:53.627 [TRACE] [nie.internal.handler.EnergenieSocket] - Solution '[-66, 42, -67, 40]' send to EG
2020-10-14 20:27:53.630 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with statcryp (int) '[-123, -123, -123, -123]' (hex) '85858585'
2020-10-14 20:27:53.633 [TRACE] [nie.internal.handler.EnergenieSocket] - Control message send to EG (int) '[1, 4, 4, 4]' (hex)'01040404'
2020-10-14 20:27:53.737 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with statcryp (int) '[-123, -123, -123, -123]' (hex) '85858585'
2020-10-14 20:27:53.739 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with status (int) '[65, 65, 65, 65]' (hex) '41414141'
2020-10-14 20:28:03.854 [TRACE] [nie.internal.handler.EnergenieSocket] - Start Condition '[17]' send to EG
2020-10-14 20:28:03.856 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with task (int) '[-26, 84, -91, -13]' (hex) 'E654A5F3'
2020-10-14 20:28:03.858 [TRACE] [nie.internal.handler.EnergenieSocket] - Solution '[65, 9, 19, 53]' send to EG
2020-10-14 20:28:03.861 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with statcryp (int) '[17, 92, 17, 17]' (hex) '115C1111'
2020-10-14 20:28:03.863 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with status (int) '[65, 65, -126, 65]' (hex) '41418241'
2020-10-14 20:28:03.911 [TRACE] [nie.internal.handler.EnergenieSocket] - Start Condition '[17]' send to EG
2020-10-14 20:28:03.913 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with task (int) '[-95, 116, 69, -82]' (hex) 'A17445AE'
2020-10-14 20:28:03.915 [TRACE] [nie.internal.handler.EnergenieSocket] - Solution '[-92, 59, -18, 50]' send to EG
2020-10-14 20:28:03.917 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with statcryp (int) '[-69, -69, -69, -69]' (hex) 'BBBBBBBB'
2020-10-14 20:28:03.919 [TRACE] [nie.internal.handler.EnergenieSocket] - EG responded with status (int) '[65, 65, 65, 65]' (hex) '41414141'

EG:

As you can see, all switches are off. But lights are on and and also the pumps.

6

Dumb Question, are these LAN or WLAN connected devices ?

7

Answer found in your first post. Seems your devices are on a newer firmware and use Protocol V21, so please delete your things and recreate them as WLAN devices. Those are the only ones using V21 according to the protocol docs.

8

Thank you for your feedback. Yes all LAN but very old I guess…
My rules are working. All lights are off via rule…
Openhab can’t init the thing with wlan.
Test now pms2, it works a little bit better. I get now status if on or off but it’s extremely wear… If I switch on and after off by hand.

9

Please create a trace log showing switching the sockets. It is normal, that you cannot switch to fast, so between, wait about 10 seconds minimum.

10

I’ll test this tomorrow and will give feedback tomorrow. Thanks for your support.

11

Sorry, correct PMS2LAN uses V21, not the WLAN device…

12

Feedback time: Yes PMS2 works on both devices now. Delay time of reaction is at first switch is immediately. Second i must wait up to 30 sec to make the next switch. E.G.: If i switch off it works directly and socket switch off. When i try to switch on, software switch goes on and stay. After a long time up to 30 sec. software switch goes off. Then i must wait again some seconds and can switch on. But via rules it seems to run perfectly.

My be the settings can depended on software version instead of device name. It will not drive crazy some users in the future. :slight_smile:

13

Hey guys.
I didn’t have any issues with the Energenie Binding until I upgraded to OH3 and the latest binding.
I removed the old binding from the textual files and added the new thing (and items) through Main UI.

When I switch on a socket it actually does get switched on, but OH sets it to OFF again immediately.

16:52:14.150 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'Energenie_Socket3State' received command ON
16:52:14.180 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'Energenie_Socket3State' predicted to become ON
16:52:14.199 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'Energenie_Socket3State' changed from OFF to ON
16:52:14.330 [INFO ] [openhab.event.ItemStateChangedEvent  ] - Item 'Energenie_Socket3State' changed from ON to OFF

Also when I use the webinterface of Energenie and switch sockets off/on, OH doesn’t recognize it.

You can see how it’s set up here:

image
image796×937 28 KB

Do you see anything suspicious here?

Thanks in advance.

14

Yes, there is a bug in my binding. Use PMS2 as your thing and it should work…

15

Perfect! Thanks a bunch for the swift reply!

16

Hi,

I will join this discussion right away, because I have a question about possible limitations of the energenie binding.

I had a rule active already under OH2, which switches some of my devices over two existing PMS2-LAN socket strips.

Under OH2 I had to insert short pauses with Thread::sleep, otherwise some problems occured.

Now I notice that it works even worse under OH3 to switch multiple devices on one bar at once. Even small sleep commands only work to a limited count of sockets (namely exactly one in a row!).

Two switching commands distributed one after the other across the two socket strips work great, but as soon as the second command is issued within one socket strip, it switches either extremely late (only with a small sleep of 2 or 3 sec. and then it needs nearly further 5-10 seconds or longer for the swtich) or not at all → the commands are simply lost.

Is there a recommended procedure for switching items for the energenie binding?

Thx a lot!

17

The openHAB 3 binding is no longer using http protocol but energenie data exchange protocol.
This has some limitations like the old implementation. You need to wait aprox 5 seconds between sending commands.

18

Thank you @hmerk - I will give it a try!