-
Notifications
You must be signed in to change notification settings - Fork 13
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
plugin corrupts domoticz system #25
Comments
Hey, delete the plugin from the folder, open the domoticz db with sqlite3 and remove the device from the DB. |
I have a fixed IP address on all my devices, including the TV, that can't be the problem. |
could you help me with another possible solution? |
I have experienced this issue when I used multiple copies from this plugin under domoticz, and modified one of them. Hope this help. |
I don't really understand your solution. Excuse me. |
Well, I have the same problem. For me it causes that my tv have old webos which not support wol. So that means my tv ip not responding when is is standby. It looks that the plugin try to pool or do something with the tv so that's why the domoticz freezing. If I turn the tv on with the remote after that the domoticz start to work again. So I think the solution would be if we can choose the webos version, and if there is no wol, the plugin can sleep while the tv is standby... |
This might be something different you are experiencing. I have observed the corrupt db issue a few times and cannot pinpoint it to anything specific. The TV is at our summer cottage and it happens only when we are there, usually once coming after some period of time - so it is somehow maybe related to the power status of the TV. TV is LG OLED A1 (2021) so it should have latest WebOS. I tried to recover from the corrupt db with editing the db file and disabling the hardware for the TV but it did not work. Going with the backup from day before works though. At home I have LG OLED B7 from few years back (WebOS 3?) and there I've never had this issue. Unlike @mapsindustrial I am not running multiple instances, only one instance per system. |
Tried to look into this a bit and this seems to fit my situation where the db corrupt/crash happens after a period of not using the TV: bramvreugd@18dc37e What I can see in the status log from time to time is: But as such this does not cause the issue - at least not in all cases. Maybe it is like it says in the commit that one would need to be loading the web front end and when this is shown as status, then Domoticz will crash. And as long as it remains the status, it will crash again when you load the web frontend. Although, I'm pretty sure it crashes in my case even sooner than I reload the UI... edit: in my own setup I have now added the time out handler to plugin.py as outlined here: bramvreugd@18dc37e |
I was not able to get this work. the handler by @bramvreugd caused the Tv status not to update at all. Any other suggestions, anyone? |
Hi all, obliviously, before to upload the backup, I deleted the relative webOs plugin folder |
I have installed this amazing plugin on a Raspberry pi3 + together with domoticz and nothing else, after a day or two of correct operation my domoticz system falls and stops working, allí domoticz stop and and it is impossible to recover it.
Help ! Any solution?
The text was updated successfully, but these errors were encountered: