Logon screen timeout

[cw-kid]

Not related but I am seeing these errors in the log:

Expression compilation error for deviceclass heatonly_thermostat hvac_control.mode: Error: Parse error on line 1:
...tochangeover:'auto'}[lower(value)] ?? va

Device 190 is the Secure Boiler Relay Switch related to the Secure Thermostat device.

2021-02-25T18:03:47.240Z <VeraController:ERR> Exception/error while updating Entity#vera>device_190
2021-02-25T18:03:47.242Z <VeraController:CRIT> ReferenceError: expr is not defined
ReferenceError: expr is not defined

[cw-kid]

OK emailed them.

Thank you

[cw-kid]

24:04 am here now, the lights scheduled to turn off at 23:55pm haven't turned off again.

Here is a screen shot of the rules summary card.

I don't know why they aren't turning off ?

Thanks

[toggledbits]

Are you in 21056?

[cw-kid]

@toggledbits Yes

Two more rules here both are set to run at 9am

One worked this morning OK and did its action, the other rule the bottom one in the screen shot, that didn't run its action.

This is the rule that didn't run, have I done something wrong ?

I've just updated to the latest version of MSR (reactor-0.1.21057-f143fd3-generic.tar) and now that rule that didn't run this morning looks like this:

[Matohl]

So it worked after the update?

[cw-kid]

@matohl I've no idea what's going on.

That rule that didn't run when it should of at 9am has now ran its action at 10.04am after I updated and restarted MSR etc, as it sent a notification to my phone in Telegram

[Matohl]

Yes, it went true when you restarted (it's still after 09.00). Why it didn't run at 09.00 I can not tell, I have similar triggers that's works fine

[cw-kid]

I have created a lot of other rules, some of them also with Constraints and none of those rules say null or no data in the Constraints in the rules summary card.

I've gone through them all now again looking and it seems I only have two rules which I have highlighted above that don't run and they say or have said null or no data in Constraints.

All my other garden lights have turned on and off OK, but they are using a sunset offset not a specific set time.

But that rule to turn off the Festoon lights at 23:55pm has never run since I created it.

I also have rules for the window coverings setup for specific times in the morning and generally they have all run at their set times OK.

I will see what happens tomorrow at 9am with this "Lounge Blind Slats" one ?

Thanks

[cw-kid]

The 11:55pm rule that never worked since I created it, I deleted it. I then created it again exactly the same as I did before. Looking at its Summary card the Constraints stated no data / null etc. I then edited the rule and changed its time to 9:00am and saved. I then edited the rule again and set it back to 11:55pm and saved.

The rule now runs and turns off my lights at 11:55pm or it did last night at least anyway. So assume it will work every night now.

I created another new rule not related to run every night at 10:30pm and that one worked first time no problems, so not sure why I have had issues with a few rules.

The 9am rule to open the Lounge Blind Slats didn't run this morning again, so I've deleted it and recreated it, see what happens with that tomorrow morning ?

[toggledbits]

Remember two things:

1. Log files are pretty good at telling what's going on, and really good at help me determine what's going on;
2. Open PRs are my highest priority.

[cw-kid]

I emailed the logs to you as you asked above.

Thanks.

[toggledbits]

OK. Not seeing an email yet... you used the address in the "Support" section of the About page?

[cw-kid]

This post is deleted!

[toggledbits]

@cw-kid I removed your post just for my own anti-spam/scraping reduction, no other reason. The address you showed is fine. If you know how to reach me in my primary domain, that's fine too. I just point out the About page because it will always be there.

[cw-kid]

No worries.

Check your patrick@ primary domain I sent the logs there on the 26th

[toggledbits]

Logs from two days ago don't help when (a) you've update the software, (b) the condition that was a problem now isn't, and (c) a condition that wasn't a problem now is. Too many changes. Need fresh logs.

The log does show that the rule "Heating turn ON Check Opened Windows" needs to be updated to use the hvac capability attribute (which didn't exist when you created the rule apparently, so you're using the device's extended attribute). You just need to go in and fix that rule. I don't have the "Trouble" system working yet, which will pick stuff like that up.

[cw-kid]

@toggledbits Thanks for the heads up. I've changed that rule to use hvac_heating_unit.setpoint instead then.

I'll do some more testing on these two problem rules with set start times. I believe one is working now after I recreated it and the other I need to see if its working now or not ?

Thanks

[toggledbits]

If it's not working, don't recreate it yet. Save the JSON file with its ID from inside storage/rules and send that to me (you can just post it on a PR--should be small/short). After you've capture it, then you can go ahead and recreate. If there's anything broken in the rule itself, I should be able to see it.