There is an issue with usb-serial devices on RC1 as reported by @Andrew_Rowe, @davorf and I experienced it on Windows 10 and Raspberry PI (using openhabian 1.5): the serial items (zwave controller and RFXcom for me) keeps reinitializing on openhab level, it is fine on the command line (using lsusb, dmesg etc…). It was causing very high memory and cpu usage and even using swap, the pi was unusable after a few hours.
Switching to latest snapshot, for me it is 1774, fixes the issue
I created this thread in the community forum and i was told that is related to the getEvent() issue.
I was not brave enough to create an issue, as i didn’t want to create more work for the project members and i thought there was already one as i thought this is related to the getEvent() issue.
Of course not! I am absolutely sorry if this was the message of my post. I am very grateful for the work of cweitkamp and the others who are contributing to this project. I just read his post and suspected that he did some work in the hue binding and is not able to pursue the support of the plugin anymore:
Not sure if this is new “feature” or an unintended consequence of recent changes, but it seems that every time I use PaperUI to add or delete a Thing or Item, an OpenHAB System restart is initiated. This did not seem happen prior to 2.5.0M6. I am running OpenHAB in Docker. Did I miss something along the way?
UPDATE: This issues seems to have resolved. I rolled back to 2.5.0M5, deleted the cache and tmp directories, updated to 2.5.0RC1 and restarted the docker 2 twice. Since doing this I have not noticed any restarts when I add Things or Items using PaperUI. I believe this glitch is real, but was easily resolved at least for now.
UPDATE2: Since I now know this thread is not intended as an alternative to bug reporting on git, this update is more of an FYI. However the restarts when using PaperUI to add a new Thing or new Item are back. It’s more of an annoyance for me and I may not have even have noticed except that I have a rule that triggers when “system started” and results in a notification being sent. However I wonder about the efficiency of this approach when adding a large number of Items or Things with PaperUi.
Before I do anything on git, can anyone confirm if this behavior Is by design or indeed a bug. As I said, I did not notice this before M6, and my rules have not changed.
I’m pretty sure this is not by design…maybe. Are you certain that OH is actually restarting, or are you just seeing your System started Rules executing again? If the former, this is not expected behavior. If the latter, I think this is expected behavior.
“System started” is somewhat of a missnomer. It runs whenever the .rules file is reloaded which can occur in response to events besides a full openHAB restart. I am not seeing OH restarting when I create an Item through PaperUI.
Rick, thanks for the insight and I guess I’m not sure which is occurring, but based on the fact that you are running docker and not seeing this I am inclined to believe that it is the latter. Also I misspoke. It occurs not with the creation of an Item per se, but linking a new item to a thing.
What is throwing me is that I did not notice this behavior before M6 and the Things and Items I was adding were not related to any of my current rules. Can you think of anything in the logs that I should pay particular attention to? I did notice that all of UI (Hapanel and BasicUi) do seem to get reloaded as well when this happens. I will dig a bit to see if I find the root cause. For me it is mostly an annoyance as my system is well developed and I would only occasionally add something new. For a new user however, if real, it could be more of an issue.
Well, what get’s printed to openhab.log should make it pretty apparent whether OH is completely restarting of the .rules files are just reloading. If restarting you will see a bunch of “stopping service X” type logs followed by “started service x” type logs when OH comes back up.
Do you see any “Loading module…” log statements when you link to an Item? Are all of your Rules in one .rules file or many .rules files? If many, do all of your system started Rules run or only some of them?
I created and linked an Item to a Channel through PaperUI that I did not previously have an Item linked to and again (new Item, new Link), I did not see anything unexpected. Neither my rules ran (I’m using Scripted Automation so can’t say if .rules files would have run) nor openHAB restarted. So I don’t think it’s specifically Docker at play here.
Removing the Link and the Item also did not cause anything unusual to happen. I’m running the latest SNAPSHOT, not RC1 (I got hit by the MQTT bug that was fixed yesterday).
You would see that behavior if OH decided it needed to reload your files for some reason.
Now that an issue has been entered and @cweitkamp is looking into it, it might be a perfect time to point you to Bountysource, where users actually CAN post a bounty on issues that they wish to have solved - and no: No bounty is too low since it can always be regarded as a kind gratitude to the developer, who picks it up, even if he isn’t impacted by the issue himself.
Thanks again Rich for taking time to respond. Based on what I can see in the logs, it does NOT look like OpenHAB is doing a full system restart. My Rules are in several different files as I’ve tried to organize them based on function and hardware interaction. I only have a single rule in “My Presence Detection” .rules file that is called when “system started”, and nowhere else. This rule sets the groupPresence to off when triggered and then notifications are sent when we arrive home and groupPresence is set to on… This happens when our phones pass through a geofence(GPSTracker) or are reconnected to our LAN or iCloud. If I create a new item and link it to a new or existing thing, then this rule is being triggered. I’ve randomly tried a number of different Things and same behavior results. Just very peculiar “New Behavior”. Don’t waste anymore of your time this as it seems to be limited to me. I’ll keep digging and if I can pin this down I will report back as down the road it afflict others.