Today I purchased 2 Shelly 1 to manage and automate garden lights. While waiting for the mail I was wondering and looking around how to integrate them into HA, what is the plan ofcourse. I can't believe I found your excellent tutorial, just because it is you again (after yesterdays VMM migration). It's coinicidental and funny at the same time. Seriously: after this video, I know what to do. I was allready in the thinking proces of flashing them and using MQTT and the lots. But I am convinced to skip all that now. Bring on the mail, I'd say!
With 150+ videos, I pop-up a lot! 😂 Glad you found it and that it was useful. Yeah, Shelly should work out of the box - no matter what type of integration you use.
I am using Shelly 1, 2.5, gas, shelly duo bulbs, plug s, and HT. Well, my experiences, based on a direct comparison between MQTT and integrations are on the MQTT side. Reason: switch responsiveness, humidity and temperature sensors information (especially battery-powered ones) - better and more stable via MQTT. For those using IoT network segmentation (firewalled subnets for this purpose), MQTT seems to work even faster. My observations were made on UDM network gear supported with 2 AP's. Yet another benefit I see is better automation functionality (ie. dimmable shelly duo's). The good thing is, Mqtt can be used in parallel with integration. So the user can pick an entity that suits (works) the best for a particular need. What I found easier to deal with is power monitoring and reporting over integration. MQTT sensor requires extra configuration to translate power units to kWh. I did not decide to integrate MQTT within hass.io, I am using it with three other self-hosted services, thus integrations only would not feed them. One of these is homebridge which helps me to integrate with other equipment. My homekit integration allows me to compare the responsiveness in home app, and here MQTT based switches and sensors work flawlessly. The integration allows picking individual entities to be exposed to the Home app. This helps to avoid exposing duplicated entities to the app. In my opinion, MQTT gives better transparency than integration, too. To wrap up, my personal opinion is that Shellies are currently the best pick due to the software capability.
Thanks for the time for the comment Tom - much appreciated! As I was playing a bit more with Shelly Gas today, ended using MQTT to add them to HA. Reason, lack of information from both internal Shelly and also ShellyForHASS integration. Some sensors were missing and I really wanted to be able to see them in HA: As I mentioned in the video, my experience was just with 2 type of devices - EM and plug s. Now I've added GAS and it's completely different story. Waiting for Shelly Uni and 1L to arrive - according to current status, they will also work better with MQTT as they are still having issues/bugs with Shelly for Hass. Great thing is that we have options and as you said, we can use them in parallel.
@@BeardedTinker Thanks for you your kind words. I forgotten to add that I use 1L in my gear, too. Works like a charm under mqtt, I did not even bother myself to use integrations. Initially I wanted to use this one for L-only connection, ended up with setting this in my 2-way switch which was built with 3- instead of 4 wires between the switches. Accidentally I solved the other issue, not even using the additional bypass from Shelly. So 1L is a really great stuff. Oh yeah, and my automations are supported with built-in feature (shelly software) - some switches turn off after given time set directly on shelly firmware. That's eliminates a need for additional HA automations and works perfectly well for these switches my kids leave permanently on.... You know... Fathers' life...
@@tomgrey3046 just to add on this - looks like MQTT version is working great, but also Internal Shelly integration is providing some entities that ShellyForHASS doesn't give. But yes, MQTT works greate here.
Note - the HACS way is outdated and does not work anymore. Spent a few hours trying until I noticed the repo wasnt maintained in favor for the HA integration.
Nice video which covers all the essentials and runs at a good pace. I have been trying out the new Shelly 1L for single wire light circuits which seems to work well.
Thank you Mark - really much appreciated!!! I'll be doing some more videos on Shelly devices in future. Definitely will try Smoke sensor, Motion sensor, but I ant also to try and add them to my switches that have no neutral wires.
More a shelly specific question. Will the device keep on working (give power to washingmachine for example) if there is no Wifi available or HA is down?
Yes, it will work. It will keep last state it had if WiFi connection is lost for a moment. Flashing the firmware will on the other hand reset power - so if you are running washing machine it would lose power for couple of seconds. In terms of power restore (if you lose power), it depends on what you selected in setup - it can be last state, off or on. More then you asked, but should cover everything ;)
Hi, thanks for the video. Have you noticed one problem with the shelly plug? I see the voltage is around 134v, and it's always a flat line. I don't think it's accurate. My other meters are measuring 120v~ I already updated all the firmware, just curious if you have ever noticed that problem? thanks
Can you help me? I tried everything and all the times that I try to turn a shelly device on in HA it turn immediately off... or vice versa... this is driving me crazy.
What device and what integration are you using? I see this behaviour only if you are using physical switch with wrong state set. (for example using push button for switch or switch for push button)
@@BeardedTinker I tried to change that on shelly but without any success, I'm not using fisical buttons. I'm using Shelly for Hass and I've Shelly1pm and Shelly EM both connected to shellyforhass over cloud. I cant ping them on my raspberry. LOG: Timeout connecting to 192.168.1.4/relay/0?turn=on [192.168.1.4] 5:39:19 PM - (ERROR) Shelly smart home (custom integration) - message first occurred at October 24, 2022 at 7:35:01 PM and shows up 5 times
Great tutorial ! I'm running Homeseer 4 but they do not have a CoAP/REST integration for free, there is a $40 plugin. Also there is no simple plugin for influxdb/grafana with HS4. I'm awaiting my delivery of 1st shelly device which is a 3EM to monitor my house usage. I do not want to loose the shelly cloud functionality, yet want to push data to influx/grafana, seems like HA built in integration is the way to go as it also has addons for influx and grafana. Thinking of spinning this in a docker container. Comments on any latest updates since you did this video will be helpful. - thanks !
I really love the possibilites to tinker around Home Assistant and expand it with addons as my as I like. But just a warning, if you go for Docker version (which works great) - you will not be able to use integrated installer for Add-Ons. Most of them can be installed as Docker images, but don't have automatic configuratio that normal add-ons have (for example security token, etc). For that you'll need Supervised or OS version of Home Assistant. That one has everything included - I run it in Virtual Machine (on Synology). And to add - I don't have Shelly cloud enabled - all is available from within Home Assistant, but I could have that too if I would need it.
Hoping to have my first Shelly Plug set up tomorrow. Still trying to decide which way to go as far as integration. Same with my Tuya devices. Part of me wants to get them off of cloud services. But I'm concerned about how it will affect current integrations with my Google Home Assistant voice control.
For Shelly, I dont think you can go wrong way whatever you opt for. And also, you can run integration in parallel, but in long term it's bad idea as you get them duplicate devices. Also, if you create Google Assistant integration, you can control any device from Home Assista, using Google home even if they don't have native control.
Would you recommend putting one of this behind every light switch? Would that be better then say going with lutron smart switches? what is the reliability and long term performance of the shelly? i have a unifi wifi 6 network
Excellent question that is not that easy to answer... It all depends - if you have neutral wires in wall switches or not. There are model that support no-neutral, but it adds to complexity. I've never tested Lutron switches, so can't compare them, but in terms of retrofit, Shelly is excellent choice if you want to leave your current wall mounted switch and add "smart" to it. I've on the other hand opted to "smart" bulbs - that way, all (most) my switches remind the same, while each bulb is individually controlled. This adds to the cost, but also allows much higher flexibility to control lights. In terms of reliability - so far I haven't had any issue (except with 2 sensors I have from Shelly, but that's different story) with any power control device from them. And some are 2+ years old.
I have shelly devices on multiple locations (via the same cloud accouynt) and want to monitor their sensors in Home assistant. How would you recommend i do that? i am quite desperate to find a easy solution
None of the current integrations pull data from the cloud. The only way (but I never tried it) would be to use MQTT service on each device and have it send data to (publicly available) MQTT service. But that's also a big security risk as MQTT servers are not known for their security.
As i know, shelly devices is supporting homekit. İf we replace the firmware with homekit, can we add this devices with homekit entegration on the homeassistant?
There is a open source version of firmware that brings HomeKit compatibility. I didn't try it so can't tell you how good it works. But yes, you should be able to add them to HA with it. At least it does say that it is compatible with stock firmware.
Hello, great video. Finally I could see an on line configuration of a shelly device. You mention the non necessity of configuring thru mqtt because the own Shelly integration is fine. In any case, I'm trying to configure it thru mqtt, but no way!. Have you a similar video, but with mqtt configuration for Shelly devices?. On the other hand, for ShellyEM device, there is one sensor not read with the Shelly own integration, and it is the reactive_power, and I'm totally lost on how to retrieve such information in HomeAssistant. Does anyboday know how to solve it?. THANKS
Hi and thanks for the comment and sorry for late reply - busy day :) I do use MQTT for some of the sensors from Shelly, but not all. I did record video on how to use Shellies autodiscovery to add Shelly devices with MQTT - here is the link to video and I hope it helps. It is part of this video: th-cam.com/video/ylCt45JUkOg/w-d-xo.html You can find time stamp for it in video description.
@@BeardedTinker I had my shelly connected to a firewalled vlan that didn't have internet access (like all my IoT devices). I didn't see a way to manually upload the new shelly firmware so I had to give the shelly internet access to update. I took it offline after it was done.
Excellent question - most of the devices have fixed/static IP address. I've created ranges for devices based on type. This may be limiting if numbers go above what I have planned, but is now much easier to manage
Nice Video, but can you tell me what I have to type in Host* to connect to my Shelly 25? I tried several IP adresses Wb adresses which I can reach the Shelly via http from my network. But nothing worked!
This shoud be just IP address of the Shelly device - can't remember if you need in front or not - no specific port is needed. BUT don't forgert to configure CoIoT on Shylle device and specify your Home Assistant IP address with port 5683. This will definitly help with speed of actions.
Hi Andre! Well, to be honest, I can't - I would need access to it to test and record the process. From what I've seen, it can be done using HACS integration, and it didn't look that hard, at least for default/minimal installation. github.com/elupus/hass_nibe But, one of the prerequisite for it to work is to have Home Assistant exposed to the internet. Although it says that you can use it with http (without SSL), please, use with SSL certificate or https type of connection only.
Just done this following your guide as I previously used the official add-in but had hoped to find an alternative particularly for the DW2's who go offline on a restart. Unfortunately it seems this doesn't resolve that problem. More concerning however is The Shelly 1L offers all entities except the on/off! Guess i'll switch back to official integration, thanks anyway.
For DW2's, that could be problem by design since they go to sleep mode - are you on latest firmware there? But I find it strange that 1L is missing most important thing - switch. I'm still waiting for mine to arrive, but I know of few ppl using them without an issue. This is definitely showstopper. Sorry you had bed experience!
@@BeardedTinker No Problem and thanks for another excellent tutorial. With the DW2's yes latest firmware, its a real pain, maybe MQTT would resolve it, though I doubt it, seems its a design issue, I need to find another solution. Also unfortunate that the switch is missing, I have two of them as well. Not sure if it could have been hidden somewhere, I couldn't find it though.
Ok, got it - what is the 1L problem. Shellyforhass still isn't supporting it. github.com/StyraHem/ShellyForHASS/issues/486 There is 0.2.2 beta version that has a support for it, but looks like it also has a bug with it according to latest issue on GitHub. So, you can try using 0.2.2beta to see if it helps or not. Will search a bit about dw2
if shelly devices are not in the same network I can still integrate them in home assistant? I have different wireless networks because the devices cover a larger area and they are not all in the same network .
Excellent question! But since we are using local integration, no. There is a way or workaround for this, but it requires a bit more complex setup. If you would use MQTT and this MQTT would be in cloud or exposed, you could do it through MQTT server. In similar way, I'm sharing my devices between 2 HA, but they are in my case both on same network. The only difference would be that I would use public IP or domain name to connect to it. AFAIK it's not using Shelly Cloud app data for control. If it would, it would also be much easier to do what you are looking for.
@@BeardedTinker if I use routers in AP mode and I ensure on all devices the same range is ip 192.168.0.2-255 even if the networks have different names it is possible to see them home assistant? I saw that install for Windows from another movie on TH-cam after starts the server has great limitations. Is there an installer for Windows that has access to all server options after the installation is complete?
If there is connectivity and network flow, it should work. But you must have routing available between access points. If you are talking about Windows Python or Windows Docker version, they are limited. You should try and run Home Assistant in Virtual Machine on Windows, to get full functionality.
I have a shelly plug exactly like in the video. The video DOES NOT explain you how to connect it. He jumps over too many steps. I plugged it into power and then..... nothing. The video does not help you to integrate the shelly plug into Home Assistant.
Hi Martin and thank you for your comment - but I think you've posted comment under wrong video - this video is for integration of Shelly devices into HA - options you have, and NOT on how to plug it in and set it up. There is difference in configuring device an integration of the device. Not a single step has been jumped over and as this video is device neutral - it works with any Shelly device - after you set it up.
I am running shellys with mqtt (4x 1pm, 2x h&t, 2x D/W2, 1x RGBW) over MQTT (with the help of ha-shellies-discovery python script). I find the MQTT more stable (and it was the only noncloud option up untill 0.118 something). Usage is more or less painless. You can also hack a dirty automation to update all the devices at once (rgbw is sort of annoying as it cycles all colors) check my config at github.com/zeridon/homeassistant (well that is the whole stack i am using)
@@BeardedTinker yep, had to hack the luftdaten2mqtt stuff so i do not go over the internet to pull the data and as a personal preference like the push model.
Today I purchased 2 Shelly 1 to manage and automate garden lights. While waiting for the mail I was wondering and looking around how to integrate them into HA, what is the plan ofcourse. I can't believe I found your excellent tutorial, just because it is you again (after yesterdays VMM migration). It's coinicidental and funny at the same time. Seriously: after this video, I know what to do. I was allready in the thinking proces of flashing them and using MQTT and the lots. But I am convinced to skip all that now. Bring on the mail, I'd say!
With 150+ videos, I pop-up a lot! 😂 Glad you found it and that it was useful.
Yeah, Shelly should work out of the box - no matter what type of integration you use.
I am using Shelly 1, 2.5, gas, shelly duo bulbs, plug s, and HT. Well, my experiences, based on a direct comparison between MQTT and integrations are on the MQTT side. Reason: switch responsiveness, humidity and temperature sensors information (especially battery-powered ones) - better and more stable via MQTT. For those using IoT network segmentation (firewalled subnets for this purpose), MQTT seems to work even faster. My observations were made on UDM network gear supported with 2 AP's. Yet another benefit I see is better automation functionality (ie. dimmable shelly duo's). The good thing is, Mqtt can be used in parallel with integration. So the user can pick an entity that suits (works) the best for a particular need. What I found easier to deal with is power monitoring and reporting over integration. MQTT sensor requires extra configuration to translate power units to kWh. I did not decide to integrate MQTT within hass.io, I am using it with three other self-hosted services, thus integrations only would not feed them. One of these is homebridge which helps me to integrate with other equipment. My homekit integration allows me to compare the responsiveness in home app, and here MQTT based switches and sensors work flawlessly. The integration allows picking individual entities to be exposed to the Home app. This helps to avoid exposing duplicated entities to the app. In my opinion, MQTT gives better transparency than integration, too. To wrap up, my personal opinion is that Shellies are currently the best pick due to the software capability.
Thanks for the time for the comment Tom - much appreciated!
As I was playing a bit more with Shelly Gas today, ended using MQTT to add them to HA. Reason, lack of information from both internal Shelly and also ShellyForHASS integration. Some sensors were missing and I really wanted to be able to see them in HA:
As I mentioned in the video, my experience was just with 2 type of devices - EM and plug s. Now I've added GAS and it's completely different story.
Waiting for Shelly Uni and 1L to arrive - according to current status, they will also work better with MQTT as they are still having issues/bugs with Shelly for Hass.
Great thing is that we have options and as you said, we can use them in parallel.
@@BeardedTinker Thanks for you your kind words. I forgotten to add that I use 1L in my gear, too. Works like a charm under mqtt, I did not even bother myself to use integrations. Initially I wanted to use this one for L-only connection, ended up with setting this in my 2-way switch which was built with 3- instead of 4 wires between the switches. Accidentally I solved the other issue, not even using the additional bypass from Shelly. So 1L is a really great stuff. Oh yeah, and my automations are supported with built-in feature (shelly software) - some switches turn off after given time set directly on shelly firmware. That's eliminates a need for additional HA automations and works perfectly well for these switches my kids leave permanently on.... You know... Fathers' life...
@@tomgrey3046 just to add on this - looks like MQTT version is working great, but also Internal Shelly integration is providing some entities that ShellyForHASS doesn't give. But yes, MQTT works greate here.
Note - the HACS way is outdated and does not work anymore. Spent a few hours trying until I noticed the repo wasnt maintained in favor for the HA integration.
Thank you! Perfect information!
It's a bit old video now - most of those Shelly devices work now natively with Home Assistant, but yes, you can also use MQTT too.
Thanks for the info, this helped me to get my two new shelly devices working.
Glad I could help - have fun with them!!!
Nice video which covers all the essentials and runs at a good pace. I have been trying out the new Shelly 1L for single wire light circuits which seems to work well.
Thank you Mark - really much appreciated!!! I'll be doing some more videos on Shelly devices in future. Definitely will try Smoke sensor, Motion sensor, but I ant also to try and add them to my switches that have no neutral wires.
More a shelly specific question. Will the device keep on working (give power to washingmachine for example) if there is no Wifi available or HA is down?
Yes, it will work. It will keep last state it had if WiFi connection is lost for a moment.
Flashing the firmware will on the other hand reset power - so if you are running washing machine it would lose power for couple of seconds.
In terms of power restore (if you lose power), it depends on what you selected in setup - it can be last state, off or on.
More then you asked, but should cover everything ;)
Thank you sooooo much! This was the easiest and best way for le to integrate my new shelly plus devices into HA OS.
Great to hear - thank you for the comment!!!
Thanks! I'm adding a couple Shelly devices to my new HA setup this week and this helped a lot.
Thank you! Shelly really has some nice devices. Hope everything works for you!
Hi, thanks for the video. Have you noticed one problem with the shelly plug? I see the voltage is around 134v, and it's always a flat line. I don't think it's accurate. My other meters are measuring 120v~ I already updated all the firmware, just curious if you have ever noticed that problem? thanks
Actually non of my Shelly plugs measure voltage. Just watts. For voltage I have Shelly EM that's measuring total W/Wh used + it also has volts info.
Can you help me? I tried everything and all the times that I try to turn a shelly device on in HA it turn immediately off... or vice versa... this is driving me crazy.
What device and what integration are you using? I see this behaviour only if you are using physical switch with wrong state set. (for example using push button for switch or switch for push button)
@@BeardedTinker I tried to change that on shelly but without any success, I'm not using fisical buttons.
I'm using Shelly for Hass and I've Shelly1pm and Shelly EM both connected to shellyforhass over cloud. I cant ping them on my raspberry.
LOG: Timeout connecting to 192.168.1.4/relay/0?turn=on [192.168.1.4]
5:39:19 PM - (ERROR) Shelly smart home (custom integration) - message first occurred at October 24, 2022 at 7:35:01 PM and shows up 5 times
Great tutorial ! I'm running Homeseer 4 but they do not have a CoAP/REST integration for free, there is a $40 plugin. Also there is no simple plugin for influxdb/grafana with HS4. I'm awaiting my delivery of 1st shelly device which is a 3EM to monitor my house usage. I do not want to loose the shelly cloud functionality, yet want to push data to influx/grafana, seems like HA built in integration is the way to go as it also has addons for influx and grafana. Thinking of spinning this in a docker container. Comments on any latest updates since you did this video will be helpful. - thanks !
I really love the possibilites to tinker around Home Assistant and expand it with addons as my as I like.
But just a warning, if you go for Docker version (which works great) - you will not be able to use integrated installer for Add-Ons. Most of them can be installed as Docker images, but don't have automatic configuratio that normal add-ons have (for example security token, etc).
For that you'll need Supervised or OS version of Home Assistant. That one has everything included - I run it in Virtual Machine (on Synology).
And to add - I don't have Shelly cloud enabled - all is available from within Home Assistant, but I could have that too if I would need it.
Hoping to have my first Shelly Plug set up tomorrow. Still trying to decide which way to go as far as integration. Same with my Tuya devices. Part of me wants to get them off of cloud services. But I'm concerned about how it will affect current integrations with my Google Home Assistant voice control.
For Shelly, I dont think you can go wrong way whatever you opt for. And also, you can run integration in parallel, but in long term it's bad idea as you get them duplicate devices. Also, if you create Google Assistant integration, you can control any device from Home Assista, using Google home even if they don't have native control.
Would you recommend putting one of this behind every light switch? Would that be better then say going with lutron smart switches?
what is the reliability and long term performance of the shelly?
i have a unifi wifi 6 network
Excellent question that is not that easy to answer... It all depends - if you have neutral wires in wall switches or not. There are model that support no-neutral, but it adds to complexity. I've never tested Lutron switches, so can't compare them, but in terms of retrofit, Shelly is excellent choice if you want to leave your current wall mounted switch and add "smart" to it.
I've on the other hand opted to "smart" bulbs - that way, all (most) my switches remind the same, while each bulb is individually controlled.
This adds to the cost, but also allows much higher flexibility to control lights.
In terms of reliability - so far I haven't had any issue (except with 2 sensors I have from Shelly, but that's different story) with any power control device from them. And some are 2+ years old.
I have shelly devices on multiple locations (via the same cloud accouynt) and want to monitor their sensors in Home assistant. How would you recommend i do that? i am quite desperate to find a easy solution
None of the current integrations pull data from the cloud. The only way (but I never tried it) would be to use MQTT service on each device and have it send data to (publicly available) MQTT service. But that's also a big security risk as MQTT servers are not known for their security.
Really best tutorial available!
Glad it was helpful Luca and thanks for the comment!!!
MQTT is key. Especially over VLANs ;-)
As i know, shelly devices is supporting homekit. İf we replace the firmware with homekit, can we add this devices with homekit entegration on the homeassistant?
There is a open source version of firmware that brings HomeKit compatibility. I didn't try it so can't tell you how good it works. But yes, you should be able to add them to HA with it. At least it does say that it is compatible with stock firmware.
Hello, great video. Finally I could see an on line configuration of a shelly device. You mention the non necessity of configuring thru mqtt because the own Shelly integration is fine. In any case, I'm trying to configure it thru mqtt, but no way!. Have you a similar video, but with mqtt configuration for Shelly devices?. On the other hand, for ShellyEM device, there is one sensor not read with the Shelly own integration, and it is the reactive_power, and I'm totally lost on how to retrieve such information in HomeAssistant. Does anyboday know how to solve it?. THANKS
Hi and thanks for the comment and sorry for late reply - busy day :)
I do use MQTT for some of the sensors from Shelly, but not all. I did record video on how to use Shellies autodiscovery to add Shelly devices with MQTT - here is the link to video and I hope it helps.
It is part of this video: th-cam.com/video/ylCt45JUkOg/w-d-xo.html
You can find time stamp for it in video description.
@@BeardedTinker Great! I have finally handled to get some variables thru Mqtt and others with Shelly own integration. Thanks a lot!!
@@joracadu that's great! Enjoy your data now if you stumble upon any interesting automation, please share 🙂
I tried to add the shelly integration but it says "The Shelly device is using an unsupported firmware version.". What do I do?
Make sure it is running latest firmware on Shelly. If not, you can upgrade via Shelly device web page.
@@BeardedTinker I had my shelly connected to a firewalled vlan that didn't have internet access (like all my IoT devices). I didn't see a way to manually upload the new shelly firmware so I had to give the shelly internet access to update. I took it offline after it was done.
Great video and im happy when i see people concerning about privacy..and not giving away china all their life info
Definitely, no matter if it's China, USA or EU, I like to keep as much of my data to myself. Shelly has servers for data only in EU but still...
Do you have dynamic or static IPs on your smart plugs?
Excellent question - most of the devices have fixed/static IP address.
I've created ranges for devices based on type. This may be limiting if numbers go above what I have planned, but is now much easier to manage
Nice Video, but can you tell me what I have to type in Host* to connect to my Shelly 25? I tried several IP adresses Wb adresses which I can reach the Shelly via http from my network. But nothing worked!
This shoud be just IP address of the Shelly device - can't remember if you need in front or not - no specific port is needed.
BUT don't forgert to configure CoIoT on Shylle device and specify your Home Assistant IP address with port 5683. This will definitly help with speed of actions.
@@BeardedTinker it was in the wrong WLAN. Thanks for helping!
@@HannesSchleeh glad you got it sorted!!!
@BeardedTinker can you make a video about adding a NIBE heatpump to HomeAssistant, I can't find a good tutorial about it.
Hi Andre! Well, to be honest, I can't - I would need access to it to test and record the process.
From what I've seen, it can be done using HACS integration, and it didn't look that hard, at least for default/minimal installation.
github.com/elupus/hass_nibe
But, one of the prerequisite for it to work is to have Home Assistant exposed to the internet. Although it says that you can use it with http (without SSL), please, use with SSL certificate or https type of connection only.
Just done this following your guide as I previously used the official add-in but had hoped to find an alternative particularly for the DW2's who go offline on a restart. Unfortunately it seems this doesn't resolve that problem. More concerning however is The Shelly 1L offers all entities except the on/off! Guess i'll switch back to official integration, thanks anyway.
For DW2's, that could be problem by design since they go to sleep mode - are you on latest firmware there? But I find it strange that 1L is missing most important thing - switch.
I'm still waiting for mine to arrive, but I know of few ppl using them without an issue. This is definitely showstopper. Sorry you had bed experience!
@@BeardedTinker No Problem and thanks for another excellent tutorial. With the DW2's yes latest firmware, its a real pain, maybe MQTT would resolve it, though I doubt it, seems its a design issue, I need to find another solution. Also unfortunate that the switch is missing, I have two of them as well. Not sure if it could have been hidden somewhere, I couldn't find it though.
Ok, got it - what is the 1L problem. Shellyforhass still isn't supporting it. github.com/StyraHem/ShellyForHASS/issues/486
There is 0.2.2 beta version that has a support for it, but looks like it also has a bug with it according to latest issue on GitHub. So, you can try using 0.2.2beta to see if it helps or not. Will search a bit about dw2
And yes, people have same issues with DW2's - github.com/StyraHem/ShellyForHASS/issues/421#issuecomment-703076238
For DW2 (if using MQTT) just enable the retain flag (or make an automation to set it to the state you prefer)
if shelly devices are not in the same network I can still integrate them in home assistant?
I have different wireless networks because the devices cover a larger area and they are not all in the same network .
Excellent question! But since we are using local integration, no. There is a way or workaround for this, but it requires a bit more complex setup.
If you would use MQTT and this MQTT would be in cloud or exposed, you could do it through MQTT server. In similar way, I'm sharing my devices between 2 HA, but they are in my case both on same network.
The only difference would be that I would use public IP or domain name to connect to it.
AFAIK it's not using Shelly Cloud app data for control. If it would, it would also be much easier to do what you are looking for.
@@BeardedTinker if I use routers in AP mode and I ensure on all devices the same range is ip 192.168.0.2-255 even if the networks have different names it is possible to see them home assistant? I saw that install for Windows from another movie on TH-cam after starts the server has great limitations. Is there an installer for Windows that has access to all server options after the installation is complete?
If there is connectivity and network flow, it should work. But you must have routing available between access points.
If you are talking about Windows Python or Windows Docker version, they are limited. You should try and run Home Assistant in Virtual Machine on Windows, to get full functionality.
Nice work man!
Thank you!!!!
So can shelly be local control like Tuya?
Yes, that's correct. I only use them locally. With stock firmware.
I have a shelly plug exactly like in the video. The video DOES NOT explain you how to connect it. He jumps over too many steps. I plugged it into power and then..... nothing. The video does not help you to integrate the shelly plug into Home Assistant.
Hi Martin and thank you for your comment - but I think you've posted comment under wrong video - this video is for integration of Shelly devices into HA - options you have, and NOT on how to plug it in and set it up. There is difference in configuring device an integration of the device. Not a single step has been jumped over and as this video is device neutral - it works with any Shelly device - after you set it up.
shelly on home assistant Is it local or cloud?
I only use local control, but if you want, you can use cloud too.
How about if I want to use local?
Use/enable CoIoT in confirmation or MQTT
there's no tutorial for shelly coIoT
@@shandradm911 there are a lot on TH-cam - here is the link to one of mine: th-cam.com/video/vaJymxB0wIw/w-d-xo.html
kinda wish shelly also made zigbee 3.0 devices - i realy like they dont force a fucking hub and they are higly configurable
But if they do Zigbee devices, they would probably need to add also HUB for all new users that buy their devices...
Neveznao za video. S čim si radio uvodnu špicu/grafiku? tnx
Joj, hmm... Neki online alat. Moram potražiti koji. Davno je to bilo.
Našao - placeit.net/video-maker
@@BeardedTinker Ok, bitno da nisu sati programiranja :D
You can skip to about 5:30 min in, this guys is extremely long winded and dry.
I recommend watching it with glass of nice beverage to unwind from a long day
I am running shellys with mqtt (4x 1pm, 2x h&t, 2x D/W2, 1x RGBW) over MQTT (with the help of ha-shellies-discovery python script). I find the MQTT more stable (and it was the only noncloud option up untill 0.118 something). Usage is more or less painless.
You can also hack a dirty automation to update all the devices at once (rgbw is sort of annoying as it cycles all colors)
check my config at github.com/zeridon/homeassistant (well that is the whole stack i am using)
Thanks for this one!!! Much appreciated - browsed through the GitHub very fast - I see that you're also using Luftdaten.
@@BeardedTinker yep, had to hack the luftdaten2mqtt stuff so i do not go over the internet to pull the data and as a personal preference like the push model.
I'm using custom component - local luftdaten sensor.