URL calling has been essential for integrating Wireless Tags with all kinds of things. While other companies increasingly make it harder for you to build integration with 3rd party products (everything from Nest discontinuing their "Works with Nest" API, Wemo dropping their UPnP API, to IFTTT limiting the number of free applet per user to 3), with our URL calling and open and straightforward web API, we are cutting out the middle man (like IFTTT, Alexa, Google Home) and putting complete control into your hands when it comes to integration. 

Since almost all 3rd party web services use OAuth2 with their API, it is important that URL calling supports HTTP Authorization header for the access token.  Until now, you could already put the access token in front of the URL like

https://[access_token]@www.api_end_point.com/some_api  

for the system to send Authorization: Bearer [access_token], or

https://[login_name]:[password]@www.api_end_point.com/some_api  

for HTTP Basic authentication. Also, the KumoApp.httpCallExternal has been supporting adding arbitrary HTTP request headers through the 4th argument.  However, these features were not very visible, most people probably did not know it. 

Today, the URL calling feature was extended to allow users to easily add a number of common HTTP request headers:

The Web API LoadEventURLConfig and SaveEventURLConfig were also updated to add the field "headers_json" to allow using scripts and other automated ways to configure these headers. 

While waiting for Chinese customs to clear our DigiKey/Mouser IC component package (hopefully by Monday!) we placed some small quantity orders of components from local Shenzhen IC distributors. These will be enough to make 100 sensor tags for us to test reliability of this local distributor and fulfill some 20 back-orders. 

Meanwhile we have fully tested the URL calling feature, which now also lets user choose if mytaglist.com server calls the URL or the Ethernet Tag Manager calls the URL. The latter option will work even if the URL is using a private local IP address (such as 192.168.0.xxx, etc), or the REST endpoint is behind a firewall. The latter option requires firmware update of the Ethernet Tag manager, so will not be available to customers (about 30) who already received our product. However, per request, we will update your firmware at no cost if you mail the Ethernet Tag Manager to us.  

Current sensor tags is under development and will be released by end of this year. This interests us immensely, imagine knowing how much electricity each appliance used each day, each month, and knowing at a glance, anywhere with Internet access, if each machine/equipment is on or off and how much electricity it is using. This tag will have a unique, custom designed transformer based 50/60Hz AC current sensor which attaches to a power outlet without physical contact (this will not be a series resistor type sensor which introduces power loss and reliability/safety concerns). No tools will be required for installation/removal.

We are also working hard to write a program to generate our JSON AJAX API document using .NET Reflection API, so any update in server side source code automatically updates the document. We recognize that having an open API is important not only for allowing advanced users to integrate our product into existing systems, but also to allow independent solution providers to develop apps for platforms not supported currently, such as Windows Phone. Our Android and iOS app is written entirely using these set of JSON AJAX API for which we will release SDK in the near future. 

 We buy the majority of our components in USA and ship to Shenzhen, China for PCB (printed circuit board) assembly. Small quantity (<4000 units) PCB assembly is a labor intensive process, because manual labor is needed to organize/sort/inventory hundreds of types of component in cut-tapes, which is why even PCB companies in US out-source PCB assembly to China. We are currently experiencing a little longer than expected Chinese Customs clearance time. Before, our shipment from USA clear Chinese customs in a few days, now it has been more than a week. There should be about 1 week delay from originally planned ship date. We will have to establish a different method of production to avoid going through Chinese customs in the future.

Calling custom URL on each type of event, and allowing user to download raw motion & temperature statistic data as Excel spreadsheet (CSV) have now been implemented and are available to our existing and future customers. The Web/android app user manual has been updated. 

Custom URL calling allows you to integrate our product with Web service (REST endpoint) enabled home automation systems such as Insteon/ISY by Universal Devices. For example, you can turn on a light when door is opened, or motion is detected. In another example, you can turn off every light at your home when a tag (that may be attached to your key chain) is out of range.