No push notifications to iOS devices was sent from midnight-12:30PM today. This was due to server certificate expiring needing renewal. Now push to iOS device started to work again.
We apologize for any inconvenience.
We are putting KumoApp live today. If you used our iOS app, you may have wondered what the "Install KumoApps..." is for. The configuration interface for KumoApp has been implemented in the iOS app since last October. "Kumo" (pronounced Koo-mo) means "cloud" in Japanese and "Kumostat" is our up-coming energy saving, Internet thermostat that will cost as little as the cheapest thermostat you can find (just like Wireless Sensor Tags is the cheapest Internet connected temperature sensor, thanks to our unique "Tag Manager" + "Cloud" architecture that moves hardware complexity to cloud where computing power is dirt-cheap). "Kumo-Sensors" are our high-end sensors with more accurate temperature and air humidity sensor + PIR or door/window designed to automate "Kumostat" to save energy and provide comfort. The adaptive, energy saving, and learning algorithms will all come from "KumoApp".
While we are waiting to get the plastic casing for Kumostat and KumoSensors done (expect Q2 2014) so we can start shipping these new products, we are putting the KumoApp engine out for everyone with Wireless Sensor Tags to use. Currently, there is only 2 app (that does not require the Kumostat hardware) already written: "log every tag updates" and "log events from IFTTT". In the next few days, we will add more apps to show-case the capabilities of KumoApp engine, that will be useful even without Kumostat hardware. You are welcome to write your own app today and test them out in your account. Show us your ideas and we will publish them for everyone to use.
We are moving mytaglist.com server to a larger capacity, faster server on Dec 22~23. During this time, mytaglist.com and wirelesstag.net may not be available, and the iOS/android app may not function. When the down time starts, the database will first be shut down so that you can not make any changes to your setup while we copy everybody's setup to the new server.
After the server is back online (expected by 4PM PST on Dec 23), your tag manager may not automatically reconnect and need a power cycle (please unplug the power cable and plug in again). We apologize for this inconvenience.
Effective immediately we are increasing the price for motion sensor tag from $19 to $21. The reasons are
We are planning to introduce a white Polycarbonate enclosure (just like that for the Tag Manager) for the motion and water sensor in near future, so that we can reduce the cost and keep offering this product at a stable price.
When you configure "Auto-Update" for a tag, the server will send a command to the tag to configure it to send periodic status update (with temperature etc) at specified interval. An "out of range" notification is sent when the server does not receive periodic status update from a tag at expected time + some margin.
Because the tag stores the interval configuration in its local volatile memory, if you remove the battery and reinsert it, the tag will forget about the periodic status update it is supposed to send. As a result, soon you will receive a false "out-of-range" notification even though the tag is well within range. When you "ping" the tag, it will come back in range right after.
When the tag tries to transmit status update the transmission fails for some reason, it thinks it is out of range and will enter into a "hibernate" mode, where it no longer sends any status update until receiving a new command from the Tag Manager. If the status update fails for enough number of times to make the tag enter hibernate mode, and then recovers afterwards, the tag does not know about it and soon you will receive a false "out-of-range" message.
We have made a simple yet effective change to the server-side algorithm to reduce these false out-of-range notifications: Just before the server is about to mark the tag "out-of-range", it automatically attempts to re-configure the tag's "Auto-Update" interval, and only marks the tag out of range when this fails. Now when you receive "out-of-range" notification you know with more certainty that the tag is really out of range. Because this change is done on the server side, no app date / firmware update is needed.
a false "out of range" notification a false "out of range" notification "out-of-range"
We discovered a bug introduced by a firmware update in Long Range Motion Tag on September 15.
This can be reproduced by the following steps:
If tag manager is kept plugged in, if the tag ever has to re-transmit due to temporary interference, this problem may appear. As a result, the system will appear very unreliable, as any re-transmission will trigger this bug.
This problem only affects Motion Sensor Tags that were shipped between September 15 and 26 2013. If you can reproduce this problem, Please send an email to email@example.com, we will send you a prepaid return shipping label for you to return the tags for firmware update.
For long range sensor tags, if auto-update interval is set to be 5 minutes or longer, you may receive false out-of-range notifications followed by re-established link notification. This problem is caused by each tag sending updates at an longer interval of about 1.5x the configured interval. We have fixed this problem from the server side. To apply the fix to your set up, please from Web App, click Settings->Wireless... and change to some different frequency, and click Migrate. For tags that did not respond, a yellow "Migrate Settings" button will show up, click it to retry migration. We apologize for the inconvenience.
In new installation of iOS app (v1.8) the push notification does not register. This issue has just been discovered and has been fixed in v1.9 App. The v1.9 App also provides other bug fixes and cleaner UI, and new features below.
For those of you who tried out our beta version motion sensor tags, problems below were discovered thanks to your feedback, and were corrected in the release version:
Since Wireless Sensor Tags were released 1 year ago, they have been tried out by thousands of customers, many of whom have provided us with valuable feedback, bug reports and requests for new features and improvements. During the first few months of the release, we were updating the software almost daily to fix bugs and adding those improvements.
However, one common issue that persisted is sporadic "loss of link" which is caused by the limited range and reliability of the wireless connection. People also noted that the sensor tag range reduced significantly when placed inside metal fridge or behind metal door. We then realized that the final hurdle to our initial goal, a product with lasting value, was to improve the wireless performance.
We spent the last eight months not on ads or marketing, but on listening to our existing customers and building the best performing wireless platform possible for our application. Wireless Sensor Tags only need to send a few bytes once a while, while WLAN or Bluetooth are used to send megabytes of videos or voice, so they are clearly not efficient for our applications. Meanwhile new "narrow band radio" chips are emerging for applications such as wireless meter reading. They are able to reach kilometers range by using very low data rate and receiver bandwidth, using expensive frequency reference (crystals) and big antennas (and with radio operator license). Utilizing these new wireless technologies, we developed a solution using less expensive crystals and same antennas to keep the same form factor to achieve 4x improvement in the range.
We did this by a combination of increasing output power to FCC limit, using optimal frequency modulation index, better crystal and new frequency control techniques to allow 7x narrower receiver bandwidth to filter noise. Completely new radio IC with better noise figure and rewritten firmware are used in each tag and tag manager. We completed FCC part 15.231a certification for both the tags and tag managers.
Taking advantage of the much improved range, we implemented features to trade-off range with battery life, because not every application requires such a long range.
All these performance improvement and new features come at only $1 increase in cost to you. This covers the increased components for a new front-end filter, higher price of the new radio IC and a better crystal.
We have added a new feature in Web/Android app to display temperature, moisture, or battery voltage history for multiple tags on the same screen. Access this feature from "Stats..." button at the bottom of the page.
Meanwhile, we have re-tuned the database that stores these log data and added more indexes to significantly reduce the loading time for the statistics page.
We have started shipping Ethernet Tag Manager with new hardware on May 6. Those who received shipment notice on May 6 or later had initial problem of not being able to associate a tag until today (May 13). This problem was caused by a lack of web server support of a last minute firmware update made to the new Ethernet Tag Manager. We have just address this issue by adding the web server support. If you have experienced this issue, please try again and your problem should go away. Our apologies for any inconvenience this problem have caused. If you still have problem, please send email to firstname.lastname@example.org. We will reply to your email within 2~3 days. Our phone support will be back on May 30.
The latest iOS app (version 1.7.2) and web interface (http://mytaglist.com/eth) now support low battery alarm feature. When configured for a tag (all types of tags are supported), user can receive email, tweet and/or push notifications when its battery voltage drops below the configured threshold. The notification can be configured to repeat per hour, per day or per week until the battery voltage goes above the threshold.
From about 1 week ago, the cloud server that passes user commands to Tag Managers had experienced performance issue. During that time, motion event/temperature information upload from tag to the cloud server (via Tag Managers) was not affected, however, user who tried to beep, arm or disarm tags may have experienced very slow response and server timeout error.
This was due to an change we made to server configuration (locally run our "user command" forwarding server that used to run on a separate Linux server on the same www.mytaglist.com Windows web server) intended to reduce service down-time, but turns out the Windows port of the server software originally written for UNIX caused performance problems.
We have recently restored the old server configuration and have confirmed that these issues are now resolved. We apologize for any inconvenience these issues have caused.
We have sold out all of our existing Tag Manager and will be shipping new Tag Manager hardware from orders received today. The lead time remains the same (no more than 7~10 days.) The new Tag Manager looks and will work exactly the same as the old one, and is 100% compatible with all existing Tags. It provides the following new features.
We are now shipping moisture/water level sensor tag with firmware v1.4. It contains the following updates:
Cao Gadgets LLC
Attn: Moisture Tag v1.4 update (Order #[Your 4 digit Shopify order number])
Aliso Viejo, CA 92656
We are upgrading our cloud server to larger memory plan currently. During this time mytaglist.com will be down. We do not expect this down time to last more than 1 hour.
On Nov 29 from around 11:30AM PST to 3PM PST, The mytaglist.com and wirelesstag.net web site experienced service interruption. After it was restored around 3PM PST, many out of range or re-established link message may have been sent to you. Please disregard these messages. We have now disabled the out of range notification by default, so that you do not get these messages unless you specifically configure in the option to have out-of-range and re-established link messages sent.
We have since determined the cause of this web site crash and configured IIS setting to reduce the chance of this happening again in future.
iOS app 1.7 with bug fixes related to sound not played has been released a few days ago. Web/Android App have been updated with the following new features.