Yes, and I can understand your confusion because it was written in uncertainty about what I wanted to talk about, thus the reason why this thread was posted. I want the roadmap to help lessen the topics that I can talk about so I can focus on things that people are most interested in, because right now that article is a representation of a map of the world, when I'm sure most people are only interested in a map of a specific city. I had to keep it very generalized just to get the idea out there about all the ways one can go about automation. It wasn't well written, but those protocols listed are all communication protocols that I use nearly everyday in the automation industry.
Everyone thinks about automation in different ways -- when I ask the average IT person what automation is they automatically think about IFTTT and networked devices, if you ask other people it's about microcontrollers and robotics, ask anyone else and it's about smart technology that uses the cloud and internet data and API's to adjust complex things manually for you like the Nest thermostats. Ask me, and it's also about another platform that I use and writing programs that deal with wired and other wireless communication types and protocols outside of TCP and UDP on a lower level...
I did not proofread the article, I wrote it as my thoughts came out but what I did mean was "Internet" connected; it can be over wifi and doesn't require internet if the network at hand has the infrastructure to achieve the end-goal, but typically this acronym implies internet in most cases to connect to the cloud to access well-matured databases of information and servers.
I'm not expecting a lecture on the article, I know it could be better written -- what I am asking is the answers to the questions I've asked in this thread to help myself write better and less disorganized articles on the topic in the future. I would pick a narrow topic if I knew what people wanted me to write about specifically, but I didn't at the time of writing the article, and that IS the question I'm looking for people to help me answer in this thread (because I do not know).
I would hardly have enough time to write about the specs of HDMI and its uses in automation just by itself though, so I have little interest in updating older articles and I'd rather just write new ones if more important information must be said. By what I know about HDMI, HDMI 1.4 spec isn't even fully implemented in 90% of the hardware I deal with or have seen. Find one device that uses an HDMI interface for network... I'd be surprised if someone could, but it is part of the HDMI 1.4 spec.
... So let me rephrase what I'm looking for here and narrow that down to just one question for now -- What kind of automation programming difficulties or interests do any of you have? I think based on the interests I read, I can get a better idea of some of the protocols & hardware I should be talking about and the kind of advice I can provide.
I sure hope I can write better articles when I know what I want to talk about but automation isn't exactly like talking about how to bake cookies.
Not entirely unfortunately... I'm having difficulty here because what I do is much lower level than apps and hardware all contained for you in small devices with API's already available to achieve what you want to do. What I'm looking to do is help people really understand what goes on underneath before the high level stuff, API's and apps. RS-232 control (baud rates, flow control, etc...), WOL magic packets, GPIO's (relays, contacts), etc...
People seem to understand the cloud and IoT and RESTful API's for interconnected devices but ask people how all that works in the background and lots of people don't have any idea. I'm not looking for definitions or criticism on the article I'm looking for problems that people are facing to help guide my articles in a certain direction. Solutions like Philips hue and others all deal with the complexity for you like communicating with ZigBee nodes and the overall mesh, but what if that isn't available for you for what you're trying to control or achieve with an automation solution? *MOST* people wouldn't have alternative solutions.
IoT solutions, platforms and pre-built kits are already out there, but I want to try to help those people that are more DIY'ers and trying to work from the ground up learning how things can communicate and talk to one another.
Anyways, I appreciate the time you've both taken to help me, but the topics I'm hoping to answer are more along the lines of:
- What protocol(s) do I need to know in order to control *this* TV with my computer?
- How do I get *this* DSP to trigger an event when the signal present threshold of *these* mics reach -10dB?
Things like this to my knowledge (at least in the commercial world right now), do not have available prepackaged API's and SDK's for people to use to achieve the desired result.
