No, homeassistant.components.mqtt.device_trigger is for device automation triggers.
You can use this if you want see device triggers:
logger:
default: warning
logs:
homeassistant.components.mqtt.device_trigger: info
Sorry Bieniu, I misunderstood and I was too fast…
So, when the INFO from device_trigger is generated?
Let me be precise on the motivation then:
- I have a log of Shellies in the house and therefore I can see a lot of logs appearing every hour. I guess over 80% of my logs are Shelly_Discovery entries. Searching thru the log is… hmmm annoying. I just wanted to find a workaround to disable Shelly Discovery logging. Also My Shelly set is stable and I’m not adding new Shellies for months.
- I’m a bit concerned about switching logs
...mqtt.device_triggerto WARN by default as I think I can miss some important reports from the other MQTT devices/integrations - Finally… turning the automation OFF and ON can be done simply from the UI (pushing a button) while changing log is changin a files+reloading etc…
Therefore… I just wanted to know if, in a situation like mine (stable set of the devices), temporary disabling of shelly_discovery automation is OK? Do I risk loosing anything important? In which situation I should re-enable shelly_discovery automation (Ha Update? Shelly Firmware Update? Adding new Shelly? Others?)
I think such information may be helpful also for the community
After event, for example shortpush, longpush.
So set for homeassistant.components.python_script warning or error.
After each Shelly Discovery update. But I don’t recommend disabling the discovery automation.
@Bieniu Since our previous conversation, all my shellies are up and integrated.
Now in my slow progression, it’s look like a device could be integrated as a switch or a cover but not both. my 2.5 come as a switch (they are in roller mode) and I rather have them in cover which is needed to make a lovelace card with slider.
Any idea how to change switch to cover ?
Please read the documentation or open post.
Sorry @Bieniu , can’t find any relevant info in the last 2 hours reading the docs. do you have a link ?
do I need to delete the switch integration before trying to create a cover ?
here you learn about cover but don’t explain how to create one.
here all about template cover , which just add to the confusion do I need a template ?
can’t find anything in your github repo.
nothing on Shelly side neither …
best I could find was here
Auto discovery is fantastic, just missing the explanation to get a cover for my 2.5 to finally be able to use it within lovelace.
I saw that, but that don’t explain how to get a cover entity from it.
Looking for a way to have something like that in my entities list
all I got is that (also show all the sensors in dev tools)
all the 2.5 was in roller mode (shelly ip webpage setting) before integration.
Use this example in your script configuration.
Have been trying to get the script working for hours but just won’t work, it’s 100% something I am doing wrong but after searching everything here still can’t find the problem.
What am I doing wrong?
Kind regards
So I have tested the hello_world.py and it is working. What is the next step?
The shellies_discovery script still can’t be found.
I think you are using service service: python_scripts.shellies_discovery but you should service: python_script.shellies_discovery in your shellies_discovery automation.
So you have to check your configuration. mode is missing.
Sorry for this but I am still new to HASS and MQTT, do you mean check the announce message in MQTT explorer, the configuration.yaml, automation.yaml or shellies.discovery.py?
What about automation?
Your script configuration is not valid. Remove shellyrgbw2-80A423: 'rgbw' line.
Big thanks legend, it’s working now.
In what use case would I add the shellyrgbw2-80A423: ‘rgbw’ line?