Learn-in doesn't work

[TeggolT]

The problem

Before I embark with you on this oddysey: Is this repo/the maintainers even active anymore?

(you can skip the oddysey and scroll down to the heading if you want. my story is probably quite unnecessary.)

Starting Point:
I live in a house with FSR12 switches. I've ordered a usb300 to try and smarthomeify it.

Note that, while it'd be terrible to do so, you could theoretically use part of this as a guide.

I.Old attempts:

1. I started off attempting to code sth up with the python and js enocean apis I found. Found no way of sending data.
2. followed a guide from the site smarthome-for-dummies (i think)(on a vm). Used the enocean integration. Basically same conclusion as before.
3. i do not even remember how or with what, but I managed to trigger a switch. The FAM lit up, but it couldn't be learned into any FSR12.
4. i had some issues other, see Log full of Waiting for device base ID #142

• the fsr12s are no longer being produced. they're starting to do weird things from time to time, like turning off randomly or switches triggering different channels than they're supposed to. no idea why, but a minor annoyance as this was rare.
• bought some 14-type modules. first, only the power supply, fam14 and one fsr14-4x, then more fsr's.
• plugged them into a wall outlet for easy access.

II.The EnoceanMQTT experience

1. spun up a new vbox vm with haos. after some network issues, started setup and managed to install the addon (for some reason, the new one wouldn't install, so i got the deprecated one.)
2. after lots of dead ends, found the "virtual switches woth fam14" guide on this website.
3. took me a big while to figure out i need to put the switches in configuration.yaml and just ignore the warnings vscode throws concerning "LEGACY_SYNTAX"
4. finally, a switch. state entities don't work (probably bc I don't know what address/id I need to put there) but i managed to make a switch. My "temporary" fix is to just use the e2m_relay_action and have ha remember its last state. suboptimal, but acceptable.
5. learn in a couple switches. the leds on the eltako flash and i hear clicking when I toggle the switch in ha. Great success.

III.The Finale

• bought raspi 4b and installed haos. struggled but eventually succeded with setting up the initial connection and setting up and forwarding an nginx proxy to a myfritz.net address.
• cleared the 14-series modules and learned in all physical switches. wired the modules up and the light switches in the house work flawlessly again.

1. attempted plugin installation. failed due to the issue detailed in Add-on could not be installed #161 . used the forked repo by kijimuna instead.

We have now arrived in the present.

I've set up all switches in homeassistant. as far as I'm concerned, it works correctly.
I've copied the config and devices file from my previous vm.
I tried learning the switches in.
The led on the fam14 flashes when clicking.
The fsr14s seem unimpressed and show no response in LRN mode.
As far as I'm concerned, there's no reason for this to happen. I don't have any errors.

What type of installation are you running?

Standalone

What version of HA_enoceanmqtt has the issue?

Version 0.1.28-2

What was the last working version of HA_enoceanmqtt?

No response

What type of Home Assitant installation are you running?

Home Assistant OS

Anything in the logs that might be useful to solve the issue? (Strongly recommended if applicable)

The end of starting up, with one virtual switch being pressed, and some delay afterwards.
Curiously, I cannot make out where the actual data for the state of the switches is sent. All I see is the IDs i entered in enoceanmqtt.devices.

2025-02-16 08:52:00,197 DEBUG: Received SUBACK
2025-02-16 08:52:10,998 DEBUG: Received PUBLISH (d0, q0, r0, m0), 'enoceanmqtt/relay/flurunten/req', ...  (59 bytes)
2025-02-16 08:52:10,999 DEBUG: Got MQTT message: enoceanmqtt/relay/flurunten/req
2025-02-16 08:52:11,000 DEBUG: enoceanmqtt/relay/flurunten: req={'R1': 0, 'EB': 1, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 1}
2025-02-16 08:52:11,002 DEBUG: Trigger message to: enoceanmqtt/relay/flurunten
2025-02-16 08:52:11,004 DEBUG: sensor data: {'R1': 0, 'EB': 1, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 1}
2025-02-16 08:52:11,005 INFO: sending: FF:A6:E4:80->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x0', '0xff', '0xa6', '0xe4', '0x80', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict()
2025-02-16 08:52:11,006 DEBUG: Clearing data buffer.
2025-02-16 08:52:11,105 INFO: Sending packet
2025-02-16 08:52:11,106 DEBUG: FF:A6:E4:80->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x0', '0xff', '0xa6', '0xe4', '0x80', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict()
2025-02-16 08:52:11,207 DEBUG: 0x02 ['0x0'] [] OrderedDict()
2025-02-16 08:52:11,208 INFO: got response packet: OK
2025-02-16 08:52:59,061 DEBUG: Sending PINGREQ
2025-02-16 08:52:59,062 DEBUG: Received PINGRESP
2025-02-16 08:53:59,132 DEBUG: Sending PINGREQ
2025-02-16 08:53:59,134 DEBUG: Received PINGRESP
2025-02-16 08:54:59,205 DEBUG: Sending PINGREQ
2025-02-16 08:54:59,208 DEBUG: Received PINGRESP
2025-02-16 08:55:59,278 DEBUG: Sending PINGREQ
2025-02-16 08:55:59,281 DEBUG: Received PINGRESP

Additional information

i speak german and will translate if necessary.

a sample switch config in the devices file:

[relay_state/kammer]
address 		= 0x003CEA19
rorg    		= 0xF6
func    		= 0x02
type    		= 0x01

[relay/kammer]
address 		= 0xFFFFFFFF
rorg    		= 0xF6
func    		= 0x02
type    		= 0x01
sender  		= 0xFFA6E493
virtual 		= 1

and the corrosponding switch:

kammer:
        friendly_name: Spielekammer licht
        value_template: "{{ is_state('select.e2m_relay_kammer_action', 'AO') }}"
        turn_on:
          - service: select.select_option
            target:
              entity_id: select.e2m_relay_kammer_action
            data:
              option: AO
        turn_off:
          - service: select.select_option
            target:
              entity_id: select.e2m_relay_kammer_action
            data:
              option: AI

Thanks for reading. Please tell me about any and all ideas you have.

[TeggolT]

I guess the plugin config yaml file might be useful as well:

enocean_port: /dev/serial/by-id/usb-EnOcean_GmbH_USB_300_DE_EO7DONS2-if00-port0
enocean_tcp: ""
device_file: /config/enoceanmqtt.devices
mapping_file: ""
eep_file: ""
log_file: /config/enoceanmqtt.log
debug: false
log_packets: false
use_dev_name_in_entity: false
mqtt_broker: {}
mqtt_discovery_prefix: homeassistant
mqtt_prefix: enoceanmqtt
mqtt_client_id: enocean_gateway
mqtt_keepalive: 60

[mclaassen]

Hi,
I#m on the same problem and have only FSR12 and FSB12 in my home environment.
The question for me is if there might be a solution to configure a virtual switch in HA, that makes the USB300 sends a command to the FAM12
I have a working configuration in FHEM, where the USB300 sends commands to FAM12 and I am able to learn the FSR12 on these.
In HA I'm not able to have a working configuration that makes the USB300 sends sth. to FAM12

Do you got any comments or reactions to your issues here in GitHub?