Where's the GitHub repo for manual install?
Looks like I'm using the old one:
1 Like
I have a sensor group with one motion sensor and three acceleration sensors, and require any two to be active to trigger the group as active. I have been finding the group going active when only the one single motion sensor is active. I have checked event logs as thoroughly as possible and I don't think I am mistaken
Hi @thebearmay,
I just tried this app to get Min Max values of temperature sensors I have around the house.
The child device do not show any values and when I go back to the App, I get this error:
And after a few tries, the App log looks like this:
And the child device log:
Any help will be appreciated.
@thebearmay , I firstly want to thank you for supporting this project. I primarily use it for grouping temp/humidity sensors in addition to power. Those functions alone are used daily for virtual thermostats, outside temp data and countless rules that allow me to optimize solar power consumption live time. I have two meters with solar at each building so grouping is the key to that.
Would it be a lot of work to add Energy to this project?
1 Like
Does this capability definition work for what you're looking for:
EnergyMeter
¶Device Selector
capability.energyMeter
Driver Definition
capability "EnergyMeter"
Attributes
energy- NUMBER, unit:kWh
3 Likes
Yes, I believe those would work perfectly.
@thebearmay First, Thank You for ressurecting this App.
It is allowing me to share fewer devices across Hub Mesh, and simplifying and improving readability of my rules.
So far, motion and contact sensor groups work perfectly, but Rule Machine doesnt see a Group of locks as a lock. The group is there, and seems to have all the requisite info, but RM doesn't show it in the dropdown for Triggers or Conditions.
Disregard. I found that by selecting custom attribute in triggers and conditions and choosing "lock" for the attribute, I could make it work.
S
3 Likes
I'll try to look at it in the morning
2 Likes
I think this is one of the app's secret powers! 
And the improved readability and ease of editing automations w/lots of devices is icing on the cake.
3 Likes
Believe I should have all of the code changes for Energy Meters moved up.
3 Likes
The child device doesn't have the lock capability since it's one way, so it won't show up under the normal "lock" device type selectors. The workaround you found is the answer there. The capability wasn't added since, by default, it adds the lock/unlock commands which aren't supported. Didn't want that causing confusion.
2 Likes
Ah. Makes sense. I was looking at it as a status, not considering that it might also add a capability.
Thank You.
Scott
I am using this with a few groups of devices but having an issue with temps.
It seems like the device current state for temperature drops and then the dashboard shows 56 degrees. Then it will show up again and the dashboard updates.
Then sometimes
Any idea why that device state keeps dropping?
What do the events show for the sensor group device?
Did that cover what you were asking for?
Any thoughts?
Doesn't look like the device attribute ever goes to 56, so not sure where the dashboard would get the number.
That device state drops though and the dashboard defaults to that value. It is not that the value is actually set to 56. I had a Rule Machine rule that uses that state and when it is gone from the device page that rule reports it's value as null.
