September 5, 2016 Leave a comment
- EYE CATCHING
- WORK PACKAGE PHASES
- PROJECT NEEDS
- EXISTING CODE
The American Council for an Energy-Efficient Economy announced their latest report the United States has moved from thirteen to eight in global positioning regarding efficiency rankings over the past two years. A product review reported Schneider Electric’s Wiser Air thermostat has gained energy consumption analysis improvements. Nest has simplified accessing time-of-use electric plans. An article shared numerous complaints have been filed by states accomplishing energy efficiency policies juxtaposed against the federal position on wholesale energy authority. A study finding smart thermostat revenue is expected to quadruple in the next ten years. An article finding the smart home will take longer to mature due to, “a lack of standardisation (sic) means that gadgets from different firms cannot communicate with each other.” A case study of setting an office ambient temperature for the occupants to find comfort. An article finding utility stocks are more financially dangerous than they appear.
The money to fund both the smart grid and the smart home is clearly turning over at faster money velocity with each passing month. The associated products and services for sale are more prevalent with each day, too. The unwillingness to either define a comprehensive standard or adhere to an agreed upon standards set is stupefying this market sector and subsequently the energy industry. The reason is mostly from the unwillingness to bear the risk involved with interoperability. This unwillingness suffers the ability to establish a system. There are isolated pieces of success but nothing close to a smart grid or a smart system running a home.
Smart Grid – Security
EE Times reported the JupiterMesh project is growing in capabilities. Oddly, JupiterMesh reports it is based on, “IEEE 802.15.4e/g media access control and physical layers” and supports, “IETF security protocols such as PANA, EAP-TLS and HIP-DEX for network access authentication and key distribution, and AES-128-CCM-based message authentication and encryption” but does not explain how they accomplish providing security to the network and transport layers. The ZigBee position is they are not responsible for these later layers. The absence of layer-to-layer security is a critical design flaw in this technology model.
An article reporting the United States Department of Energy has spent thirty-four million USD for improved information technology security associated with the national electrical grid while the FERC has requested comments regarding a new set of technologies standards. A recently released book explains how to infiltrate many technologies related to the Internet of Things concept.
Clearly, those involved with the security aspect of the smart grid are the most popular in this market segment. The ability to access smart grid technologies is so concise a book has been written and commercially published instructing how to violate these technologies. The existing grid cannot be protected fast enough while more technologies are implemented to make the grid more intelligent. The result is less security of the existing national electrical grid.
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 establishing strategic partnerships to further this effort of the software project. The discussions are going well. Stay tuned for more information.
|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!