How to get data from manager locally? I mean without download from internet cloud.

[Weigang Shogan Li]

Guys, 

I am thinking about how to get the data out from the manager locally and immediately to my computer. I mean without let the manager sent data to cloud and send back to me by internet. 

Does anybody think about this before? Have you ever try? Please share your insight or way to achieve this. 

Thanks a lot~ 

---Shogan

[Zhiheng Cao]

A lot of the processing is done at the server side, for example, when a 3D compass sends the X,Y,Z reading, the server has to calculate arc tangent based on the reading and the previous reading to determine if the angle is more than the user programmed door opening threshold. For radio communication, the server has to check the received signal strength indicator and send command to adjust transmit power. There are many more. By pushing most of the complicated processing to the server side each tag can not only be very cost efficient but also have very low power consumption which leads to small battery size and long battery life. 

--
You received this message because you are subscribed to the Google Groups "Wireless Sensor Tags" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wireless-sensor-...@googlegroups.com.
To post to this group, send email to wireless-s...@googlegroups.com.
Visit this group at http://groups.google.com/group/wireless-sensor-tags.
To view this discussion on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/1955279c-b7ae-4d58-a4f4-597a02f702cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Weigang Shogan Li]

Alright, got your point. 

It's seem it is a trade off to cut functions on sensor tags side to achieve long battery life and small size. 

Thanks~   

On Tuesday, August 4, 2015 at 9:05:36 PM UTC-4, mytaglist.com support wrote:

A lot of the processing is done at the server side, for example, when a 3D compass sends the X,Y,Z reading, the server has to calculate arc tangent based on the reading and the previous reading to determine if the angle is more than the user programmed door opening threshold. For radio communication, the server has to check the received signal strength indicator and send command to adjust transmit power. There are many more. By pushing most of the complicated processing to the server side each tag can not only be very cost efficient but also have very low power consumption which leads to small battery size and long battery life. 

On Tue, Aug 4, 2015 at 5:49 PM, Weigang Shogan Li <weigang...@gmail.com> wrote:

Guys, 

I am thinking about how to get the data out from the manager locally and immediately to my computer. I mean without let the manager sent data to cloud and send back to me by internet. 

Does anybody think about this before? Have you ever try? Please share your insight or way to achieve this. 

Thanks a lot~ 

---Shogan

--
You received this message because you are subscribed to the Google Groups "Wireless Sensor Tags" group.

To unsubscribe from this group and stop receiving emails from it, send an email to wireless-sensor-tags+unsub...@googlegroups.com.

[James Hughes]

I agree with unloading most of the processing from the tags, but can see no reason there could not be a local solution to handle the calculations which need to be done. Weather a stand alone local service, or a plugin for other software which is running 24/7, such as HomeSeer. The reliance that all data must be sent to the cloud is the main thing holding me back from expanding my use of your tags. I have 10 from when they first became available, other then changing batteries, most of them are still working.

[Badger]

I don't buy this "too complicated" argument.

Given that the functionality already exists - it is a relatively simple matter to provide a code library to export that functionality - arguably simpler than providing that same functionality via a web interface as now.

With any luck the internal structure of the software running on the server in the cloud is configured to separate out this functionality from the code that supports the web services anyway (and if not it certainly ought to be for reasons of maintainability if nothing else).

Sounds to be like there is too much focus on what is easy for the company rather than what is best for their customers.

Oh well, I guess I will just have to find another supplier for my requirements instead.

[Mark Hargrove]

I'm sure this decision has nothing whatsoever to do with "what's good for their customers" and everything to do with "what's good for their business plan."

Any startup these days has to be thinking about their revenue model, and any revenue model that doesn't include recurring revenue streams ("subscriptions") isn't very interesting to investors -- so while the cloud-based hosting for the tags is free today, you can expect that it won't stay that way forever, and that fact has already got to be baked into their business plan.   If that were not the case, they would have pushed out a source repo for the server side for the people interested in it a long time ago.  

I mean, seriously:  would YOU want to maintain a service for hundreds of technically oriented home-automation geeks like us?  --or would you rather just say:  "OK, folks, here's the server-side code for the tag manager -- have at it" ?

[Automation Geek]

So any solution found to read Tag Manager Locally?

On Tuesday, August 4, 2015 at 8:49:18 PM UTC-4, Weigang Shogan Li wrote:

[mytaglist.com support]

I disagree with your accessment. The reason we do not release server side code into public domain is mainly because of intellectual property protection.
If we released that, we would see companies in countries with little IP protection laws use that code and reverse engineered firmware from the tags to come up with similar products at much lower price because they did not have to invest in research and development.

The pricing we have is all determined by market supply & demand. Suppose we added subscription fee then we would have to lower up front product price a lot to maintain the same sales volume, because of market competition. If we added subscription fee to existing customer when promising "no subscription fee for life" when they bought, we would be facing lawsuits and morally that's something we would never do.

We opt to the "higher up front price - zero subscription fee" to reduce the extra overhead in managing subscription & transaction fees, and to get more up front operation capital so we can invest in development without borrowing money.

[Erik]

I totally understand that you want to protect your investment. I feel that with the APIs it is not necessary to get access to the logs/data locally.

But one feature I would really like locally is "URL Callback with private IP" to work without first sending the request to the cloud and back again. I use the PIRs to turn on and off light in my house, most of the time it turn on the light immediately, but some times it can take up to 10-15 sec before the lights turn on, and it is no problem with the internet connection while the delay occours. Is this something that you may consider to implement?

Erik

[Zhiheng Cao]

Are you using Wemo light or Hue lamp? Have you considered the possibility that the 10-15 sec delay is in the light or Wemo's server responding to HTTP command from the tag manager?

--

You received this message because you are subscribed to the Google Groups "Wireless Sensor Tags" group.

To unsubscribe from this group and stop receiving emails from it, send an email to wireless-sensor-...@googlegroups.com.

To post to this group, send email to wireless-s...@googlegroups.com.

Visit this group at https://groups.google.com/group/wireless-sensor-tags.
To view this discussion on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/4b86dba7-b06b-44cb-8055-18668f9a87e6%40googlegroups.com.

[Erik]

I'm using neither, I have a Home Automation unit/server which receive the URL callback and then do the correct action depend on that. As said, it works very good and immediately most of the time. When it is delayed some lights on the tag manager is on while the delay, I will check next time which light is on. I also check the internet connection and ping to external sites have low response time while the delay of turning on light. 

I have start looking at the request sent out while the PIR detected movment, As I understand is that the field "fifo" that contain the information I'm looking for. May it be possible to get the information on how to decode this field, or decode just which PIR sensor and which event is triggered? it would really help.

Erik   

tirsdag 1. mars 2016 19.34.37 UTC+1 skrev mytaglist.com support følgende:

Are you using Wemo light or Hue lamp? Have you considered the possibility that the 10-15 sec delay is in the light or Wemo's server responding to HTTP command from the tag manager?

On Tue, Mar 1, 2016 at 2:59 AM, Erik <erik...@gmail.com> wrote:

I totally understand that you want to protect your investment. I feel that with the APIs it is not necessary to get access to the logs/data locally.

But one feature I would really like locally is "URL Callback with private IP" to work without first sending the request to the cloud and back again. I use the PIRs to turn on and off light in my house, most of the time it turn on the light immediately, but some times it can take up to 10-15 sec before the lights turn on, and it is no problem with the internet connection while the delay occours. Is this something that you may consider to implement?

Erik

tirsdag 1. mars 2016 00.37.49 UTC+1 skrev mytaglist.com support følgende:

I disagree with your accessment. The reason we do not release server side code into public domain is mainly because of intellectual property protection.
If we released that, we would see companies in countries with little IP protection laws use that code and reverse engineered firmware from the tags to come up with similar products at much lower price because they did not have to invest in research and development.

The pricing we have is all determined by market supply & demand. Suppose we added subscription fee then we would have to lower up front product price a lot to maintain the same sales volume, because of market competition. If we added subscription fee to existing customer when promising "no subscription fee for life" when they bought, we would be facing lawsuits and morally that's something we would never do.

We opt to the "higher up front price - zero subscription fee" to reduce the extra overhead in managing subscription & transaction fees, and to get more up front operation capital so we can invest in development without borrowing money.

--
You received this message because you are subscribed to the Google Groups "Wireless Sensor Tags" group.

To unsubscribe from this group and stop receiving emails from it, send an email to wireless-sensor-tags+unsub...@googlegroups.com.

To post to this group, send email to wireless-s...@googlegroups.com.
Visit this group at https://groups.google.com/group/wireless-sensor-tags.

[Zhiheng Cao]

If you are seeing the orange up arrow on, that's when the tag manager has just received transmission from a tag and uploading the data to web server. Even if we changed the tag manager firmware to do the URL calling without going through the server, you will still get this delay in such case, because the tag manager has only 2 threads, one for listening for tag transmission, check CRC, fill FIFO and sending radio ack, another for uploading data in FIFO to server.  If the FIFO has something in it it will work on uploading them and have delay before getting to the point where it can call URL. 

If you are seeing the red "!" mark on, that's when the tag manager initiated URL calling, and it's waiting for the URL endpoint to send HTTP response header. The delay in this case is the delay in your URL endpoint returning HTTP response. 

On Tue, Mar 1, 2016 at 11:02 AM, Erik <erik...@gmail.com> wrote:

I'm using neither, I have a Home Automation unit/server which receive the URL callback and then do the correct action depend on that. As said, it works very good and immediately most of the time. When it is delayed some lights on the tag manager is on while the delay, I will check next time which light is on. I also check the internet connection and ping to external sites have low response time while the delay of turning on light. 

I have start looking at the request sent out while the PIR detected movment, As I understand is that the field "fifo" that contain the information I'm looking for. May it be possible to get the information on how to decode this field, or decode just which PIR sensor and which event is triggered? it would really help.

Erik   

tirsdag 1. mars 2016 19.34.37 UTC+1 skrev mytaglist.com support følgende:

Are you using Wemo light or Hue lamp? Have you considered the possibility that the 10-15 sec delay is in the light or Wemo's server responding to HTTP command from the tag manager?

On Tue, Mar 1, 2016 at 2:59 AM, Erik <erik...@gmail.com> wrote:

I totally understand that you want to protect your investment. I feel that with the APIs it is not necessary to get access to the logs/data locally.

But one feature I would really like locally is "URL Callback with private IP" to work without first sending the request to the cloud and back again. I use the PIRs to turn on and off light in my house, most of the time it turn on the light immediately, but some times it can take up to 10-15 sec before the lights turn on, and it is no problem with the internet connection while the delay occours. Is this something that you may consider to implement?

Erik

tirsdag 1. mars 2016 00.37.49 UTC+1 skrev mytaglist.com support følgende:

I disagree with your accessment. The reason we do not release server side code into public domain is mainly because of intellectual property protection.
If we released that, we would see companies in countries with little IP protection laws use that code and reverse engineered firmware from the tags to come up with similar products at much lower price because they did not have to invest in research and development.

The pricing we have is all determined by market supply & demand. Suppose we added subscription fee then we would have to lower up front product price a lot to maintain the same sales volume, because of market competition. If we added subscription fee to existing customer when promising "no subscription fee for life" when they bought, we would be facing lawsuits and morally that's something we would never do.

We opt to the "higher up front price - zero subscription fee" to reduce the extra overhead in managing subscription & transaction fees, and to get more up front operation capital so we can invest in development without borrowing money.

--
You received this message because you are subscribed to the Google Groups "Wireless Sensor Tags" group.

To unsubscribe from this group and stop receiving emails from it, send an email to wireless-sensor-...@googlegroups.com.

To post to this group, send email to wireless-s...@googlegroups.com.
Visit this group at https://groups.google.com/group/wireless-sensor-tags.

To view this discussion on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/4b86dba7-b06b-44cb-8055-18668f9a87e6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Wireless Sensor Tags" group.

To unsubscribe from this group and stop receiving emails from it, send an email to wireless-sensor-...@googlegroups.com.

To post to this group, send email to wireless-s...@googlegroups.com.
Visit this group at https://groups.google.com/group/wireless-sensor-tags.

To view this discussion on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/e45f20eb-0956-4c98-a417-0c3f377341e2%40googlegroups.com.