Problems With New Mode Manager

Fair enough, I don’t use any times at the moment so that makes sense.

Cheers.

I've a new problem with platform 2.3.3.125

I primarily use 3 modes...Home, Away, Guest.

Home and Away are set purely by presence.
Guest is set manually and is used to prevent the mode changing to away if we both leave.
Several times over the past 2 days my wife has set the mode to Guest, however, no reference to Guest ever shows in the Events list for Mode Manager.

events
show current mode

If Mode Manager is not the app changing the mode, I would not expect it to show in App Events for Mode Manager. (The App Events page itself, for any app, is somewhat of an odd place, very rarely used these days, which is another story...but apparenty this is one!)

If you want a general history of hub modes, set via whatever means, that is part of what you will see under Logs > Location events.

1 Like

Many thanks, I'm sure it used to but I'm glad you pointed me to location events. How had I not noticed that before? :slight_smile:

Hi all,

I recently migrated from mode manager legacy to the new version, and since the migration, the mode fails to switch to "away" when all relevant presence sensors depart. Is there an update coming soon to fix this issue?

For latest known issues, please be sure to check the Known Issues thread, first, under Release Notes category, for upcoming bug fixes.

With that being said, we are not aware of issues with changing to "away" mode. Mind sharing more details about your app settings and pertinent logs?

Hi Bobby,

Thanks for the reply. Attached are the away mode settings (automatically created from the legacy migration), mode events log, and the presence log. You can see from my presence sensor that away mode should have activated at 09:06 (I was the last to leave the house), and after I noticed at 09:24 that it had not, I manually changed it. When I returned at 10:05, Day mode was correctly activated. I have updated the hub to version 2.3.3.133 and at 11:45 I manually changed my presence to "departed" in order to see if this fixed the issue, which you can see from the timestamp log that it did not. The 11:55 Away mode change was triggered by testing my webcore failsafe piston. Is there anything else I can provide to help with fixing this issue?



Your setup has a conflict about All Leave trying to set two modes. Don't you want Any Arrive for Day? Also, show your time table. If you have Day and Night defined with times, then you don't need entries for them in the presence table, as you Return From Away will use the time settings.

It's different presence sensors. I use the withings integration and sleep sensors to trigger night mode when we get into bed, and day mode when we both get up. All worked perfectly with the legacy version, and still does, bar setting away mode when all presence sensors are departed.

Could you show me a screenshot of the old MM setup page. I will look into what the problem is.

Unfortunately I can’t, I removed the old app once the migration was complete, but it was exactly as per these settings, I haven’t changed anything and checked the settings before deleting the app.

Can you post screenshot of logs for the app showing this?

How do I get log's from the app?

On the Logs page (from left side menu). You can filter to a particular app at the top of the logs.

This?

The only time it has changed to away is when I manually change it, not triggered by everyone departing like it used to.

Those are the right logs. But I need to see it when everyone has departed, showing the last presence sensors departed, and some evidence that all are in fact not present at that point in time. Yours is the only report of All Leave not setting Away as expected out of a large number of people using this same setting. You have 7 sensors that all must be gone; are you certain they are all not present?

For independent verification of this, you could create a simple rule in Rule Machine, that has a trigger of all of those same presence sensors leaving. Turn on Event and Trigger logging for the rule. If they all leave, it will log that trigger happening at the time the last one leaves. So it would be useful to see the rule succeed and Mode Manager to fail at the same time following the same events. In Logs you can filter on two apps at the same time so we can see both sets of logs in one screenshot. Like this:

I'm 1000% certain that they are all departed. Three of them live at different properties (Dan/Lewis/Ella), one was at school (Lexie), just myself (James) and my partner (Nikky) here. We left together and returned together today. You can see from the attached screenshots that this is the case as I described.

I will create the rule as requested and post the results tomorrow.






Your screenshots show some as present. Instead of Events from individual devices, which can only be tediously examined as to event times, we need to see Logs. On the Logs page you can filter for all of the Presence devices and Mode Manager, and the rule when you set it up. That will tell the full story all in one place. I'm not saying there is not some problem with Mode Manager, but it is strange that you are the only one who has reported this problem and we cannot reproduce it.

I just set it up with 6 sensors, and this is what the logs look like:

I’ve setup the rule as requested, but you can see from the logs that only myself and Nikky were present at 09:06 this morning when we left together, all other sensors had already departed. The mode changed to away when I manually changed it at 09:24, and back to Day automatically as it should when we both returned at 10:05.

I’ll trigger the event tomorrow and send the evidence you require.