Yea, fixed it now, I'll update my git driver and re post
edit, try this
https://raw.githubusercontent.com/Mark-C-uk/Hubitat/master/ZemiSmart%20Zigbee%20Blind
1 Like
Damn just found this post. I originally had this Zemismart bead chain motor but couldn't get it working with the driver I found. I returned it and bought the AM43 (with solar panel) from aliexpress. Unfortunately that one also has issues such as showing "closing" permanently when reaching its upper limit. I'm using the driver by amosyuen for it.
Strange I don't have that issue with my AM43. Try setting the upper limit a couple of notches down. The biggest issue I had was getting the tension right on the chain so it wouldn't slip. Other than that mine has been working flawlessly..
Yeah I detailed it ages ago on the other thread. Limit is fine, it's already set well below the blind top out/physical limit. I can either get it working at full speed in lift mode but the position reporting is all to pot OR I can switch it to tilt mode and the position reporting works fine but it permanently shows "closing" or "opening" incorrectly. I wondered if it's down to the forward/reverse setting. Obviously you can switch that to suit whether the cord is on the right or the left, but mine is a Roman Blind not a roller and I wondered if it's perceivable that it needs to rotate in the opposite direction to lift or lower. Whatever I did it always seemed to be wrong. Anyway it's fine for now as I've just got it raising and lowering fully in a sunset/sunrise rule.
Thanks. Probably should say Iām using the roller blinds, will this driver work for that as well?
I have it running on the tube motor blind
1 Like
Strange.... Mine open and close normally and report normally even in increments. I too have a roman shade for our kitchen
those who have this model - i've had it for a 1 year now and the batteries are not lasting.
has anyone found a better quality alternative by chance? may need to just do it properly with the ikea zigbee blinds.
friends I have a problem, it does not let me change the direction of the buttons from the device, so when the buttons are upside down, has it happened to someone?
I don't get to change the address, I give save preferences and configure and it doesn't do anything, any idea? The problem is that when you press the buttons on the blind, they work backwards...
Well, I'm in a pickle of a mess. I have had these Zemismart roller shade motors operating on Hubitat for about a year now. Over the past 2 months one of them mysteriously just decides to open all on its own. I've removed it and rejoined it to the hub (zigbee) about 10 times. Still the problem persists. I have finally captured in the logs what I believe is the culprit.
[dev:1891] 2022-05-09 08:54:03.488 pm [info] arrived at position :100
[dev:1891] 2022-05-09 08:54:03.487 pm [debug] catchall: 0104 EF00 01 01 0040 00 EC08 01 00 0000 02 01 00010302000400000064
[dev:1891] 2022-05-09 08:54:03.486 pm [debug] dp = 515
[dev:1891] 2022-05-09 08:53:39.330 pm [debug] levelEventMoving - currentLevel: 100 lastLevel: 0
[dev:1891] 2022-05-09 08:53:39.329 pm [trace] remote opening
[dev:1891] 2022-05-09 08:53:39.328 pm [debug] dp = 1031
Can anyone help me understand what the log entry for "Remote Opening" or "DP=1031" means, outside of the obvious. If remote opening is because the "BT remote" opened it, I assure you, that is not the case. Also, this particular shade is installed in a double window case with another one just next to it and that motor never has any problems. In fact, all 9 others I have installed, never fail, just this one.
Please if anyone has deep understanding of the Tuya commands used in the driver and how to prevent this from occurring it would be a tremendous relief.
Thanks..
Also, this is what I received when I used the remote to close the shade. My open/close is reversed in my application, completely normal.
[dev:1891] 2022-05-09 09:28:26.053 pm [info] arrived at position :0
[dev:1891] 2022-05-09 09:28:26.036 pm [debug] catchall: 0104 EF00 01 01 0040 00 EC08 01 00 0000 02 01 00010302000400000000
[dev:1891] 2022-05-09 09:28:26.032 pm [debug] dp = 515
[dev:1891] 2022-05-09 09:28:01.784 pm [debug] Ignore invalid reports
[dev:1891] 2022-05-09 09:28:01.782 pm [debug] levelEventMoving - currentLevel: 100 lastLevel: 100
[dev:1891] 2022-05-09 09:28:01.780 pm [trace] remote opening
[dev:1891] 2022-05-09 09:28:01.778 pm [debug] dp = 1031
It appears as though "remote opening" is triggered by the BT remote. I even took the batteries out of the remote some time ago, aside from the test above, so I can't figure how it would receive a BT remote command.
Looks like this part of the driver decodes the command for Remote:
case 1031: // 0x04 0x07: Confirm opening/closing/stopping (triggered from remote)
def data = descMap.data[6]
if (descMap.data[6] == "01") {
log.trace "remote closing"
levelEventMoving(0)
}
else if (descMap.data[6] == "00") {
log.trace "remote opening"
levelEventMoving(100)
}
else {log.debug "parsed else case $dp open/close/stop remote $data"}
break;
So, what is descMap.data[6] == "01" ? It looks like an array variable at position 6, but what does 01 or 00 mean and how is this derived?
This is strange or I'm misunderstanding the flow:
case 1025: // 0x04 0x01: Confirm opening/closing/stopping (triggered from Zigbee)
def data = descMap.data[6]
if (descMap.data[6] == "00") {
if(logEnable) log.debug "parsed opening"
levelEventMoving(100)
case 1031: // 0x04 0x07: Confirm opening/closing/stopping (triggered from remote)
..
..
else if (descMap.data[6] == "00") {
log.trace "remote opening"
levelEventMoving(100)
@s1godfrey can you please obtain and post your device fingerprint? ( temporary switch to HE inbuilt 'Device' driver and hit 'Get Info' button.
So far I have identified 20 (twenty!) different variations Zemismart blinds/shades/motors and most of them have slightly different behaviors. Some models have reverse position reporting, others have reversed Open/Close/Stop commands, others report the final and the current positions using one and the same Tiya command (dp), etc, etc..
Compare the problematic device 'Manufacturer' value to the other blinds that work OK. Is it the same? It is not unusual for Tuya products sellers to ship different models (or different firmware versions) even when in one and the same purchase order.
@kkossev Do you mean this data:
- endpointId: 01
- application: 52
- softwareBuild:
- inClusters: 0000,000A,0004,0005,EF00
- outClusters: 0019
- model: TS0601
- manufacturer: _TZE200_fzo2pocs
1 Like
Yes, this is the 21st different model/manufacturer of Zemismart motors...
Are all of your motors the same 'Manufacturer' ? Or the Manufacturer ID of the one that behaves erratically differs from the rest that work OK?
They all report the same data. And were bought at different times, some several months apart from each other. The one that is acting up was the first one purchased.
This is the one from Zemismart site order history. Purchased Dec 7th 2020. I bought both the 'bad' one and the 'good' one for a double window as a set.
Zemismart Tuya Zigbee Roller Shade Motor For 38mm tube SmarThings Alexa Echo Google Home Control Electric Engine Shutter Rod
Providing the Manufacturer ID is the same and the firmware version ( shown as 'Application' - in your case 52) are the same for all your motors, then it looks like a hardware problem ... The first thing to check is usually the power supply/battery. But your model seems to have the AC power supply built-in, so it will be not very easy to check whether the power supply is acting up.
1 Like
