[APP][Pro] Mode Switch - Smart home modes for lights, climate and devices — fully automated

Hi Dietrich

I’ve updated the PayPal link, so hopefully it works now. Thank you so much in advance, I really appreciate it!

That difference is intentional, so the user knows that the device has finished but still requires some action, such as taking the laundry out of the washing machine.

That’s also why the reset option is included. You can reset the status in different ways so that it returns to standby. For example, for a washing machine, you could configure it to reset when motion is detected in the laundry room.

It could also be that you have configured a reset for one device but not for another. In that case, the device without a reset configured will remain in the “Bereit” state.

Thank you for the explanation.

The PayPal link is now working.

Now that v3.2.4 is live, I’ve been able to add the fix for the contact counter to the test version. Could you please test it and let me know if it works correctly?

I tested it, but is still the same.

  1. Door open → light on / door closed → light stays on
  2. Door open → light off → light on / door closed → light stays on

DId I have the right version 3.2.4 experimental ?

Ok, I now installed the new test version 3.2.5.

And it’s working ok !

Thank you

Version 3.2.6 deployed to test: Added color and white balance support to all light setting locations (where supported by the device)

Hi, I tested it, but the light don’t switch from color mode to white mode.

Hi, I’ll take a look at it, thanks so much for letting me know. It was probably a bit too quick to put that version into test; I should have tested it a bit more myself first. I really thought it was working completely.

Hi, I’ve put version 3.2.7 into test. I tested it multiple times myself, switching colors, going to white balance, and switching back. Seems to be working fine now.:crossed_fingers:

Good morning Erikje,

The switching of the light modes is now working well.

But I now recogniced the following beavior:

  1. Open door → light on / counter set to 1
  2. Close door → light stays on
  3. Open door → light off / counter set to 0
  4. Close door → light stays off

So far so well but the next circle:

  1. Open door → light on / counter set to 1
  2. Close door → light stays on
  3. Open door → light stays on / counter is still 1
  4. Close door → light stays on
  5. Open door → light off / counter set to 0
  6. Close door → light stays off

THen back to from start

It seems there is a problem with the counter.

Hi Dietrich,

I have version 3.2.8 in test. I made some adjustments so that when a timer is running, it checks the status of contact sensors more frequently. However, I’m worried this might cause the app to crash. Please let me know if it does. I’m not currently using this feature myself, so the app keeps working fine on my end.

Hi,

It seems to work. No crash :+1:

Hi Erikje,

I now discovered something strange. I thought a submodus is a on top modus. But I have the main modus ‘at home’ and the submodus ‘tv on’ . The door sensor configured to react on modus ‘at home’ and the flow card ‘if modus is at home’ is not true anymore.

It seems you ask the submodus and not the main modus.

For the flow card there should be one for ‘activ main mode’ and one for ‘activ sub mode’.

And sensor and other things configured for the main mode should also trigger if a sub mode is selected.

All modes are currently separate modes in the app. I didn’t want a massive list, and I also wanted to hide certain modes from view, for example, you’re never going to watch TV while sleeping. So right now, you would indeed need to use multiple cards in a flow if every sub-mode counts. What I could try to do, though, is see if I can create a flow card that bundles everything into a main mode.

Good morning,

you are right, it’s hard to watch tv while sleeping :rofl:

For the sensors and light definition I found the solution. I only have to include the sub modes into the sensor/ light definition. I didn’t thought about that before.

For the flow definition I have one use case where I have to use multiple flow cards at the moment.

I switch on the music (Alexa) in the bathroom if someone enters the room while the modus is ‘at home’ . This can olso happen if the modus is ‘tv on’. If the modus is ‘sleeping’ I don’t switch the music on. That is why I asked for a flow card only asking whitch main mode is selected.

Hi Paul,

I haven’t forgotten about you. I’ve got news: the upcoming version will allow you to manually add a devices, like your dishwasher. It can then be started and stopped through a flow. Because the Siemens/Bosch app includes a ‘program started’ card, you’ll only need to set that up. Additionally, you’ll be able to use the remaining time value of the dishwasher in your settings.

This card will be in the next update. Still need to do some testing, then I’ll push it to the test environment for everyone.

I’ll probably also create some more cards once the mode has changed, since the main mode will need to be included there as well.

Hi Erikje,

I don’t understand why you include the submodes.

A set of of following cards should do the trick

Main mode is

Sub mode is

Main mode changed

Sub mode changed

What I mean by that is, for example, everything under ‘Home’ is included. So, say the ‘Watching TV’ mode is active, and you’ve created a flow with the main ‘Home’ mode card, the flow will recognize this as correct and continue running. With the Current mode card, that exact mode has to be active, and it won’t look beyond that specific mode.

Thank you for the explanation. I get that.