i keep the idea for X gang in virtual and physics way. 
@blutch32 : Contact sensors as unknown - need device interview data to add support and more deails about your device please.
Interviews are in this post : [APP][Pro] Universal TUYA Zigbee Device App - test - #1011 by blutch32
If you need something more please let me know 
Installed V5.5.890 where the PR from packetninja is included. Sadly all the bseed (even both 1 gang switch _TZ3000_ysdv91bk TS0001 and _TZ3000_blhvsaqf TS0001 is still installed as zigbee unknown devices.
15869329-ad28-4691-8449-1cf7f8b58331
Hello Dylan.
Thanks for your work. I saw this: “5.5.891”: {
“en”: “
Bseed Switch: Added _TZ3000_ysdv91bk variant (Pieter_Pessers forum). PR #116 closed with thanks to packetninja.”
I installed V5.5.894, but it is still seen as zigbee unknow device.
Ver.894. Water sensor installs, but no alarm. Contact sensors still install in reverse.
I couldn’t care less about a name, so having it unbranded is fine to me.
However, I would suggest (or rather we must) then align it with the type of device. A built-in module is different from an actual switch with integrated zigbee module. Just because of the cluster-id’s, but also from a functionality perspective.
SO i must make some changes beciauses there is also others 1 gang devices witho use tuya instead of zcl or sometimes bith of them, so i must support all of them :).
1gang isn’t the only thing that defines the device. As far as I can determine the current 1gang driver refers to the module that someone would build in.
How about we add the tag “integrated” if it concerns an integrated switch/module like the two PR from me? E.g switch_1gang_integrated and switch_dimmer_1gang_integrated ?
Unfortunately it does not work.
f089e2e7-ef9f-465e-8240-7dc3c00d22db
“ids”: { “modelId”: “TS0601”, “manufacturerName”: “_TZE284_o3x45p96” }, “endpoints”: { “ieeeAddress”: “a4:c1:38:5d:15:01:6a:9a”, “networkAddress”: 43702, “modelId”: “TS0601”, “manufacturerName”: “_TZE284_o3x45p96”, “endpointDescriptors”: [ { “status”: “SUCCESS”, “nwkAddrOfInterest”: 43702, “_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 } ] } } } } }
Works perfectly on version 5.5.890, thanks 
Hi Dylan here an update again about behavior Multisensor HOBEIAN ZG-204ZV.
The fluctuating stopped 
Motion and Luminance are working fine now, Temperature and Humidity no data from sensor.
And still false option Distance in app.
Also no Battery options.
Good luck and many thanks Peter.
Hello Dylan.
Sorry to disturb you again. Just wanted to let you know BSEED wallswitches and the water valve control is still not working.
See 2a176cd4-b4d4-4472-b7dc-4facec0873f7
Best regards: Pieter.
Which wallswitch do you have?
version updated , device re paired ?
I have the:
BSEED 1 button wallswitch zigbee with neutral. _TZ3000_ysdv91bk TS0001
BSEED 1 button wallswitch zigbee with neutral. _TZ3000_blhvsaqf TS0001
BSEED 2 button wallswitch zigbee with nuetral _TZ3000_l9brjwau TS0003
BSEED 3 button wallswitch zigbee with neutral _TZ3000_qkixdnon TS0003
Removed and reconnected. V5.5.907
@dlnraja I believe that @Pieter_Pessers ysdv91bk button will work if you add it to my PR. The blhvsaqf is the same as I have, so that should work when the PR is included.
I have a 2 button (2gang) wall switch as well, but didn’t get a chance to install that yet. I will try that this week and make a PR for a new driver for that as well. I don’t have a use-case for a 3 button though, but I expect that would work similar to the 1/2 button though.
1 Like
Could you help Dylan if i give you a interview of my BSEED wallswitches?
I just added ysdv91bk to my fork and made a PR. I’m pretty sure that will make both 1 button versions work for you.
If you feel to experiment, feel free to install my fork until Dylan has time to include the PR. The forum somehow doesn’t allow me to link to a git repo, so I sent it to you in a Slack message.
1 Like
Thank you, Atilla.
I hope i found out how to install a fork. Is that with NPM homey?
It is indeed. You can use the homey cli for that.
- clone the repo: git clone
- in the directory do an “npm install”
- Then a homey app install (or run if you want to see logs)
