[V4] Enocean Integration

Development
21

Hi!

I’m diving right into this discussion, like a gatecrasher. In short, I’ve been following this project from afar for a while, without being able to dream of home automation at home. Recently, it’s finally accessible. So I have a bunch of switches at home working with enocean.

I’m not a developer by training, I’m just resourceful. So @Jean-Philippe, I’m really keen to test your integration. I’ve already retrieved and installed your branch. Is it also compatible with the 310 USB dongles? Anyway, I’m up for as much information as possible to be able to provide complete feedback (or even dabble a bit in JS :stuck_out_tongue: …?).

22

Hello!

Yes, it should work, is this the TCM310 USB key? I have that.

It’s relatively simple, in the integration view, you go here:

image
image1222×361 24.8 KB

You select the port of your dongle (/dev/ttyUSB0?) and you connect.

Then you go to the Learning page and you put your equipment in Teach In (or Learn), and they should appear.

Don’t hesitate to give me feedback, maybe in PM to avoid clutter, but I would be happy to improve the thing, maybe we are many to have enocean sleeping :smiley:

23

It doesn’t pollute, on the contrary, so everyone can see the progress and the feedback made :slight_smile: It’s better here I think!

24

Hello!

A brief update. I managed to tinker for an hour or two, without success. My first attempt was probably due to an old machine missing some slots (literally), so it couldn’t do anything with the dongle (connection impossible).

I started cleaning up a Raspberry Pi to set up an instance based on the enocean-service branch. I haven’t had the chance to complete the installation yet. I wish I had more time, but I wanted to at least not leave a big gap after my first intervention.

25

:thinking: :sleepy:
After several attempts and different methods, it is impossible to get the dongle recognized by Gladys. /dev/ttyUSB0 is indeed there, the machine is well configured (at least according to the manufacturer’s documentation), but no, the connection is not established. I systematically get this error:
Error: no confirmation from Enocean device for sending this telegram: 5500010005700838

26

Strange this!
I have never encountered this error, is the connection to the port /dev/ttyUSB0 working properly or does the error occur at this moment?

27

How did you deploy Gladys? In dev mode or via Docker?

This smells like a permission issue.

28

Yes yes! That was it. After correction, I can control the dongle (but only at server launch; if I disconnect, I have to restart everything). I am in dev mode.

I was able to see that it picks up my switches, without knowing what they are; I need to find my documentation to know their code and test more in depth. I don’t have any other hardware but since Gladys can take it into account, I think I will get one or two sensors to see.

Thanks!

29

Cool.

For reconnection, I think there is no automatic recovery, you should be able to reconnect it in the integration management page, without having to restart Gladys, right?

To be improved anyway.
For the switches, are you able to manipulate them despite everything?

30

In fact, it reconnects each time it is restarted, but in development, this is expected since everything restarts. Otherwise, unless you disconnect the dongle, it’s not bothersome.

I think I have rocker switches with the EEP F6-02-XX (I need to confirm the XX); so I have my first relevant question: for the learning process, I had to do everything in the distribution board, on the relays. Do I need to repeat this operation? Because the switches don’t have anything else. When I log the data from onMessage (which is indeed called when I use a switch), I have the correct key but the byte is empty.

RadioERP1 { _raw: ByteArray(0) [] }

31

When you talk about the division board, have you paired your switches with modules on the board?

You would need to check the documentation to see how to put it in pairing mode.

I have switches in F6-0X.. that systematically send a Teach In payload.
While built-in modules of type D2-0x.. need to explicitly go into Teach In.

Then, you need to be in the Learning view of the integration to see what Gladys recognizes.

32

Okay, I’m running my module at home.

So first problem indeed, it’s the access to the USB dongle, for my part, I added a udev rule:

in:
/etc/udev/rules.d/100-rules

ACTION=="add", ATTRS{idVendor}=="id", ATTRS{idProduct}=="id", SUBSYSTEMS=="usb", MODE="0666

Then, I updated the library and the dependencies used, which must be the cause of your empty payload.

33

I have the impression that Gladys loses communication with the USB key after a few hours.. nothing specific, I don’t really see any traces in the logs…

I use serialport in my dependencies, if that rings a bell to anyone…

34

That doesn’t ring a bell… try adding logs everywhere (I think serialport must expose quite a few events?)

35

Serial port access is exclusive, if you try to access it with another software, it « kicks » Gladys.

I had the opposite problem with my Z-Wave dongle. (I had to disable Gladys’s Z-Wave service to use zwavejs2mqtt)

36

Hello,
I just installed Gladys but I see that unfortunately the EnOcean integration doesn’t seem to exist yet (80% of my setup is EnOcean).
Since the topic is old, is it still planned to eventually integrate this branch?
If not, is it possible to go through something other than an integration?
Thanks in advance for your answers and have a great summer :slight_smile:

37

Hi @fmouton !

As far as I know there is no active development of EnOcean compatibility on Gladys.

However, you can use Node-RED with Gladys and connect your EnOcean devices to Node-RED :slight_smile:

38

Hello,

I confirm, currently I don’t have time to work on Gladys, so the integration that I started writing exists only « on my machine ».