-
Notifications
You must be signed in to change notification settings - Fork 697
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] ZLinky_TIC - add more sensors #2583
Comments
This likely needs to be implemented as a sensor in ZHA / HA Core.
This can be generated (although the currently uploaded quirk-generator on a branch is outdated) or manually written. Your device already has a quirk though: A generated "stub" quirk for your device would basically look like this: (doesn't do anything -- just applies the quirk). Possible STUB quirk for your device"""Quirk for LiXee ZLinky_TIC."""
from zigpy.profiles import zha, zgp
from zigpy.quirks import CustomDevice
from zigpy.zcl.clusters.general import (
Basic,
GreenPowerProxy,
Identify,
Ota,
PowerConfiguration,
)
from zigpy.zcl.clusters.homeautomation import (
ElectricalMeasurement,
MeterIdentification,
)
from zigpy.zcl.clusters.smartenergy import (
Metering,
)
from zhaquirks.const import (
DEVICE_TYPE,
ENDPOINTS,
INPUT_CLUSTERS,
MODELS_INFO,
OUTPUT_CLUSTERS,
PROFILE_ID,
)
class LixeeZlinkyTic(CustomDevice):
"""Lixee ZLinky_TIC custom device implementation."""
signature = {
MODELS_INFO: [("LiXee", "ZLinky_TIC")],
ENDPOINTS: {
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.METER_INTERFACE,
INPUT_CLUSTERS: [
Basic.cluster_id,
PowerConfiguration.cluster_id,
Identify.cluster_id,
Metering.cluster_id,
MeterIdentification.cluster_id,
ElectricalMeasurement.cluster_id,
0xff66,
],
OUTPUT_CLUSTERS: [
Ota.cluster_id,
],
},
242: {
PROFILE_ID: zgp.PROFILE_ID,
DEVICE_TYPE: zgp.DeviceType.PROXY_BASIC,
INPUT_CLUSTERS: [
GreenPowerProxy.cluster_id,
],
OUTPUT_CLUSTERS: [
GreenPowerProxy.cluster_id,
],
},
},
}
replacement = {
ENDPOINTS: {
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.METER_INTERFACE,
INPUT_CLUSTERS: [
Basic.cluster_id,
PowerConfiguration.cluster_id,
Identify.cluster_id,
Metering.cluster_id,
MeterIdentification.cluster_id,
ElectricalMeasurement.cluster_id,
0xff66,
],
OUTPUT_CLUSTERS: [
Ota.cluster_id,
],
},
242: {
PROFILE_ID: zgp.PROFILE_ID,
DEVICE_TYPE: zgp.DeviceType.PROXY_BASIC,
INPUT_CLUSTERS: [
GreenPowerProxy.cluster_id,
],
OUTPUT_CLUSTERS: [
GreenPowerProxy.cluster_id,
],
},
},
} |
FYI, there is a upstream request to the Zlinky TIC product manufacturer/developer (LiXee) here -> fairecasoimeme/Zlinky_TIC#18 @fairecasoimeme Zlinky TIC owners requesting better integration in Home Assistant's built-in ZHA integration component code: https://github.com/home-assistant/core/tree/dev/homeassistant/components/zha |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions. |
Not resolved, still a thing for those who want to use that device. |
I have the same request to add the following attribute as an entity:
It's really important for those who subscribed to a TEMPO contract |
For reference follow these two related discussions and work-in-progress to create a new "Quirk V2" (next-generation quirk) for it: PS: Again, there is still also an ongoing ZHA support feature request to upstream (Zlinky TIC product firmware developer) here: |
Problem description
Current device support doesn't show the entire list of attributes of the device in the sensor.
As per example in my case I need to get the electricity metering for three phases, not just phase 1.
When I try manually, the device gets the values, see screenshot example below:
Solution description
I would need to get the information related to phase b & c as sensors so I can use them for graphs.
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]
Device signature
Device signature
Diagnostic information
Diagnostic information
[Paste the diagnostic information here]
Logs
Logs
Custom quirk
Custom quirk
Additional information
Side question, how can we build custom quirk from existing device signature? I can have a look at that if needed.
Thanks!
The text was updated successfully, but these errors were encountered: