Open ErikDB87 opened 3 weeks ago
On request of @lsiepel, attached is the TRACE
log (the Linux machine running openHAB was rebooted, and openhab.log
notes 2024-11-03 14:40:08.273
as the moment of Starting openHAB 4.2.2 (Release Build)
).
I only reinitiated the gateway at 14h46, which is shown in the logs: 2024-11-03 14:46:30.803 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - shutting down transceiver
. Before this moment, there's no entry with Received header
.
This issue has been mentioned on openHAB Community. There might be relevant details there:
Expected Behavior
After a Linux reboot (or
sudo systemctl restart openhab.service
), the EnOcean gateway should be able to send commands and listen for updates.Current Behavior
After a Linux reboot (or
sudo systemctl restart openhab.service
), the EnOcean gateway is able to send commands to the devices, but doesn't listen for updates...If I reinitiate the gateway, these updates start kicking in. I'm
TRACE
logging the binding, and after the reinitiation entries likeReceived header
appear, but not before.Possible Solution
No idea. As a workaround, I might be able to reinitiate the gateway after openHAB startup, but that doesn't seem like a serious solution.
Steps to Reproduce (for Bugs)
No idea...
Context
I want to receive updates from my wall switches.
Your Environment
See also https://community.openhab.org/t/beginners-guide-for-implementing-eltako-fsr14-fsb14-fud14-via-fgw14/136872/91