Yeah it is not a big deal cause it did save the settings without issue. And the "App List" button does bring me back to the HE app page. I was just wondering.
Also thanks for the latest update! I noticed that there is a restrict option for presence sensors now and I was literally about to post about this feature. I was having the issue when my wife and I would both leave in the same car and come back both garage doors would open. Now I can setup a restricting that if a certain Iris fob is present to prevent that door from opening.
I deleted 100% of your code and started over, one step at a time, still getting the 500 error
Next after installing the container app, I went ahead and installed the current Parent and Child apps and guess, what, the Container app now works. I was able to build new Presence Central apps.
Starting from scratch is not what solved it, it was installing the PC parent and child apps before the container app would work. I could never get the container app to install PC or any other app for that matter
I think I've realised your issue.
When you installed Cobra Apps you needed to update the parent and child code for the app you wanted to install?
If there is not a line of code referencing the cobra apps parent then it will not install into the container.
This is the line (around line 57)
parent: "Cobra:Cobra Apps", // ******** Comment this out if not using the 'Cobra Apps' container
The apps that go into the container have been specifically updated with this code to use the container.
I was struggling to duplicate your error until I installed an older version of one of the parent/child apps
Then I got the same 500 error that you did.
Sort of, I uninstalled all code, parent/child and container and started over
I guess where I got crossed up is in the process steps, it indicates the selected apps will be installed... Which implies the PC parent/child apps don't need to be installed first.
Just want to clarify something regarding the app. What I'd like to do is set up an automation that will set my hubs mode to Home if ANYONE is present and set it to Away if EVERYONE is gone. From your brief description at the top of this thread, it seems like that is what Group 2 does. The description in the app, however, makes me wonder if it will set the hub to Away if ANYONE leaves (even if one of us is still home). Could you clarify which is the case? Right now I have one automation set up under Group 2 that has both presence sensors set as triggers, and tells it to change the mode to home when someone arrives and away when someone leaves. Will this work how I'm intending?
@murray.sean.d, they way you've got it setup sounds correct to me, just the way I have it and I agree the wording in the app is a little misleading.
Oh and it's working like that for my wife and I.
Now that I read back, it seems exactly like what @murray.sean.d posted two posts before mine...
I have the following setup, and everyone is home (and presence sensors show present). If I toggle the vGuestPresence present/not present the mode changes to AWAY even though per OPTION 2 it shouldn't do that unless everyone is not present...
