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
[BUG]: failure after adding a sensor triggered area #647
Comments
I just experienced another crash after adding a weather-triggered second area:
I'll pull the container again and this will fix this mess |
Latest is a newer version... should work. I used that for testing but I will remove it. For now stick with the version 4.1.0 And in order to reset this, just remove the database files at location |
I already did this, while testing with different configurations. The problems appear every time, I add a second area. I'll do more testing tomorrow.. |
And another Problem after adding a second mqtt-service.
Additionally, mqtt doesn't work (I don't see any logins on the mqtt-Server) at all but throws no errors. |
I am currently making a new docker image (version First issue is that you have selected a dependency on you lights area. That does not work. You should toggle the Second one looks something not correct on the lights area. Not sure how many you have configured, but at least one is faulty. It could be fixed with the And the notification part is not yet finished in the 4.1.0 version. In the test version is should almost be finished. But I have not tested with two MQTT accounts. But with one account, I think it should work. I have made a connection to an external server without an error and sending messages is also not giving an error. Therefore I guess it should work with at least one account. |
First of all: thanks for the super fast response Something went wrong with the encryption in matrix... This morning, I tried the config (that didn't work in docker) on fresh normal installation and it worked.
Ahh ok! That makes sense. But then, I didn't understand this field.. ;)
I had only the one area for the lights and the switch was set, but it seems to be working for now.
I tested with correct and false crendetials, ports and hostname but there are no reactions in the logs at all. |
After some further investigation, It turned out, that the load_setup(self, setup_data) is only excecuted at the startup, not after a save-operation of the gui. Therefore, the mqtt-config is not tested, until the system is restarted. After a restart, I've got this Error:
I'm now trying to find, what's the problem here. |
Hi, did we fix this during a Matrix chat? Only thing left is (re)loading the service after changing/adding... |
Hi! |
So the reloading should now also be fixed. And when there are errors with the MQTT server, it will not hammer over and over but just stops with an error. |
So, if you can test this, and confirm, then we can close this issue |
From my point of view, the test-docker-version is the latest version, isn't it? Nonetheless, a miss-config doesn't lead to a halt. |
No, not the docker version. Docker builds takes 2 hours... so I sparsely make them, just for me to test a new docker update. But it will not have the latest code. The last fix in mqtt is only available in the git source code |
So I fixed now the last issue with reloading the MQTT settings and losing the version number in the client id. That is now fixed and I would like to close this issue. |
Setup:
Describe the bug
First of all, I added the lights and that worked as expected.
After adding an area for the humidity or for the heating (both ended up in the same failure with excatly the same lines of code),
I got the following issue.
After this failure, the frontend slowly dies and the container changes into "unhealthy"-state.
Only a roleback to the previous-config brings the system back to life.
Log:
After killing and restarting the container some additional lines appear in the log:
config-screenshot:
If you need something else, just let me know.
The text was updated successfully, but these errors were encountered: