-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use custom EEP.xml #109
Comments
Hi @OlwinFroon, TL;DR This will be fixed by 0.1.29. Collapse to see the detailed explanationThe issue comes from the EEP_FILE_LOCATION=$(find / -name "EEP.xml" -print -quit 2>/dev/null) This will look for a file named EEP.xml in the whole Docker container (yes, an addon is a Docker container) and select the first one encountered as there should always be only one. This can be fixed by excluding the EEP_FILE_LOCATION=$(find / -path /config -prune -o -name 'EEP.xml' -print -quit 2>/dev/null) Version 0.1.29 will fix this issue. |
Oh. So the issue wouldn't have occured if I just renamed the custom to anything else but EEP.xml. Gotta try that ... |
Woo hoo, renamed it to myEEP.xml and it works :D |
As simple as that 😅 |
Okay, the workaround works, the fix will come with the next version. |
Reopened for tracking |
The problem
As depicted here, HA_enoceanmqtt stops working as soon as I edit a custom EEP file into the configuration.
Perhaps it is because of my configuraition setup. I didn´t want to clutter up my config root directory, so I added a directory /config/enoceanmqtt to hold
device file, custom mappin and EEP and the log.
Insights so far:
a) adding a custom EEP.xml will cause E2M to stop right after the start.
There are no log entries.
b) adding a copy of the same custom EEP.xml to the /config directory (without removing the one in the subdirectory or changing the configuration) will cause E2M to run, but it will ignore the custom EEP.
c) the reason for this issue lies in the
run.py
script of HA_enoceanmqtt-addon.What type of installation are you running?
Addon
What version of HA_enoceanmqtt has the issue?
0.1.28-1
What was the last working version of HA_enoceanmqtt?
0.1.28
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)
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: