This button is part of my next video! I was having a lot of trouble with this button until I realized there was a firmware update. After that, it's fairly responsive! Great tutorial! The Shelly cloud part that lets you use this when you're not in your home network... That's pretty cool!
What version where you on? 1.10, or 1.09? I think I still haven't updated mine to 1.11, that was just released few weeks ago (1-2 days after I recorded that video).
In the Shelly configuration details, you show configuring both CoIoT and MQTT. And then in Home Assistant, you show the differences in the entities that appear for each of the two integrations (built-in Shelly, which is based on CoIoT, and MQTT). But you don't say whether you need both, and I don't think you do. And while the built-in integration has fewer entities, it's not clear that's actually a difference in functionality. The built-in integration is based on events, rather than entities. So automations check the _type_ of the event (single, double, etc.), instead of watching for specific, different entities going on. To my eyes (squinting at the screens in your video), it appears that the only things you get with MQTT that aren't in the built-in integration are the button's IP address on the Wi-Fi network (which I can look up elsewhere), and the availability of a device firmware update (which is useful, but secondary). Could you perhaps provide additional details of the differences between the two integration approaches, advantages and disadvantages, and so on? Any reliability differences that you know of? Is one more responsive than the other? Is one more reliable than the other?
Hi! No, you don't need both of them. Using just internal/CoIoT is enough (or MQTT). As for what to go for - it's matter of preference. If using CoIoT, you can often get unavailable, as device state goes to sleep, while you can avoid that with using MQTT and retain option there. But that's just matter of personal preference... Device will in both cases operate the same in terms of functionality from what I recall. I use it with MQTT as I like to have devices available even during HA restarts.
Great video, thank you very much! I installed MQTT mosquitto (add-on & integration) in HA just because of how you automated it, however for some weird reason I'm not able to have HA auto-discover it. I followed all the steps on MQTT config on the shelly button but still nothing. Is there any other step that might be needed and it is not in the video?
I just got this working. It only worked after I used the shelly discovery script and it does not show single, double, triple or long press as entities but when you create an automation with the button after discovery in MQTT it works as it should.
Hi, thanks very much for this great and very useful video! Did you have to define the button actions etc in your configuration file to make MQTT work, or does it 'auto discover'? I can't work out how to expose all the entities via MQTT. Thanks - Andrew
I have Shellies Discovery script installatied. It helps with proper setup of MQTT Shelly devices. Did you try that one? github.com/bieniu/ha-shellies-discovery
@@BeardedTinker Ahhh!! Thank you so much, I didn't know anything about the scripts. All installed and working perfectly. Thanks again for replying and pointing me in the right direction. I learn something new about HA thanks to guys like you.
Hi, please can you help me. When i go to my Homeassistant the Adressbar shows 192.168.178.60:8123 But i dont know what to type into ColoT peer and Mqtt Server by the shelly button?!
For CoIoT, use IP address of home assistant (192.168.178.60) with port 5683 - full address is 192.168.178.60:5683 . MQTT is not needed if you use CoIoT and also if you don't have it installed.
That's not easy to answer - depends. If the WiFi device is always powered on and connected to WiFi, then it should be - of course depending once again on signal quality and network load. If it's battery powered, it has to connect to wifi and send action after that so it can take longer time. Other protocols such as Zigbee or Z-wave can be faster in that case. But once again, depending on the network. For button, it will be a bit slower as it is battery power operated device.
This would be a great replacement of the Samsung buttons which are now Aeotech and getting expensive. The price of these Shelly buttons are good and no batteries to replace.
Just be aware of delay from button press to action. That's the only downside that I see in this one. There is new firmware in works that could/should reduce this for a fraction of time, but we have to wait for it.
@@BeardedTinker I have a couple of Button1's in my possession now. If you let the button "sleep" the press after say 30 minutes of non-use is really quick to connect to the AP and trigger automations, if you try another button press within say 2-3 minutes, the wifi AP connect will timeout but eventually it will connect and the command will be sent out. You can tell by the led colors, white will flash for 3 to 5 seconds, then red, then finally green. That second button event can be up to 5 to 8 seconds as it re-associates with the AP and sends commands. I don't know if it due to AP settings or their firmware or both. If you run the button on USB power it always stays connect and thus none of this delay.
Hi, I see You are using Configuration.Yaml 4 MQTT. I have Mosquito. Can you tell what are the differences and what is best to use to have an easy life?
I think that this configuration.yaml is leftover from when Home Assistant internal integration was done via configuration.yaml. I use now mostly MQTT version of integration, and that's easiest way of adding them, but you need to add one Python script (github.com/bieniu/ha-shellies-discovery) - this will add all existing or new devices properly formatted to Home Assistant. In my opinion this is very fast in terms of response and should also handle well any Home Assistant restarts if any sensor data is changed while it was offline.
@@BeardedTinker thanks for the Quick reply. I’ll lookup how to manage those python’s since this is all new to me. Have my HA up and running with a simple node red implementation to achieve my goals, but maybe there is a way to make it more responsive with Mqtt in stead of using the binary sensors I now use.
@@BeardedTinker thx for the link - I've switched back and forth between Shelly and ShellyforHass for a long time now trying to reduce the press delay and this seems to work the best so far. After upgrading to the latest firmware it's now between a 1-10 second delay rather than a 4-10 second delay. The problem is it's about 1-2 seconds the first time I press it - if I push the button immediately after the blue light on the button goes off (i.e. to turn a lamp back off/on) it seems to have a sort of cooldown where if I keep doing that, it will become longer and longer until I can press the button again without a delay. Are you experiencing this at all by chance or is it just my config?
@@BeardedTinker Thanks for your response! I have both the MQTT/Mosquitto and the Shelly integrations. There are a couple of MQTT entities for the buttons, but nothing for short/long presses, just power on/off, battery level, and one or two more that are not useful.
@@BeardedTinker Well, thought I would follow up with this... I appears that my configuration was corrupted. I restored the original backup I made right after I initially logged in for the first time. I updated the core and started re-adding the integrations. Interestingly, I am getting no entities for MQTT now (even though it is seeing the messages when I press the buttons). However, the new Shelly integration sees single, double, triple, and long presses now. So at this point, I am going to leave it there and use the Shelly integration.
It depends on what you're using to respond to clicks on the button. If you're using it with Home Assistant, then the buttons can control anything that you've connected to Home Assistant. The only limitation is your skill with automations.
Thanks for the video! I have integrated the shelly button via MQTT. the shelly discovery script is also running. but I can't see the entities for short press, long press etc. th-cam.com/video/Le3qj23EARY/w-d-xo.html do i need to configure this extra?
@@BeardedTinker you can build that for $5 from AliExpress, still, mass production capabilities of Shelly and bump the price to $10 and you make double anyway and you will crush the competition in the process.
I'm having a bit of a hard time here. Freshly setup both the button and Mosquitto, when I listen to # in Mosquitto, the button show up e.g: Nachricht 4 empfangen auf shellies/shellybuttonvz/input_event/0 um 13:32: { "event": "S", "event_cnt": 10 } But entities are added to Home Assistant. Am I doing something wrong?
Are you using Shellies Discovery script? It needs this script if you are adding Shelly devices via MQTT to Home Assistant. github.com/bieniu/ha-shellies-discovery You need to follow few steps from here to get it working enable python_script, copy *.py file and add 2 automations to Home Assistant - if I remember correctly.
@@BeardedTinker That would have been useful information a couple of hours ago (>; I’m a relatively new HA user and was trying to figure out why I only had one entity, and only three old devices connected to a MQTT… had me puzzled for way too long. I finally gave up and just started adding an automation to the button and then I could see the single, double, triple press choices. Easy peezy.
This was super helpful. I'm new to MQTT in HA so this was great. Also, I really love your accent, it's weirdly soothing. Subscribed for more.
Thanks for subbing! And compliment :)
This button is part of my next video! I was having a lot of trouble with this button until I realized there was a firmware update. After that, it's fairly responsive! Great tutorial!
The Shelly cloud part that lets you use this when you're not in your home network... That's pretty cool!
What version where you on? 1.10, or 1.09?
I think I still haven't updated mine to 1.11, that was just released few weeks ago (1-2 days after I recorded that video).
@@BeardedTinker I never thought to write it down or record it! I want to say the date was from 2020.
Thanks for the overview, now let’s play for a bit! 😁
Any time!
Haha, saw your older comment about some helping scripts, trying that
In the Shelly configuration details, you show configuring both CoIoT and MQTT. And then in Home Assistant, you show the differences in the entities that appear for each of the two integrations (built-in Shelly, which is based on CoIoT, and MQTT).
But you don't say whether you need both, and I don't think you do. And while the built-in integration has fewer entities, it's not clear that's actually a difference in functionality. The built-in integration is based on events, rather than entities. So automations check the _type_ of the event (single, double, etc.), instead of watching for specific, different entities going on. To my eyes (squinting at the screens in your video), it appears that the only things you get with MQTT that aren't in the built-in integration are the button's IP address on the Wi-Fi network (which I can look up elsewhere), and the availability of a device firmware update (which is useful, but secondary).
Could you perhaps provide additional details of the differences between the two integration approaches, advantages and disadvantages, and so on? Any reliability differences that you know of? Is one more responsive than the other? Is one more reliable than the other?
Hi! No, you don't need both of them. Using just internal/CoIoT is enough (or MQTT).
As for what to go for - it's matter of preference. If using CoIoT, you can often get unavailable, as device state goes to sleep, while you can avoid that with using MQTT and retain option there. But that's just matter of personal preference...
Device will in both cases operate the same in terms of functionality from what I recall. I use it with MQTT as I like to have devices available even during HA restarts.
Great video, thank you very much! I installed MQTT mosquitto (add-on & integration) in HA just because of how you automated it, however for some weird reason I'm not able to have HA auto-discover it. I followed all the steps on MQTT config on the shelly button but still nothing. Is there any other step that might be needed and it is not in the video?
same issue, you ever figure it out?
I just got this working. It only worked after I used the shelly discovery script and it does not show single, double, triple or long press as entities but when you create an automation with the button after discovery in MQTT it works as it should.
Yes, there was a change after video was recorded how HA sees the events (or presents them).
Glad you got it working!!!
Hi, thanks very much for this great and very useful video! Did you have to define the button actions etc in your configuration file to make MQTT work, or does it 'auto discover'? I can't work out how to expose all the entities via MQTT. Thanks - Andrew
I have Shellies Discovery script installatied. It helps with proper setup of MQTT Shelly devices. Did you try that one? github.com/bieniu/ha-shellies-discovery
@@BeardedTinker Ahhh!! Thank you so much, I didn't know anything about the scripts. All installed and working perfectly. Thanks again for replying and pointing me in the right direction. I learn something new about HA thanks to guys like you.
That's fantastic! Glad you got it working!!
Hi, please can you help me. When i go to my Homeassistant the Adressbar shows 192.168.178.60:8123
But i dont know what to type into ColoT peer and Mqtt Server by the shelly button?!
For CoIoT, use IP address of home assistant (192.168.178.60) with port 5683 - full address is 192.168.178.60:5683 . MQTT is not needed if you use CoIoT and also if you don't have it installed.
I wish you would have demonstrated it in actual use so I could get an idea of the reaction time...
Does wifi devices provide better reaction? I mean smaller delay for actions.
That's not easy to answer - depends. If the WiFi device is always powered on and connected to WiFi, then it should be - of course depending once again on signal quality and network load. If it's battery powered, it has to connect to wifi and send action after that so it can take longer time.
Other protocols such as Zigbee or Z-wave can be faster in that case. But once again, depending on the network.
For button, it will be a bit slower as it is battery power operated device.
This would be a great replacement of the Samsung buttons which are now Aeotech and getting expensive. The price of these Shelly buttons are good and no batteries to replace.
Just be aware of delay from button press to action. That's the only downside that I see in this one.
There is new firmware in works that could/should reduce this for a fraction of time, but we have to wait for it.
@@BeardedTinker I have a couple of Button1's in my possession now. If you let the button "sleep" the press after say 30 minutes of non-use is really quick to connect to the AP and trigger automations, if you try another button press within say 2-3 minutes, the wifi AP connect will timeout but eventually it will connect and the command will be sent out. You can tell by the led colors, white will flash for 3 to 5 seconds, then red, then finally green. That second button event can be up to 5 to 8 seconds as it re-associates with the AP and sends commands. I don't know if it due to AP settings or their firmware or both. If you run the button on USB power it always stays connect and thus none of this delay.
Thanks for the great video
Glad you liked it Krastyo!
Hi, I see You are using Configuration.Yaml 4 MQTT. I have Mosquito. Can you tell what are the differences and what is best to use to have an easy life?
I think that this configuration.yaml is leftover from when Home Assistant internal integration was done via configuration.yaml.
I use now mostly MQTT version of integration, and that's easiest way of adding them, but you need to add one Python script (github.com/bieniu/ha-shellies-discovery) - this will add all existing or new devices properly formatted to Home Assistant.
In my opinion this is very fast in terms of response and should also handle well any Home Assistant restarts if any sensor data is changed while it was offline.
@@BeardedTinker thanks for the Quick reply. I’ll lookup how to manage those python’s since this is all new to me. Have my HA up and running with a simple node red implementation to achieve my goals, but maybe there is a way to make it more responsive with Mqtt in stead of using the binary sensors I now use.
@@BeardedTinker thx for the link - I've switched back and forth between Shelly and ShellyforHass for a long time now trying to reduce the press delay and this seems to work the best so far. After upgrading to the latest firmware it's now between a 1-10 second delay rather than a 4-10 second delay. The problem is it's about 1-2 seconds the first time I press it - if I push the button immediately after the blue light on the button goes off (i.e. to turn a lamp back off/on) it seems to have a sort of cooldown where if I keep doing that, it will become longer and longer until I can press the button again without a delay. Are you experiencing this at all by chance or is it just my config?
I use Mosquito(MQTT) that can't find this button. Is this the reason?
It should work with MQTT without any issue. Just configure MQTT server in device configuration.
I don't get all the push options in my system. Just power on/off, battery, etc. It's showing as a switch, not a button. Any advice?
How did you connect it - using internal Shelly integration or by using MQTT?
@@BeardedTinker Thanks for your response! I have both the MQTT/Mosquitto and the Shelly integrations. There are a couple of MQTT entities for the buttons, but nothing for short/long presses, just power on/off, battery level, and one or two more that are not useful.
@@BeardedTinker Well, thought I would follow up with this... I appears that my configuration was corrupted. I restored the original backup I made right after I initially logged in for the first time. I updated the core and started re-adding the integrations. Interestingly, I am getting no entities for MQTT now (even though it is seeing the messages when I press the buttons). However, the new Shelly integration sees single, double, triple, and long presses now. So at this point, I am going to leave it there and use the Shelly integration.
@@paul454 Glad you got it working, although not the easiest way...
Can you only conttrol shelly lights, or also other “tuya wifi” lamps
I don't have any Shelly lights, controling IKEA and Elgato lights with it.
It depends on what you're using to respond to clicks on the button. If you're using it with Home Assistant, then the buttons can control anything that you've connected to Home Assistant. The only limitation is your skill with automations.
so it is not possible to turn the LED light on and off from home assistant?
Sorry, didn't catch you - what light? LED ring light on button?
@@BeardedTinker yes, the led ring, can you turn it on and off from remote?
@@jayemess6622 unfortunately, as far as I know - no, you can't disable it from Home Assistant.
Thanks for the video!
I have integrated the shelly button via MQTT. the shelly discovery script is also running. but I can't see the entities for short press, long press etc. th-cam.com/video/Le3qj23EARY/w-d-xo.html
do i need to configure this extra?
What are you talking about, I love micro USB.
Me too, when I'm sober. 😂
Maybe you meant you had preferred USB-C ?
I think these "simple" devices are still way too expensive.... 10USD would be OK
Yes, they are a bit expensive, have to agree on that.
@@BeardedTinker you can build that for $5 from AliExpress, still, mass production capabilities of Shelly and bump the price to $10 and you make double anyway and you will crush the competition in the process.
I'm having a bit of a hard time here. Freshly setup both the button and Mosquitto, when I listen to # in Mosquitto, the button show up e.g:
Nachricht 4 empfangen auf shellies/shellybuttonvz/input_event/0 um 13:32:
{
"event": "S",
"event_cnt": 10
}
But entities are added to Home Assistant. Am I doing something wrong?
Are you using Shellies Discovery script? It needs this script if you are adding Shelly devices via MQTT to Home Assistant.
github.com/bieniu/ha-shellies-discovery
You need to follow few steps from here to get it working enable python_script, copy *.py file and add 2 automations to Home Assistant - if I remember correctly.
@@BeardedTinker This was missing from the video - very pleased to find the answer in the comments - many thanks
@@BeardedTinker That would have been useful information a couple of hours ago (>; I’m a relatively new HA user and was trying to figure out why I only had one entity, and only three old devices connected to a MQTT… had me puzzled for way too long. I finally gave up and just started adding an automation to the button and then I could see the single, double, triple press choices. Easy peezy.