Seems to have cleared whatever was wrong.
Unrelated - non breaking issue:
I have some WebCore Pistons that interface with the rooms. As soon as I saved one of the rooms the piston I had linked to it started throwing this:
df489399-539c-4dd2-9e51-27d685fdb42f 11:49:57 AM: error ╔ Event processing failed (170ms)
df489399-539c-4dd2-9e51-27d685fdb42f 11:49:57 AM: error ║ An error occurred within executeEvent: groovy.json.JsonException: Unable to determine the current character, it is not a string, number, array, or object
The current character read is ‘o’ with an int value of 111
Unable to determine the current character, it is not a string, number, array, or object
line number 1
index number 0
occupied[microDeviceTile:[type:standard, icon:st.Home.home18, backgroundColor:#32b399]]
^ @line 920 (executeEvent)
df489399-539c-4dd2-9e51-27d685fdb42f 11:49:57 AM: info ╚ Received event [Office Occupancy].occupancy = vacant with a delay of 70ms
9/15/2018, 10:34:57 AM +244ms
+1348ms ║An error occurred within executeEvent: groovy.json.JsonException: Unable to determine the current character, it is not a string, number, array, or object The current character read is ‘v’ with an int value of 118 Unable to determine the current character, it is not a string, number, array, or object line number 1 index number 0 vacant[microDeviceTile:[type:standard, icon:st.locks.lock.unlocked, backgroundColor: #ff6666]] ^
No the error is when I use the repo and try to update from repo. I manually entered the code and assigned the repo to it. This is the first time I had to do it that way.
Yes, tested last night and is working good. I noticed after testing that the maintain temperature is not populating. I removed a room, recreated it and all rules, but still no luck. Seemed to work before update.
It does seem to be maintaining the temp properly, just not displaying it in the room view.
@bangali thanks for the update! I have a small update myself, don’t be mad . I just discovered that I configured a Fibaro Motion as a Fibaro Dimmer 2 and after fixing no more errors (everything stable for 30+ minutes) . Everything is responsive again, yesterday all the rooms were constantly “stuck” in Engaged or Occupied driving me nuts. The adjacent room feature also works without hiccups without the update!
TL;DR a faulty or misconfigured (motion) sensor can break everything and make you go crazy.
Been a while, everything was working very smoothly. Since the latest update(s) my rules now only switch lights on on change from vacant to occupied / engaged, they no longer switch lights off on change away from Occupied / Engaged to Vacant. This means all lights stay on unless I manually switch off via Hue.
My hallway motion also seems to be stuck on Occupied / Engaged and will not change to Vacant.
Any ideas? I have combed back through all the rules and can’t figure it out.