# Openhab shelly i4dc addon channels missing

**URL:** <https://community.openhab.org/t/openhab-shelly-i4dc-addon-channels-missing/149461>\
**Category:** Bindings\
**Tags:** shelly-binding\
**Created:** [September 9, 2023, 4:41pm UTC](https://community.openhab.org/t/openhab-shelly-i4dc-addon-channels-missing/149461 "2023-09-09T16:41:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![d\_valchev](https://community.openhab.org/user_avatar/community.openhab.org/d_valchev/32/14947_2.png) [@d\_valchev](https://community.openhab.org/u/d_valchev)\
**Post date:** [September 9, 2023, 4:41pm UTC](https://community.openhab.org/t/openhab-shelly-i4dc-addon-channels-missing/149461/1 "2023-09-09T16:41:51Z")

</div>

Hi all,

I connected Shelly Plus Add-On to Shelly Plus i4 DC (FW: 1.0.0-gaec0744).  
The device has been discovered by the binding but no Add-On channels, like sensors, configured to the thing (i4DC’s ones are OK). However, OH Shelly Binding docs completely missing this scenario - attaching Shelly Plus Add-On to Shelly Plus i4 DC. So, my question is if this is something that could be easily added as supported binding feature? Also, how can I create manually the channels … if possible at all or this could be supported via binding only?

I’m new to the Shelly items and apologise if my questions are stupid.  
10x

Edited: I’m running OH v 4.0.2

---

<div class="post-metadata">

**Author:** ![Oliver2](https://community.openhab.org/letter_avatar_proxy/v4/letter/o/df705f/32.png) [@Oliver2](https://community.openhab.org/u/Oliver2)\
**Post date:** [September 9, 2023, 9:28pm UTC](https://community.openhab.org/t/openhab-shelly-i4dc-addon-channels-missing/149461/2 "2023-09-09T21:28:16Z")

</div>

You better ask this question in this thread

> [@Shelly Binding](https://community.openhab.org/t/shelly-binding/56862):
>
> Hi, I started to develop a binding for Shelly products. I have a Shelly1 and a Shelly2. These will be implemented and tested for the time being, the rest of the product family I will implement as well as possible, but can not test. Is there any interest in having the binding published in due course? I’m only doing it because I wanted to work on programming bindings and I’m not really a fan of MQTT slight_smile You can just contact me and let me know if someone is interested or not.

This is where the maintainer answers questions

---

<div class="post-metadata">

**Author:** ![d\_valchev](https://community.openhab.org/user_avatar/community.openhab.org/d_valchev/32/14947_2.png) [@d\_valchev](https://community.openhab.org/u/d_valchev)\
**Post date:** [September 10, 2023, 7:38am UTC](https://community.openhab.org/t/openhab-shelly-i4dc-addon-channels-missing/149461/3 "2023-09-10T07:38:45Z")

</div>

Thanks @Oliver2, as recommended I created new post.

---

<div class="post-metadata">

**Author:** ![Riccardo1979](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/3be4f8/32.png) [@Riccardo1979](https://community.openhab.org/u/Riccardo1979)\
**Post date:** [April 27, 2024, 3:15pm UTC](https://community.openhab.org/t/openhab-shelly-i4dc-addon-channels-missing/149461/4 "2024-04-27T15:15:15Z")

</div>

Hi, have you solved the problem with the temperature probes on ADDON? because I also have the same problem…thank you

---

<div class="post-metadata">

**Author:** ![d\_valchev](https://community.openhab.org/user_avatar/community.openhab.org/d_valchev/32/14947_2.png) [@d\_valchev](https://community.openhab.org/u/d_valchev)\
**Post date:** [April 27, 2024, 5:36pm UTC](https://community.openhab.org/t/openhab-shelly-i4dc-addon-channels-missing/149461/5 "2024-04-27T17:36:20Z")

</div>

@Riccardo1979,

After waiting couple of months for the binding to get supported the i4DC I decided to use http binding to retrieve the values out of the addon.

**http.items**

```auto
...
Number DS18B20_Temp1 "Temp [%.1f °]" <temperature> (gTempSensors) ["Measurement", "Temperature"] {
    channel="http:url:<id>:http101"
}
Number Power_Supply "Power Supply [%.1f V]" <energy> (Sensors) ["Measurement", "Voltage"] {
    channel="http:url:<id>:http100"
}
...

```

**http thing** sample (configured via UI)

```auto
UID: http:url:<id>
label: Shelly AddOn HTTP
thingTypeUID: http:url
configuration:
  authMode: DIGEST
  ignoreSSLErrors: true
  baseURL: http://<shelly_ip>
  password: '<your_shelly_password>'
  delay: 5
  stateMethod: GET
  refresh: 60
  commandMethod: GET
  contentType: text/plain
  timeout: 9000
  bufferSize: 2048
  username: <shelly_login_user>
channels:
  - id: http101
    channelTypeUID: http:number
    label: AddOn Channel 101
    description: http:shelly:sensor:temperature:101
    configuration:
      mode: READONLY
      stateExtension: /rpc/Temperature.GetStatus?id=101
      stateTransformation: REGEX:.*\"tC\":(\d*.\d*).*
  - id: http100
    channelTypeUID: http:number
    label: AddOn Channel 100
    description: Get Shelly Voltage via HTTP
    configuration:
      mode: READONLY
      stateExtension: /rpc/Voltmeter.GetStatus?id=100
      stateTransformation: REGEX:.*\"voltage\":(\d*.\d*).*
...

```

Not sure but I think the shelly binding still doesn’t support i4dc with addon.

---

<div class="post-metadata">

**Author:** ![Freeride79](https://community.openhab.org/letter_avatar_proxy/v4/letter/f/3bc359/32.png) [@Freeride79](https://community.openhab.org/u/Freeride79)\
**Post date:** [May 18, 2024, 7:49am UTC](https://community.openhab.org/t/openhab-shelly-i4dc-addon-channels-missing/149461/6 "2024-05-18T07:49:17Z")

</div>

Hello Dimitar,  
I have been using several temperature sensors via Shelly 1 add-ons for several years. All integrated without any problems via the Shelly Binding. With the new Shelly Plus1 PM with addon, I don’t see any temperature values either. I spended hours to test and update and finally I coppied your code to the http thing and I was ready within 5 Minutes.  
Looking out of the box can be quite helpful.  
Thanks for your solution!

```auto
UID: http:url:test
label: Shelly temp http
thingTypeUID: http:url
configuration:
  authMode: DIGEST
  ignoreSSLErrors: true
  baseURL: http://xxx.yyy.zzz.iii
  delay: 5
  stateMethod: GET
  refresh: 60
  commandMethod: GET
  contentType: text/plain
  timeout: 9000
  bufferSize: 2048
channels:
  - id: http101
    channelTypeUID: http:number
    label: AddOn Channel 101
    description: http:shelly:sensor:temperature:101
    configuration:
      mode: READONLY
      stateExtension: /rpc/Temperature.GetStatus?id=101
      stateTransformation: REGEX:.*\"tC\":(\d*.\d*).*
  - id: http102
    channelTypeUID: http:number
    label: AddOn Channel 102
    description: http:shelly:sensor:temperature:102
    configuration:
      mode: READONLY
      stateExtension: /rpc/Temperature.GetStatus?id=102
      stateTransformation: REGEX:.*\"tC\":(\d*.\d*).*
  - id: http103
    channelTypeUID: http:number
    label: AddOn Channel 103
    description: http:shelly:sensor:temperature:103
    configuration:
      mode: READONLY
      stateExtension: /rpc/Temperature.GetStatus?id=103
      stateTransformation: REGEX:.*\"tC\":(\d*.\d*).*
  - id: http100
    channelTypeUID: http:number
    label: AddOn Channel 100
    description: http:shelly:sensor:temperature:100
    configuration:
      mode: READONLY
      stateExtension: /rpc/Temperature.GetStatus?id=100
      stateTransformation: REGEX:.*\"tC\":(\d*.\d*).*

```