honestly much of what's left is almost self-explanatory by the name or rarely used in the Hubitat environment
That's a judgement call. And wrong. I know of more than one app that uses state variables. That barb is meant to say... if it is NOT documented, then it's NOT in there, so you are biased towards thinking that almost all of the documentation is "self-explanatory or rarely used" because you're only thinking of what IS in there. Which is in large part stubs! And being mixed with help/tutorials, well, frankly that bias is understandable, because when you think "documentation" you think... I dunno, "documents" (the whole thing, all help docs).
unless you have not looked since then
object docs have been added to a little
So I'm right. Unless you conflate tutorials with documentation (and even linguistically, they don't mean the same thing) documentation hasn't improved much.
This is gonna be a theme... They aren't "object documentation". They are "developer documentation". Yes, objects are documented, but so too are functions, system variables, commands, etc. But "help documentation" isn't a thing ("help documentation" would be documenting help, like style guides or article tracking).
They are separated. These are under the "Developer" heading and the /developer URL. Yes, the navigation and search are the same for all.
I'm curious what you thought I meant? That it doesn't give the attributes for the AirQuality capability in the middle of a guide on troubleshoot a Z-Wave network problem? Like "On the page, press the Repair button * airQualityIndex - NUMBER, range:0..500*, then wait for at least...." Again, my barb has a point, which is these tow things fundamentally don't go together. Dev documentations tend to be minimalist and strictly factual; help documents tends to give a narrative. And of course the target audience is different (tho that's a bit fuzzy with us). By intertwining them, I have noticed the different forms bleed into each other.
This is also not true.
My bad. I must be misremembering my surprise at stumbling over them (Buttons!! omg buttuunnnnns....) as them not being in there. In my defense, I did a cursory search, and of course it only displays as "preferences", which is only helpful for either those who already know wtf they are (that is, "it's self-explanatory") or 2) Read dev docs like they're tutorials. So, to give the dead horse another kick (stupid horse!), they should be separated, and I am very glad that you say there's plans to do that.
The only problems I've seen is when people try to replace the entire state object with an entirely different Map , which won't work (the keys themselves must be manipulated).
Other way around. state.var.remove('key') doesn't work. state.var = map does. I've been told if it's not in the documentation, you can just do a quick forum search, like "state variable not working".... (Okay, that one was just pure snark, sorry.) atomicState doesn't seem to update - #5 by Roguetech
)
