Comments (9)
It turns out those entities came from the native Shelly integration. I must have enabled it a long time ago and had completely forgotten about it. I am now only using MQTT via Shellies Discovery. Thank you so much for your help in debugging this - much appreciated.
from ha-shellies-discovery.
Your trigger configuration is invalid, example of a valid configuration:
- platform: device
domain: mqtt
device_id: 8b0d2dd5099fa8d8664ab14cd4a30f87
type: button_long_press
subtype: button_1
discovery_id: shelly1l-xxxxxx-input-0 button_long_press
from ha-shellies-discovery.
Thank you, I will try that.
I think I found the problem: When I add a device trigger for the Shelly, the first five options are as follows:
- "First button" released
- "First button" continuously pressed
- "First button" pressed
- Button long clicked
- Button single clicked
I selected the Button long clicked, which resulted in yaml like I mentioned above. But selecting "First button" continuously pressed results in the yaml you showed.
What's the reason for the "Button * clicked" options? Can you remove the options if they should not be used?
Also: I suggest to rename "First button" continuously pressed to "First button" long press
from ha-shellies-discovery.
I think I found the problem: When I add a device trigger for the Shelly, the first five options are as follows:
Where do you see these triggers? Only the first three are available:
Also: I suggest to rename "First button" continuously pressed to "First button" long press
These are default strings coming from HA not from Shellies Discovery.
from ha-shellies-discovery.
They are right there after I select to "show 11 more":
These are default strings coming from HA not from Shellies Discovery.
Ok, I see. I guess this wouldn't have been an issue if the "Button long clicked" trigger weren't there to cause the confusion in the first place.
from ha-shellies-discovery.
Show me please the triggers section in MQTT Info for this device.
from ha-shellies-discovery.
from ha-shellies-discovery.
This may be related: I noticed that my Shelly has two controls, while yours has just one (Sterowanie):
The top one is switch.livingroom_salon_table_light_switch_relay_0 while the bottom one is light.shelly1_93ef98. Should I have both? Keep in mind I have had Shellies configured with your HA extension for a few years, so there may potentially be some stuff that has not been properly cleaned up along the way.
These are the 8 entities that belong to the device:
The switch belongs to the MQTT integration, not Shelly:
If I go to Integrations->MQTT-> x devices, I get this:
Should they be doubled up like this? If no, which do I get rid of and any suggestions as to how?
from ha-shellies-discovery.
I think those entities and triggers come from ShellyForHass custom component and are not related to Shellies Discovery.
from ha-shellies-discovery.
Related Issues (20)
- Improve sensor templates
- Remove Wh -> kWh conversion
- Devices naming similar to Native Shelly Addon HOT 1
- Feature request: add long- and shortpush sensors again please HOT 5
- Support for SHCB-1 (Shelly Bulb RGBW GU10) HOT 12
- Shelly Door/Window 2 always show up as unavaliable after a restart of home assistant HOT 1
- Please add support for Shelly 3EM sensors when using the optional neutral current transformer
- Info: "mqtt":disabled? HOT 4
- SystemError: AST constructor recursion depth mismatch (before=33, after=60) HOT 10
- discovering shelly devices HOT 3
- Shelly UNI second binary input is not mapped
- Invalid event type error in logs HOT 1
- Invalid event type with latest version HOT 4
- TRV - Mapping valve_min_report and calculation of Idle/Heating mode HOT 10
- error: The device name prefix will be stripped... HOT 2
- Shelly Gen1 is not discovered correctly HOT 3
- Entities become unavailable when the battery-powered device goes to sleep with firmware 1.1.0
- Shelly UNI "ext_" parameters implementation to sensor HA block (entity) HOT 2
- Problem with Shelly Dimmer and MQTT connection flag. HOT 4
- Shelly Plus2PM announces with changed attributes HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ha-shellies-discovery.