December 6, 2016 Leave a comment
- EYE CATCHING
- WORK PACKAGE PHASES
- PROJECT NEEDS
- EXISTING CODE
Google Home is expected to overtake Amazon’s Smart Echo by 2020. A review of Google Home found almost as many positive features as negative. The expected United Kingdom release date for the offering is November 2016. An article recently asserted the need for high-speed Internet to accomplish integrating the Smart Grid, as Smart Grid development lags behind in rural areas. The FERC said they, “are taking a more “open” avenue instead of a piecemeal approach” for deciding market power matters regarding the buying and selling of electricity. Nest is operating a field test of fifty-thousand thermostats running concurrently. Austin, Texas now requires Smart Thermostats in all new home construction. The requirement does not clearly distinguish homeowner rights. Note the language contained in the ordinance on page four, section C403.2.18 and page five, section C405.2.6. The text of this ordinance passes all security responsibility to the OpenADR protocol.
The race to bring the residential premises into the Smart Grid is accelerating. The Constrained Application Protocol (CoAP) is a developing technology standard for enabling simple devices to communicate with the Internet. It is likely CoAP will intersect with existing security protocols soon. It is unclear how security will be handled by CoAP. The opportunity cost to build the Smart Grid without clearly defined technology standards embracing adequate network security is a high price for any nation to pay. The cost is the expense of the residential premises. A single security incident would vacate much forward momentum of Smart Grid integration. The Austin mandate to not only require residential construction to allow access into the home by the electrical utility but also mandate control is clear evidence of how much force is being applied to bring the residential premises into the Smart Grid.
Smart Grid – Security
A vulnerability existing for over a decade in OpenSSH has led to today’s Internet of Things devices being used in targeted attacks. The reason is the devices are not being updated with the latest version of software. A recent study of taking the residential premises connected to the Smart Grid and using it as a weapon to harm the Internet was presented. The findings show bringing the Internet to a slower transfer rate is not only possible but has occurred.
The connectivity of a device to the Internet is neither good nor bad. It is a risk which must be managed. The risk is soon to be regulated by more examples of the Austin requirements, as previously stated.
GNU remotecontrol shared earlier this year we have entered the firmware aspect of the residential network connected HVAC thermostat (smart) thermostat. We are in the process of selecting a kernel distribution. The research is going slow, but the work is progressing. An outcome of our efforts so far has highlighted the need to structure the many inquiries and discussions about establishing strategic partnerships with GNU remotecontrol and the need to also establish technology alliances.
Partnerships and Alliances
GNU remotecontrol is at the point of leveraging for-profit organizations to establish both strategic partnerships and technology alliances. The discussions have shown us there are two barriers to the economic side of our growth plan as a software project. First, the financial versus technological relationship. Second, the small amount of system thinking on the part of our applicants. The findings clearly demonstrate the inability to achieve conceptual thinking by establishing productive agreements.
The goal of a for-profit organization to prioritize the financial aspect of the relationship is fair but suffers the ability to come to an agreement when the financial aspect is the dominant factor in the negotiations. The goal of not wanting to be a part of system thinking is not fair, as the software project is a system. The insufficient amount of conceptual thinking on the part of many applicants seeking to form either a partnership or an alliance with GNU remotecontrol requires us to refine our application process further. GNU remotecontrol must gain a more concise understanding during early discussions of applicant’s goals and objectives in their desire to form either a partnership or an alliance with GNU remotecontrol. This understanding will help reduce our time spent in discussions with applicants who are not a productive match for the software project.
|WORK PACKAGE PHASES|
GNU remotecontrol accomplishes productive work output through structured work packages. This approach helps to organize our efforts and keep things on track to achieve publishing our work. We have ten different phases for our work packages.
GNU remotecontrol Work Package Phases
|6||UAT||User Acceptance Testing|
The GNU remotecontrol team does not perform any work output outside of structured work packages.
| PROJECT NEEDS
GNU remotecontrol Project Help Wanted
Many people have asked us about adding other types of thermostats to GNU remotecontrol. There are three questions that need to be answered before we can offer GNU remotecontrol support for any IP thermostat. These questions are:
- How to CONNECT to it (NETWORK).
- How to READ from it (CODE).
- How to WRITE to it (CODE).
It is our hope to have dozens and dozens of thermostat types that work with GNU remotecontrol.
| EXISTING CODE
Whatever you do…..don’t get beat up over your Energy Management strategy. GNU remotecontrol is here to help simplify your life, not make it more complicated. Talk to us if you are stuck or cannot figure out the best option for your GNU remotecontrol framework. The chances are the answer you need is something we have already worked through. We would be happy to help you by discussing your situation with you.
…..UNTIL NEXT MONTH!