Testing the fire alarm of the Shelly Smoke Plus by pressing and holding the push button for 3 seconds does not set the binary sensor to ‘on’. (but it will make sound)
Just got the same fire alarm and noticed the same. Not sure if bad implementation of HA integration or the Shelly firmware. It seems to differentiate between smoke and test in the Shelly app as well.
I set up one of these over the weekend and discovered the same. This is quite unexpected, since one cannot test automations. One is not supposed to make smoke just to test this, so I don’t see any other way to perform a real test.
@Bieniu apologies for tagging you like this, but perhaps there’s a good reason for this.
Please open an issue on GitHub and attach the debug log for Shelly integration from the test.
OK awesome, I’ll do that a bit later. Thank you.
Do I then log this under the core repo or the aioshelly lib that core uses?
For visibility: Shelly Smoke test alarm isn’t turning its binary sensor on · Issue #100948 · home-assistant/core (github.com).
I realised I don’t need the binary sensor to turn on for a test alarm, because:
- One can create a webhook for the test alarm by configuring an action via the Shelly app or web UI (tested and works).
- One can use the HA dev tools to set a sensor’s state for the purposes of testing (this allows me to test my automations).
As Bieniu pointed out on the GitHub issue, we agree that the semantics of a real and test alarm shouldn’t be mixed. If anything, there should be a separate test sensor.
Hello how are you ?
Can I ask you something ?
After two minutes the shelly smoke goes back to normal mode and after that I can not ping anymore or use the web interface?!
How can I test whether the smoke detector maintains connection with homeassistant?
Yes I did set the websocket: ws://192.168.x.xxx:8123/api/shelly/ws
is this normal behaviour?
thanks
Yes, it’s in the manual: it goes into deep sleep mode to save the battery, but will trigger just fine if something’s detected (it will wake up).
Please don’t take screenshots of forum text (or code/config). Highlight the text and hit “quote”.
You need to be more specific about where you’re getting stuck and what you’ve tried or read.
- Go to the Shelly config page by visiting the device’s IP address. There is a section to configure a webhook. Create and automation to trigger on this webhook.
This example will trigger on either a real signal or a test one:
- alias: "Alert When Smoke Detected"
trigger:
- platform: state
entity_id:
- binary_sensor.kitchen_smoke
to: "on"
id: "real"
# https://shelly-api-docs.shelly.cloud/gen2/ComponentsAndServices/Smoke/
# curl -s -X GET http://<host>:<port>/api/webhook/kitchen_smoke_alarm_test
- platform: webhook
webhook_id: kitchen_smoke_alarm_test
local_only: true
# HTTP GET and HEAD requests are not enabled by default
# https://www.home-assistant.io/docs/automation/trigger/#webhook-trigger
allowed_methods:
- GET
id: "test_kitchen_smoke"
# etc.
- Under the HA dev tools you can select an entity, input a state into the input box and hit the set state button. In other words, you can set a test state for your smoke detector without actually having to trigger the device with a real flame/smoke (not advised). In my example above you’d set it for
binary_sensor.kitchen_smoke.
Do you have an example of how to set the Webhook on a Shelly Smoke?
It’s not in the GUI right now. Maybe you can add this to the topic?
Welcome to the forum.
Mine is a Shelly Smoke Plus. Perhaps your model doesn’t have it or you need a firmware update.
Either way, I think they call it “actions” on the web UI. I need to wake one up to double check, but I can’t do that right now.
Look at the screenshot here:
Shelly Plus Smoke web interface guide
Yes, thanks I have found it!!
1 Like