core: Wemo power consumption sensors not being reported when insight switch off

I can confirm all my wemo plugs reset between 00:00:02 and 00:00:25 for the last even if they were in off state Great thanks for the fix!

Oh excellent, i will install it and let you know… greatly appreciated

Awesome news. Thanks for working on this with me!

It worked!! Right at midnight (with time zone set to -7) the today counters reset to 0!!! Want to see it Happen one more time but this is fantastic!!

I will stay right on 2021.8.8

Some more info… ive started working with some tuya-compatible topgreener plugs… using tuya convert you can easily put tasmota on there. These plugs also measure power AND they are the smaller single outlet format so they dont block the second plug. So far so good. Just throwing this out there because the wemo devices are not performing properly and wemo doesnt seem to have a solution so far.

Another interesting development. With the timesync timezone set to 0, both of them reset today at 5pm PST. So i figure. 5 plus 7h offset from UTC gets me to UTC time of midnight… so I may be on to something here. Maybe its the way the timezone thing is entered. Im going to leave it for another day and see if they reset at 5pm again and then play with the settings. Wemo is still helping out but havent come back with much yet.

So things did not reset when i expected them to… but i tweaked a couple more things and still testing… will report back

Thanks very much for that! That’s really helpful… Well i think i have everything set properly on my insight so let’s see if the counters reset at midnight tonight. Thanks for that.

A bit more… Seems you can read the time through both urn:Belkin:service:deviceinfo:1#GetInformation and urn:Belkin:service:metainfo:1#GetExtMetaInfo. You can set the time using both urn:Belkin:service:deviceinfo:1#GetDeviceInformation (notice this is different than first one, ‘getdeviceinformation’ vs ‘get information’, and you can also set the time with urn:Belkin:service:timesync:1#TimeSync.

The timesync action takes the following format:

<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <s:Body>
        <u:TimeSync xmlns:u="urn:Belkin:service:timesync:1">
            <UTC>1328358323</UTC>
            <TimeZone>-7</TimeZone>
            <dst>0</dst>
            <DstSupported>0</DstSupported>
        </u:TimeSync>
    </s:Body>
</s:Envelope>

The action GetDeviceInformation accepts the same format:

<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
   <s:Body>
      <u:GetDeviceInformation xmlns:u="urn:Belkin:service:deviceinfo:1">
         <UTC>1481906270</UTC>
         <TimeZone>-5</TimeZone>
         <dst>0</dst>
         <DstSupported>0</DstSupported>
      </u:GetDeviceInformation>
   </s:Body>
</s:Envelope>

I think that would work great… just as an update, we are past 7pm PST here and the aggregate total daily power usage has NOT reset… so we’ll see if it does it at midnight… fingers crossed.

Might have gotten a little further. Im using the deviceinfoservices services and did this POST:

<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <s:Body>
        <u:GetInformation xmlns:u="urn:Belkin:service:deviceinfoservice:1">
        </u:GetInformation>
    </s:Body>
</s:Envelope>

I got this back:

            <Information>&lt;Device&gt;&lt;DeviceInformation&gt;&lt;firmwareVersion&gt;WeMo_WW_2.00.11532.PVT-OWRT-Insight&lt;/firmwareVersion&gt;&lt;iconVersion&gt;0&lt;/iconVersion&gt;&lt;iconPort&gt;49153&lt;/iconPort&gt;&lt;macAddress&gt;94103E42100C&lt;/macAddress&gt;&lt;binaryState&gt;1&lt;/binaryState&gt;&lt;hwVersion&gt;v1&lt;/hwVersion&gt;&lt;deviceCurrentTime&gt;1628297494&lt;/deviceCurrentTime&gt;&lt;productName&gt;Insight&lt;/productName&gt;&lt;FriendlyName&gt;Lean-To Greenhouse&lt;/FriendlyName&gt;&lt;currentFWUpdateState&gt;4&lt;/currentFWUpdateState&gt;&lt;CountdownEndTime&gt;0&lt;/CountdownEndTime&gt;&lt;/DeviceInformation&gt;&lt;/Device&gt;</Information>

you can see the current time in there… and when i convert that time to human readable i get this:

And this is the correct time and timezone adjusted time. So perhaps that setting i did in the timesync service actually properly set the time and timezone.

ok some findings… i am using this POST call:

<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <s:Body>
        <u:TimeSync xmlns:u="urn:Belkin:service:timesync:1">
            <UTC></UTC>
            <TimeZone>-6</TimeZone>
            <dst>1</dst>
        </u:TimeSync>
    </s:Body>
</s:Envelope>

and its working… im only playing with the dst and timezone settings… but when do this, it seems to reset the daily power consumption value… check this graph out from home assistant… i just seemed to have reset it:

So i set some variables… and it took it but there is an odd catch… first off i sent this:

<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <s:Body>
        <u:TimeSync xmlns:u="urn:Belkin:service:timesync:1">
            <UTC>1628295577</UTC>
            <TimeZone>-7</TimeZone>
            <dst>0</dst>
        </u:TimeSync>
    </s:Body>
</s:Envelope>

the first UTC value is epoch time in seconds where i am… the second timezone setting is PST (guessing here, its an INT value) and dst 0 (off)… it takes this… but there was one point where i had to set UTC first with timezone blank, and then set timezone.