Shellyforhass: Slow update of current consumption

[dodg3r]

Hi.

I dont understand why you close the thread before I can reply.
This is not the case...

If revert back to version beta 8 it works.
There is something wrong i the latest version.

Look at this video: https://share.icloud.com/photos/0uG8d6kRDC-HsNPHxXhUuJNCA

My DEV install on the right is on beta 8.
My PROD install is on latest 0.1.6

when I turn on my plug:

2020-02-25 13:53:00 DEBUG (SyncWorker_7) [pyShelly] http://192.168.1.70/relay/0?turn=on
2020-02-25 13:53:00 DEBUG (SyncWorker_7) [pyShelly] http://192.168.1.70/relay/0?turn=on - Ok
2020-02-25 13:53:00 DEBUG (CoAP) [pyShelly] CoAP msg: 192.168.1.70 b'P\x1e\x8a\xfe\xb3cit\x01s\xed\x0b\xec\x03SHPLG-S#*#1\xd2C\x96\x00\x82\x82\x00\xff{"G":[[0,111,0.00],[0,112,1],[0,113,30.37],[0,114,86.67],[0,115,0]]}'
2020-02-25 13:53:00 DEBUG (CoAP) [pyShelly] CoAP msg: 30 192.168.1.70 bytearray(b'P\x1e\x8a\xfe\xb3cit\x01s\xed\x0b\xec\x03SHPLG-S##1\xd2C\x96\x00\x82\x82\x00\xff{"G":[[0,111,0.00],[0,112,1],[0,113,30.37],[0,114,86.67],[0,115,0]]}')
2020-02-25 13:53:00 DEBUG (CoAP) [pyShelly] CoAP Code: 30, Type SHPLG-S, Id , Payload *{"G":[[0,111,0.00],[0,112,1],[0,113,30.37],[0,114,86.67],[0,115,0]]}
2020-02-25 13:53:00 INFO (CoAP) [pyShelly] Update id:* state:True stateValue:None values:None info_values:{'over_power': False, 'current_consumption': 0, 'total_consumption': 902}
2020-02-25 13:53:00 INFO (CoAP) [pyShelly] Update id:* state:0.0 stateValue:None values:None info_values:None

4 seconds later it states the consumption:

2020-02-25 13:53:04 DEBUG (CoAP) [pyShelly] CoAP msg: 30 192.168.1.70 bytearray(b'P\x1e\x8b\x00\xb3cit\x01s\xed\x0b\xec\x03SHPLG-S#*#1\xd2C\x96\x00\x82\x84\x00\xff{"G":[[0,111,24.27],[0,112,1],[0,113,30.43],[0,114,86.77],[0,115,0]]}')
2020-02-25 13:53:04 DEBUG (CoAP) [pyShelly] CoAP Code: 30, Type SHPLG-S, Id , Payload *{"G":[[0,111,24.27],[0,112,1],[0,113,30.43],[0,114,86.77],[0,115,0]]}
2020-02-25 13:53:04 INFO (CoAP) [pyShelly] Update id:* state:True stateValue:None values:None info_values:{'over_power': False, 'current_consumption': 24, 'total_consumption': 902}
2020-02-25 13:53:04 INFO (CoAP) [pyShelly] Update id:* state:24.27 stateValue:None values:None info_values:None

But it doesnt update lovelace until 40 sec later.

I think this delay started after you changed the sensors name from _consumption to _current_consumption.

[vistalba]

@dodg3r

Is host 192.168.1.68 in the same subnet as hassio.local?
Shelly uses CoAP discovery which is mDNS/multicast based and doesn't work (without extra configuration) in different networks.

Are both (dev/prod) Homeassistant installations in same Subnet as the Shelly? As it looks to me like it updated after 60 seconds (timeout to pull the device manually?)

[dodg3r]

Yes they are on same subnet, dev is on 192.168.1.93.

If I update my dev installation with 0.1.6 i get the same delays. I then reverted to beta 8 and the delays is gone.
Is there someone out there with 0.1.6 without the delays ?

[chemelli74]

If I update my dev installation with 0.1.6 i get the same delays. I then reverted to beta 8 and the delays is gone.

Just to clarify: you receive CoAP message after few seconds;
with 0.1.6b8 you have a lovelace update after few seconds;
instead with 0.1.6 final you have a lovelace update after 40 seconds.

Please correct me if I'm wrong.

Simone

[dodg3r]

Yes youre right.

In my dev installation with beta 8 installed i get the first coap message 4 seconds after turning on my plug. Lovelace updates at that point and shows the consumption.

In my prod installation with 0.1.6 installed i get the first coap message after 4 seconds after turning on my plug but lovelace doesnt update, it still shows 0 in consumption.

[chemelli74]

Do you mind testing also b9 and b10 ? So we can narrow the issue down to a specific bild.

Simone

[dodg3r]

Hi.

Updated to beta 9 and the delays are back.
So beta 8 is working and beta 9 - 0.1.6 is not working.

[dodg3r]

Hi.

Running 0.1.6 and I can see that current_consumption in attributes updates within 4 seconds. But the sensor current_consumption doesnt update until next poll.
Look at the video
https://1drv.ms/v/s!AgZRSIF72Mnv6hySBDHXf3OoChkW?e=7hZLtt

[hakana]

If you look in your dialog on the consumption attribute it is updated in 5 sec. So this is more like a bug in HA I think. Try to add the sensor in a card in lovelace. The delay of 5 sec is a bug in the Shelly FW.

[dodg3r]

Hi.
Yes, I tried to explain that in the comment before :)
Even if I try to put it in a lovelace card it has the delays.

I think its strange that if I revert back to 0.1.6 beta 8 it works...

I have a drainpump in an automation so if the drainpump starts I will get a push notice.
The drainpump only runs for 15 secs and because of the delays I dont get the push after version 0.1.6 beta8

Is there any changes in setting up the config after beta 8 that I have missed ?

[chemelli74]

Latest beta fixed hte issue for me, no more than 5 sec to get the lovelace update.
@dodg3r, please check and confirm.

Simone

[vistalba]

@chemelli74 Any breaking change in the beta or is it easy to revert back ?

[dodg3r]

Latest beta fixed hte issue for me, no more than 5 sec to get the lovelace update.
@dodg3r, please check and confirm.

Simone

YYEEESS, now it works :)

Great !