Problem with Shelly new ht plus sensor

Confirmed!

Anyone still having trouble with this
works well over MQTT with the default mosquito addon for HA

MQTT code in mqtt.yaml

# Shelly Plus HT sensor
    - name: "Temperature C"
      state_topic: "shellyplusht-c049ef88edb4/status/temperature:0"
      value_template: "{{ value_json.tC}}"
      unit_of_measurement: "°C"
      device_class: "temperature"
      icon: "mdi:thermometer"

    - name: "Temperature F"
      state_topic: "shellyplusht-c049ef88edb3/status/temperature:0"
      value_template: "{{ value_json.tF}}"
      unit_of_measurement: "°F"
      device_class: "temperature"
      icon: "mdi:thermometer"

    - name: "Relative humidity"
      state_topic: "shellyplusht-c049ef88edb3/status/humidity:0"
      value_template: "{{ value_json.rh}}"
      unit_of_measurement: "%"
      device_class: "humidity"
      icon: "mdi:water-percent"  
1 Like

Using DuckDNS with Let’s Encrypt certificates and https.

Shelly Plus H&T with latest firmware 0.14.1.

Outbound Websocket set to Connection Type: Default TLS and Server: wss://FQDN:8123/api/shelly/ws

This results in the Shelly Plus H&T showing that it is connected to HA via Websocket, but no entities visible in HA.

The solution for me was to add an additional port forwarding rule in my router to forward external port 443/tcp to internal 443/tcp port to my Home Assistant instance.

Previously, I only had a rule to forward port 8123/tcp, and that triggered the problem of having a Shelly Plus H&T device show up in Home Assistant with no entities.

Did you ever get the spikes figured out? I’m seeing this now too even with the newest Shelly firmware and Home Assistant 2023.4.5

I also noticed that it will also spike if you reload the Shelly unit and spike higher after each instance of a reload. When the Temp changes, it will go back down to normal. It’s almost like the C->F is being applied each time it reloads.

1 Like

JUST tested, looks like it’s still happening. The arrow is a HA restart I just did:

The spikes for me happen when I manually wake up the HT as well. Any ideas?

1 Like

For what it is worth, I got two new HT Plus sensors that came out of the box with firmware 20230220-122828/0.13.2-plushtprod3-g4961547 and had no problems setting them up

  1. Insert batteries
  2. Click reset button once
  3. Connect to the AP
  4. Configure Wifi settings
  5. Save
  6. Wait for device to connect to wifi, and load the device’s page from my PC
  7. Configure the outbound websocket with Default TLS and ws://IP:8123/api/shelly/ws (note I don’t have TLS setup on port 8123 for my HA instance)
  8. Save, Reboot device, re-enter setup mode with button click
  9. Add device to HA using builtin Shelly integration
2 Likes

But if you restart HA, do you get a temp spike until the unit updates?

Ramblurr
just followed your guide and after 3 frustrating days. The CRUCIAL part is - ensure that the device is in setup mode when adding device to HA integration.
All 6 entities now exposed with no frustrating ‘unknown’ signal for temperature and humidity sensors.
Back into the sauna for this little muffin.
This post should be in the FAQ
Pat

1 Like

I found this only worked when using

ws://homeassistant.local:8123/api/shelly/ws

Not ws://192.168.x.y:8123/api/shelly/ws

Hope this helps others that may be struggling

1 Like

cant thank you enought mate!

I have the same sensor, and it is working fine so far.

I’ve used the ws://192.168.x.y/api/shelly/ws

I’ve seen many trial and error attempts with ws and with wss.

ws = not secured, thus not certifcate required
wss = secured and therefore a certifcate is required.

as long it stays within your network, suggested this is ws.
no certificate selection is needed.

I had the issue that it dropped the status to unknown.
removed it, and re-added it manually from the integration page. and not working stable for at least 2 weeks already.

Followed these instruction,

  1. Once connected and the device was added to HA it was all grayed out like the image 1.
  2. Did a full reboot and it connected up straight away. If you look at the shelly app you will see it connected. Like image 2

Home Assistant 2023.8.3
Supervisor 2023.08.1
Operating System 10.5
Frontend 20230802.1 - latest

Shelly Plus H&T
Firmware: 20230503-095514/v1.13.0-g9aed950


Hope this helps

First experience with Shelly and might be my last. Cannot get HT or HT Plus integrated. None of the fixes from above have worked for me, except I have not tried MQTT and will probably not. I will limit this to HT Plus as that is the thread name.
HA Info:
HA 2023.8.4
Supervisor 2023.08.3
OS 10.5

Shelly Info:
HT Plus Firmware 20230803-125304/1.0.0-gaec0744
HT Plus Build 230803114014-7c705cbd-HEAD

Setup Description:
Using TLS with Lets Encrypt Certificate, internal DNS, internal NTP, FQDN used for both internal and external access with no issues. Verified HT Plus is using internal DNS. HA is in a DMZ and IoT is own network. No issues with traffic between networks seen. Have tried all versions of websocket config (ws://{{myip}8123/api/shelly/ws ssl_ca="*", wss://{myfqdn}:8123/api/shelly/ws ssl_ca= ca.pem and also my Lets Encrypt cert).

Issue:
Device is immediately connected with no entities. Checking HA debug can see http requests getting data and also can see with packet captures but the 8123 port appears to be getting re-transmitted.

I have already asked to return all the Shelly devices I just bought but was going to give this a chance to see if someone can provide some insight of possible issue or troubleshooting tips, this would be appreciated. Thinking I am not going to like the Temp and Humidity sensors for my use but was also wanting to use their EM devices.

Thanks in advance!

Update:
Upgrade came out to HA 2023.9.0 and had an update to Shelly integration that added support to a specific Shelly product. Decided to Update and try again. After update and configuring as outlined both the HT Plus and HT device are working. Still not sure if they will work for me, but at least now I can try them out.

Hello, this seems to be an everlasting problem no metter what HA version people are running.
I’m currently operating on:
Home Assistant 2023.10.3
Supervisor 2023.10.0
Operating System 11.0

I integrate my Shelly H&T plus quite smoothly, but without any data: it becomes a device without entities.

Anyone could find out what’s wrong with this device/integration, why it is so unreliable and how to fix this (for now and for good)?

Thank you

Introduction

I want to start off by expressing my deep appreciation for the contributors to this thread, especially @claessens, whose detailed post provided a foundational guide for my setup. While their guide was immensely useful, some things have changed over the past year—likely due to updates in both Shelly and Home Assistant. Hence, I’ve documented the process that worked for me, hoping to help others navigate the updated setup landscape.

Environment

  • Home Assistant Version: 2023.10.3
  • Shelly Plus H&T Firmware: 20230912-081941/1.0.3-g6176478
  • Hardware: gen2 (SNSN-0013A)

Steps to Follow

  1. Integrate Shelly in Your Network with Shelly App: Initiate by connecting your Shelly H&T Plus to the same network as your Home Assistant. This can be done during the initial onboarding via Bluetooth through the Shelly app.
  2. Find Outbound Websocket Settings: Navigate to Settings > Networks > Outbound Websocket in either the Shelly app or the Shelly Cloud.
  3. Enable Outbound Websocket / “SSL Connectivity”: The straightforward option to enable the websocket was missing in my case. I had to enable an “SSL connectivity” switch and chose “*” from the dropdown menu. Some have opted for a pem file, but this setting worked for me.
  4. Enter WebSocket URL: Next, enter your WebSocket URL. For me, it was ws://192.168.1.157:8123/api/shelly/ws. Hit “Save” afterward.
  5. Wake Up Device: Press the small black button on the back of your Shelly H&T Plus device, next to the batteries. Wait a moment, then press it again.
  6. Trigger Device Reboot: Navigate back to the Shelly app or Shelly Cloud to initiate a device reboot. Wake up the device again using the small black button.
  7. Check WebSocket Connection: At this point, the connection should be established. If it’s not, troubleshoot and resolve the issue before proceeding to the next steps.
  8. Update Home Assistant: Remove any previous integrations of Shelly H&T Plus with Home Assistant if they exist.
  9. Final Steps: Wait for Home Assistant to detect your Shelly H&T Plus and add it as a new integration. I had to reboot Home Assistant to make the new device visible. Be patient, as it took several minutes for the entity and sensors to appear in Home Assistant.
6 Likes

Just got it working, here is a small write up: Go to your Shelly app and select your Shelly H&T Plus device > Settings > Networks > Outbound websocket ? select ca.pem. And write below it ws://192.168.1.xxx:8123/api/shelly/ws Offcourse replace the xxx with your own numbers. Then press save. Now re…

Thank You @claessens
This works…

…be careful with the case sensitivity. I had “/api/Shelly/ws” and not “/api/shelly/sw”

1 Like

Thank you for this guide!

It appeared to work for me, however I cannot get the sensors on my H&T Plus device to trigger home assistant automations.

Is there a special method for creating automations which operate as web socket consumers rather than the usual http polling method?

This fixed the issue for me. Thanks!
(Make sure you see the “connected” on the webhooks section on the shelly device)

After the update to 2024.1, the web hook option doesn’t seem to be working anymore on my 2 Shelly Plus H&T sensors. Did anyone else notice this?
The web GUI shows that it is connected, but nothing is showing up in HA.