Cheero Repo
QRCode sneaked in.
Was easier than expected.
Based on ZXing implementation.
Now focus on the status bar temperature. I forgot how underutilized/underestimated/badly supported are those space up there and the whole android notification ecosystem.
Notifications should be a huge part of an OS workflow and user experience but nobody seem to really realize how powerful they could be.
Time to re-utilize some of the tricks I used with this notification volume control.
Good news everybody, the Ambient Weather’s API return the station’s data even if the owner decide to not share them.
Sadly they don’t retun the station’s geoposition coordinates there…
Adding the widget and the temperature (or what else? Humidity?) in the notification bar and I’ll push version 0.9 to the store. Let see if I can make it before March.
Android “Ambient Weather” app progress.
API is pretty straightforward. I have the data from the station:
Need to find a decent way to help Joe Schmo to configure and share their Stations.
I wish Ambient Weather website would share a QRCode for each station’s apikey.
I’ ll implement a QRcode generator on the app landing page with the instructions. Not ideal but better than nothing.
Not sure if Ambient Weather people are going to be happy about it.
Writing a simple Android Wear and Android App that pull data from the Ambient weather API.
I think the API is maintained by a single hero:
https://github.com/owise1 while the main company that actually sell the station seem almost unaware of its marketing potential.
Would be nice to have a station’s QRcode ready to be shared with people that don’t have an Ambient weather account instead of forcing the owner to dig into the ambientweather.net account’s profile (that is different from the ambientweather.com account… sigh).
That would make configuring my app super simple and I can see local business owner’s sharing their station as a promotional bonus (scan the QRCcode and you get local real time weather data).
https://ambientweather.docs.apiary.io/#reference/0/device-data/query-device-data?console=1
---------- List User's Devices
## List User's Devices [/v1/devices/{macAddress}{?apiKey,applicationKey}]
+ Parameters
+ macAddress (required) - device Mac Address
+ apiKey (required) - API Key for user account
+ applicationKey (required) - Application Key
---------- Get request
https://api.ambientweather.net/v1/devices?applicationKey????????????????????????????????????????????????????????????????&apiKey=????????????????????????????????????????????????????????????????
---------- Answer (JSON)
[
{
"macAddress": "??:??:??:??:??:??",
"lastData": {
"dateutc": 1550265900000,
"winddir": 272,
"windspeedmph": 2.2,
"windgustmph": 2.2,
"maxdailygust": 6.9,
"tempf": 62.8,
"hourlyrainin": 0,
"dailyrainin": 0,
"weeklyrainin": 0.91,
"monthlyrainin": 0.91,
"totalrainin": 29.24,
"baromrelin": 29.58,
"baromabsin": 29.12,
"humidity": 69,
"tempinf": 68.5,
"humidityin": 41,
"uv": 1,
"solarradiation": 113.16,
"feelsLike": 62.8,
"dewPoint": 52.47,
"lastRain": "2019-02-13T00:59:00.000Z",
"date": "2019-02-15T21:25:00.000Z"
},
"info": {
"location": "???? ????",
"name": "???? ????"
}
}
]
----------------------------------------------
---------- Device Data
## Device Data [/v1/devices/{macAddress}{?apiKey,applicationKey,endDate,limit}]
+ Parameters
+ macAddress (required) - device Mac Address
+ apiKey (required) - API Key for user account
+ applicationKey (required) - Application Key
+ endDate (optional) - The most recent datetime. Results descend from there. If left blank, the most recent results will be returned. Date format should be in milliseconds since the epoch or string representations outlined here: https://momentjs.com/docs/#/parsing/string/. Note: datetimes are stored in UTC.
+ limit (optional, number) - The maximum number of results to return (max: 288)
+ Default: 5
---------- Get request
https://api.ambientweather.net/v1/devices/??:??:??:??:??:???apiKey=????????????????????????????????????????????????????????????????&applicationKey=????????????????????????????????????????????????????????????????
---------- Answer (JSON)
[
{
"dateutc": 1550430300000,
"winddir": 64,
"windspeedmph": 0.4,
"windgustmph": 1.1,
"maxdailygust": 10.3,
"tempf": 39.2,
"hourlyrainin": 0,
"dailyrainin": 0.01,
"weeklyrainin": 0.01,
"monthlyrainin": 1.66,
"totalrainin": 29.99,
"baromrelin": 29.82,
"baromabsin": 29.35,
"humidity": 85,
"tempinf": 67.3,
"humidityin": 40,
"uv": 0,
"solarradiation": 57.25,
"feelsLike": 39.2,
"dewPoint": 35.08,
"lastRain": "2019-02-17T12:59:00.000Z",
"date": "2019-02-17T19:05:00.000Z"
},
{
"dateutc": 1550430000000,
"winddir": 74,
"windspeedmph": 0.9,
"windgustmph": 2.2,
"maxdailygust": 10.3,
"tempf": 39.2,
"hourlyrainin": 0,
"dailyrainin": 0.01,
"weeklyrainin": 0.01,
"monthlyrainin": 1.66,
"totalrainin": 29.99,
"baromrelin": 29.81,
"baromabsin": 29.34,
"humidity": 85,
"tempinf": 67.1,
"humidityin": 40,
"uv": 0,
"solarradiation": 54.19,
"feelsLike": 39.2,
"dewPoint": 35.08,
"lastRain": "2019-02-17T12:59:00.000Z",
"date": "2019-02-17T19:00:00.000Z"
},
{
"dateutc": 1550429400000,
"winddir": 129,
"windspeedmph": 2.2,
"windgustmph": 3.4,
"maxdailygust": 10.3,
"tempf": 39.2,
"hourlyrainin": 0,
"dailyrainin": 0.01,
"weeklyrainin": 0.01,
"monthlyrainin": 1.66,
"totalrainin": 29.99,
"baromrelin": 29.8,
"baromabsin": 29.34,
"humidity": 85,
"tempinf": 67.6,
"humidityin": 40,
"uv": 0,
"solarradiation": 78.05,
"feelsLike": 39.2,
"dewPoint": 35.08,
"lastRain": "2019-02-17T12:59:00.000Z",
"date": "2019-02-17T18:50:00.000Z"
},
{
"dateutc": 1550429100000,
"winddir": 143,
"windspeedmph": 4,
"windgustmph": 5.8,
"maxdailygust": 10.3,
"tempf": 39.2,
"hourlyrainin": 0,
"dailyrainin": 0.01,
"weeklyrainin": 0.01,
"monthlyrainin": 1.66,
"totalrainin": 29.99,
"baromrelin": 29.81,
"baromabsin": 29.34,
"humidity": 84,
"tempinf": 67.8,
"humidityin": 40,
"uv": 0,
"solarradiation": 83.19,
"feelsLike": 36.39,
"dewPoint": 34.78,
"lastRain": "2019-02-17T12:59:00.000Z",
"date": "2019-02-17T18:45:00.000Z"
},
{
"dateutc": 1550428800000,
"winddir": 66,
"windspeedmph": 1.6,
"windgustmph": 2.2,
"maxdailygust": 10.3,
"tempf": 39,
"hourlyrainin": 0,
"dailyrainin": 0.01,
"weeklyrainin": 0.01,
"monthlyrainin": 1.66,
"totalrainin": 29.99,
"baromrelin": 29.8,
"baromabsin": 29.34,
"humidity": 85,
"tempinf": 67.8,
"humidityin": 40,
"uv": 0,
"solarradiation": 80.25,
"feelsLike": 39,
"dewPoint": 34.88,
"lastRain": "2019-02-17T12:59:00.000Z",
"date": "2019-02-17T18:40:00.000Z"
}
]
Should be pretty easy to replicate the mixing capabilities of those Microsoft headphones.
Excellent library / documentation:
https://github.com/nayuki
https://www.nayuki.io/page/qr-code-generator-library
Really poor integration on any popular OS / platform.
Surprisingly lack of quality 3rd party solutions with no clear leader.
Win32
Installer 7.7 MB
CodeTwo QR Code Desktop Reader & Generator
Windows store
IOS
MacOS
Protocol: Z-Wave, Scene and NWI Capable Wall Mounted Switch, Series 300.
Compatible with SmartThings
Standalone ZWave master controller or can be used as secondary controller.
Tested with Smartthings
First, do a full reset on the remote (to disassociate it with any previous controller). On the HA09, that consists of:
To add HA07 controller
Turn on include on Smartthings hub
Press and hold INCLUDE for 5 seconds COPY will flash
Release the INCLUDE button
Press and release Channel 1 OFF/DIM on the HA07 controller
The display will show “RA” (wait a few min for ST to add it)
Add modules to HA07
add devices to channels on the remote (‘Include’):
The Static update controller (SUC) is a special function of a static controller. Most static controllers (a controller with fixed location and powered by mains) can perform as an SUC. However, the function typically needs to be activated first. The SUC receives the updated routing table from the primary controller and offers this routing table to all other controllers in the network. Because the SUC is a static controller and therefore always active in the network, any other controller can frequently request an updated routing table from the SUC. To make sure that all other nodes and particularly other controllers are aware of the presence of a SUC in the network, the Node ID of an activated SUC is communicated within the network periodically.
Having an active SUC in the network allows you to keep the primary controller role on a portable controller. Every change of the network caused by inclusion or exclusion of a node by the primary controller will be reported to the SUC and is then available to all other controllers, even if the primary controller is not active.
Since most of the controllers are battery operated and therefore not active all the time, these controllers have to request an updated routing table periodically or at least when woken up, by pressing a button. To perform this task the mobile battery operated controllers need to be informed about the presence of a SUC in the network. If the original – mobile – battery operated primary controller is lost or damaged, the SUC can assign the primary privilege to a new mobile controller, protecting the user from re-establishing the whole network with a brand new primary controller, and having a different Home ID.
Even a SUC in the system does not solve the problem that only one controller has the primary privilege and can include new device. This limitation is overcome by enhancing the SUC functionality by another function called SIS = Static ID Server.
The SIS acts as depot for new Node IDs that can be as signed by mobile controllers . Having an SIS present in the network allows every controller in the network to include a further device. The controller will just request a new node ID from the SIS and assign this new Node I D to the server. With the SI S it is made sure that no two nodes get as signed the same node ID. The only requirement is a mobile controller needs to fulfil in order to include new devices, is that it has a network connection to the SIS server to request a node ID.
This kind of configuration with server SIS has the following advantages and disadvantages:
Advantages:
Disadvantages:
Since the SUC/SIS functionality is already included in the firmware of most modern static controller, or a USB dongle, most Z-Wave networks can take advantage of these functions if a static controller is present. However, this function needs to be activated.
A static controller can also be a primary controller, as well as have SUC/SIS functionality. This configuration is typical in real networks.
The zwave USB stick ZW090-A from Aeotec is a fine piece of hardware but it seem pretty sensible to whatever receive from the USB port and it get stuck into the apocalypse rainbow error mode:
regular color cycle.
Do anybody else experience anything similar?