View single post by Majik
 Posted: Tuesday Nov 7th, 2017 08:39 pm
 PM  Quote  Reply  Full Topic 
Majik

 

Joined: Saturday Aug 26th, 2006
Location:  
Posts: 33
Status: 
Offline

  back to top

I general, I think support of some sort of advanced network API is far more important than a built-in web Interface.

My personal preference would be JSON+REST, and I would see the ultimate aim to be able to move to the point where all control and even programming could be done via this sort of interface.

The big advantage of REST is, assuming the API is sensibly defined, this makes it possible (and relatively easy) to build client-side control web-apps entirely in html/javascript.

In other words, you wouldn't necessarily need to embed a web-interface into the ETH04 at all; it could be a separate app that people could host on a local server/Raspberry Pi.

Of course, including it on the ETH04 makes it a nice, out-of-the-box package.

The other option is, of course, IoT style automation with cloud-based control.

Cloud-based is really required to support Alexa, Google Home, and IFTTT. The most straightforward approach would be for Cytech to build a cloud-based service that customers can optionally connect their systems to. This can then be used for external control across the Internet without messing around with firewalls and port forwarding.

In this scenario, the ETH04 would register with the Cloud app and then communicate with it via an encrypted data "bridge". This is typically HTTP or MQTT based. Then, typically, all user control goes via the Cloud application, although it is also possible to provide local control.

Amongst others, Google (https://cloud.google.com/solutions/iot/ )and Amazon (https://aws.amazon.com/iot-platform/ ) provide frameworks to make it easier to develop and host cloud based IoT solutions. Note that both Google and AWS support a variety of protocol bridges including MQTT.

The big issues are all around privacy and security. This includes security of protocol, security of cloud service, and questions like "What happens if the Internet service goes down?".

Personally, I would like to see both local control and programming via a network API which can be kept within the local network, and the option for some Cloud based services that can work with Alexa/Home/IFTTT, etc. but which would be more limited in scope (without, for instance, the ability to reprogram the system).

Cheers,

Keith

Last edited on Tuesday Nov 7th, 2017 08:43 pm by Majik

 Close Window