Closed lorenzodeveloper closed 1 year ago
It's a new event that was introduced last minute into openHAB. Unfortunately the only way to fix this issue is to revert back to openHAB 3.2.
If you are feeling adventurous you can try the beta which fixes this issue but introduces other breaking changes. You find the beta thread in the openHAB forums under "apps & services" -> "3rd party"
Hi! Thank you for the quick feedback!
I tried to revert to OH 3.2.0 but it has not gone so well (don't know why, but openhab things stored in jsondb managed to disappear after downgrading, recommended to do always a backup before reverting/upgrading). So I decided to install again 3.3.0 and upgrade habapp to the beta version. At first it didn't work because some dependencies required Python>=3.8, so consider to upgrade python if you, like me had Python 3.7.3. Then I updated habapp to the beta version, changed the "listen_event" / "run_every" calls, updated the configuration file both logging and config yaml files and now everything is working like a charm :)
The only thing that now is popping up in the log, but seems to not affect the normal functioning of habapp is an error related to
BufferEventFile:
class: logging.handlers.MemoryHandler
capacity: 10
formatter: HABApp_format
target: EventFile
level: DEBUG
in logging.yml
file.
Here is the thread mentioned by @spacemanspiff2007 -> https://community.openhab.org/t/habapp-1-0-beta-test/136952
Hope it helps. Thank you again!
Fixed with 1.0
Hi, After I updated openhab to v3.3.0 I cannot make my rules to work again. There is only an error that is popping up every time in the logs:
What I tried:
System info
Release = Debian GNU/Linux 10 (buster) - openhabian Kernel = Linux 5.10.103-v8+ Platform = Raspberry Pi 4 Model B Rev 1.4 OpenHAB version = 3.3.0 stable HABApp version = 0.31.2 Python version = 3.7.3
Is there anything I can do? Thank you.