The naming of the individual channels for multi-channel devices in the integrations menu is a known issue. We’ll look into it. I agree that the devices list should distinguish between the channels properly.
Hi! Yes the problem still exists. I am on the beta 3.70~61. All my relay-equipped Shelly devices are discovered properly, but PM models which only measure power/energy are not found. There is no password protection on any of my Shellys.
Ideally I would like to assign a heat pump role to two of my shelly units (non-relay models, on purpose). Perhaps in the future this could help DESS prediction accuracy.
I have the same problem, Shelly works fine in Home Assistant with password.
Shelly with no-password are discovered by Victron, but when secured with a password, Shelly is nog found.
Thanks to the Victron team for adding native support for Shelly . A few months ago, I spent a lot of time implementing it via Node-RED and a virtual device.
I have 1x Shelly 1PM Gen4 (with Shelly Plus Add-on and DS18B20 temperature sensor connected) and 2x Shelly Plug S Gen3 connected.
Issues?
It automatically found only one device, but after adding the IP addresses of the other two, they appeared normally. No idea why.
I do not see Shellys relay switch in VRM.
Question:
Are there plans to integrate support for the Shelly add-on so that the Shelly temperature sensors are displayed as temperature device connected directly to Cerbo GX?
It would be great if I could use the Shelly relay as an internal relay in Cerbo GX. In my case I would love to use Shelly relays with Temperature control rules. Is something like that in pipeline?
I have all use cases running through Node-RED, but I think it would be cool to have it so that even my wife could find and adjust something in the settings.
The GX only connects to shelly devices of Gen2 or higher over the LAN. We currently don’t have plans to support connection over bluetooth. Most devices (esp. Gen2+) have bluetooth and wifi/ethernet, so supporting bluetooth as well does not add that much value.
Switching the shellies directly from the controls pane in VRM is not (yet) supported.
Are there plans to integrate support for the Shelly add-on so that the Shelly temperature sensors are displayed as temperature device connected directly to Cerbo GX?
There are no plans for this at the moment. I am also not sure how many users have such add-ons.
It would be great if I could use the Shelly relay as an internal relay in Cerbo GX. In my case I would love to use Shelly relays with Temperature control rules. Is something like that in pipeline?
Actually, this is in the pipeline and it is a bit broader than just Shelly. We are planning to add support for such functions (like the temperature relay) for most (if not all) switchable devices in the switch pane. So also for the Victron GX IO extender, for example. Due to the wide range of devices, adding this may take a while.
After going from v.3.70~61 To v.3.70~74 - my Victron Ekrano GX could not longer auto detect my prior auto-detected Shelly Plugs. (Tried GX reboot etc no change). Manually adding IP addresses to the GX made them available again.
The “Shelly Devices” “press to refresh” does not seem to do anything either? Press it (via remote console) and seemingly nothing happens.
Apart from that “Online check for firmware update results in error message “Firmware check timed out” but maybe that is expected behaviour.
I’m not getting offered ~76 due to this :Apart from that “Online check for firmware update results in error message “Firmware check timed out” but maybe that is expected behaviour.
I can try and switch back to ~61 and then check for firmware update again?
I am doing everything remote - and VRM remote works fine - so the unit does have full internet access.
Apologies, I now see ~76 has not been released yet.
As per your original report:
After going from v.3.70~61 To v.3.70~74 - my Victron Ekrano GX could not longer auto detect my prior auto-detected Shelly Plugs. (Tried GX reboot etc no change). Manually adding IP addresses to the GX made them available again.
I also tested this now on a device with ~74 installed and can confirm this behavior. Not sure yet what’s causing it. I’ll look into it.