It is already there. install:
Zigbee Temp Sensor and Child Thermostat Mc
From @Mariano_Colmenarejo channel
It is already there. install:
Zigbee Temp Sensor and Child Thermostat Mc
From @Mariano_Colmenarejo channel
It has the valve, but doesnβt expose the flow sensor capability. I was wondering how hard (or if itβs possible) to add that.
I bought this Neo zigbee Siren on aliexpress, do you think it is possible to add it to your driver?
It is possible but with @w35l3y driver, since this device is using EF00 cluster.
This is his tread you better try his driver first
Hi @Kimmo_Liias
Added to driver some time ago
Hi @sidk
Added to this driver version
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Name Zigbee Temp Sensor and Child Thermostat Mc
Version 2023-11-03T21:15:46.2500653
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
- id: "_TZ3000_rdhukkmi/TS0201"
deviceLabel: Tuya TS0201
manufacturer: _TZ3000_rdhukkmi
model: TS0201
deviceProfileName: temp-humid-battery
An added to this driver thermostat without child device
ββββββββββββββββββββββββββββββββββββββββββββββββββββ
Name Zigbee Temp Sensor with Thermostat Mc
Version 2023-11-03T21:18:46.336949326
ββββββββββββββββββββββββββββββββββββββββββββββββββββ
Hi @brenthaag
I have no idea how Sinope implements the flow meter.
I donβt know if it uses a custom cluster or reuses one of the standard ones like 0702, to measure flow instead of electricity consumption.
Iβm sorry, if it seems complicated to me with the information I have, if there is some documentation that explains it it could be possible
Hi @cordell25
This was posted almost a month ago.
No problemβ¦I appreciate you looking anyway. I have asked the manufacturer and they wonβt share the info.
Thank you - Iβm a bit confused so I must be doing something wrong.
When I look at my Driver in Smartthings it shows βZigbee Switch Mcβ and the version is β2023-10-10β¦β - the link you posted shows that it should be β2023-10-12β¦β to see those new updates so do you know why I seem to be on an old version (I just installed the Edge driver yesterday)
Could it be a fingerprint issue?
posting some screenshots in case it helps with the issue:
The driver should have been updated to the latest version automatically if your hub is enrolled in my channel.
These are the two devices in the driver, I donβt know the fingerprints of yours.
( mfr = β_TZ3210_dse8ogfyβ, model = βTS0001β)
( mfr = β_TZ3210_j4pdtz9vβ, model = βTS0001β)
@Mariano_Colmenarejo why are you adding again Sonoff Motion Sensor and Sonoff Contact Sensor? They were previously deleted or what? They were already in your driver before.
Hi I have the same issue here, the version is still 2023-10-10T
And the fingerprint is _TZ3210_dse8ogfy, model TS0001.
Published last version β2023-10-12T14:08:48.900600395β again.
I donβt know why itβs not on the channel, maybe I forgot, it could be
Models SNZB-03 and SNZB-04 did not exist in the drivers, nor do they exist in the stock drivers.
There were models DS01 and MS01.
I also added yesterday the DS01 model from the manufacturer βzbeaconβ instead of eWeLink, it must be another brand from Sonoff
Could you add this to Zigbee Temp Sensor with Thermostat Mc. One device makes all much easier to handle automations etc.
I mean this device I previously asked:
Manufacturer
_TZ3000_dowj6gyi
Model
TS0201
Added to this driver version
ββββββββββββββββββββββββββββββββββββββββββββββββββββ
Name Zigbee Temp Sensor with Thermostat Mc
Version 2023-11-04T10:07:10.496537802
ββββββββββββββββββββββββββββββββββββββββββββββββββββ
- id: "_TZ3000_dowj6gyi/TS0201"
deviceLabel: Tuya TS0201
manufacturer: _TZ3000_dowj6gyi
model: TS0201
deviceProfileName: temp-humid-therm-battery-05
Problem solved. Many thanks!
Thank you! That did the trick.
It appears to be working for the most part. A couple of notes:
The FingerBot Down Motion and FingerBot Up Motion are displayed as % but I donβt believe that is what the values represent. Instead itβs more of a scale of 0-100 where 0 is the top and 100 is the bottom. So you can set a value from 1-50 (50 being the middle) to control how far up the arm moves before stopping. And a value of 50-100 to control how far down the arm moves before stopping. I donβt think displaying it as a percentage makes sense.
I also found that the Up Motion setting seems to be working correctly but the Down Motion setting doesnβt seem to be doing anything differently when I change its value. Could you check that and see if something in the driver is off?
Thank you again for making this driver!
Hi @cordell25
Iβm sorry to disagree with you on this.
% seems like the perfect unit for this case.
0 to 100 could be mm, cm, dm, m, km, which would not make any sense.
Almost everyone understands that 100% is the maximum, 50% is middle and 0% is the minimum of whatever.
Thatβs why the downward range of motion is between 50 - 100 and the upward range of motion is between 0 - 50.
I did about 1000 tests to make it work, the values that the driver shows are those that the device returns as accepted into the data point ranges
I commented in the post that the device itself does not accept any combination of up and down movement values and readjusts them, in certain cases, to the values that it considers logical to correct function.
Sometimes I donβt understand Tuyaβs logic too and itβs the best he can get.
The driver code is in my guthub repository, if someone wants to improve it I would be very happy, but I give up, at the moment I donβt need more.
Edit:
By the way, I also tried it with a hub and the Tuya app and it worked the same, except that it has adjustment sliders, but it seemed less precise to me.
The device may have a firmware or design defect.