Shutters not working with USB300 (ESP3)

[grimmpp]

Sent by tden159 in HA Community.

after the release of v1.4. i tried out your solution with an USB300 as my gateway. I was able to integrate all my lights without any problems. However with my cover/shutter integration i have a problem which i cant solve on my own.

Logs:

2024-04-14 08:06:54.961 ERROR (Thread-5) [enocean.communicators.SerialCommunicator] Received ESP3 response with with return code WRONG_PARAM (3) - 0x02 ['0x3'] [] OrderedDict() 
2024-04-14 08:06:56.771 ERROR (Thread-5) [enocean.communicators.SerialCommunicator] Received ESP3 response with with return code WRONG_PARAM (3) - 0x02 ['0x3'] [] OrderedDict() 
2024-04-14 08:06:58.484 ERROR (Thread-5) [enocean.communicators.SerialCommunicator] Received ESP3 response with with return code WRONG_PARAM (3) - 0x02 ['0x3'] [] OrderedDict() 

My setup:
HA OS → USB300 → FAM14 → FSB14
Eltako v1.4.2

My config (abstract):

eltako:
  gateway:
  - id: 1
    base_id: FF-88-03-00
    device_type: enocean-usb300 
    devices: 

        light:
        - id: FF-8F-AB-01
          name: F4SR14_LED FF-8F-AB-01 (1/4)
          eep: M5-38-08
          sender: 
            id: FF-88-03-01
            eep: A5-38-08

        cover:
        - id: FF-8F-AB-96
          name: FSB14 FF-8F-AB-96 (1/2)
          eep: G5-3F-7F
          sender: 
            id: FF-88-03-40
            eep: H5-3F-7F
          device_class: shutter
          time_closes: 25
          time_opens: 25

Sender ID is in the PCT14 with function 31.

I tried to understand the Error Message, but couldnt figure if the problem is based on my config or some other problem with the integration.

[schlegel]

I have exactly the same error "Received ESP3 response with return code WRONG_PARAM (3) - 0x02 ['0x3'] [] OrderedDict()".

Can I help somehow with more information?

[grimmpp]

Can you let me know when it happens and which gateway and version of the integration are you using?

[schlegel]

I'm using a usb300 gateway and the feature-branch version of the integration. It happens when I click a button (up or down) on a cover.

[schlegel]

[schlegel]

I kinda found the problem. I set the base id to FF-80-80-00 (like shown in https://github.com/grimmpp/home-assistant-eltako/tree/main/docs/gateways). After some crazy debug with logging, I found out that I have a total different base id. Setting the correct base id fixed everything. Do you know a better way how to get the base id of the usb stick? Might be a good addition to the documentation.

[grimmpp]

There are commands and tools to query the base_id via serial protocol.

The easiest way I know is to use eo_man. Just plugin ESP300 and it should work similar to FAM14 like described in here.

[grimmpp]

I've looked into the code but I don't see a relation between base_id and the cover command. Did you also use a sender id which was not based on the base_id?

[schlegel]

yes, both base_id and therefore also sender_id were not aligned with my esp300. as the bus can query the base_id of the stick, maybe you know a way to show it in home assistant. could help some people

[grimmpp]

Theoretically there would be a way but only for a new gateways. And the question is when to display. Actually you need to provide the config beforehand. That's why I developed eo_man which can autogenerated a default config containing all the things configured in your bus devices. Kai Schlegel ***@***.***> schrieb am Mi., 17. Juli 2024, 21:59:

…

yes, both base_id and therefore also sender_id were not aligned with my esp300. as the bus can query the base_id of the stick, maybe you know a way to show it in home assistant. could help some people — Reply to this email directly, view it on GitHub <#96 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC4PCJ2MMVSSIU4JNG5KACDZM3EIZAVCNFSM6AAAAABGPDX7XSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZUGE2DSNJZGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[schlegel]

maybe a warning at startup if the base ids are not matching? anyways, it was not a bug, but only a misuse from my side. i hope it‘s the same for the original author of this bug

[grimmpp]

I've tried that earlier. At this time the com-lib did not provided it.
I've put in onto my backlog.