Hi,
I have manually upgraded to version 2, the test date and test house modes. I can tick the box but the items stay grayed out. I have cleared my internet cache and rebooted vera. am I missing anything else?
Paul
Well, that snuck through a month of beta testing… 
Good catch!
Download the stable branch version of J_ReactorSensor_UI7.js (right-click, Save link as…) and upload it to your Vera. No Luup reload needed (so you can turn that checkbox off), just hard-flush/reload your browser, then go to town.
I did try uploading the file but that did not solve the problem, so I have uploaded a full copy from the develop branch and it now works.
Thanks for your help 
and all of the great plugins you have created.
Paul
That’s living on the cutting edge! Should be fine, though. No big changes going on at the moment.
they is someone at the helm of the project with good skills
Hi,
Just a quick bug / question, when I change the Test Date and click restart on the status tab it just hangs at starting. if I try the Test House Mode it starts ok.
Which is the best was to get some logs for you?
Paul
[quote=“pukka, post:6, topic:200341”]Hi,
Just a quick bug / question, when I change the Test Date and click restart on the status tab it just hangs at starting. if I try the Test House Mode it starts ok.
Which is the best was to get some logs for you?
Paul[/quote]
On the Reactor master device, there’s a state variable DebugMode that you can set to 1. Then you need to reload Luup. After that, do your sensor test, restarting 2-3 times to ensure that the log flushes the part we want to look at. Then send me that log. Turn your DebugMode back off, or your logs will get REALLY BIG REALLY FAST. Reactor logs a lot of stuff in debug mode. Log transfer via PM or email (on my profile) is best at the moment. Thank you!
I have been playing and i am not sure if its the Weekday setting as a condition, If i remove the weekday condition the plugin works ok. once i add m/t/w/t/f and then go back to Status and click restart it just hangs at “Starting”
I have emailed you some files.
OK. Good news for me, I suppose… this occurs only in the development version you have installed, but not the stable or release versions. So you’re special! That’s the living on the bleeding edge thing…
The log files confirmed, but I was pleased to see that I could identify the problem from the Logic Summary alone, that the operator field wasn’t being set correctly in config by the UI and confusing the Lua code. This is fixable in JavaScript alone, so download the latest version of J_ReactorSensor_UI7.js from the develop branch and push it up to your Vera. No Luup restart needed, but you will need a full browser refresh with a cache flush. Then go in and edit your weekday condition, and fix the operator. From there on out, existing and new should be OK.
Thanks for the support in tracking this down!
Anyone else reading this post: this problem is particular to pukka’s install (running my dev code). DO NOT download and install the above JS file on any other version! The file is not compatible with current release and stable versions. Always check the announcements post for current information on any patches that apply to the current released version.
Looks like that might work will test more later.
Scrap that just rolled past 5pm and the Activities ran. but did not wait until all conditions were met.
No screen shots… logic summary
lets try that
At 5pm the time condition was no longer met, so it ran the untrip scene. What am I missing?
/Pukka gets coat and exits stage left 
I will make sure the door does not hit me on the way out.
My brain was thinking all of the conditions need to be false for the untrip action :o just need to create another reactor to make it work.
All sorted now Thank you very much for your help
Thank you! Your posts and logs were super-helpful.