Hi, could you fix the gas sensor _TZE204_chbyv06. Now it detects but doesn’t work correctly..
Unfortunately no success yet.
During generic installation this error message occurs:
If I install the Tuya DP thermostat I can set the TARGET temp without an error message, but the temp is not transferred to the device.
However, no actual temperature is displayed. If other settings are made:
31078a93-7341-45a3-b925-baaa70116251"ids": { "modelId": "TS0601", "manufacturerName": "_TZE284_o3x45p96" }, "endpoints": { "ieeeAddress": "a4:c1:38:5d:15:01:6a:9a", "networkAddress": 52110, "modelId": "TS0601", "manufacturerName": "_TZE284_o3x45p96", "endpointDescriptors": [ { "status": "SUCCESS", "nwkAddrOfInterest": 52110, "_reserved": 22, "endpointId": 1, "applicationProfileId": 260, "applicationDeviceId": 81, "applicationDeviceVersion": 0, "_reserved1": 1, "inputClusters": [ 4, 5, 61184, 0, 60672 ], "outputClusters": [ 25, 10 ] } ], "deviceType": "enddevice", "receiveWhenIdle": false, "capabilities": { "alternatePANCoordinator": false, "deviceType": false, "powerSourceMains": false, "receiveWhenIdle": false, "security": false, "allocateAddress": true }, "extendedEndpointDescriptors": { "1": { "clusters": { "groups": { "attributes": [ { "acl": [ "readable", "reportable" ], "id": 0, "name": "nameSupport", "value": { "type": "Buffer", "data": [ 0 ] }, "reportingConfiguration": { "status": "NOT_FOUND", "direction": "reported" } }, { "acl": [ "readable", "reportable" ], "id": 65533, "name": "clusterRevision", "value": 2, "reportingConfiguration": { "status": "NOT_FOUND", "direction": "reported" } } ] }, "scenes": { "attributes": [ { "acl": [ "readable", "reportable" ], "id": 0, "reportingConfiguration": { "status": "NOT_FOUND", "direction": "reported" } }, { "acl": [ "readable", "reportable" ], "id": 1, "reportingConfiguration": { "status": "NOT_FOUND", "direction": "reported" } }, { "acl": [ "readable", "reportable" ], "id": 2, "reportingConfiguration": { "status": "NOT_FOUND", "direction": "reported" } }, { "acl": [ "readable", "reportable" ], "id": 3, "reportingConfiguration": { "status": "NOT_FOUND", "direction": "reported" } }, { "acl": [ "readable", "reportable" ], "id": 4, "reportingConfiguration": { "status": "NOT_FOUND", "direction": "reported" } }, { "acl": [ "readable", "reportable" ], "id": 65533, "name": "clusterRevision", "value": 2, "reportingConfiguration": { "status": "NOT_FOUND", "direction": "reported" } } ] }, "basic": { "attributes": [ { "acl": [ "readable", "reportable" ], "id": 0, "name": "zclVersion", "value": 3 }, { "acl": [ "readable", "reportable" ], "id": 1, "name": "appVersion", "value": 80 }, { "acl": [ "readable", "reportable" ], "id": 2, "name": "stackVersion", "value": 0 }, { "acl": [ "readable", "reportable" ], "id": 3, "name": "hwVersion", "value": 1 }, { "acl": [ "readable", "reportable" ], "id": 4, "name": "manufacturerName", "value": "_TZE284_o3x45p96" }, { "acl": [ "readable", "reportable" ], "id": 5, "name": "modelId", "value": "TS0601" }, { "acl": [ "readable", "reportable" ], "id": 6, "name": "dateCode", "value": "" }, { "acl": [ "readable", "reportable" ], "id": 7, "name": "powerSource", "value": "battery" }, { "acl": [ "readable", "writable", "reportable" ], "id": 65502 }, { "acl": [ "readable", "reportable" ], "id": 65533, "name": "clusterRevision", "value": 2 }, { "acl": [ "readable", "reportable" ], "id": 65534, "name": "attributeReportingStatus", "value": "PENDING" }, { "acl": [ "readable", "reportable" ], "id": 65506 }, { "acl": [ "readable", "reportable" ], "id": 65507 }, { "acl": [ "readable", "writable", "reportable" ], "id": 65487 } ] } }, "bindings": { "ota": {}, "time": { "attributes": [ { "acl": [ "readable" ], "id": 65533, "name": "clusterRevision", "value": 1 } ] } } } } }
Hello Dylan.
Sadly all BSEED wall switches still seen as unknown zigbee device on V5.5.932.
ad00e674-dbdc-47cd-bd56-8638fbe3f12c
Best regards: Pieter.
Hi @dlnraja
Thanks for all your work for this app, good to see that this app improves everyday.
For the presence sensor i still have the same issue, connected as unknown device.
Please let me know if you need a new interview or report.
Thanks JJ
Hi @dlnraja
I am still unable to use my Moes 4 button wireless scene switch. _TZ3000_zgyzgdua. No response to flows when pressing physical button or icons. Version 934.
Here is the diagnostic log.
ad2e946e-e40b-477f-912c-7825383619fb
Thanks for the amazing work.
Fred
Yessss. Where getting somewhere. I sideloaded (node.js cli) V5.5.941 and the BSEED wall switches with 1 button are recognized.
Thank you Dylan and ofcourse @Attilla .
Recognized:
BSEED 1 button wall switch zigbee with neutral. _TZ3000_ysdv91bk TS0001
BSEED 1 button wall switch zigbee with neutral. _TZ3000_blhvsaqf TS0001
Seen as “unknown zigbee devices”:
BSEED 2 button wallswitch zigbee with neutral _TZ3000_l9brjwau TS0003
BSEED 3 button wall switch zigbee with neutral _TZ3000_qkixdnon TS0003
1 Like
Hi Dylan you nearly fixed it again 
The readings are all there including the Battery again, the only thing is the Humidity that’s maybe need a multiplayer of 10 because it should be around 90% outside now instead of 9%.
Great job again, so many many thanks for that
Best regards Peter.
No problem, I just needed it myself. We now have light on the toilet. 
@dlnraja I put in one more small PR that I forgot to commit earlier. Then it is really done. 
Btw, you can remove “switch_dimmer_1gang“ completely, because “wall_dimmer_1gang_1way” is a replacement of that.
:bssed and non bssed device might be different , i will check
My apologies, I’m mixing up names now. Another good reason for clear naming
Hi @dlnraja, thanks a lot for all the effort you’re putting into this app, much appreciated!
I tried adding a Tuya Fingerbot after the recent update, but it doesn’t seem to work yet. The device shows up in the list, but I see a red exclamation mark and I’m unable to select or add it.
I needed to do another small PR to fix a small issue and update the assets, which I did.
However, I noticed that when I do a “homey app run”, it fails to run because of the size:
$ homey app run
✓ Pre-processing app...
✓ Validating app...
✓ App validated successfully against level `debug`
✓ Creating Remote Debug Session...
✖ <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Payload Too Large</pre>
</body>
</html>
This wasn’t the case yesterday, so I was wondering if something changed upstream that might cause this.
The MANUFACTURER_IDS_AUDIT.json is 23MB - that’s the problem! Let me remove large unnecessary files and update .homeyignore:
1 Like
I see you removed it, but still seeing the same
Ver.954 Watersensor still inactivated. Contact sensor still in reverse. Thanks.
i have added an seeetign on the app seting ( device setting ) to reverse the contact.
v 972 will be released soon with this fix or upper version
Hi Dylan,
no change with 5.5.960.
can I provide you with more information about that?
Thanks. I do appreciate your hard work.
i don’t know why i’an publish or push to homey server anymore , perhaps homey app server seams bussy.
