Mimiix
commented
6 months ago @Smanar is this a bug or feature request?
Closed sanluca closed 6 months ago
Mimiix
commented
6 months ago @Smanar is this a bug or feature request?
sanluca
commented
6 months ago @Smanar is this a bug or feature request?
I'm not sure if it's supposed to work this way or if there needs to be an option to invert the values. I don't have any other products to compare it to
Smanar
commented
6 months ago I don't see this device on DDF or legacy code. So I think we can create a DDF to reverse the value returned by deconz if the problem is from deconz.
On deconz rules are
shutter closed
on = true
bri = 255
open = false
lift = 100%I don't now if the HA plugin do a reverse. It's a module, so you have wired command, thoses one work in correct side ? There is command to reverse covering, but it reverse command AND return, the issue exist only is command are reversed according to return. Can you check in the API if deconz return the good one ? For exemple in phoscon/help/API Information/light.
If value are reversed, can you share the auto generated DDF on the editor (on text version, not picture), else the complete json from the API you have get just before ?
With DDF I will be able to return the value returned, but not the requests made.
Mimiix
commented
6 months ago In that case I'm going to ask for a device request @sanluca
Does the issue really belong here?
Is there already an existing issue for this?
Describe the bug
Hi guys, I'm using a _TZ3000_iaxvag8w roller shutter module produced by TS130F. However, I'm facing an issue with OpenHAB. The roller shutter module indicates a fully open state as 100% and a closed state as 0%. Conversely, OpenHAB interprets the states differently: 0% indicates an open shutter and 100% indicates a closed one. Is there a way to invert the state of the Zigbee module? thanks
Steps to reproduce the behavior
.
Expected behavior
.
Screenshots
No response
Environment
deCONZ Logs
No response
Additional context
No response