Closed jtjart closed 1 year ago
@lovery, @fruggy83 - is the binding still working for you, or do you think this is some specific scenario?
I had some strange issue recently - the power went down for few hours and after that the bridge stayed in "trying to get bridge base id". I tried multiple things - restarting the machine, restarting openhab, unplug the dongle. I had the bridge definition in a file and I moved it to the UI, unpluged the dongle and restart the openhab and at some point it worked.
I remember that my error log looked similar to uploaded one. Currently I am using openHAB 3. I will install openHAB 4 and try to reproduce the error the following weeks.
I observe the same behaviour:
The add-on runs without issues on 3.44
This issue has been mentioned on openHAB Community. There might be relevant details there:
https://community.openhab.org/t/openhab-4-0-release-discussion/147957/12
This issue has been mentioned on openHAB Community. There might be relevant details there:
Same error picture with "enoceanpi" bridge on Raspberry 4 running openhabian, after updating to OH4 release packages, OS does initialize bridge correctly:
[ 1.570848] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 35, base_baud = 0) is a PL011 rev2
But afterwards, looping messages:
==> /var/log/openhab/openhab.log <==
2023-07-24 23:11:52.894 [INFO ] [ernal.transceiver.EnOceanTransceiver] - Transceiver shutdown
2023-07-24 23:11:52.904 [INFO ] [ernal.transceiver.EnOceanTransceiver] - EnOceanSerialTransceiver initialized
2023-07-24 23:11:52.908 [INFO ] [ernal.transceiver.EnOceanTransceiver] - EnOceanSerialTransceiver RX thread started
2023-07-24 23:11:52.909 [INFO ] [nternal.handler.EnOceanBridgeHandler] - EnOceanSerialTransceiver RX thread up and running
==> /var/log/openhab/events.log <==
2023-07-24 23:11:52.896 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'enocean:bridge:enoceanpi' changed from OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id... to OFFLINE (CONFIGURATION_PENDING): opening serial port...
2023-07-24 23:11:52.908 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'enocean:bridge:enoceanpi' changed from OFFLINE (CONFIGURATION_PENDING): opening serial port... to OFFLINE (CONFIGURATION_PENDING): starting rx thread...
2023-07-24 23:11:52.911 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'enocean:bridge:enoceanpi' changed from OFFLINE (CONFIGURATION_PENDING): starting rx thread... to OFFLINE (CONFIGURATION_PENDING): trying to get bridge base id...
Some more details here:
@fruggy83 You have any idea on that? Due to the forced update to OH4 my setup is actually useless as home automation.
It is now suspected that the regression might be caused by #14023 - see https://community.openhab.org/t/enocean-usb300-initialization-fails-with-oh-4-0-0-m3-and-oh-4-0-0-3512/147466/20
@lovery @jtjart are you able to test the PR @dalgwen created?
I have tested the PR from @dalgwen today, and it is working with these changes. Thank you! Will this be implemented in the next hotfix?
Expected Behavior
The USB 300 gateway should get initialized after it has been added as a thing.
Current Behavior
When I add the USB 300 gateway as a thing (via UI or .thing-file) the status stays OFFLINE with the comment "trying to get bridge base id...". It is working with the same hardware when I install the openHABian image 1.7.5 running openHAB 3 instead of openHABian 1.8 running openHAB 4. I have also already tried using different USB Ports for the gateway, without success. I attached the log file with Debug/Trace level of detail. enocean-error.log
Possible Solution
I suggest some changes in openHABian 1.8 or openHAB 4 has caused the issue
Steps to Reproduce (for Bugs)
Context
Your Environment