[OH 4.2] Fronius inspired energy flow widget [4.2.1; 5.0.0]

Add-on Marketplace UI Widgets
41

Hi and thank you, I am glad you like it.

There are only two mouseover events: Battery and Inverter. I could not think of any useful additional information for the other icons.

Regarding your second question: The mechanism for the analyze gadget probably is pretty similar. The hard part would be to get the graphs from the database. I don’t think there are any suitable generic widgets for this functionality. Basically you would need to fetch the data and pack it into some hidden SVG-code that becomes visible on mouseover (or any other event you’d like to use for it).

42

I would like openhab do the collection of data and show them in a diagram. I just want to define the triggers somewhere within your widget.

I thought of something like would do the job.

                      - component: oh-link
                        config:
                          action: analyzer
                          actionAnalyzerCoordSystem: time
                          actionAnalyzerItems: =[props.batterylevel]

We can define actions and their types for certain items. For example, it is possible to define actions for labels

I don’t know which of the GUI components from your widget can server as object to add the action

If we click on the GUI component, the action and the analyzer would be launched

another example from one of my gauge-cards

component: oh-gauge-card
config:
  title: Autarkie
  item: Fronius_Symo_Inverter_Autonomy
  type: circle
  action: analyzer
  actionAnalyzerItems:
    - Fronius_Symo_Inverter_Autonomy
  footer: Autarkiegrad in Prozent
  outline: false
  bgColor: lightgrey
43

I am not an expert on these things, but my guess would be that any component with an id like few_solarpanel, few_battery, few_grid and so on would be suitable.

44

no it doesn’t work

None of the components within the yaml code of this custom widget seems to allow actions.

The problem seems to be that the widget is one big f7-block and does not define any oh-icon within the code. An f7-block or oh-icon would accept actions. It is built-in

45

That’s what I meant: You would have to code up your own action. I wanted to avoid using preexisting components, because it gave me a lot more flexibility. It does mean to do everything manually though, but it is possible. The components themselves are built like this.