SA smart plugs that can be flashed with Tasmota

[SauRoNZA]

I know that you can change this in Tasmota, and that some people have made rules to switch the reporting rate higher when the load shifts to higher than say 10w.

Looking at my geyser's CBI astute, which is tuya based and using tuya-local, I see it has been stuck on the same wattage for 26 mins.

I'm not aware of any way of changing this. But I want to say you should be able to change it in ESPHOME? View attachment 1827786

A geyser being on for 26 minutes isn’t abnormal though?

It makes sense to me it would only send out an updated value if it changes.

My geyser behaviour is much the same and I don’t use Tasmota.

 

[Tinuva]

A geyser being on for 26 minutes isn’t abnormal though?

It makes sense to me it would only send out an updated value if it changes.

My geyser behaviour is much the same and I don’t use Tasmota.

I know you are inexperienced with Tasmota, but even with non-Tasmota devices the behavior can be very different.

Have 2 different zigbee mains powered devices.

Plug #1: Updates at a constant interval, every 60 seconds (could be 300 but I think its 60)
Plug #2: Updates realtime, when the power (W or kW) changes more than a certain %.

Now, depending on your use case, either could be better.

#1 is better when you want to keep the amount of updates to your history database to a minimum. However, accuracy is not great, if the power use shoots up right after an update, you loose up to 59 seconds worth of usage.

#2 is better when you want more accuracy on usage. Because it will update realtime.

So in my opinion, even ignoring tastmota, your use case, should drive the type of reporting the plug does. So I think the @Jebula999 has a valid question/concern.

 

[RoganDawes]

I know you are inexperienced with Tasmota, but even with non-Tasmota devices the behavior can be very different.

Have 2 different zigbee mains powered devices.

Plug #1: Updates at a constant interval, every 60 seconds (could be 300 but I think its 60)
Plug #2: Updates realtime, when the power (W or kW) changes more than a certain %.

Now, depending on your use case, either could be better.

#1 is better when you want to keep the amount of updates to your history database to a minimum. However, accuracy is not great, if the power use shoots up right after an update, you loose up to 59 seconds worth of usage.

#2 is better when you want more accuracy on usage. Because it will update realtime.

So in my opinion, even ignoring tastmota, your use case, should drive the type of reporting the plug does. So I think the @Jebula999 has a valid question/concern.

FWIW, ESPHome can be set to use either or both of the above approaches.

Usually update every N period, unless it changes by more than M%, in which case send an update immediately.

Sensor Component

Instructions for setting up sensor components in ESPHome.

esphome.io

 

[SauRoNZA]

I know you are inexperienced with Tasmota, but even with non-Tasmota devices the behavior can be very different.

Have 2 different zigbee mains powered devices.

Plug #1: Updates at a constant interval, every 60 seconds (could be 300 but I think its 60)
Plug #2: Updates realtime, when the power (W or kW) changes more than a certain %.

Now, depending on your use case, either could be better.

#1 is better when you want to keep the amount of updates to your history database to a minimum. However, accuracy is not great, if the power use shoots up right after an update, you loose up to 59 seconds worth of usage.

#2 is better when you want more accuracy on usage. Because it will update realtime.

So in my opinion, even ignoring tastmota, your use case, should drive the type of reporting the plug does. So I think the @Jebula999 has a valid question/concern.

I have plenty of experience with Tasmota, I still have 10 of them in my house.

If your end goal is total usage then you wouldn’t be tracking this sensor in the first place but the difference on the total usage sensor.

Hence it’s not really all that important and you won’t be losing any data accuracy.

And even in the case of a load shedding type automation it won’t be a problem because you’ll likely turn it off anyway, not base it on the current usage.

My aircons run on CBI Astutes with the standard firmware and because it’s a variable device the updates are pretty much real time.

The geyser also on a CBI Astute doesn’t need to update constantly because the usage is constant. It simply updates when the usage actually changes, which is pretty much the same thing as real time…the only different is it doesn’t phone home just to say things are still the same.

His concern is more that updates aren’t happening, but this would be very simple to test by turning it off so the actual usage changes and then seeing if it updates quickly enough. If it does, no problem. If it doesn’t…then worry about adjusting it.

****

In fact my Alarm is still on Tasmota and it gets a state change virtually instantly. But only when the state is actually changed, not in an ongoing manner.



This is a perfectly reasoned behaviour and no need for a geyser to be different.

My point is there isn’t really a problem here.

 

[Tinuva]

I have plenty of experience with Tasmota, I still have 10 of them in my house.

If your end goal is total usage then you wouldn’t be tracking this sensor in the first place but the difference on the total usage sensor.

Hence it’s not really all that important and you won’t be losing any data accuracy.

And even in the case of a load shedding type automation it won’t be a problem because you’ll likely turn it off anyway, not base it on the current usage.

My aircons run on CBI Astutes with the standard firmware and because it’s a variable device the updates are pretty much real time.

The geyser also on a CBI Astute doesn’t need to update constantly because the usage is constant. It simply updates when the usage actually changes, which is pretty much the same thing as real time…the only different is it doesn’t phone home just to say things are still the same.

His concern is more that updates aren’t happening, but this would be very simple to test by turning it off so the actual usage changes and then seeing if it updates quickly enough. If it does, no problem. If it doesn’t…then worry about adjusting it.

****

In fact my Alarm is still on Tasmota and it gets a state change virtually instantly. But only when the state is actually changed, not in an ongoing manner.

View attachment 1827839

This is a perfectly reasoned behaviour and no need for a geyser to be different.

My point is there isn’t really a problem here.

Good for you, but it may not work for someone else. There is still use cases for real time updates.

 

[SauRoNZA]

Good for you, but it may not work for someone else. There is still use cases for real time updates.

Sure, but @ebendl seems to think there is a problem, which there isn’t.

That’s the only point I was making before you went off on a tangent again.

My comment has nothing to do with @Jebula999 and whatever conversation you were having.

Also has nothing to do with Tasmota…but somehow you injected that and yourself into the conversation yet again while also making massive assumptions along the way.

This is the second time now you’ve been a supreme ******** for no reason whatsoever. You might want to take an introspective look at yourself.

 

[ebendl]

Sure, but @ebendl seems to think there is a problem, which there isn’t.

Not saying there's a problem. I would imagine even a geyser would have some variability in its usage - which obviously my CBI isn't picking up if it is relatively small (e.g. couple of watts up or down).

This just indicated to me - without bothering to go online and check - that the CBI only sends updates on significant changes. It doesn't send regular updates (like teleperiod in Tasmota) as I would then see more constant changes every X seconds.

And indeed - looking at the numbers now it does show some changes:
But overall in the grander scheme of things a couple of watts on 4kw isn't really going to skew any numbers I'm interested in, so I'm not bothered by this.

 

[SauRoNZA]

Not saying there's a problem. I would imagine even a geyser would have some variability in it's usage - which obviously my CBI isn't picking up if it relatively small (e.g. Couple of watts up or down).

This just indicated to me - without bothering to go online and check - that the CBI only sends updates on significant changes. It doesn't send regular updates (like teleperiod in Tasmota) as I would then see more constant changes every X seconds.

And indeed - looking at the numbers now it does show some changes: View attachment 1827956
But overall in the grander scheme of things a couple of watts on 4kw isn't really going to skew any numbers I'm interested in, so I'm not bothered by this.

Yeah like I said for any metering you wouldn’t look at the wattage anyway, but rather at the total power consumed which it works out internally.

Something like a geyser with a resistive load will be very flat and constant like you’ve seen.

Whole different story with something like a fridge that goes up and down constantly but even that works just fine.

 

[Tinuva]

Sure, but @ebendl seems to think there is a problem, which there isn’t.

That’s the only point I was making before you went off on a tangent again.

My comment has nothing to do with @Jebula999 and whatever conversation you were having.

Also has nothing to do with Tasmota…but somehow you injected that and yourself into the conversation yet again while also making massive assumptions along the way.

This is the second time now you’ve been a supreme ******** for no reason whatsoever. You might want to take an introspective look at yourself.

Thanks for the insulting words. It was a well laid out post with good technical information. Seems you just don't like my my posts, no matter how useful they are.

 

[SauRoNZA]

Thanks for the insulting words. It was a well laid out post with good technical information. Seems you just don't like my my posts, no matter how useful they are.

It’s my pleasure.

And exactly the same applies to you.

You are so hell bent on imposing your way of doing things in the most condescending manner possible on everyone you completely missed the fact it wasn’t even the same conversation at all and an entirely different post I was responding to.

Which is fine, it takes one to know one, just understand that we are exactly the same coming from different sides.

Your way isn’t the only way and equally doesn’t apply to everyone. Things can be done differently and that’s just fine, but no need to be an ******* about it.

You love to over complicate things unnecessarily by default. Some people love that, but it’s not the only way.

 

[Tinuva]

It’s my pleasure.

And exactly the same applies to you.

You are so hell bent on imposing your way of doing things in the most condescending manner possible on everyone you completely missed the fact it wasn’t even the same conversation at all and an entirely different post I was responding to.

Which is fine, it takes one to know one, just understand that we are exactly the same coming from different sides.

Your way isn’t the only way and equally doesn’t apply to everyone. Things can be done differently and that’s just fine, but no need to be an ******* about it.

Takes one to know one? OK. Guess you said it, imposing your way in the most condescending way...

I will take my exit here.

 

[SauRoNZA]

Takes one to know one? OK. Guess you said it, imposing your way in the most condescending way...

I will take my exit here.

Only responding in like for like.

Every time we’ve gone down this road you’ve started it because you can’t possibly fathom that different people want different things.

It’s Tinuva’s way or it’s wrong. Just take a moment and look at how you started responding to me and then you seem surprised that you got the same back? Doesn’t work like that mate. You aren’t the victim here.

If you want to dish it out then be prepared to take it back in kind.

****

By the way I do like your posts. They are a wealth of technical information I often refer to.

I just don’t appreciate the dripping sarcasm and condescension that gets directly applied when responding to me specifically, just because I intentionally offer simpler solutions and question whether things are really necessary.

 

[Jebula999]

FWIW, ESPHome can be set to use either or both of the above approaches.

Usually update every N period, unless it changes by more than M%, in which case send an update immediately.

Sensor Component

Instructions for setting up sensor components in ESPHome.

esphome.io

On a lighter note, this looks to be exactly what I need.
I went ahead and order 1 of each plug (Zigbee and ESPHome) to test.

Looking forward to seeing what they have to offer

 

[SilverBullet]

Hi Guys.

Im brand new to this and recently purchased some of the EWeLink 3 pin 16A SA plugs.

eWeLink Smart Plug (Energy Monitoring) - SmartPad

eWeLink Wi-Fi Smart Socket 3 Pin Plug South Africa Outlet Adapter with Energy Monitoring.Integrates with the eWeLink app. Dimensions - 56mm X 56mm X 40mm.

store.smartpad.co.za

I’ve managed to get them into eWeLink and setup from what I can see. However the power monitoring doesn’t seem to be very active. Am I just being impatient (not sure how often it should refresh or give info)

Anyone able to offer some advice or guidance?

 

[RoganDawes]

Hi Guys.

Im brand new to this and recently purchased some of the EWeLink 3 pin 16A SA plugs.

eWeLink Smart Plug (Energy Monitoring) - SmartPad

eWeLink Wi-Fi Smart Socket 3 Pin Plug South Africa Outlet Adapter with Energy Monitoring.Integrates with the eWeLink app. Dimensions - 56mm X 56mm X 40mm.

store.smartpad.co.za

I’ve managed to get them into eWeLink and setup from what I can see. However the power monitoring doesn’t seem to be very active. Am I just being impatient (not sure how often it should refresh or give info)

Anyone able to offer some advice or guidance?View attachment 1833266
View attachment 1833267
View attachment 1833268

Not the right place for this question, I’m afraid. There’s 36 pages of people who wanted nothing to do with Ewelink in this thread. Maybe start your own thread with your question?