Closed realhik closed 6 years ago
The sv_widget attribute is not designed to accept lists. (It did not accept lists in conf format either).
sv_widget had to be one string:
sv_widget: "{{ device.rtr('item', 'Heizt mit ', 'item', 'item.soll', 'item.mode', 'item.mode', 'item.mode', '', 'item.state', '0.5') }} {{ plot.rtr('foyer-history', 'item', 'item.soll', 'item.state') }}"
You can insert cr-lf for better readability though:
sv_widget: "{{ device.rtr('item', 'Heizt mit ', 'item', 'item.soll', 'item.mode', 'item.mode', 'item.mode', '', 'item.state', '0.5') }} {{ plot.rtr('foyer-history', 'item', 'item.soll', 'item.state') }}"
It seems that
sv_widget = {{ device.rtr('item', 'Heizt mit ', 'item', 'item.soll', 'item.mode', 'item.mode', 'item.mode', '', 'item.state', '0.5') }} | {{ plot.rtr('foyer-history', 'item', 'item.soll', 'item.state') }}
was kind of supported as it showed both plots in different containers.
Using one string in YAML as proposed results in a merged (and not separated) view for device.rtr and plot.rtr.
Ok, I see the problem. It has nothing to do with YAML though.
The list isn't handled by the routine to expand relative item pathes. It should already exist in SmartHomeNG v1.3 version of the plugin.
By the way: You are not using the actual plugin. The error
File "/usr/local/smarthome-v1.4-rc1/plugins/visu_smartvisu/__init__.py", line 91, in parse_item
item.expand_relativepathes('sv_widget', "'", "'")
Is logged for line 91. In the actual plugin the conflicting statement is in line 106.
The v1.4-rc1 branch was never intended to be used as an installation source, so it didn't reference the actual commit in the plugin repository. So, you are using a lot of old plugin versions.
If you are not using relative item pathes with the sv_widget attributes, you could comment out that line (until the plugin is fixed)
The problem should be fixed with SmartHomeNG v1.4.1. Could you test and give feedback?
Tested for 1.4.1-rc1. Works now as expected. Thx for fixing.
Classic configuration of multiple sv_widgets, as
is no longer supported for yaml
It throws error: