What do you mean when you say that the Shellies are not on your network? Are they in another location?
The Shellies must be connected to the same network as your Home Assistant system. If that’s the case, this component will work whether or not the Shellies are also on the cloud.
Just curious, I’m currently using my shellys via mqtt, and all is well, but to try it out I loaded the integration and I can’t seem to get it to find any devices. My wifi is a diff vlan and I have multicast forwarding setup on my router. Is there anything else I may be missing? Thanks!
I am using just shellyforhass to control my two shelly 2.5’s and I really like the implementation. There are too many rabbit holes to go down right now for me so I do not want to get into mqtt just yet.
My only gripe is I am trying to be very consistent with my entity ids and names (like all power sensors end in _power, not _current_consumption). I tried integrating with GUI first but it kept renaming my entities back to its auto generated ones. Now using yaml and thought it was solved but last reboot changed my power entity_id and names again.
I know that you can override the auto generated names but I dont know how to specify it down to each entity_id vice each device. For instance my Shelly 2.5 - 10BC51 has 2 device id’s one for each switch:
Shelly 2.5 - 10BC51-1 and Shelly 2.5 - 10BC51-2. the 10BC51-1 goes to my entertainment center outlet so I want the entity id of the power to be named as such. The relay will be disabled to never turn off, and the switch will actually operate my couch lights via automation. So I want that switch entity to be named couch lights.
If I could set all that stuff in stone via yaml that would be great, it is very tedious to keep renaming the entities via GUI even for just two shelly 2.5s so I will not be adding any more until I can get a solution to this
Just set up two shelly 1 switches. The integration discovered the switches and they can be controlled by the HA GUI. The only issue is the status in lovelace seems to take a full pooling interval, which is at the default of 60 seconds, before the GUI updates indicating a change. Anyone aware of a configuration option to make the switch state update happen shortly after the initial click?
I’m using several Shelly1 and Shelly2.5 and they react instantly. How is the signal quality for these Shelly’s? Do you have the same behaviour in the Shelly app?
I should have been clearer. The issue is associated with using a “Picture Elements Card”. Using the shelly web interface works without issue. If I use just a “Entities Card” to toggle on and off it work as expected. The “Picture Elements Card” appears to wait for the status in the database to actually be updated, which doesn’t happen until the polling interval. I use a picture elements card because it allows the displaying of a floor plan.
Actually if I switch the light off using the picture element card and then look at the entities card, the entity card also doesn’t update until the polling interval. So the entity card only appears to work because the GUI changes the state immediately if you click on that toggle.
The shelly 1 support mqtt, which I hadn’t previously utilized in my implementation. I enabled the HA provided mqtt broker, changed the switch to communicate with the broker and then configured the sensors in my ha configuration.yaml. This approach provides the expected performance. Configuration was pretty simple:
You need CoAP multicast working in your network. You can look on the attribute “protocols” and see if “coap-msg” are there. The CoAP working, other there is poll, mDns etc. coap-discovery mening it is discovered but coap-msg is where it get the status updates.
You can try enable/disable igmp in your router/switch/AP.