home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.11k stars 29.79k forks source link

Tuya Smart PJ-1203 Energy Monitor lost entities when upgrade 2024.7.1 to 2024.7.4 #122960

Closed prairietrees closed 2 weeks ago

prairietrees commented 1 month ago

The problem

Upgraded HA Core from 2024.7.1 to 2024.7.4 yesterday. After upgrade I lost all entities - Amps, Volts, etc on my PJ-1203 energy monitor. I though I had a bad piece of hardware, so swapped out 3 other devices, all new, with same result. I then reverted back to 2024.7.1 and everything works fine, all entities are back to normal. When I say I lost the entities, I mean they were literally gone, not listed at all.

What version of Home Assistant Core has the issue?

2024.7.4

What was the last working version of Home Assistant Core?

2024.7.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tuya PJ-1203 energy monitor

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

## System Information

version | core-2024.7.1
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.12.4
os_name | Linux
os_version | 6.6.31-haos-raspi
arch | aarch64
timezone | America/Chicago
config_dir | /config

<details><summary>Home Assistant Community Store</summary>

GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 5000
Installed Version | 1.34.0
Stage | running
Available Repositories | 1390
Downloaded Repositories | 2
HACS Data | ok

</details>

<details><summary>Home Assistant Cloud</summary>

logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok

</details>

<details><summary>Home Assistant Supervisor</summary>

host_os | Home Assistant OS 12.4
-- | --
update_channel | stable
supervisor_version | supervisor-2024.06.2
agent_version | 1.6.0
docker_version | 26.1.4
disk_total | 57.8 GB
disk_used | 6.0 GB
healthy | true
supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization | 
board | rpi4-64
supervisor_api | ok
version_api | ok
installed_addons | Studio Code Server (5.15.0), Samba share (12.3.2), Terminal & SSH (9.14.0)

</details>

<details><summary>Dashboards</summary>

dashboards | 2
-- | --
resources | 1
views | 3
mode | storage

</details>

<details><summary>Recorder</summary>

oldest_recorder_run | July 31, 2024 at 3:12 AM
-- | --
current_recorder_run | July 31, 2024 at 10:01 AM
estimated_db_size | 87.26 MiB
database_engine | sqlite
database_version | 3.45.3

</details>

Additional information

Log: 2024-07-31 10:01:14.794 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-07-31 10:01:27.557 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call await hass.http.async_register_static_paths([StaticPathConfig("/hacsfiles/frontend", "/config/custom_components/hacs/hacs_frontend_experimental", False)]); This function will be removed in 2025.7 at custom_components/hacs/frontend.py, line 49: hass.http.register_static_path(, please create a bug report at https://github.com/hacs/integration/issues 2024-07-31 10:01:27.567 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call await hass.http.async_register_static_paths([StaticPathConfig("/hacsfiles/iconset.js", "/config/custom_components/hacs/iconset.js", True)]); This function will be removed in 2025.7 at custom_components/hacs/frontend.py, line 57: hass.http.register_static_path(, please create a bug report at https://github.com/hacs/integration/issues 2024-07-31 10:01:27.576 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues 2024-07-31 10:01:27.586 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call await hass.http.async_register_static_paths([StaticPathConfig("/hacsfiles", "/config/www/community", True)]); This function will be removed in 2025.7 at custom_components/hacs/base.py, line 1162: self.hass.http.register_static_path(, please create a bug report at https://github.com/hacs/integration/issues 2024-07-31 10:01:28.244 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.greenhousewestfankwh (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using state class 'total_increasing' which is impossible considering device class ('power') it is using; expected None or one of 'measurement'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+utility_meter%22 2024-07-31 10:01:28.250 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.testkwh (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using state class 'total_increasing' which is impossible considering device class ('power') it is using; expected None or one of 'measurement'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+utility_meter%22 2024-07-31 10:01:31.303 WARNING (ImportExecutor_0) [zhaquirks] Loaded custom quirks. Please contribute them to https://github.com/zigpy/zha-device-handlers 2024-07-31 10:01:42.071 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 642: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues 2024-07-31 10:04:29.682 WARNING (Thread-7) [pychromecast.socket_client] [Kitchen TV(192.168.12.135):8009] Heartbeat timeout, resetting connection 2024-07-31 10:11:55.523 DEBUG (MainThread) [bellows.zigbee.application] Sending packet ZigbeePacket(timestamp=datetime.datetime(2024, 7, 31, 15, 11, 55, 523254, tzinfo=datetime.timezone.utc), src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0000), src_ep=0, dst=AddrModeAddress(addr_mode=<AddrMode.Broadcast: 15>, address=<BroadcastAddress.ALL_ROUTERS_AND_COORDINATOR: 65532>), dst_ep=0, source_route=None, extended_timeout=False, tsn=169, profile_id=0, cluster_id=<ZDOCmd.Mgmt_Permit_Joining_req: 0x0036>, data=Serialized[b'\xa9\xfe\x00'], tx_options=<TransmitOptions.NONE: 0>, radius=0, non_member_radius=0, lqi=None, rssi=None) 2024-07-31 10:11:55.526 DEBUG (MainThread) [bellows.ezsp.protocol] Sending command sendBroadcast: (0xFFFC, EmberApsFrame(profileId=0, clusterId=54, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_RETRY|APS_OPTION_ENABLE_ROUTE_DISCOVERY: 320>, groupId=0, sequence=169), 0, 170, b'\xa9\xfe\x00') 2024-07-31 10:11:55.533 DEBUG (bellows.thread_0) [bellows.ash] Sending frame DataFrame(frm_num=3, re_tx=False, ack_num=4, ezsp_frame=b'\x8a\x00\x016\x00\xfc\xff\x00\x006\x00\x00\x00@\x01\x00\x00\xa9\x00\xaa\x03\xa9\xfe\x00') + FLAG 2024-07-31 10:11:55.533 DEBUG (bellows.thread_0) [bellows.ash] Sending data 34c821a9622ae94d59947c25aa55d2489c4e8eab47cdce75fd700f7e 2024-07-31 10:11:55.535 DEBUG (MainThread) [bellows.ezsp.protocol] Sending command addTransientLinkKey: (ff:ff:ff:ff:ff:ff:ff:ff, 5a:69:67:42:65:65:41:6c:6c:69:61:6e:63:65:30:39) 2024-07-31 10:11:55.539 DEBUG (bellows.thread_0) [bellows.ash] Semaphore is locked, waiting 2024-07-31 10:11:55.547 DEBUG (bellows.thread_0) [bellows.ash] Received data 44c8a1a9622a156acf7c7e 2024-07-31 10:11:55.548 DEBUG (bellows.thread_0) [bellows.ash] Received frame DataFrame(frm_num=4, re_tx=0, ack_num=4, ezsp_frame=b'\x8a\x80\x016\x00\x00\xd8') 2024-07-31 10:11:55.551 DEBUG (bellows.thread_0) [bellows.ash] Sending frame AckFrame(res=0, ncp_ready=0, ack_num=5) + FLAG 2024-07-31 10:11:55.551 DEBUG (bellows.thread_0) [bellows.ash] Sending data 8520dd7e 2024-07-31 10:11:55.557 DEBUG (bellows.thread_0) [bellows.ash] Received data 54c8b5a94d2a89cbf57e64c8b1a97d312a10b259a24a25aa5593499c96d8abedce9874fe6f9d89c0ee7e 2024-07-31 10:11:55.557 DEBUG (bellows.thread_0) [bellows.ash] Received frame DataFrame(frm_num=5, re_tx=0, ack_num=4, ezsp_frame=b'\x8a\x94\x01\x19\x00\x9c') 2024-07-31 10:11:55.557 DEBUG (bellows.thread_0) [bellows.ash] Sending frame AckFrame(res=0, ncp_ready=0, ack_num=6) + FLAG 2024-07-31 10:11:55.558 DEBUG (bellows.thread_0) [bellows.ash] Sending data 8610be7e 2024-07-31 10:11:55.558 DEBUG (bellows.thread_0) [bellows.ash] Received frame DataFrame(frm_num=6, re_tx=0, ack_num=4, ezsp_frame=b'\x8a\x90\x01E\x00\x05\x00\x006\x00\x00\x00\x00\x01\x00\x00\xd8\xff\x00\x00\x00\xff\xff\x03\xa9\xfe\x00') 2024-07-31 10:11:55.558 DEBUG (bellows.thread_0) [bellows.ash] Sending frame AckFrame(res=0, ncp_ready=0, ack_num=7) + FLAG 2024-07-31 10:11:55.559 DEBUG (bellows.thread_0) [bellows.ash] Sending data 87009f7e 2024-07-31 10:11:55.586 DEBUG (bellows.thread_0) [bellows.ash] Sending frame DataFrame(frm_num=4, re_tx=False, ack_num=7, ezsp_frame=b'\x8b\x00\x01\xaf\x00\xff\xff\xff\xff\xff\xff\xff\xffZigBeeAlliance09') + FLAG 2024-07-31 10:11:55.587 DEBUG (bellows.thread_0) [bellows.ash] Sending data 47c921a9fb2aea4da66bb5da55aac820fb0c42ceaca20be29ca800eccc47ec627e 2024-07-31 10:11:55.590 DEBUG (MainThread) [bellows.ezsp.protocol] Received command sendBroadcast: [<EmberStatus.SUCCESS: 0>, 216] 2024-07-31 10:11:55.591 DEBUG (MainThread) [bellows.ezsp.protocol] Received command stackStatusHandler: [<EmberStatus.NETWORK_OPENED: 156>] 2024-07-31 10:11:55.591 DEBUG (MainThread) [bellows.zigbee.application] Received stackStatusHandler frame with [<EmberStatus.NETWORK_OPENED: 156>] 2024-07-31 10:11:55.591 DEBUG (MainThread) [bellows.ezsp.protocol] Received command incomingMessageHandler: [<EmberIncomingMessageType.INCOMING_BROADCAST_LOOPBACK: 5>, EmberApsFrame(profileId=0, clusterId=54, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=0, sequence=216), 255, 0, 0x0000, 255, 255, b'\xa9\xfe\x00'] 2024-07-31 10:11:55.592 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_BROADCAST_LOOPBACK: 5>, EmberApsFrame(profileId=0, clusterId=54, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=0, sequence=216), 255, 0, 0x0000, 255, 255, b'\xa9\xfe\x00'] 2024-07-31 10:11:55.592 DEBUG (MainThread) [bellows.zigbee.application] Ignoring message type: <EmberIncomingMessageType.INCOMING_BROADCAST_LOOPBACK: 5> 2024-07-31 10:11:55.597 DEBUG (bellows.thread_0) [bellows.ash] Received data 75c9a1a9fb2a15dbf47e 2024-07-31 10:11:55.597 DEBUG (bellows.thread_0) [bellows.ash] Received frame DataFrame(frm_num=7, re_tx=0, ack_num=5, ezsp_frame=b'\x8b\x80\x01\xaf\x00\x00') 2024-07-31 10:11:55.598 DEBUG (bellows.thread_0) [bellows.ash] Sending frame AckFrame(res=0, ncp_ready=0, ack_num=0) + FLAG 2024-07-31 10:11:55.598 DEBUG (bellows.thread_0) [bellows.ash] Sending data 8070787e 2024-07-31 10:11:55.615 DEBUG (MainThread) [bellows.ezsp.protocol] Received command addTransientLinkKey: [<EmberStatus.SUCCESS: 0>] 2024-07-31 10:11:55.625 DEBUG (MainThread) [bellows.ezsp.protocol] Sending command permitJoining: (254,) 2024-07-31 10:11:55.640 DEBUG (bellows.thread_0) [bellows.ash] Sending frame DataFrame(frm_num=5, re_tx=False, ack_num=0, ezsp_frame=b'\x8c\x00\x01"\x00\xfe') + FLAG 2024-07-31 10:11:55.640 DEBUG (bellows.thread_0) [bellows.ash] Sending data 50ce21a9762aeb51ee7e 2024-07-31 10:11:55.660 DEBUG (bellows.thread_0) [bellows.ash] Received data 06cea1a9762a15365d7e 2024-07-31 10:11:55.661 DEBUG (bellows.thread_0) [bellows.ash] Received frame DataFrame(frm_num=0, re_tx=0, ack_num=6, ezsp_frame=b'\x8c\x80\x01"\x00\x00') 2024-07-31 10:11:55.661 DEBUG (bellows.thread_0) [bellows.ash] Sending frame AckFrame(res=0, ncp_ready=0, ack_num=1) + FLAG 2024-07-31 10:11:55.661 DEBUG (bellows.thread_0) [bellows.ash] Sending data 8160597e 2024-07-31 10:11:55.695 DEBUG (MainThread) [bellows.ezsp.protocol] Sending command setPolicy: (<EzspPolicyId.TRUST_CENTER_POLICY: 0>, <EzspDecisionBitmask.ALLOW_JOINS|ALLOW_UNSECURED_REJOINS: 3>) 2024-07-31 10:11:55.702 DEBUG (MainThread) [bellows.ezsp.protocol] Received command permitJoining: [<EmberStatus.SUCCESS: 0>] 2024-07-31 10:11:55.721 DEBUG (bellows.thread_0) [bellows.ash] Sending frame DataFrame(frm_num=6, re_tx=False, ack_num=1, ezsp_frame=b'\x8d\x00\x01U\x00\x00\x03\x00') + FLAG 2024-07-31 10:11:55.721 DEBUG (bellows.thread_0) [bellows.ash] Sending data 61cf21a9012a15b1591d7d5d7e 2024-07-31 10:25:05.348 WARNING (Thread-7) [pychromecast.socket_client] [Kitchen TV(192.168.12.135):8009] Heartbeat timeout, resetting connection

mib1185 commented 1 month ago

Hi @prairietrees

With which integration exactly do you add these tuya device? if possible please download and provide the diagnostics data for this integration.

thx 👍

prairietrees commented 1 month ago

On Wed, Jul 31, 2024 at 11:02 AM Michael @.***> wrote:

Hi @prairietrees https://github.com/prairietrees

With which integration exactly do you add these tuya device? if possible please download and provide the diagnostics https://www.home-assistant.io/integrations/diagnostics data for this integration.

thx 👍

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/122960#issuecomment-2260864790, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM66DJTLRFBBU5C6Y6ZOLETZPEDCLAVCNFSM6AAAAABLYXJ7PSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQHA3DINZZGA . You are receiving this because you were mentioned.Message ID: @.***>

{ "home_assistant": { "installation_type": "Home Assistant OS", "version": "2024.7.1", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.12.4", "docker": true, "arch": "aarch64", "timezone": "America/Chicago", "os_name": "Linux", "os_version": "6.6.31-haos-raspi", "supervisor": "2024.06.2", "host_os": "Home Assistant OS 12.4", "docker_version": "26.1.4", "chassis": "embedded", "run_as_root": true }, "custom_components": { "hacs": { "documentation": "https://hacs.xyz/docs/configuration/start", "version": "1.34.0", "requirements": [ "aiogithubapi>=22.10.1" ] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "after_dependencies": [ "onboarding", "usb" ], "codeowners": [ "dmulcahey", "adminiuga", "puddly", "TheJulianJES" ], "config_flow": true, "dependencies": [ "file_upload" ], "documentation": "https://www.home-assistant.io/integrations/zha", "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp", "universal_silabs_flasher" ], "requirements": [ "bellows==0.39.1", "pyserial==3.5", "zha-quirks==0.0.117", "zigpy-deconz==0.23.2", "zigpy==0.64.1", "zigpy-xbee==0.20.1", "zigpy-zigate==0.12.1", "zigpy-znp==0.12.2", "universal-silabs-flasher==0.0.20", "pyserial-asyncio-fast==0.11" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "2652", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "10C4", "pid": "EA60", "description": "slzb-07", "known_devices": [ "smlight slzb-07" ] }, { "vid": "1A86", "pid": "55D4", "description": "sonoffplus", "known_devices": [ "sonoff zigbee dongle plus v2" ] }, { "vid": "10C4", "pid": "EA60", "description": "sonoffplus", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "tubeszb", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "tubeszb", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "zigstar", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "conbee", "known_devices": [ "Conbee II" ] }, { "vid": "0403", "pid": "6015", "description": "conbee", "known_devices": [ "Conbee III" ] }, { "vid": "10C4", "pid": "8A2A", "description": "zigbee", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "zigate", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "zigate", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "bv 2010/10", "known_devices": [ "Bitron Video AV2010/10" ] } ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "zigate" }, { "type": "_zigstar_gw._tcp.local.", "name": "zigstar" }, { "type": "_uzg-01._tcp.local.", "name": "uzg-01" }, { "type": "_slzb-06._tcp.local.", "name": "slzb-06" }, { "type": "_xzg._tcp.local.", "name": "xzg" }, { "type": "_czc._tcp.local.", "name": "czc" } ], "is_built_in": true }, "setup_times": { "null": { "setup": 0.00016144300025189295 }, "5e80c4a5b1188a09dd7539a788287c2e": { "wait_import_platforms": -0.0005077559981145896, "wait_base_component": -0.001333083004283253, "config_entry_setup": 16.933942993004166 } }, "data": { "ieee": "REDACTED", "nwk": 15783, "manufacturer": "_TZE204_cjbofhxw", "model": "TS0601", "name": "_TZE204_cjbofhxw TS0601", "quirk_applied": true, "quirk_class": "ts0601_din_power.TuyaPowerMeter", "quirk_id": null, "manufacturer_code": 4098, "power_source": "Mains", "lqi": 200, "rssi": -50, "last_seen": "2024-07-31T11:24:54", "available": true, "device_type": "Router", "signature": { "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.FullFunctionDevice|MainsPowered|RxOnWhenIdle|AllocateAddress: 142>, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, allocate_address=True, is_alternate_pan_coordinator=False, is_coordinator=False, is_end_device=False, is_full_function_device=True, is_mains_powered=True, is_receiver_on_when_idle=True, is_router=True, is_security_capable=False)", "endpoints": { "1": { "profile_id": "0x0104", "device_type": "0x0051", "input_clusters": [ "0x0000", "0x0004", "0x0005", "0x0702", "0x0b04", "0xef00" ], "output_clusters": [ "0x000a", "0x0019" ] } }, "manufacturer": "_TZE204_cjbofhxw", "model": "TS0601" }, "active_coordinator": false, "entities": [ { "entity_id": "sensor.ampswestgreenhouse_apparent_power", "name": "_TZE204_cjbofhxw TS0601" }, { "entity_id": "sensor.ampswestgreenhouse_current", "name": "_TZE204_cjbofhxw TS0601" }, { "entity_id": "sensor.ampswestgreenhouse_voltage", "name": "_TZE204_cjbofhxw TS0601" }, { "entity_id": "sensor.ampswestgreenhouse_ac_frequency", "name": "_TZE204_cjbofhxw TS0601" }, { "entity_id": "sensor.ampswestgreenhouse_power_factor", "name": "_TZE204_cjbofhxw TS0601" }, { "entity_id": "sensor.ampswestgreenhouse_power", "name": "_TZE204_cjbofhxw TS0601" }, { "entity_id": "sensor.ampswestgreenhouse_instantaneous_demand", "name": "_TZE204_cjbofhxw TS0601" }, { "entity_id": "sensor.ampswestgreenhouse_summation_delivered", "name": "_TZE204_cjbofhxw TS0601" }, { "entity_id": "update.ampswestgreenhouse_firmware_2", "name": "_TZE204_cjbofhxw TS0601" } ], "neighbors": [], "routes": [], "endpoint_names": [ { "name": "SMART_PLUG" } ], "user_given_name": "AmpsWestGreenhouse", "device_reg_id": "563588dca0bbb7c543d6cce093e2ad44", "area_id": "greenhouse", "cluster_details": { "1": { "device_type": { "name": "SMART_PLUG", "id": 81 }, "profile_id": 260, "in_clusters": { "0x0000": { "endpoint_attribute": "basic", "attributes": { "0x0001": { "attribute_name": "app_version", "value": 70 }, "0x0004": { "attribute_name": "manufacturer", "value": "_TZE204_cjbofhxw" }, "0x0005": { "attribute_name": "model", "value": "TS0601" } }, "unsupported_attributes": {} }, "0x0004": { "endpoint_attribute": "groups", "attributes": {}, "unsupported_attributes": {} }, "0x0005": { "endpoint_attribute": "scenes", "attributes": {}, "unsupported_attributes": {} }, "0xef00": { "endpoint_attribute": "tuya_manufacturer", "attributes": { "0xef00": { "attribute_name": "mcu_version", "value": "1.0.0" } }, "unsupported_attributes": {} }, "0x0b04": { "endpoint_attribute": "electrical_measurement", "attributes": { "0x0603": { "attribute_name": "ac_current_divisor", "value": 1000 }, "0x0602": { "attribute_name": "ac_current_multiplier", "value": 1 }, "0x050b": { "attribute_name": "active_power", "value": 681 }, "0x0508": { "attribute_name": "rms_current", "value": 6277 }, "0x0505": { "attribute_name": "rms_voltage", "value": 122 } }, "unsupported_attributes": { "0x0600": { "attribute_name": "ac_voltage_multiplier" }, "0x0601": { "attribute_name": "ac_voltage_divisor" }, "0x0401": { "attribute_name": "ac_frequency_divisor" }, "0x0400": { "attribute_name": "ac_frequency_multiplier" }, "0x0604": { "attribute_name": "ac_power_multiplier" }, "0x0605": { "attribute_name": "ac_power_divisor" }, "0x0000": { "attribute_name": "measurement_type" }, "0x0403": { "attribute_name": "power_divisor" }, "0x0402": { "attribute_name": "power_multiplier" }, "0x0508": { "attribute_name": "rms_current" }, "0x050a": { "attribute_name": "rms_current_max" }, "0x050b": { "attribute_name": "active_power" }, "0x0507": { "attribute_name": "rms_voltage_max" }, "0x050d": { "attribute_name": "active_power_max" }, "0x050f": { "attribute_name": "apparent_power" }, "0x0510": { "attribute_name": "power_factor" }, "0x0300": { "attribute_name": "ac_frequency" }, "0x0302": { "attribute_name": "ac_frequency_max" } } }, "0x0702": { "endpoint_attribute": "smartenergy_metering", "attributes": { "0x0302": { "attribute_name": "divisor", "value": 1000 }, "0x0300": { "attribute_name": "unit_of_measure", "value": 0 } }, "unsupported_attributes": { "0x0400": { "attribute_name": "instantaneous_demand" }, "0x0301": { "attribute_name": "multiplier" }, "0x0000": { "attribute_name": "current_summ_delivered" }, "0x0303": { "attribute_name": "summation_formatting" }, "0x0304": { "attribute_name": "demand_formatting" }, "0x0100": { "attribute_name": "current_tier1_summ_delivered" }, "0x0306": { "attribute_name": "metering_device_type" }, "0x0102": { "attribute_name": "current_tier2_summ_delivered" }, "0x0104": { "attribute_name": "current_tier3_summ_delivered" }, "0x0106": { "attribute_name": "current_tier4_summ_delivered" }, "0x0108": { "attribute_name": "current_tier5_summ_delivered" }, "0x010a": { "attribute_name": "current_tier6_summ_delivered" }, "0x0001": { "attribute_name": "current_summ_received" }, "0x0200": { "attribute_name": "status" } } } }, "out_clusters": { "0x000a": { "endpoint_attribute": "time", "attributes": {}, "unsupported_attributes": {} }, "0x0019": { "endpoint_attribute": "ota", "attributes": {}, "unsupported_attributes": { "0x0002": { "attribute_name": "current_file_version" } } } } } } } }

home-assistant[bot] commented 1 month ago

Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `zha` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zha` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


zha documentation zha source (message by IssueLinks)

mib1185 commented 1 month ago

please attache the diagnostics data as file, thx :+1:

further, it seems you're using custom quirks?

2024-07-31 10:01:31.303 WARNING (ImportExecutor_0) [zhaquirks] Loaded custom quirks. Please contribute them to https://github.com/zigpy/zha-device-handlers
prairietrees commented 1 month ago

please attache the diagnostics data as file, thx 👍

further, it seems you're using custom quirks?

2024-07-31 10:01:31.303 WARNING (ImportExecutor_0) [zhaquirks] Loaded custom quirks. Please contribute them to https://github.com/zigpy/zha-device-handlers

Yes, I am using custom quirks. This website links how I did it - https://smarthomescene.com/reviews/tuya-zigbee-single-clamp-energy-meter-review/

I'll also add the ts0601_din_power.py file as a .txt file. You'll need to change to .py to run. ts0601_din_power.txt

prairietrees commented 1 month ago

Here's the diagnostic data as a file zha-5e80c4a5b1188a09dd7539a788287c2e-_TZE204_cjbofhxw TS0601-563588dca0bbb7c543d6cce093e2ad44.txt

puddly commented 1 month ago

If you're using a custom quirk and the quirk does not work, this isn't a problem with Home Assistant. Only quirks part of the ZHA quirks library (https://github.com/zigpy/zha-device-handlers/) are officially supported. If you locally install your own quirks, it's up to you to figure out why they aren't working, unfortunately.

See if you can help get a quirk tested and merged: https://github.com/zigpy/zha-device-handlers/pull/2961

prairietrees commented 1 month ago

Got it. I did not know this; thanks for letting me know. Two questions:

  1. I found there is a Tuya folder in the
  2. If there is no such official quirk, how important is it for me to upgrade the Core?

On Wed, Jul 31, 2024 at 12:17 PM puddly @.***> wrote:

If you're using a custom quirk and the quirk does not work, this isn't a problem with Home Assistant. Only quirks part of the ZHA quirks library ( https://github.com/zigpy/zha-device-handlers/) are officially supported. If you locally install your own quirks, it's up to you to figure out why they aren't working, unfortunately.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/122960#issuecomment-2260994871, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM66DJV2NRYYLDYNHN2ZI2LZPELZJAVCNFSM6AAAAABLYXJ7PSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQHE4TIOBXGE . You are receiving this because you were mentioned.Message ID: @.***>

puddly commented 1 month ago

how can I tell if there's a quirk in there that works with my device?

You can remove your custom quirk and see if another one is applied from zhaquirks. It's sort of hard to do by hand because quirks can match based on many criteria and it's not straightforward in some cases. A good way with Tuya devices is to search for variant identifier (the random-looking string that is the device manufacturer).

If there is no such official quirk, how important is it for me to upgrade the Core?

Custom quirks are code someone else wrote. There is no way to update the quirk or fix it if something breaks unless you do it yourself. The primary purpose of custom quirks is to allow people to test out quirks in development and provide feedback, they're not supposed to be used for just "using" a device.

prairietrees commented 1 month ago

You may have misunderstood my last question. If there is no such official quirk, how important is it for me to upgrade the HA Core? Meaning, how important is it for me to upgrade to the 2024.7.4 HA Core? I have successfully upgraded to 2024.7.3, so it's just 2024.7.4 causing the issue. So I'm wondering if I can put off updating to 2024.7.4 and hope an official quirk is created - which may happen once everyone realizes ts0601_din_power.py, custom quirk, is no longer bridging the issue. As a side note, I use this to monitor current (amp) usage in a greenhouse. Looking at the HA compatible device database, there are no alternatives, so I'd guess there'd be interest in have at least one working device. Thanks for all your help today - at least I know what I'm up against...:)

On Wed, Jul 31, 2024 at 2:43 PM puddly @.***> wrote:

how can I tell if there's a quirk in there that works with my device?

You can remove your custom quirk and see if another one is applied from zhaquirks. It's sort of hard to do by hand because quirks can match based on many criteria and it's not straightforward in some cases. A good way with Tuya devices is to search for variant identifier (the random-looking string that is the device manufacturer).

If there is no such official quirk, how important is it for me to upgrade the Core?

Custom quirks are code someone else wrote. There is no way to update the quirk or fix it if something breaks. The primary purpose of custom quirks is to allow people to test out quirks in development and provide feedback, they're not supposed to be used for just "using" a device.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/122960#issuecomment-2261311620, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM66DJVR5KHEMYPD6TJIGRLZPE477AVCNFSM6AAAAABLYXJ7PSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRRGMYTCNRSGA . You are receiving this because you were mentioned.Message ID: @.***>

issue-triage-workflows[bot] commented 3 weeks ago

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 Home Assistant 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.