hmerk / main_widget Goto Github PK

Describe the bug
The first blog has a margin -1em.
This means that, for example, the WeatherCard is not displayed correctly.

To Reproduce
This is what it looks like.

Expected behavior

Screenshots
shown up

Fix suggestion
The first step is to remove the margin.
The second step is to examine the general layout in order to design it responsively.

I think it's an interresting information to know who is currently home.

So I would like to add an additional card to the "homeCard" displaying the status of list elements (same as the scene card) of people that are home.

Proposal of a new PresenceCard: #22

Describe the bug
The floorbuttons have the parameter large. This should be removed so that all buttons are the same.

Will be fixed with the next PR.

Describe the bug
A Swiper Row does not yet have a height attribute.

Will be fixed with the next PR.

Is your feature request related to a problem? Please describe.
Currently, the navigation buttons are located inside the container. This is unattractive because the chevrons overlap the buttons for rooms.
Pressing the swiper buttons correctly is not always possible.

Describe the solution you'd like
Move f7-swiper buttons from the container to the outside.
Better operability due to larger button area.

Additional context

Describe the bug
The Filter function is wrong:

filter: (loop.roomArray.metadata) && ((loop.roomArray.metadata.semantics.value).includes("Room") || (loop.roomArray.metadata.semantics.value).includes("Corridor")) && (loop.roomArray.metadata.semantics.config.hasLocation == vars.objVar.floor)

should be

filter: (loop.roomArray.metadata) && ((loop.roomArray.metadata.semantics.value).includes("Room") || (loop.roomArray.metadata.semantics.value).includes("Corridor"))

because the objVar.floor isn't set in this moment.
It is not noticeable because invisibility is set.
visible: '=!vars.objVar ? false : (vars.objVar.selectSection=="SECTION2" && !vars.objVar.floor) ? true : false'

The aim is to display all rooms.

Is your feature request related to a problem? Please describe.

• The mainWidget is not designed for responsive design.
• oh-repeaters can be reduced to possibly improve performance.
• Several areas do not comply with the DesignSpecs.

Describe the solution you'd like

• Integration of f7-swiper instead of oh-repeaters.
• Diverese style adjustments.
• Create basis for responsive design.
• Icon adjustment of the bottomNavbar to use Iconify. Use different sources is not advised. (svg-container). Preparation to eventually introduce an svg icon set as a local source.
• Definition of css classes for efficient styling.

Describe alternatives you've considered
...
Additional context

Describe the bug
The display of things in widget_Floors&Rooms is not correct in my opinion.
When I click on Floors all lights of the Smarthome appear.
When I click on Rooms all the lights of the Smarthome appear.
When I click on Floors
-> Floors -> all lights of the Smarthome
-> Floors -> Shades -> all shutters of the Smarthome
-> Floors -> Climate -> all heaters of the Smarthome
The same when I click on Rooms.
The same when I click on Floors -> LivingRoom

To Reproduce
see above

Expected behavior

In my opinion:

-> Floors -> all things of Smarthome
-> Floors -> Lights -> only Lights of the Smarthome
-> Floors -> Livingroom -> all things of LivingRoom
-> Floors -> Livingroom -> Lights -> only the Lights of LivingRoom

To be accurate, initially should always be displayed all Things.

For discussion ;-)

Is your feature request related to a problem? Please describe.
The visibility of the oh-repeater content is too slow.

Describe the solution you'd like
The slow speed comes from the visible parameter in the rows.
I suggest using cdd atrribute display: none & display: "".
The containers are created initially and only made invisible.
First tests show a performance improvement.

Actual:

            - component: f7-row
              config:
                style:
                  width: 100%
                visible: '=vars.objVar ? (vars.objVar.selectSection=="SECTION1") ? true : false : false'

Suggestion:

            - component: f7-row
              config:
                class:
                  - align-items-center
                  - display-flex
                style:
                  width: 100%
                  height: auto
                  display: '=vars.objVar ? (vars.objVar.selectSection=="SECTION1") ? "" : "none !important" : "none !important"'

Hi,

what do you think about the idea of adding cards for the specifics of a manufacturer?

e,g, I have lots of equipment of Homematic-IP that have certain features that are not covered

• rollershutters: mode changes to activate different timing programs (e.g. holiday, workday, absence)
• thermostats: mode changes (party, absence), boost mode, auto/manual, show window contact
• ...

and other things that do not really work as others

• rollershutters: you cannot read the percentage from the same item used to set the percentage

so the idea is that we have widgets in each folder - that the user can choose. e.g.

• main_widget_RadiatorControl_Card

• main_widget_RadiatorControl_Card_HomematicIP

• main_widget_RadiatorControl_Card_Bosch

• main_widget_Rollershutter_Card

• main_widget_Rollershutter_Card_HomematicIP

• main_widget_Rollershutter_Card_Bosch

So the community can add/extend the main cards with extentions for a brand.

Please comment on that though if it would go with your concept ideas.

instead of equipment item. This will remove the need to have the uiSemantics set for the equipment item. It also allows to have more than one „simple“ light (just having a switch item) in the same equipment.