-
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
discovering shelly devices #468
Comments
Your configuration is deprecated, read the documentation to avoid this message.
You can find information about MQTT options in the documentation: https://www.home-assistant.io/integrations/binary_sensor.mqtt/#expire_after |
thanks, @bieniu Note that the device is discovered with the Shelly integration with the CoIoT protocol, but I want to switch to MQTT I did not find anything useful in the docs. What step am I missing to access the device in HA?
|
If your config looks like this sensor:
- platform: mqtt it is deprecated.
I don't know 🤷♂️ I won't guess what your configuration looks like. If you have a problem with the Shellies Discovery script, please open a ticket and describe it. If you need help setting up MQTT... sorry, but this isn't the place to do it. |
Hi,
I came across your blog with the templates for MQTT Shelly integration with HA
Based on your template, I created an entry for a Shelly i3 device and restarted HA, but I do not see this device.
Before I install your automated device discovery tool, I want to be able to find my device and understand the various entries in the template.
When I test the MQTT integration by publishing a "shellies/command; announce" I get several messages from the device. This indicates that the communication configuration is OK.
I entered the template for the i3 (with the device id, and a chosen name), but after restarting HA, I get the following error message in HA:
btw, your template has the field:
expire_after: 604800
, is that necessary?does it mean that if the device was silent for a week it should be removed?
The text was updated successfully, but these errors were encountered: