forum

Ah I see, it's quite possible it's because of the MQTT plugin, we're currently troubleshooting an issue with it over on github: https://github.com/Edubits/Zway-MQTT/issues/16 When I started looking into the zway crashes I noticed that the MQTT plugin had a lot of errors in the zway log (thousands in...

Ok, so here are roughly 2000 lines from strace and the results from lsof:
http://mukkas.se/blandat/strace-zway.txt
http://mukkas.se/blandat/lsof-zway.txt

I guess I should do this after it breaks huh? Right now I'm running a scheduled restart of z-way-server every six hours to prevent this from happening. If I don't it usually breaks withing 12 hours. The funny thing is that it runs normally for quite a while, when I ran lsof after restarting the serv...

And after checking lsof after the system once again stopped working, I found this line repeating ~65000 times:

I have the same issue. I've noticed that the log seems to be filled with "Too many open files" errors: [2017-01-05 11:10:08.270] [I] [core] Error: can not write back config to storage: Error: Too many open files [2017-01-05 11:10:08.318] [I] [core] [BaseModule-44] Set lastLevel to 1.2 for ...

Not quite, it works but the interview never completes:

Not really sure what happened but I tried going back through both 2.2.0 and 2.1.1 with no luck. Ended up re-including the dimmers and now they work, re-installed 2.2.1 as well. As an added bonus I was finally able to create a direct association from two of my motion sensors to the dimmers which had ...

Before 2.2.1 my dimmers actually worked even though the interview never completed, but now I no longer see the actual dimmers, only a ton of alarms and power meters. So 2.2.1 made my dimmers useless because now all my automation with the lights is broken. Here's the interviews: http://i.imgur.com/ec...

Still not resolved in 2.2.1...

I also have this problem with v2.2.1-rc3. I have three Fibaro Dimmer 2 (FGD-212) and they all create a bunch of these warnings. I've been able to alleviate it for a few hours by restarting the server. I thought I had fixed it yesterday by changing the Device Description in Expert UI, but after a few...