Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blitzwolf BW-SHP13 #2988

Closed
1 of 7 tasks
SkyThes opened this issue Jun 27, 2020 · 46 comments
Closed
1 of 7 tasks

Blitzwolf BW-SHP13 #2988

SkyThes opened this issue Jun 27, 2020 · 46 comments

Comments

@SkyThes
Copy link

SkyThes commented Jun 27, 2020

Device

  • Product name: Blitzwolf BW-SHP13
  • Manufacturer: _TZ3000_3ooaz3ng
  • Model identifier: TS0121
  • Device type:
    • Light
    • Lock
    • Remote
    • Sensor
    • Siren
    • Thermostat
    • Other:

Screenshots

Screenshot1
Screenshot2
Simple metering cluster
Electrical Measurement

If you need more info let me know!

@SwoopX
Copy link
Collaborator

SwoopX commented Jun 27, 2020

Thanks for raising the request. Could you please apply a load to the plug and let it run for some time? Unfortunately, I cannot deduce the measurement units undoubtly.

So I need the last 2 screenshots once again after some time a load has been applied and please take then while the load is still applied.

@SwoopX SwoopX self-assigned this Jun 27, 2020
@SkyThes
Copy link
Author

SkyThes commented Jun 27, 2020

Withload1
Withload2

Just took those screenshots with a load (laptop charger) connected for almost a hour.

@SwoopX
Copy link
Collaborator

SwoopX commented Jun 27, 2020

Thanks. Ok, so for power, we use the raw values as I thought.

However, for instantaneous demand the value of 1 feels just wrong, considering the applied load. If it would be 1kWh, that would be way too high. 1Wh can also not be. Based on that, I assume we need to apply a multiplier.

If it jumps to 2 any time soon, I'd assume the measurement unit is dWh...

@SkyThes
Copy link
Author

SkyThes commented Jun 27, 2020

You mean the Current Summation Delivered (id 0x0000)? This value actually jumped to 2 in the last couple of minutes.
If you want to be sure I will be able to connect a known load (stable current drawing device) tomorrow for a specific amount of time so we can calculate how the values should be interpreted.

@SwoopX
Copy link
Collaborator

SwoopX commented Jun 27, 2020

That would be awesome!

@SwoopX
Copy link
Collaborator

SwoopX commented Jun 27, 2020

Hm, interestingly, seems to be the exact same device as here #2677

@SkyThes
Copy link
Author

SkyThes commented Jun 28, 2020

That would be awesome!

I just connected a 200W load (4x 50W halogen bulbs) for exactly 15min to the plug. This are the values when I turned on the load:
Screenshot1 200w load
Screenshot2 200w load

This are the values after 15min:
Screenshot3 200w load
Screenshot4 200w load

This load is using 0,2kWh so I used 0,05kW in this 15min. The Current Summation Delivered went from 3 to 8 so I think it is safe to say that this value represents 0,01kWh or 10Wh.

@SwoopX
Copy link
Collaborator

SwoopX commented Jun 28, 2020

Cool, thanks for checking out. Already took that assumption with my commit.

@tekgator
Copy link

tekgator commented Jul 4, 2020

Is there anything we can contribute to get it working? The SHP13 connected successfully but only on/off is possible in Home Assistant. Load etc. is not available.

@SwoopX
Copy link
Collaborator

SwoopX commented Jul 9, 2020

Wait for the next release

@J05HI
Copy link

J05HI commented Jul 18, 2020

How to pair it?
Is it a Switch -> Other?

@jvyoralek
Copy link

I added it as light and it works. But only on/off functionality is available for now so waiting for the next release.

@SwoopX
Copy link
Collaborator

SwoopX commented Jul 19, 2020

Closing this as device is now supported with .79 beta.

@SwoopX SwoopX closed this as completed Jul 19, 2020
@jvyoralek
Copy link

I've updated deCONZ version to 2.05.79 and consumption in kWh + power in W are available in HA now what is amazing!

The only minor issue remains - Manufacturer name is still _TZ3000_3ooazng and version contains a crazy value.
image

Thanks for the great work already!

@Webserve
Copy link

@jvyoralek i removed the old entity and now the right info is showed

deconnn

@darkhaek87
Copy link

Hey @SwoopX I have one question: Rest-API support is not provided for this Smart plug, right? Because the smart plug is not listed neither as lights nor as sensors.

How can I help to get it into Rest-API?

My cconfiguration is:
RaspBee: 0x26370500
deCONZ: V2_05_82 (i also tried V2_05_79)

@Mimiix
Copy link
Collaborator

Mimiix commented Sep 18, 2020

@darkhaek87 Hey!

I've got this in use with HA. So it does show with the rest-api in some way.

@darkhaek87
Copy link

@Mimiix I wonder why it works with HA, but reading the Rest-API for example with Firefox REST Client I did not find the smart plug.

FYI: For my automation I use Node Red.

@Mimiix
Copy link
Collaborator

Mimiix commented Sep 18, 2020

@morfei1 could help

@morfei1
Copy link

morfei1 commented Sep 18, 2020

@darkhaek87 If the plug is paired correctly to deCONZ it should be visable in the rest-api. I have 4 of them.

Plug itself is visable in ..../lights
It's 2 senors are visible in .../sensors
in the rest-api

If your NodeRed is paired correctly to deCONZ, the plug will be visable in the deCONZ nodes with it's phoscon name.
Note that the plug sensors are visable with their default names TS....something. You can't change their names nigher in phoscon nor in deCONZ. You can only change them in the rest-api.

If you are able to control your other deCONZ devices in NodeRed your connection is ok, and it seems the plug is not paired or not paired correctly. You can check that in deCONZ. The simple way to resolve this is to reset the plug and hit the search button in phoscon for another try. If you don't see any of you devices in the NodeRed, there is no konection between deCONZ and NR.

@morfei1
Copy link

morfei1 commented Sep 18, 2020

The only minor issue remains - Manufacturer name is still _TZ3000_3ooazng and version contains a crazy value.
image

Thanks for the great work already!

@jvyoralek This is actually the correct name of the plug, IMHO. At first it's always Heiman, but if you read the basic cluster of it's node in deCONZ it will change to TZ3000 something.

@CarJu
Copy link

CarJu commented Oct 17, 2020

Hello!
I use 2.05.83 and I also can only connect to the "Light". There is no sensor in the list.
What am I doing wrong?
Vendor in my case is Heiman,

Thank you!

@SwoopX
Copy link
Collaborator

SwoopX commented Oct 17, 2020

Which list? You wont see anything else in Phoscon. The REST API tells you what is available.

If you have no corresponding sensors in the API, enter sensor search in Phoscon, apply a load to the plug and switch the plug on. That should do the trick.

@bcutter
Copy link

bcutter commented Feb 7, 2021

Can someone confirm this device is working
a) without any issues,
b) giving at least switch, current consumption, total consumption values (perfect would be overpower warning and temperature in addition) and
c) there´s no need to push the button once the connection to deCONZ has been lost.

I´m looking for a stable alternative to the Xiaomi Mi Smart Plug which has too many problems to be used with deCONZ (#4238).

Thanks for any feedback, maybe especially from Home Assistant users.

@morfei1
Copy link

morfei1 commented Feb 7, 2021 via email

@bcutter
Copy link

bcutter commented Feb 7, 2021

Yes, it's OK. I have 5-6 of them. They can do all you want, but they can't monitor the temp.

Thanks. Xiaomi has an internal temperature sensor to detect overtemp (automatic shutdown at 65 °C) next to overpower detection. It´s optional for me, much more important is a stressles pairing with deCONZ and painless integration into Home Assistant. I think I´ll give the BW-SHP13 a try.

@jantielens
Copy link

I'm trying to get the BW-SHP13 working with my Conbee II stick plugged into a Raspberry Pi (default installation). So far I can only control the plug, but it's not reporting power consumption in Home Assistant. There are the steps I did:

Manually updated the firmware to the latest version:
image

Removed the BW-SHP13 light/plug from the device list, and paired it again. So the plug is added as a light:
image

I can now control the plug through the Phoscon App UI and Home Assistant, but I don't see the power consumption showing up anywhere. Can you give some tips where to look? Should I find a sensor in the Phoscon App?

@morfei1
Copy link

morfei1 commented Feb 15, 2021 via email

@jantielens
Copy link

Thanks, where should I look in Home Assistant? My device only shows:
image

@jantielens
Copy link

Ok, strange thing happened: I added another plug (which was never paired before the upgrade), and this one does report power consumption in HA! So I guess I need to figure out how to really delete the first plug. :)

@morfei1
Copy link

morfei1 commented Feb 15, 2021 via email

@userMak
Copy link

userMak commented Feb 25, 2021

Ok, strange thing happened: I added another plug (which was never paired before the upgrade), and this one does report power consumption in HA! So I guess I need to figure out how to really delete the first plug. :)

Hi, did you manage to add the particular plug? If yes can you explain how please? I am trying but I always got only the on off function in HA and not the sensors. Thanks

@morfei1
Copy link

morfei1 commented Feb 25, 2021 via email

@userMak
Copy link

userMak commented Feb 25, 2021

Update to the latest deconz and read the basic descriptor of the plug/s or just hard rest and re-pair them without delete them from phoscon.

On Thu, Feb 25, 2021, 19:49 userMak @.***> wrote: Ok, strange thing happened: I added another plug (which was never paired before the upgrade), and this one does report power consumption in HA! So I guess I need to figure out how to really delete the first plug. :) Hi, did you manage to add the particular plug? If yes can you explain how please? I am trying but I always got only the on off function in HA and not the sensors. Thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2988 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO4LI5HQZF4GPKNMP6N6NZ3TA2ET5ANCNFSM4OKBUABA .

Please (I am new to this) can you explain what do you mean to "read the basic descriptor" or give me a link to read how to hard reset the plug.

@morfei1
Copy link

morfei1 commented Feb 25, 2021 via email

@bcutter
Copy link

bcutter commented Mar 6, 2021

...or just hard rest and re-pair them without delete them from phoscon.

I guess that somehow did the trick for me. Ended up with only switch entity after first pairing, missing current and total consumption entities. Tried everything (reading basic cluster attributes, reading simple descriptors, deleting and re-pairing), wild guess: in the end resetting the device (initializing pairing sequence by holding power button for more than 5 seconds) while having pairing mode/sensor search active in Phoscon some kind of "re-joined" the plug to the ConBee/ZigBee mesh. In Home Assistant both missing entities were immediately available.

I´ll test this with another plug of the same model, hope to finally see some plug and play (getting all entities in the first place).

@SAOPP
Copy link

SAOPP commented Mar 8, 2021

Guys, I plan to order a similar outlet, as far as I see there is no support of power outage memory?

@Mimiix
Copy link
Collaborator

Mimiix commented Mar 9, 2021

@SAOPP I haven't checked that tbh. I'll test later if you want?

@SAOPP
Copy link

SAOPP commented Mar 9, 2021

Yes sure, I'm wondering if the socket is able to adjust the state after a power loss? After power on - turn on or turn off? Like in z2m... Thanks in advance homie!

@SAOPP
Copy link

SAOPP commented Mar 9, 2021

And also... power and consumption is present via deconz?

@SAOPP
Copy link

SAOPP commented Mar 9, 2021

For now, I have full confirmation when working through z2m:

image

@morfei1
Copy link

morfei1 commented Mar 9, 2021 via email

@SAOPP
Copy link

SAOPP commented Mar 9, 2021

This is of course good, this is similar behavior to the heiman sockets, but at the same time it is not quite what is needed, since there are sockets that must be turned off by default, even if they were turned on, this is a very big drawback of working with sockets on the deconz side.

@SAOPP
Copy link

SAOPP commented Mar 9, 2021

Actually, this is why I keep my sockets on the z2m.

@morfei1
Copy link

morfei1 commented Mar 9, 2021 via email

@cobch
Copy link
Contributor

cobch commented Sep 30, 2022

This is of course good, this is similar behavior to the heiman sockets, but at the same time it is not quite what is needed, since there are sockets that must be turned off by default, even if they were turned on, this is a very big drawback of working with sockets on the deconz side.

Do you know if the following as memory state on z2m?

  • Aqara single module T1 (no neutral)
  • Aqara smart plug

I am struggling on Deconz with that and that is really enjoying.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests