Jump to content
WallDisplay: 2.0.0-beta3 is uploaded and ready for test ×

Approach to realize Virtual Button with Value to control MQTT device


Recommended Posts

I want to realize the following project:

On the Shelly Wall Display I want to have a Virtual Component, that represents my Boiler Connected To My Heatpump, something like this

image.png.d41c759cdac02d2c668af6f37757a80d.png

A press on the Virtual Component should ENABLE or DISABLE the Drinking Water Heating by the Heatpump. And the temperature should represent the current temperature in the boiler. My heatpump will be Modbus TCP capable in the near future, thus I think about a setup like this

HEATPUMP & MODBUS  <-> MQTT <-> SHELLY WALL DISPLAY

where the MQTT messages will both deliver updates on the drinking water temperature and receive messages on activating/deactivating the drinking water heating.

Considering the current functionality of the Shelly Wall Display realization seems not possible. I think the separate parts to be implemented are

  1. State and Functionality Representation of the Virtual Component
  2. Communication and state update of 1 via MQTT
  3. UI Representation of 1

For (1) I guess that a combination of a Virtual Button with a Virtual Number in a Virtual Group should be capable of representing the local model. For (2) the respective Virtual components should support MQTT related actions and state updates. For (3) I could not find any information on developing such a UI tile.

It would be very nice if somebody could point me the directions either for documentation or the necessary "entries" to realize this functionality! (I'm a seasoned developer so any direct programmatic hint is also very much appreciated)

 

 

Link to comment
Share on other sites

Hy Dimitar, thanks for your response. When calling http://shelly/rpc/Virtual.ListSupported the only supported elements returned are
 

{
    "types": [
        "Button"
    ]
}

If the documentation in https://shelly-api-docs.shelly.cloud/gen2/DynamicComponents/Virtual/Number is correct then somehow this should support a basic variant. Do you plan to support the "Number" type in the near future? I guess that the `meta.ui.icon` value, if supported, should provide a step for this functionality. Yet documentation does not elaborate on a combination of Button and Number to reach the required functionality?!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...