Basically, yes. But how do you authenticate that the thing telling the TV to turn off actually has the authority to tell it to turn off? This is a whole nother level of complexity which consumers will need to navigate after the API for all the things are standardized and many companies are going to screw up the security way worse than they are currently screwing up the interoperability.
The real problem with IoT isn't the standardization of the transfer medium, it's the security implications of having your things on an internet.
That is actually pretty close to how we define components in the FBP protocol. You'll just want to add a bit more information about the inputs, and a possible set of outputs too (for example, a temperature reading?)
http://noflojs.org/documentation/protocol/#component
For IoT use the default WebSocket transport isn't desirable, of course. But maybe something like MQTT?
A subset of the protocol already works with serial-over-USB when talking to microcontrollers
If a TV is around, I can easily turn it on/off, switch channels, volume, etc.
No need for specialized apps, they're universal APIs every device can access, provided some level of security or trust.
Is that the IoT we want?