Ah, yes that was exactly it, TZ env variable was missing, no idea why it went away after portainer recreated the container.
Yeah, I'm running on linux (ubuntu 18.04lts) but I use portainer to manage my containers.
Thanks for the tip for resolving the error, I'll poke around and see if i can find one that got corrupted. I don't think I've ever had this disk ever go full before but this server has had a couple annoying crashes over the past year, maybe one of them corrupted something in reactor.
Hi, I've been using msr for a while now and haven't had timezone issues until today when I updated to latest docker image (latest-22080-ae7212f)
both docker date command and my local date command show the same time, same timezone, but for some reason MSR shows the host time as 2 hours in the past as a result all my timed rules run 2 hours late.
my locale is set correctly in the host machine and is bound into the container as well.
One possible hint I get is maybe this from the container startup log, but other than timezone stuff everything else seems to be working fine and all my settings loaded up just fine.
[latest-22080]2022-04-07T07:52:52.423Z <SystemController:null> Module SystemController v22080
root {}
CommonJS loading
[latest-22080]2022-04-07T07:52:57.236Z <Engine:CRIT> SyntaxError: Unexpected end of JSON input
SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at IndividualFileStrategy.getDataObject (/opt/reactor/server/lib/IndividualFileStrategy.js:121:46)
at Container.getDataObject (/opt/reactor/server/lib/Container.js:102:53)
at new GlobalExpression (/opt/reactor/server/lib/GlobalExpression.js:105:179)
at Function.getInstance (/opt/reactor/server/lib/GlobalExpression.js:123:89)
at /opt/reactor/server/lib/Engine.js:1349:67
at Array.forEach (<anonymous>)
at Engine.initializeGlobalExpressions (/opt/reactor/server/lib/Engine.js:1345:145)
at Engine.start (/opt/reactor/server/lib/Engine.js:590:285)
at /opt/reactor/app.js:362:103
Let me know if I can provide further info to help debug this.
Thanks
Not sure if anyone's suggested this, but it would be great if the expressions could be grouped. Like for me I have tons of variables for my thermostats, tracking all sorts of house parameters which all of the thermostats share. Would be great to have an object to contain them all so I don't have all of the expressions mixed up. something like thermostat.first_floor.heat_current_setpoint would be really cool.
Thanks, that worked for my needs. So far I like this new system, seems much snappier.
Let me know if this is correct, I'm using a reaction in a rule to set the global average expression to my local ${{average}}. Is that the correct way?
Ah, so I can't copy over some of my vera reactor logic.
How do I reference global variables within rules? do they just work like local variables? or is there some sort of global scope object I have to use?
I'm guessing I can pass data between rules by using a global expression
Also, how do you recommend structuring one of your old guides where a bathroom humidity sensor samples humidity into a dictionary then calculates averages and such. then another vera reactor was consuming that average and checking if it's above/below current humidity and turning a fan on off?
Thanks
I've found I can see variables from other rule sets within the rules themselves, via the "Variable Value" condition type. Just need to figure out now how to get to this in an expression.
Is there a way to get a variable from a rule into an expression of some other rule?
Just like what Vera Reactor did with the Export button then allowing you to reference that variable in another rule set. I'm guessing there's a function like there was in vera getstate()? Thanks
Hopefully my question is clear, it's late 