# \[Solved\] Adding new device on opensmarthouse

**URL:** <https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769>\
**Category:** Items & Sitemaps\
**Tags:** smokedetector, z-wave, openhab3\
**Created:** [February 25, 2023, 2:05pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769 "2023-02-25T14:05:43Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![zynex](https://community.openhab.org/letter_avatar_proxy/v4/letter/z/c0e974/32.png) [@zynex](https://community.openhab.org/u/zynex)\
**Post date:** [February 25, 2023, 2:05pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/1 "2023-02-25T14:05:43Z")

</div>

Not sure if this is the right place to post this, but I recently got a Nexa Smoke Detector (ZSD-109) that doesn’t exist in the database. I’m trying to add it but just get an error without any description. I’m using the node XML from OpenHAB as stated in the docs.

Not sure if there’s some error on opensmarthouse site itself, because I can’t post a ticket there either (won’t save it). Maybe @chris know’s whats happening here? 🙂

Here’s the XML I try to use anyway.

```auto
<node>
  <homeId>0xe2fb1d4d</homeId>
  <nodeId>3</nodeId>
  <version>4</version>
  <manufacturer>0x266</manufacturer>
  <deviceId>0x1</deviceId>
  <deviceType>0x5</deviceType>
  <listening>false</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>true</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>
  <sleepDelay>500</sleepDelay>
  <nodeInformationFrame>
    <commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
    <commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
    <commandClass>COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION</commandClass>
    <commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
    <commandClass>COMMAND_CLASS_TRANSPORT_SERVICE</commandClass>
    <commandClass>COMMAND_CLASS_VERSION</commandClass>
    <commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
    <commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
    <commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
    <commandClass>COMMAND_CLASS_BATTERY</commandClass>
    <commandClass>COMMAND_CLASS_SECURITY_2</commandClass>
    <commandClass>COMMAND_CLASS_ALARM</commandClass>
    <commandClass>COMMAND_CLASS_WAKE_UP</commandClass>
    <commandClass>COMMAND_CLASS_SUPERVISION</commandClass>
  </nodeInformationFrame>
  <associationGroups class="concurrent-hash-map">
    <entry>
      <int>1</int>
      <associationGroup>
        <index>1</index>
        <maxNodes>0</maxNodes>
        <name>Lifeline</name>
        <profile1>0x0</profile1>
        <profile2>0x1</profile2>
        <commands>
          <commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
          <commandClass>COMMAND_CLASS_ALARM</commandClass>
          <commandClass>COMMAND_CLASS_BATTERY</commandClass>
        </commands>
        <associations>
          <associationMember>
            <node>1</node>
          </associationMember>
        </associations>
      </associationGroup>
    </entry>
    <entry>
      <int>2</int>
      <associationGroup>
        <index>2</index>
        <maxNodes>0</maxNodes>
        <name>SensorSmok Basic set(ON/OFF)</name>
        <profile1>0x71</profile1>
        <profile2>0x1</profile2>
        <commands/>
        <associations/>
      </associationGroup>
    </entry>
    <entry>
      <int>3</int>
      <associationGroup>
        <index>3</index>
        <maxNodes>0</maxNodes>
        <name>Smok Alarm Report</name>
        <profile1>0x71</profile1>
        <profile2>0x1</profile2>
        <commands>
          <commandClass>COMMAND_CLASS_ALARM</commandClass>
        </commands>
        <associations/>
      </associationGroup>
    </entry>
    <entry>
      <int>4</int>
      <associationGroup>
        <index>4</index>
        <maxNodes>0</maxNodes>
        <name>SensorHeat Basic set(ON/OFF)</name>
        <profile1>0x71</profile1>
        <profile2>0x4</profile2>
        <commands/>
        <associations/>
      </associationGroup>
    </entry>
    <entry>
      <int>5</int>
      <associationGroup>
        <index>5</index>
        <maxNodes>0</maxNodes>
        <name>Heat Alarm Report</name>
        <profile1>0x71</profile1>
        <profile2>0x4</profile2>
        <commands>
          <commandClass>COMMAND_CLASS_ALARM</commandClass>
        </commands>
        <associations/>
      </associationGroup>
    </entry>
  </associationGroups>
  <endpoints class="concurrent-hash-map">
    <entry>
      <int>0</int>
      <endPoint>
        <deviceClass>
          <basicDeviceClass>BASIC_TYPE_ROUTING_SLAVE</basicDeviceClass>
          <genericDeviceClass>GENERIC_TYPE_SENSOR_NOTIFICATION</genericDeviceClass>
          <specificDeviceClass>SPECIFIC_TYPE_NOTIFICATION_SENSOR</specificDeviceClass>
        </deviceClass>
        <endpointId>0</endpointId>
        <secureCommandClasses/>
        <supportedCommandClasses class="concurrent-hash-map">
          <entry>
            <commandClass>COMMAND_CLASS_NO_OPERATION</commandClass>
            <COMMAND __CLASS__ NO__OPERATION>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
            </COMMAND __CLASS__ NO__OPERATION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_BASIC</commandClass>
            <COMMAND __CLASS__ BASIC>
              <version>0</version>
              <instances>0</instances>
              <control>false</control>
              <versionSupported>0</versionSupported>
              <isGetSupported>true</isGetSupported>
            </COMMAND __CLASS__ BASIC>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
            <COMMAND __CLASS__ ASSOCIATION __GRP__ INFO>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>3</versionSupported>
              <autoSubscribeGroups>
                <int>1</int>
                <int>3</int>
                <int>5</int>
              </autoSubscribeGroups>
            </COMMAND __CLASS__ ASSOCIATION __GRP__ INFO>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
            <COMMAND __CLASS__ DEVICE __RESET__ LOCALLY>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
            </COMMAND __CLASS__ DEVICE __RESET__ LOCALLY>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
            <COMMAND __CLASS__ ZWAVEPLUS__INFO>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <zwPlusVersion>1</zwPlusVersion>
              <zwPlusRole>ROLE_TYPE_SLAVE_SLEEPING_REPORTING</zwPlusRole>
              <zwPlusNodeType>NODE_TYPE_ZWAVEPLUS_NODE</zwPlusNodeType>
              <isGetSupported>true</isGetSupported>
            </COMMAND __CLASS__ ZWAVEPLUS__INFO>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
            <COMMAND __CLASS__ CONFIGURATION>
              <version>0</version>
              <instances>0</instances>
              <control>false</control>
              <versionSupported>0</versionSupported>
              <configParameters/>
            </COMMAND __CLASS__ CONFIGURATION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_ALARM</commandClass>
            <COMMAND __CLASS__ ALARM>
              <version>8</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>8</versionSupported>
              <alarms>
                <entry>
                  <alarmType>SMOKE</alarmType>
                  <alarmState>
                    <alarmType>SMOKE</alarmType>
                    <reportedEvents>
                      <int>2</int>
                      <int>3</int>
                      <int>4</int>
                      <int>6</int>
                    </reportedEvents>
                    <outer-class reference="../../../.."/>
                  </alarmState>
                </entry>
                <entry>
                  <alarmType>HEAT</alarmType>
                  <alarmState>
                    <alarmType>HEAT</alarmType>
                    <reportedEvents>
                      <int>2</int>
                      <int>7</int>
                      <int>8</int>
                      <int>9</int>
                    </reportedEvents>
                    <outer-class reference="../../../.."/>
                  </alarmState>
                </entry>
              </alarms>
              <v1Supported>true</v1Supported>
              <isGetSupported>true</isGetSupported>
            </COMMAND __CLASS__ ALARM>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
            <COMMAND __CLASS__ MANUFACTURER__SPECIFIC>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <initSerialNumber>false</initSerialNumber>
              <deviceManufacturer>614</deviceManufacturer>
              <deviceType>5</deviceType>
              <deviceId>1</deviceId>
            </COMMAND __CLASS__ MANUFACTURER__SPECIFIC>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
            <COMMAND __CLASS__ POWERLEVEL>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
              <powerLevel>0</powerLevel>
              <powerTimeout>0</powerTimeout>
            </COMMAND __CLASS__ POWERLEVEL>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_BATTERY</commandClass>
            <COMMAND __CLASS__ BATTERY>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
              <batteryLevel>100</batteryLevel>
              <batteryLow>false</batteryLow>
              <isGetSupported>true</isGetSupported>
            </COMMAND __CLASS__ BATTERY>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_WAKE_UP</commandClass>
            <COMMAND __CLASS__ WAKE__UP>
              <version>2</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <targetNodeId>1</targetNodeId>
              <interval>7200</interval>
              <minInterval>3600</minInterval>
              <maxInterval>86400</maxInterval>
              <defaultInterval>7200</defaultInterval>
              <intervalStep>60</intervalStep>
              <isGetSupported>true</isGetSupported>
            </COMMAND __CLASS__ WAKE__UP>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
            <COMMAND __CLASS__ ASSOCIATION>
              <version>2</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <maxGroups>5</maxGroups>
            </COMMAND __CLASS__ ASSOCIATION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_VERSION</commandClass>
            <COMMAND __CLASS__ VERSION>
              <version>2</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <libraryType>LIB_SLAVE_ROUTING</libraryType>
              <protocolVersion>4.61</protocolVersion>
              <applicationVersion>1.1</applicationVersion>
              <hardwareVersion>255</hardwareVersion>
            </COMMAND __CLASS__ VERSION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION</commandClass>
            <COMMAND __CLASS__ MULTI __CHANNEL__ ASSOCIATION>
              <version>3</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>3</versionSupported>
              <maxGroups>5</maxGroups>
            </COMMAND __CLASS__ MULTI __CHANNEL__ ASSOCIATION>
          </entry>
        </supportedCommandClasses>
      </endPoint>
    </entry>
  </endpoints>
  <nodeNeighbors>
    <int>1</int>
  </nodeNeighbors>
  <lastReceived>2023-02-25 13:36:12.16 UTC</lastReceived>
</node>

```

---

<div class="post-metadata">

**Author:** ![apella12](https://community.openhab.org/user_avatar/community.openhab.org/apella12/32/117154_2.png) [@apella12](https://community.openhab.org/u/apella12)\
**Post date:** [February 25, 2023, 6:00pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/2 "2023-02-25T18:00:05Z")

</div>

> [@zynex](#):
>
> Nexa S

My guess is that this is a new manufacturer (0x0266) for OH. On another site it is listed as  
“0x0266”: “Siterwell Technology HK Co., Ltd.”,

However neither (Nexa or Siterwell) is listed in DB. Chris will have to add.

---

<div class="post-metadata">

**Author:** ![chris](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/958977/32.png) [@chris](https://community.openhab.org/u/chris)\
**Post date:** [February 25, 2023, 6:02pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/3 "2023-02-25T18:02:25Z")

</div>

There shouldn’t be an issue with tickets on the OSH site - I see tickets from other people at least, so it is working for others.

Sorry for the potentially silly questions, but I guess you have an account and I gave you access (sorry - I’m travelling at the moment so can’t log on to check).

---

<div class="post-metadata">

**Author:** ![anon71759204](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/2acd7d/32.png) [@anon71759204](https://community.openhab.org/u/anon71759204)\
**Post date:** [February 25, 2023, 6:58pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/4 "2023-02-25T18:58:55Z")

</div>

Just for reference:

> **[SITERWELL-safe,Alarm,Fire](https://www.siterwellhome.com/)**
>
> SITERWELL ELECTRONICS CO.,LIMITED which was established in 2010

[https://products.z-wavealliance.org/products/2599?selectedFrequencyId=-1](https://products.z-wavealliance.org/products/2599?selectedFrequencyId=-1)

---

<div class="post-metadata">

**Author:** ![zynex](https://community.openhab.org/letter_avatar_proxy/v4/letter/z/c0e974/32.png) [@zynex](https://community.openhab.org/u/zynex)\
**Post date:** [February 26, 2023, 2:38pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/5 "2023-02-26T14:38:47Z")

</div>

Hmm, might be something here then. Tried both Firefox, Falkon and Firefox on Android. Know it have worked, I created a ticket in january 🙂

Yepp, I have an account and have access to adding new things to the database. Tried pasting the above XML, but just get an error when trying to add it.

---

<div class="post-metadata">

**Author:** ![zynex](https://community.openhab.org/letter_avatar_proxy/v4/letter/z/c0e974/32.png) [@zynex](https://community.openhab.org/u/zynex)\
**Post date:** [February 26, 2023, 2:42pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/6 "2023-02-26T14:42:49Z")

</div>

Might use the same hardware or something? Nexa is a Swedish company that started its business 1997.

---

<div class="post-metadata">

**Author:** ![chris](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/958977/32.png) [@chris](https://community.openhab.org/u/chris)\
**Post date:** [February 26, 2023, 2:45pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/7 "2023-02-26T14:45:24Z")

</div>

I’ve added this manufacturer now…

---

<div class="post-metadata">

**Author:** ![zynex](https://community.openhab.org/letter_avatar_proxy/v4/letter/z/c0e974/32.png) [@zynex](https://community.openhab.org/u/zynex)\
**Post date:** [February 26, 2023, 2:59pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/8 "2023-02-26T14:59:21Z")

</div>

> [@zynex](#):
>
> opensmarthouse

Great! Could add it now 🙂

---

<div class="post-metadata">

**Author:** ![apella12](https://community.openhab.org/user_avatar/community.openhab.org/apella12/32/117154_2.png) [@apella12](https://community.openhab.org/u/apella12)\
**Post date:** [February 28, 2023, 11:37pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/9 "2023-02-28T23:37:20Z")

</div>

If you are done, don’t forget to “Request review” on the overview tab.

---

<div class="post-metadata">

**Author:** ![zynex](https://community.openhab.org/letter_avatar_proxy/v4/letter/z/c0e974/32.png) [@zynex](https://community.openhab.org/u/zynex)\
**Post date:** [March 1, 2023, 1:16pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/10 "2023-03-01T13:16:16Z")

</div>

I’m aware, trying to get some information about the device from the company but haven’t heard from them yet.

---

<div class="post-metadata">

**Author:** ![zynex](https://community.openhab.org/letter_avatar_proxy/v4/letter/z/c0e974/32.png) [@zynex](https://community.openhab.org/u/zynex)\
**Post date:** [March 1, 2023, 1:40pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/11 "2023-03-01T13:40:53Z")

</div>

@anon71759204 Just talked to Nexa them self, but the didn’t have any extended manual. But the links you provided should do the trick I think. Any nice soul wanna help adding it, never done it before. Don’t wanna mess it up 🙂

[EDIT] Think I got it 😃

---

<div class="post-metadata">

**Author:** ![zynex](https://community.openhab.org/letter_avatar_proxy/v4/letter/z/c0e974/32.png) [@zynex](https://community.openhab.org/u/zynex)\
**Post date:** [May 6, 2023, 7:48pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/12 "2023-05-06T19:48:35Z")

</div>

Can confirm that the info I added to the z-wave database about the device is working. Triggers on smoke (didn’t test heat), and battery is reporting it’s status. Only available in snapshot at the time of writing though.

---

<div class="post-metadata">

**Author:** ![Oden](https://community.openhab.org/letter_avatar_proxy/v4/letter/o/ccd318/32.png) [@Oden](https://community.openhab.org/u/Oden)\
**Post date:** [July 27, 2024, 10:54am UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/13 "2024-07-27T10:54:30Z")

</div>

Hijacking this thread. Bought three of the same smoke detector (ZSD-109) based on this thread, and can confirm that they are all being discovered, but none of the detectors report anything, all channels (linked to items, of course) say NULL, eventhough I triggered the test several times.  
I have tried to wake them up (although not sure that this can be done in similar fashion as Fibaro’s door sensors etc.) by tripple-clicking the button. Nothing is reported in the logs when this is done. They have been laying close to the z-wave bridge for 24h now. Any suggestions?

---

<div class="post-metadata">

**Author:** ![zynex](https://community.openhab.org/letter_avatar_proxy/v4/letter/z/c0e974/32.png) [@zynex](https://community.openhab.org/u/zynex)\
**Post date:** [July 27, 2024, 11:07am UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/14 "2024-07-27T11:07:04Z")

</div>

Unfortunately not, I had some other devices that didn’t work with OpenHAB at all, so I ended up migrating everything to Home Assistant. There both smoke detectors and and other devices (some from Aqara) worked without any issues.

---

<div class="post-metadata">

**Author:** ![apella12](https://community.openhab.org/user_avatar/community.openhab.org/apella12/32/117154_2.png) [@apella12](https://community.openhab.org/u/apella12)\
**Post date:** [July 27, 2024, 2:58pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/15 "2024-07-27T14:58:26Z")

</div>

> [@Oden](#):
>
> They have been laying close to the z-wave bridge for 24h now. Any suggestions?

The only thing I see in reviewing the ZW DB is that the controller is not automatically put in Lifeline. (group 1). add that and test again.

> [@zynex](#):
>
> Unfortunately not, I had some other devices that didn’t work with OpenHAB at all

First I’ll concede that Zwave-js (the zwave “binding” or “Integration”) for HA has more devices configured as the HA user base is bigger. However, any ZW device can be added to the OH binding (like you did in solving this thread). In addition, I have added devices from the OH ZW DB that were missing from Zwave-js ZW DB, so it goes both ways to some degree.

Also possible: I’m using [Zwave-js with OH](https://community.openhab.org/t/zwave-js-ui-in-place-of-oh-zwave-binding/150007). So have the best of both worlds (IMO).

---

<div class="post-metadata">

**Author:** ![zynex](https://community.openhab.org/letter_avatar_proxy/v4/letter/z/c0e974/32.png) [@zynex](https://community.openhab.org/u/zynex)\
**Post date:** [July 27, 2024, 3:13pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/16 "2024-07-27T15:13:22Z")

</div>

That’s true. The issues I had was with Zigbee though, a couple of the devices didn’t work. The got discovered, but most entities didn’t work at all with OH (missing sensors), but did with HA. I had some stability issues with OH to unfortunately, while HA works excellent with my current setup (just some minor hiccups).

---

<div class="post-metadata">

**Author:** ![Oden](https://community.openhab.org/letter_avatar_proxy/v4/letter/o/ccd318/32.png) [@Oden](https://community.openhab.org/u/Oden)\
**Post date:** [July 29, 2024, 1:36pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/17 "2024-07-29T13:36:44Z")

</div>

Thanks. I have just made the update to all three things. I suppose I will have to wait for the next heal-time for it to take effect.  
I will let you guys know the outcome.

---

<div class="post-metadata">

**Author:** ![apella12](https://community.openhab.org/user_avatar/community.openhab.org/apella12/32/117154_2.png) [@apella12](https://community.openhab.org/u/apella12)\
**Post date:** [July 29, 2024, 1:46pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/18 "2024-07-29T13:46:25Z")

</div>

> [@Oden](#):
>
> I suppose I will have to wait for the next heal-time for it to take effect

FYI The Association group update should happen when the battery device wakes. The network heals for battery devices also occur upon waking, not at the time configured on the UI controller page.

---

<div class="post-metadata">

**Author:** ![Oden](https://community.openhab.org/letter_avatar_proxy/v4/letter/o/ccd318/32.png) [@Oden](https://community.openhab.org/u/Oden)\
**Post date:** [July 29, 2024, 8:17pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/19 "2024-07-29T20:17:48Z")

</div>

Thanks. I am not on site, helping a friend. Hopefully, the devices will wake up at regular intervals. There is not much in way of documentation from the manufacturer…

---

<div class="post-metadata">

**Author:** ![Oden](https://community.openhab.org/letter_avatar_proxy/v4/letter/o/ccd318/32.png) [@Oden](https://community.openhab.org/u/Oden)\
**Post date:** [August 13, 2024, 6:15pm UTC](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769/20 "2024-08-13T18:15:37Z")

</div>

No luck. 2 weeks later and all linked items are still NULL. They must wake up occasionally, right?  
In OH 2.4 I recall that you could see whether a setting was pending or “committed”/received but cannot seem to find the same in OH 4.2.  
Do you know if a wakeup or poll or something can be seen?

[Next page](https://community.openhab.org/t/solved-adding-new-device-on-opensmarthouse/144769.md?page=2)