# Ubisys J1 Calibration

**URL:** <https://forum.phoscon.de/t/ubisys-j1-calibration/3386>\
**Category:** Bug reports\
**Created:** [March 15, 2023, 8:33am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386 "2023-03-15T08:33:57Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![jan666](https://forum.phoscon.de/user_avatar/forum.phoscon.de/jan666/32/972_2.png) [@jan666](https://forum.phoscon.de/u/jan666)\
**Post date:** [March 15, 2023, 8:33am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/1 "2023-03-15T08:33:57Z")

</div>

Hello,

I have a awning running with an Ubisys J1. I installed it in 2020 and calibrated it like described here: [Add ubisys J1 calibration and switch configuration. by ma-ca · Pull Request #813 · dresden-elektronik/deconz-rest-plugin · GitHub](https://github.com/dresden-elektronik/deconz-rest-plugin/pull/813). Works great since then.

Now I installed a new shader with a new Ubisys J1. I just wanted to calibrate it but the call does not work anymore:

```auto
$ curl -XPUT http://[...]/sensors/71 --data '{"windowcoveringtype" : 0}'
[{"error":{"address":"/sensors/71/windowcoveringtype","description":"parameter, windowcoveringtype, not available","type":6}}]%

```

It looks like the windowcoveringtype moved to config. So I tried

```auto
$ curl -XPUT http://[...]/sensors/71 --data '{ "config": {"windowcoveringtype" : 0} }'
[{"success":{"/sensors/71/config/windowcoveringtype":0}}]%

```

and the calibration started. It moved down a little bit, up and down til the end. But it looks like its not really calibrated.

This is my sensor:

```auto
{
  "config": {
    "group": "20001",
    "mode": "momentary",
    "on": true,
    "reachable": true,
    "windowcoveringtype": 0
  },
  "ep": 2,
  "etag": "60abe4984746c88f55a9c11831be3323",
  "lastannounced": null,
  "lastseen": "2023-03-15T08:28Z",
  "manufacturername": "ubisys",
  "mode": 1,
  "modelid": "J1 (5502)",
  "name": "Rolloschalter Wohnzimmer",
  "state": {
    "buttonevent": 2002,
    "lastupdated": "2023-03-15T08:21:19.490"
  },
  "type": "ZHASwitch",
  "uniqueid": "00:1f:ee:00:00:00:53:33-02-0102"
}

```

This is my “Light”

```auto
{
  "config": {
    "groups": []
  },
  "etag": "79f5fb7faea237f10a04268ac3e78379",
  "hascolor": false,
  "lastannounced": null,
  "lastseen": "2023-03-15T08:32Z",
  "manufacturername": "ubisys",
  "modelid": "J1 (5502)",
  "name": "Rollo Wohnzimmer",
  "state": {
    "bri": 648,
    "lift": 0,
    "on": false,
    "open": true,
    "reachable": true,
    "tilt": 0
  },
  "swversion": null,
  "type": "Window covering device",
  "uniqueid": "00:1f:ee:00:00:00:53:33-01"
}

```

---

<div class="post-metadata">

**Author:** ![jan666](https://forum.phoscon.de/user_avatar/forum.phoscon.de/jan666/32/972_2.png) [@jan666](https://forum.phoscon.de/u/jan666)\
**Post date:** [March 15, 2023, 12:13pm UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/2 "2023-03-15T12:13:56Z")

</div>

I can’t get it to work.

Is there a way to confirm calibration was successful?

---

<div class="post-metadata">

**Author:** ![jan666](https://forum.phoscon.de/user_avatar/forum.phoscon.de/jan666/32/972_2.png) [@jan666](https://forum.phoscon.de/u/jan666)\
**Post date:** [March 15, 2023, 12:38pm UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/3 "2023-03-15T12:38:42Z")

</div>

I tried to run the calibration steps on my own - but the clusters I have to write are read-only.

 ![J1](https://forum.phoscon.de/uploads/default/original/2X/c/c3a7258b27700e534f6ecbfaf54cde647befa764.png)

---

<div class="post-metadata">

**Author:** ![jan666](https://forum.phoscon.de/user_avatar/forum.phoscon.de/jan666/32/972_2.png) [@jan666](https://forum.phoscon.de/u/jan666)\
**Post date:** [March 16, 2023, 7:58am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/4 "2023-03-16T07:58:30Z")

</div>

I just noticed this. Why is “Tuya Window Covering Setting” here? Is this correct…?

 ![TUYA](https://forum.phoscon.de/uploads/default/original/2X/7/7fe460fc74d45256ac78dcfc98bee1e9d005181e.png)

when I try to read the 3:

 ![unsupported](https://forum.phoscon.de/uploads/default/original/2X/4/485507fa93369a213fc98c0b69f4c784fe8e4b96.png)

---

<div class="post-metadata">

**Author:** ![jan666](https://forum.phoscon.de/user_avatar/forum.phoscon.de/jan666/32/972_2.png) [@jan666](https://forum.phoscon.de/u/jan666)\
**Post date:** [March 16, 2023, 8:26am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/5 "2023-03-16T08:26:00Z")

</div>

there are differences between the old awning and the new shader:

 ![J1](https://forum.phoscon.de/uploads/default/original/2X/9/9e1ddc18dd23b53dd2ca51d49e8e89b3dbe3bf0b.png)

Bug in deCONZ?

---

<div class="post-metadata">

**Author:** ![Swoop](https://forum.phoscon.de/letter_avatar_proxy/v4/letter/s/b77776/32.png) [@Swoop](https://forum.phoscon.de/u/Swoop)\
**Post date:** [March 16, 2023, 10:43am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/6 "2023-03-16T10:43:42Z")

</div>

I’m afraid you totally lost me on this one and you’re seeing “bugs” where there are none.

Is the device now working or not?

---

<div class="post-metadata">

**Author:** ![jan666](https://forum.phoscon.de/user_avatar/forum.phoscon.de/jan666/32/972_2.png) [@jan666](https://forum.phoscon.de/u/jan666)\
**Post date:** [March 16, 2023, 10:55am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/7 "2023-03-16T10:55:02Z")

</div>

I have 2 devices. Awning and Shutter. The Awning was installed 2020, calibrated via POST request und works perfect since then. The shutter is new.

The device is working uncalibrated. So I dont have the state. But I can move up and down til the motos stops.

Calibration via POST (curl -XPUT […]/sensors/74/config --data ‘{“windowcoveringtype” : 2}’) starts but does not really follow the steps it should (it drived up, drives down a little bit, drives up again and nothing else). So after the POST calibration its like it was not calibrated at all.

I can start the calibration manually but either the “move down” or “move up” step do not finish (ends before the motor stops). After the manual calibration I have a state but its not correct. It’s a little bit erratic where is 0 % and where is 100 % - but i cant really open or close it.

According to [https://www.ubisys.de/wp-content/uploads/ubisys-j1-technical-reference.pdf:](https://www.ubisys.de/wp-content/uploads/ubisys-j1-technical-reference.pdf:)

> When calibration is complete attributes 0x10F2:0x1002 and 0x10F2:0x1004 are different from 0xFFFF  
> and hold the times that J1 has measured for your physical setup consisting of motor and blind. The  
> values can be close together (typically lift & tilt blinds match closely) or have significant differences  
> (down-to-up takes e.g. 100% longer than up-to-down due to gravity). Instead of auto-calibration you  
> can also write the values directly if you know them.

but I dont have the 1xxx clusters - see my screesnhots. They’re not visible at the Awning (which works fine), too. So this might be a bug in deCONZ (missing clusters?) - but I can see TUYA Clusters but when I try to read them they’re “unsupported”.

---

<div class="post-metadata">

**Author:** ![ChrisHae](https://forum.phoscon.de/letter_avatar_proxy/v4/letter/c/e5b9ba/32.png) [@ChrisHae](https://forum.phoscon.de/u/ChrisHae)\
**Post date:** [March 16, 2023, 11:18am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/8 "2023-03-16T11:18:19Z")

</div>

I have contact with a Ubisys employee. He said manufacture specific attributes need to be written.  
I’ll look which attributes specifically. The technical-refrence.pdf is very detailed.  
Perhaps they are not in the general.xml file. So they wouldn’t be in deCONZ.

Could also be the WindowCoveringType Attribute should be writeable. Then it would also be a bug in the general.xml

---

<div class="post-metadata">

**Author:** ![ChrisHae](https://forum.phoscon.de/letter_avatar_proxy/v4/letter/c/e5b9ba/32.png) [@ChrisHae](https://forum.phoscon.de/u/ChrisHae)\
**Post date:** [March 16, 2023, 11:40am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/9 "2023-03-16T11:40:39Z")

</div>

@jan666 I think you have to use the FC00 Cluster. Could you please share a Screenshot of that Cluster and Attributes.

---

<div class="post-metadata">

**Author:** ![jan666](https://forum.phoscon.de/user_avatar/forum.phoscon.de/jan666/32/972_2.png) [@jan666](https://forum.phoscon.de/u/jan666)\
**Post date:** [March 16, 2023, 11:48am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/10 "2023-03-16T11:48:26Z")

</div>

![FC00](https://forum.phoscon.de/uploads/default/original/2X/b/bef11ea01e15b7358ba5c68bc18e0fa20c533d12.png)

---

<div class="post-metadata">

**Author:** ![Swoop](https://forum.phoscon.de/letter_avatar_proxy/v4/letter/s/b77776/32.png) [@Swoop](https://forum.phoscon.de/u/Swoop)\
**Post date:** [March 16, 2023, 10:40pm UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/11 "2023-03-16T22:40:29Z")

</div>

The J1 auto-calibrates just fine here 🤷‍♂️

---

<div class="post-metadata">

**Author:** ![jan666](https://forum.phoscon.de/user_avatar/forum.phoscon.de/jan666/32/972_2.png) [@jan666](https://forum.phoscon.de/u/jan666)\
**Post date:** [March 17, 2023, 5:30am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/12 "2023-03-17T05:30:30Z")

</div>

Can you see / write the clusters 0x10F2:0x1002 and 0x10F2:0x1004?

---

<div class="post-metadata">

**Author:** ![ChrisHae](https://forum.phoscon.de/letter_avatar_proxy/v4/letter/c/e5b9ba/32.png) [@ChrisHae](https://forum.phoscon.de/u/ChrisHae)\
**Post date:** [March 17, 2023, 9:26am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/13 "2023-03-17T09:26:54Z")

</div>

I have just seen in the webplugin c++ code and it is all there. the calibration and the attributes tha need to be written. Don’t know why it should not work anymore. I have never used this device. So i can’t say how the calibration should look like when it is finished.

In the deCONZ GUI the manufacturer specific attributes aren’t shown.  
But the could be added to the GUI by editing the general.xml file.

---

<div class="post-metadata">

**Author:** ![jan666](https://forum.phoscon.de/user_avatar/forum.phoscon.de/jan666/32/972_2.png) [@jan666](https://forum.phoscon.de/u/jan666)\
**Post date:** [March 17, 2023, 9:38am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/14 "2023-03-17T09:38:53Z")

</div>

> [@ChrisHae](#):
>
> I have never used this device. So i can’t say how the calibration should look like when it is finished.

According to [https://www.ubisys.de/wp-content/uploads/ubisys-j1-technical-reference.pdf:](https://www.ubisys.de/wp-content/uploads/ubisys-j1-technical-reference.pdf:)

> When calibration is complete attributes 0x10F2:0x1002 and 0x10F2:0x1004 are different from 0xFFFF  
> and hold the times that J1 has measured for your physical setup consisting of motor and blind. The  
> values can be close together (typically lift & tilt blinds match closely) or have significant differences  
> (down-to-up takes e.g. 100% longer than up-to-down due to gravity). Instead of auto-calibration you  
> can also write the values directly if you know them.

I could confirm this with my awning because thats calibrated. But the clusters aren’t shown. Can you tell me how to edit the general.xml to see the clusters?

> Write attribute 0x10F2:0x0000 (“WindowCoveringType”) accordingly.  
> Write attribute 0x10F2:0x0010 (“InstalledOpenLimitLift”) as 0x0000 = 0cm.  
> Write attribute 0x10F2:0x0011 (“InstalledClosedLimitLift”) as 0x00F0 = 240cm.  
> Write attribute 0x10F2:0x0012 (“InstalledOpenLimitTilt”) as 0x0000 = 0°.  
> Write attribute 0x10F2:0x0013 (“InstalledClosedLimitTilt”) as 0x0384 = 90.0°.  
> Write attribute 0x10F2:0x1001 (“LiftToTiltTransitionSteps”) as 0xFFFF = invalid.  
> Write attribute 0x10F2:0x1002 (“TotalSteps”) as 0xFFFF = invalid.  
> Write attribute 0x10F2:0x1003 (“LiftToTiltTransitionSteps2”) as 0xFFFF = invalid.  
> Write attribute 0x10F2:0x1004 (“TotalSteps2”) as 0xFFFF = invalid.

These clusters should be rw but they’re just r.

---

<div class="post-metadata">

**Author:** ![ChrisHae](https://forum.phoscon.de/letter_avatar_proxy/v4/letter/c/e5b9ba/32.png) [@ChrisHae](https://forum.phoscon.de/u/ChrisHae)\
**Post date:** [March 17, 2023, 1:12pm UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/15 "2023-03-17T13:12:28Z")

</div>

These are attributes not cluster. They are manufacturer specific attributes which are read/writeable. in deCONZ only the standard attributes which are only readable are present. I try to add these here to the general.xml and then report back.

---

<div class="post-metadata">

**Author:** ![Swoop](https://forum.phoscon.de/letter_avatar_proxy/v4/letter/s/b77776/32.png) [@Swoop](https://forum.phoscon.de/u/Swoop)\
**Post date:** [March 20, 2023, 9:55am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/16 "2023-03-20T09:55:09Z")

</div>

Ok, so I’ve now completely reset my J1 just to see what’s going on here and it appears indeed that the auto-calibration is not fully working.

@jan666 Could you please file a bug report on Github for this?

@ChrisHae Unfortunately, adding the writable versions of the attributes through general.xml will not work properly, as the GUI has issues if the same attribute exists with **AND** without mfcode. Manup should know about that 🙂

---

<div class="post-metadata">

**Author:** ![jan666](https://forum.phoscon.de/user_avatar/forum.phoscon.de/jan666/32/972_2.png) [@jan666](https://forum.phoscon.de/u/jan666)\
**Post date:** [March 20, 2023, 10:13am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/17 "2023-03-20T10:13:58Z")

</div>

> <https://github.com/dresden-elektronik/deconz-rest-plugin/issues/6812>
>
> \<!--
> - Use this issue template to report a bug in the deCONZ REST-API.
> - A…nything that is not clearly a bug can implicate manual closure. For support we recommend the forum: https://forum.phoscon.de 
> - If you want to report a bug for the Phoscon App, please head over to: https://forum.phoscon.de
> - Make sure not to remove any headers and fill the template completely. If you remove the headers, the issue will be auto-closed.
> - If you're unsure if the bug fits into this issue tracker, please ask for advise in our Discord chat: https://discord.gg/QFhTxqN
> - Please make sure sure you're running the latest version of deCONZ: https://github.com/dresden-elektronik/deconz-rest-plugin/releases
> \--\>
> 
> \## Describe the bug
> \<!--
> Describe the issue you are experiencing here to communicate to the
> maintainers. Tell us what you were trying to do and what happened.
> 
> Help us understand the issue by providing valuable context.
> \--\>
> 
> The Ubisys J1 needs to be calibrated before it's fully usable. This is (like described here: https://github.com/dresden-elektronik/deconz-rest-plugin/pull/813) done via REST-API call \`PUT /sensors/xx/config {"windowcoveringtype" : 0}\`.
> 
> When I installed my first J1 in 2020 this worked perfect (see https://github.com/dresden-elektronik/deconz-rest-plugin/issues/3147).
> 
> No I installed my second J1 and it's not working anymore (confirmed here: https://forum.phoscon.de/t/ubisys-j1-calibration/3386 by @SwoopX)
> 
> \## Steps to reproduce the behavior
> \<!--
> If the problem is reproducable, list the steps here:
> 
> 1. Go to '...'
> 2. Click on '....'
> 3. Scroll down to '....'
> 4. Observed error
> 
> If the problem can't be reproduced and is sporadic, please provide some details
> on how often and when the issue happens.
> \--\>
> 
> 0. Reset the J1 if its already calibrated
> 1. send the \`PUT /sensors/xx/config {"windowcoveringtype" : 0}\` to your J1-ZHASwitch-Sensor
> 
> \## Expected behavior
> \<!--
> If applicable, describe what you expected to happen.
> \--\>
> 
> The J1 should drive a little bit down, drive completely up, completely down, completely up again to and be calibrated.
> 
> \## Screenshots
> \<!--
> If applicable, add screenshots to help explain the problem.
> \--\>
> 
> \## Environment
> \<!--
> The deCONZ and firmware versions are found in the Phoscon App: Menu -\> Settings -\> Gateway,
> as well as in the deCONZ GUI: Menu \> Help \> About deCONZ.
> \--\>
> 
> - Host system: Raspberry Pi
> - Running method: Raspbian
> - Firmware version: 26780700
> - deCONZ version: 2.20.01 / 19.9.2022
> - Device: ConBee II
> - Do you use an USB extension cable: yes
> - Is there any other USB or serial devices connected to the host system? Yes, a "Technischer Alternative" D-LOGG
> 
> \## deCONZ Logs
> \<!--
> Debug logs can help to investigate certain problems like device pairing and communication issues.
> Logging can be enabled on the command line as described in:
> https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/deCONZ-debug-flags
> Secondly, for versions above 2.05.87: In the deCONZ GUI: click Help \> debug view. Output of APS,ZDP, ZCL and INFO can be handy. 
> 
> \--\>
> 
> \## Additional context
> \<!--
> If relevant, add any other context about the problem here, like network size, number of routers and end-devices
> and what kind of devices/brands are in the network.
> \--\>
> 
> See here: https://forum.phoscon.de/t/ubisys-j1-calibration/3386

---

<div class="post-metadata">

**Author:** ![Mimiix](https://forum.phoscon.de/user_avatar/forum.phoscon.de/mimiix/32/10_2.png) [@Mimiix](https://forum.phoscon.de/u/Mimiix)\
**Post date:** [March 20, 2023, 11:01am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/18 "2023-03-20T11:01:33Z")

</div>

As this is now tracked on Github, i am moving this topic away to bug reports and lock it. Just to be sure we don;t have 2 discussions going on.

Thanks for report @jan666🙂

---

<div class="post-metadata">

**Author:** ![Mimiix](https://forum.phoscon.de/user_avatar/forum.phoscon.de/mimiix/32/10_2.png) [@Mimiix](https://forum.phoscon.de/u/Mimiix)\
**Post date:** [March 20, 2023, 11:01am UTC](https://forum.phoscon.de/t/ubisys-j1-calibration/3386/19 "2023-03-20T11:01:46Z")

</div>

Closed on March 20, 2023, 11:01am UTC


