How to upgrade from an old version of MSR?

[cw-kid]

I tried to create a Schedule to turn my lounge lamps on 40 minutes before Sunset.

But it didn't run and the lights didn't come on.

This screen shot is now, well after sunset time.

Triggers:

Constraints: None:

Set Reaction: (Action)

In the reactor.yaml file I have the lat / long :

Not sure if I have done something wrong or if there is a potential problem ?

Maybe I've got too many digits. I've change them to these off another website:

Will see what happens tomorrow ?

EDIT just noticed it was set for 40 minutes after sunset.

Had to use -40 and it says before sunset now, maybe that was the problem then.

Thanks

[toggledbits]

The offsets for sunrise/sunset can add a little confusion in the context of "before" and "after" operators on the conditions. This is in the docs, but to reiterate here, for time-only conditions (like sunrise/sunset, and date/time with only time components):

before <time> -- will be true between midnight and time (changes to false at time);
after <time> -- will be true between time and midnight (changes to false at midnight).

Remember that action takes place on changes, which is why "after <time>" is equivalent to "at <time>", but improved by the fact that if the system is down at <time>, when it comes back up, the condition will then be satisfied and the missed action performed.

Now, with respect to sunrise/sunset, if you want the lights on at 30 minutes after sunset, thats "after sunset + 30". If you want the lights on from 30 minutes before sunset (so from 30 before sunset to midnight), that's "after sunset - 30".

[cw-kid]

Yeah my bad.

I selected "before" and added in 40 and thought that would be 40 minutes before sunset and I didn't look at it closer in the first screen shot, what you call that area? the rule summary.

When I did notice it, I change it to -40 and now it says: Sunrise/Sunset: until 40 minutes before sunset

Interestingly I can edit that offset minutes field and insert the minus or remove the minus and save the rule OK. i.e save a rule I have just modified.

But I cannot save a rule if I make other edits, like adding a whole new trigger as just discussed.

[toggledbits]

@cw-kid said in Sunset with offset didn't run:

But I cannot save a rule if I make other edits, like adding a whole new trigger as just discussed.

Sorry, but I'm just not able to reproduce this. I've just gone through every field on every condition type and every option. No joy. Maybe there's something broken in your rule otherwise behind the scenes that's making it choke. Let's do this... Go into the install directory, and do:

tar czf storage.taz storage/

The attach that file to a comment in the bug tracker.

[cw-kid]

@toggledbits said in Sunset with offset didn't run:

tar czf storage.taz storage/

Its not just me reporting the issue though. I know I am good at finding bugs however haha...

So what am I doing?

I ran that command in putty on the Pi

I now have these folders:

[cw-kid]

Also I have seen this saving problem on more than just one rule.

I've seen in on a few rules when either adding items like additional triggers or removing items.

Then you cannot click either of the two save buttons.

Only the red exit w/o saving button works.

[toggledbits]

It doesn't matter who is reporting the issue if I can't reproduce it myself without more information. One of the bugs you are connecting to this was entered by me days ago and was reproduced, found and fixed. The other is from a user on a mobile/Android browser which is currently not supported. I don't know how many people are using this thing right now, but you are the only one reporting no save conditions in the absence of an error indication on any field.

[kfxo]

@cw-kid said in Sunset with offset didn't run:

Also I have seen this saving problem on more than just one rule.

I've seen in on a few rules when either adding items like additional triggers or removing items.

Then you cannot click either of the two save buttons.

Only the red exit w/o saving button works.

I have been able to possibly reproduce your saving issue. I have noticed with rules that have a Date/Time After Trigger cannot be modified and saved.

[cw-kid]

It's 2 29 am here now this rule just fired and turned on my lounge lamps.

[cw-kid]

Actually any time I manually turn off the lounge lamps via my Harmony remote it's now firing the MSR rule and turning them back on.

[cw-kid]

@toggledbits as I said your welcome to connect to my laptop and edit the rules for yourself and press a save button to see what happens.

[cw-kid]

I was also the one who had issues saving PLEG changes many years ago and Richard eventually got to the bottom of it and managed to sort out the issue.

Maybe I have bad luck, but I cannot currently save any MSR rules I modify by adding new triggers or deleting them.

I am only reporting what I am seeing.

[kfxo]

@cw-kid said in Sunset with offset didn't run:

It's 2 29 am here now this rule just fired and turned on my lounge lamps.

I think there might be something going on with sunrise/sunset too. Im pretty sure sunset was 90 minutes late triggering for me. Im doing some more testing on that though to confirm.

@cw-kid said in Sunset with offset didn't run:

Actually any time I manually turn off the lounge lamps via my Harmony remote it's now firing the MSR rule and turning them back on.

If your rule is the same as posted above, this is because you have a condition in the rule for the lamp being false, meaning the rule will be false when the lamp is on and then when it goes off, it becomes true again.

[cw-kid]

I'm not saying my rule is correct.

It most likely isn't

I wanted to include a check that the turn on lamps rule is only run if the lamps are off in the first place.

If the lamps are already on then there's no need to have the rule action run.

So if I've set it up wrong what is the best way to handle this

I am a Reactor newbie..

Thanks.

[kfxo]

@cw-kid said in Sunset with offset didn't run:

I'm not saying my rule is correct.

It most likely isn't

I wanted to include a check that the turn on lamps rule is only run if the lamps are off in the first place.

If the lamps are already on then there's no need to have the rule action run.

So if I've set it up wrong what is the best way to handle this

I am a Reactor newbie..

Thanks.

You need to use the constraints. These are new and Im not exactly positive on the answer at this time but I think you would check if the lights are off in the constraint.

[cw-kid]

OK thanks. I was advised not to use Contraints whilst learning MSR.

Seems I have a learning curve to get over and I apologise for being a pain in the arse for the next few months to everyone in this forum..

[Black Cat]

Stop thinking PLEG......It will only frustrate you especially if you are trying to test the status of a device.
I'm not sure if you can actually do it as you would in PLEG, yes, I know it's frustrating but to move forward you need to unlearn what you already know.

[toggledbits]

Make sure you upgrade to 21050 if you haven't already.

[cw-kid]

I have the same issue using a different web browser Microsoft Edge. I added a new trigger to an existing rule and the save buttons aren't clickable.

Are there any instructions on how to upgrade to the new version of Reactor for Raspberry Pi ?

Thank you

I've found the update instructions trying it now.

[Elcid]

@cw-kid

Installation - Reactor - Multi-Hub Automation