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
Use as light switch in integration #155
Comments
I will check this |
Would getting the type from cloud work ? You can set socket or light in Shelly app. Simone |
Hi. Yes, good idea.. |
Hi guys, |
You can set that in config.yaml. see readme file. |
Thanks a lot @hakana |
I think the guy was talking about the integration way, wich shall ignore configuration.yaml when activated. |
It is not possible to set as light when using integration way. It will be possible in 0.1.8 |
That's nice
That's nice, thank you hakana. |
Can you please see if this work in the latest release 0.1.8 |
I also had same issue earlier. |
Are you running to integrations of ShellyForHass, one in config.yaml and on in UI? |
Using config.yaml with 0.16 (reverted to that because of this and issues with entity renaming on restart) First tried conversion to UI setup for 0.17 a few weeks ago. (reverted back to 0.16 then aswell) Any tips on how can I revert from UI setup to config-setup? Perhaps that would solve my issue? |
I am using the integration ui, still seeing them as switch and cant see the option to make them appear as a light. |
@SuperCocov9 The option to change them to light is only available when using config.yaml In the next release, it will check if you have set them to light in the app and use this setting and show them as light in HA. |
I also found this works as expected with the integration ui vetsion 0.16, and not anymore with 0.17 or 0.18. Using 0.16 you still have to define the light entity in the config.yaml. |
Added in 0.1.9-b1 |
Please update to latest beta (0.1.9.b1) and recheck. Simone |
At first sight, works like a charm! Many thanks! |
Don't take this the wrong way, but IMHO using the cloud setting is not a solution for the issue, just a "dirty" workaround. |
@d3m3trius I don't get your point, what do you think is wrong with using the settings from the Shelly app? I nether see how this is related to moving from config.yaml. We are moving from config.yaml but the GUI options for a integration in HA are very limited so there is no good way to configure device settings there. We work on a solution with a configuration page for Shelly where all options will be available. |
Same here. Nice |
I for one don't use any of the Shelly cloud functionality, and don't plan to. Only reason for using this integration is that the Shelly Plug S can't be flashed with custom firmware, which is the only way to guarantee devices are local only. Is this setting stored in "cloud", or on the device? |
@oscar-b For the users using the app it is a nice function as you see on the comments above. If you don't want to use the cloud you can configure that in the config.yaml or do your own light_switch templates. I don't agree that the only reason to use this is that Shelly Plug S not flashable for you. Majority using Shellys out of the box without flashing. So the option is still there for running 100% locally! BTW, why can't you flash your Shelly Plug S? |
The "problem" and confusion here is that functionality was removed; previously it was possible to setup a switch to be exposed as a light without using the Shelly app or using a template.
No of course not, but for me it is :) I prefer to know exactly what's running on my IoT devices, especially hardware. But this addon is really nice!
There are no exposed headers, and the shell seemed quite hard to open without breaking it. Running ESPHome on all my Shelly 1/2/2.5 otherwise :) |
Looked it up again, seems it is possible after all, will give it a try :) (ah now I remember, I needed the energy monitor support which ESPHome didn't have at the time at least). |
@hakana, good one; works really fine. Just one small improvement: can you delete the old "switch" when creating the new one as light ? Simone |
Im not sure if it good to do that automaticly and loose statistics etc. But I will have a look on that. |
@hakana One of the main use of HA (for me) is to avoid proprietary apps and cloud. |
Take care that this is your view, not mandatory for all other users.
Solution is already there: you need to configure each switch manually as light. Simone |
I've just tried the 0.19b1 but this doesn't work for me. I checked and the lights (on Shelly 1 devices) are set as lights but when I remove the integration and re-add they come back as switches :( |
Did you set your cloud key and server of shelly cloud on the integration? |
I hadn't and that fixes it perfectly...thank you!! |
Hi, I just found out this great integration. But I see too that shelly 1 devices will be set as 'switch' and cannot be changed to 'light' through the UI. Do I understand the above information correctly hat it will possible to change devices from 'switch' to 'light' in an upcoming update? I hope so :) Thanks! |
You can do that if you use config.yaml setting up ShellyForHass. We will add that in GUI shortly. |
and if you use Cloud, type can be loaded from Shelly App config ;-) Simone |
I’ll wait for it :) Thanks! Any rough idea about when this will be available? |
Nooo :) No cloud for me if it’s not necessary haha |
Hi.
Is it possible to get an option in the integration page to use shelly plugs as lights ?
I know I can do this by using light_switch: true i yaml but it would be rather nice having it in the integrations page :)
Thanks for all the great work !!
The text was updated successfully, but these errors were encountered: