BUG report: Wemo status reported back as ON while it is OFF.

[wiigor zweeffan]

I made a wemo app to turn on and off a dehumidifier based on humidity of a sensor. 4/24/2015 8:10 AM Turning ON Wemo because the humidity is:64.166259765625 which is higher than the turn on value of: 64

The app has turned the wemo on 12 hours ago. The wemo also is showing as green ON all these 12 hours in the web and mobile interface. also when i refresh. There have been no errors like wemo not connected to internet. But i was flaberguested as humidity kept rising. So i logged in with the WEMO application itself and it shows the wemo switch as OFF and consumption as 0. So a WEMO switch that is OFF is being reported as ON by wirelesstag.

[Zhiheng Cao]

Sounds like the app is controlling the wrong wemo device. Please unassociate the wemo and use either Android or iOS app to associate the wemo back. Then make sure the wemo turn on/off from the light on/off button actually works. 

--
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/a9422218-079a-4ec4-865b-e8913340e765%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[wiigor zweeffan]

It is not controlling the wrong wemo device. The wemo device was being controlled correctly in the same run of the kumoapp as can be seen from the log. configuration has not been changed, nor has the code been changed or the app restarted. If you connect to the wemo open api you will see they report the switch as off and its actually off and wireless tag is reporting it as on.

On Friday, April 24, 2015 at 9:03:39 PM UTC+2, mytaglist.com support wrote:

Sounds like the app is controlling the wrong wemo device. Please unassociate the wemo and use either Android or iOS app to associate the wemo back. Then make sure the wemo turn on/off from the light on/off button actually works. 

On Fri, Apr 24, 2015 at 11:49 AM, wiigor zweeffan <zwee...@gmail.com> wrote:

I made a wemo app to turn on and off a dehumidifier based on humidity of a sensor. 4/24/2015 8:10 AM Turning ON Wemo because the humidity is:64.166259765625 which is higher than the turn on value of: 64

The app has turned the wemo on 12 hours ago. The wemo also is showing as green ON all these 12 hours in the web and mobile interface. also when i refresh. There have been no errors like wemo not connected to internet. But i was flaberguested as humidity kept rising. So i logged in with the WEMO application itself and it shows the wemo switch as OFF and consumption as 0. So a WEMO switch that is OFF is being reported as ON by wirelesstag.

--
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.

[Zhiheng Cao]

I understand. What I was saying is that maybe the link between WeMo and our app is broken which caused the Wemo to not be able to controlled by the light on/off button manually inside our app, either. 

If so, please unassociate the wemo and try to add it back using our iOS or Android app. 

On Fri, Apr 24, 2015 at 1:39 PM, wiigor zweeffan <zwee...@gmail.com> wrote:

It is not controlling the wrong wemo device. The wemo device was being controlled correctly in the same run of the kumoapp as can be seen from the log. configuration has not been changed, nor has the code been changed or the app restarted. If you connect to the wemo open api you will see they report the switch as off and its actually off and wireless tag is reporting it as on.

On Friday, April 24, 2015 at 9:03:39 PM UTC+2, mytaglist.com support wrote:

Sounds like the app is controlling the wrong wemo device. Please unassociate the wemo and use either Android or iOS app to associate the wemo back. Then make sure the wemo turn on/off from the light on/off button actually works. 

On Fri, Apr 24, 2015 at 11:49 AM, wiigor zweeffan <zwee...@gmail.com> wrote:

I made a wemo app to turn on and off a dehumidifier based on humidity of a sensor. 4/24/2015 8:10 AM Turning ON Wemo because the humidity is:64.166259765625 which is higher than the turn on value of: 64

The app has turned the wemo on 12 hours ago. The wemo also is showing as green ON all these 12 hours in the web and mobile interface. also when i refresh. There have been no errors like wemo not connected to internet. But i was flaberguested as humidity kept rising. So i logged in with the WEMO application itself and it shows the wemo switch as OFF and consumption as 0. So a WEMO switch that is OFF is being reported as ON by wirelesstag.

--
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/a9422218-079a-4ec4-865b-e8913340e765%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 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/c6f7cf28-3d84-4a39-a5c0-d63b5bf092b5%40googlegroups.com.

[wiigor zweeffan]

That assumption seems to be incorrect.

This is what I did.

1. verified using the wemo app the wemo insight was off and the consumption was 0
   
2. verified that in the wireless tag web interface the wemo was marked as on
3. in the wireless tag web interface manually turned the wemo to off.
4. verified using the wemo app the wemo insight was off and the consumption was 0
5. in the wireless tag web interface manually turned the wemo to on
6. verified using the wemo app the wemo insight was on and the consumption was 350 watt

So concluding. The the link between WeMo and the app was not broken.

my dehumidifier app commanded the switch to go to on.

the kumoapp interface reported no error. (this means succesful operation)

then as the wemoapp checked the status of the switch about every 10 minutes with wemoSwitch.lit  it always returned on.

so the problem seems to be some sort of caching of

wemoSwitch.lit

This value should not be cached it should be fetched on every request from the wemo servers. Else it will be stale data.

On Friday, April 24, 2015 at 10:42:31 PM UTC+2, mytaglist.com support wrote:

I understand. What I was saying is that maybe the link between WeMo and our app is broken which caused the Wemo to not be able to controlled by the light on/off button manually inside our app, either. 

If so, please unassociate the wemo and try to add it back using our iOS or Android app. 

On Fri, Apr 24, 2015 at 1:39 PM, wiigor zweeffan <zwee...@gmail.com> wrote:

It is not controlling the wrong wemo device. The wemo device was being controlled correctly in the same run of the kumoapp as can be seen from the log. configuration has not been changed, nor has the code been changed or the app restarted. If you connect to the wemo open api you will see they report the switch as off and its actually off and wireless tag is reporting it as on.

On Friday, April 24, 2015 at 9:03:39 PM UTC+2, mytaglist.com support wrote:

Sounds like the app is controlling the wrong wemo device. Please unassociate the wemo and use either Android or iOS app to associate the wemo back. Then make sure the wemo turn on/off from the light on/off button actually works. 

On Fri, Apr 24, 2015 at 11:49 AM, wiigor zweeffan <zwee...@gmail.com> wrote:

I made a wemo app to turn on and off a dehumidifier based on humidity of a sensor. 4/24/2015 8:10 AM Turning ON Wemo because the humidity is:64.166259765625 which is higher than the turn on value of: 64

The app has turned the wemo on 12 hours ago. The wemo also is showing as green ON all these 12 hours in the web and mobile interface. also when i refresh. There have been no errors like wemo not connected to internet. But i was flaberguested as humidity kept rising. So i logged in with the WEMO application itself and it shows the wemo switch as OFF and consumption as 0. So a WEMO switch that is OFF is being reported as ON by wirelesstag.

--
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 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/a9422218-079a-4ec4-865b-e8913340e765%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-tags+unsub...@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.

[wiigor zweeffan]

In my wemoapp I now first check if the wemoswitch is on and if its on i set it to on with the lighton function.
Same for when its off.

I think its ugly and should not be needed. But hopefully it works.

[Zhiheng Cao]

Hi Wiigor,

Now you can call the update() method (http://mytaglist.com/kumoapp/71/update) to get the latest WeMo on/off state in the lit property. 

Please give it a try. Before reading the .lit property simply call the update() method once. You can also cascade:  instead of writing wemo.lit, write wemo.update().lit

Unlike your suggestion of updating WeMo state automatically when lit property is read, we decided against it because if a script reads lit property many times, it will cause unnecessary load on the server. 

--
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/87a9ad22-8ac7-4c97-95cf-006829198585%40googlegroups.com.

[wiigor zweeffan]

Did the update button of the web app use the lit property before for wemo switches? and is it using update() now?
Because I hit update many times (yesterday) on the web app and the status remained wrong. (which could have been explained by the web app using the lit value on update of wemo switches)

Anyways I will change the kumoapp script to use the update() and see how long it keeps running :)

Thanks for your support.

On Saturday, April 25, 2015 at 1:01:45 AM UTC+2, mytaglist.com support wrote:

Hi Wiigor,

Now you can call the update() method (http://mytaglist.com/kumoapp/71/update) to get the latest WeMo on/off state in the lit property. 

Please give it a try. Before reading the .lit property simply call the update() method once. You can also cascade:  instead of writing wemo.lit, write wemo.update().lit

Unlike your suggestion of updating WeMo state automatically when lit property is read, we decided against it because if a script reads lit property many times, it will cause unnecessary load on the server. 

On Fri, Apr 24, 2015 at 2:42 PM, wiigor zweeffan <zwee...@gmail.com> wrote:

In my wemoapp I now first check if the wemoswitch is on and if its on i set it to on with the lighton function.
Same for when its off.

I think its ugly and should not be needed. But hopefully it works.

--
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 http://groups.google.com/group/wireless-sensor-tags.

[wiigor zweeffan]

When invoking the update function on a wemo switch I get the following error:

The parameterized query '(@mac varchar(12),@cap float,@lit bit,@updated bigint,@updater c' expects the parameter '@updater', which was not supplied.