-
Notifications
You must be signed in to change notification settings - Fork 712
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
[Device Support Request] for TZ3000_xkap8wtb TS000F #2447
Comments
Update: I managed to make a custom quirk myself. The first time, so not sure it is according to all the rules:
This gist contains the latest version of my custom quirk: https://gist.github.com/erkr/5d4addf1b4c8e18d68d2adb154c6be93 Maybe one of the active contributors ( @TheJulianJES @dmulcahey ) can have a look to decide if my quirk can be adopted into the official tuya list?! For me, it works.
Best Eric |
Yep, quirk looks mostly good to me. Power factor entity shouldn't be created, as it's not supported, but it's a minor issue in ZHA for all power monitoring devices at the moment (and nothing that can/should be fixed in a quirk).
That seems to be attribute |
Thanks for reviewing my first custom quirk. Good feedback 🙏 The option to change the device type in configuration.yaml is new to me. Will use that to remove my custom quirk without breaking my statistics 😊 I will try to add TuyaZBExternalSwitchTypeCluster and report back if that works later this week👌 Best Eric |
@TheJulianJES PS: Will my device also be part of 2023.10.x? (as it is not a TS0011 plug)?! |
@erkr hola, and thank you for supporting the community and your ZHA contributions! I tried your custom quirk (...because I'm "lucky" to have same TZ3000_xkap8wtb as a pilot for in-line power meters I want to install for few circuits) but it either didn't pick up or mine didn't work. I still see ridiculous number of A in current and RMS is out of whack. Likely I didn't do something simple. Anyways, do you plan doing a Pull Request to Once again, huge thanks for your support! Looking forward to see your quirk working in main branch! |
@arsenyspb |
@erkr @TheJulianJES OK I think I've got it working, finally see sane numbers... As a reminder one needs to also delete wrong metrics' history (see here):
now
This outputs the mad readings for power and Amps. Next, clean them up:
Profit. |
@arsenyspb Great, thanks for organising a delivery. I think when the review remarks are processed it's ready to rock and roll 🤓
|
Nice it works for you as well😊 |
@arsenyspb It reached the 2023.10.4 release. Removed my custom version and it works great with the released one. Thx. |
Fix zigpy#2447 --------- Co-authored-by: TheJulianJES <[email protected]>
Fix zigpy#2447 --------- Co-authored-by: TheJulianJES <[email protected]>
I'm a bit confused, because from what I understand this fix made it into the 2023.10.4 release. However, I'm on 2024.8.0 and I have the same exact same symptoms with the Ts000f, namely current off by 1000 and energy used off by 100. Has this regressed or is there something I need to do to activate the fix? |
@klibro zhaquirks.tuya.ts000f_switch.Tuya_1G_Wall_Switch_Metering No regression seen |
Yes, I realise that the quirk is part of the distribution and should be being picked up. The reported model is definitely TS000F, and that should be enough to trigger the quirk, shouldn't it? Other quirks for other ZHA devices I have are being picked up. I'm also successfully applying a custom quirk. I have tried copying the distribution quirk and putting it into my custom quirk directory, but still this is not being picked up after a restart. I have just installed two TS000F devices, so although I can believe one might have glitched, for two not to work seems like it is a deeper issue. Is there some way to troubleshoot why quirks don't get applied? |
I figured this out. The quirk in the release specifies a signature with endpoints 1 and 242, but upon inspecting my device, I found that it was only reporting a signature with the "1" endpoint. So the signature wasn't matching and hence the quirk wasn't being applied. |
Problem description
I have a zigbee 3.0 wall switch with power monitoring. Switching and power readout work fine.
The current readout is a factor 1000 to high though. Not sure if the usage readout is correct. Will report on that later.
Solution description
I guess a quirk can translate the reading to the right value. I hope someone can help to create a custom quirk I can use to test/modify till it is correct.
Screenshots/Video
Screenshots/Video
This is the switch readout with a 40 watt bulb:
![image](https://private-user-images.githubusercontent.com/4363599/249792965-1e891c67-1f30-4974-81b7-5f7f5f43d5d0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzQ0MjAxODksIm5iZiI6MTczNDQxOTg4OSwicGF0aCI6Ii80MzYzNTk5LzI0OTc5Mjk2NS0xZTg5MWM2Ny0xZjMwLTQ5NzQtODFiNy01ZjdmNWY0M2Q1ZDAucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MTIxNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDEyMTdUMDcxODA5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NmIwZjg3ZjNlNTc0MDYwZDcxZjhmNTAxMjc2MDdhM2FjYjhkMzM5YTM1NWU4MjE4ZDNkNzg5NGU5ODk4NTc0NiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.0XCrtw8_bjfDTxbNwK21anUyGMLTQyKu8j3ZJpjZi6w)
The current should be around 0.2A
Device signature
Device signature
Diagnostic information
Diagnostic information
Logs
Logs
Na
Custom quirk
Custom quirk
Na
Additional information
No response
The text was updated successfully, but these errors were encountered: