Capability soundPressureLevel

A capability to display the current sound pressure level in decibels.

I might suggest soundPressure, so as not to be confused with volume level (as in audio equipment)
In the pro audio world they shorthand this to SPL (sound pressure level)

Sure. If that’s the correct term, that is what it should be. I just want to be able to subscribe to sound pressure levels from my ubi and netatmo devices.

The netatmo already has this ability to subscribe to the noise level. My netatmo monitor app will monitor it for you.

That works for purpose built smart apps such as yours, but for outside access; not so much. I first need to get a users permission to access their devices, then subscribe to the device’s events. Without a capability, I cannot ask if they have it or not.

1 Like

As long as the device shows in STs it will report on any attribute setup in the device-type. Maybe i’m not understanding what you are really trying to do?

You cannot ask a users permission to subscribe to an attribute.

Allow Endpoint to Control These Things…

  • Which Switches?
  • Switch 1
  • Which Air Pressure Sensors
  • Air Presssure 1


1 Like

Not to mention things IFTTT and other data logging services. Without it being a real capability, the only thing left is a device specific hack to get it to log out to those services.

1 Like

can you do this now with capabilities? Why would you want to subscribe to my homes sound pressure level? or any other capability/attribute?

I’m intrigued where you are going with this and what it’s practical applicaiton would be. I like new things. How would this work and what value does it add? :smile:

By subscribing to the power capability I was able to generate this chart. I can generate a chart for any capability I can subscribe to. It’s not that “I” want to subscribe to your house’s sound pressure level. I can’t ask your permission to let you access it at this point.

Ahhhh I think I understand. You’re refering to yourself, or a STs account, as the “user” in this statement. 3rd party to a STs account.

The phrasing was throwing me off lol. I try not to refer to people as “users”. It reminds me to much of Tron lol!

Ad hoc Attributes (public attributes in a Device Type but not in a Capability) are an aberration and should be deprecated and eventually disallowed.

This is both for subscription (device list filter) purposes as discussed by @jody.albritton here, and to ensure many Device Types can implement a specific Capability consistently (ie with same Attributes (datatype, units, meaning) and Commands.

This capability has been added and documented.

1 Like

There are two types of sound detection. Sound pressure level takes a numeric value.

sorry, my bad, further in the list is SPL, I didn’t understand that two sound related capabilities were being added.
Sorry for being cranky today, it’s one of those days.