Is there any way to speed up the swipe animation? Since there is an intermediate blank screen, I think the animation would look best if it was twice as fast

Really useful card! Thanks for pointing it out to me and keeping it alive.

I'm not sure if I should preventDefault touch events within the plotly graphs card or if there is an elegant way of "fixing" from within hass-swipe-navigation.

Tested this successor of the original integration and it works perfectly, as expected (and well-known) 👍 Unfortunately a former fellow friend seems to still exist, see here for the bug report:

https://github.com/maykar/lovelace-swipe-navigation/issues/55

Add 'UI Card for Better Thermostat' to exceptions.

When using the slider to change the temperature it activates the swipe navigation. I'm not entirely sure why this happens only to the 'Better Thermostat' and not the default. Also there is some strange behavior on the default one (swiping right works, left not), which is unrelated imo.

I recorded a short clip to demonstrate the behavior:

https://user-images.githubusercontent.com/43964592/209462382-59132f04-f13e-469e-93a9-ab65d009a848.mp4

Signed-off-by: Christos Sidiropoulos [email protected]

Hopefully I'm committing this the proper way. First time.

The my-slider is included in this projects' exception list, but that project has been rewritten and is now my-slider-v2 (https://github.com/AnthonMS/my-cards/blob/main/docs/cards/slider-v2.md). Overarching project (https://github.com/AnthonMS/my-cards)

Could this be added to the exception list? I'm using this my-slider-v2 as an element inside another card, would the exception then still work?

Thank you and happy holidays!

I just noticed something: hass-swipe-navigation makes the sliders not as smooth as the originals. I had realized that Mushroom sliders weren't as smooth, but I had not linked it to hass-swipe-navigation at all.

When testing the new sliders, I thought "wow, they are so smooth". And after the update to 1.7.0 to ignore them, not anymore and it clicked. I reverted to 1.6.5 to confirm, and indeed. I also removed the add-on and tested Mushroom sliders, and smooth again.

It is a very small difference, and only really noticeable on slow movements and for sure not everyone will even notice, and it's a decent compromise for the received funcitonality, but is this a known side effect?

Let's see if the screen recording allows to show it (if reduced to 30FPS, it's not noticeable).

https://user-images.githubusercontent.com/63130724/206449085-a2b59533-5597-4809-ab4b-8e60ae5d596a.mp4

https://user-images.githubusercontent.com/63130724/206449098-8fb516fe-94ff-4d5f-89ef-692d95edc38c.mp4

Thanks again!

This add-on doesn't work over sliders and that's great.

Features: [...] Option to ignore swipes over certain elements (e.g. sliders or maps)

(Although I don't know where the option is. It has worked great by default on all my sliders incl. Mushroom.

However, 2022.12 (released today) introduced the new Features for some Tile cards like lights, and swipe navigation acts when sliding them.

https://www.home-assistant.io/blog/2022/12/07/release-202212/#tile-card-gets-features

Hoping an update can easily fix this, or happy to learn if this needs to be configured on my end.

Thank you :)

Hello, im using the app to swipe between homeassistant pages. Since a few releases, there is the option "two-finger-zoom" which enabled to zoom in pages. I am using this for zooming in my camera feed. But when i zoom out, with tends to move more to the side, the page get changed due to this add on. Can a swipe only be registered, when the page is fully zoomed out?

How are you doing? First at all THANK YOU for maintaining this amazing feature for HA.

Since last update it have been working from time to time, pretty erratic until a few hours back (now it doesn't work anymore). The weird thing is that even tho I tried a downgrade, it still not working (maybe something wrong with the manual install). But, if I install the old repo, from Hacs, it works. Weird, right?

Hi, I have the following configuration on my dashboard: swipe_nav: prevent_default: true swipe_amount: 20 skip_hidden: true wrap: true skip_tabs: 5,6

I have 6 tabs on the dashboard and I want to skip the last two (they are some grafana charts, no need to see those on the mobile). If i'm on the 4th tab and swipe right I want to wrap swipe to the first tab but it goes to the 5th tab, ignoring the skip_tabs configuration.

Dashboard has 6 tabs only, no hidden tabs.

Thanks

When dragging a custom:apexcharts-card graph to see more data, the view is changed. Can you kindly add an exception for Apex Charts?

My Apex Chart is inside another card so just in case I am providing the YAML of the whole thing:

type: custom:tabbed-card
tabs:
  - card:
      type: custom:apexcharts-card
      header:
        show: true
        title: Fridge
        show_states: true
        colorize_states: true
      yaxis:
        - id: temperature
          decimals: 1
          max: 10
          min: 0
        - id: humidity
          decimals: 0
          max: 100
          min: 0
          opposite: true
      apex_config:
        legend:
          show: false
      all_series_config:
        stroke_width: 2
        curve: smooth
      series:
        - entity: sensor.fridge_sensor_temperature
          yaxis_id: temperature
          name: Temperature
        - entity: sensor.fridge_sensor_humidity
          yaxis_id: humidity
          name: Humidity
          unit: '%Rh'
    attributes:
      label: Fridge
  - card:
      type: statistics-graph
      chart_type: line
      period: hour
      days_to_show: 2
      entities:
        - sensor.fridge_sensor_temperature
      stat_types:
        - mean
        - min
        - max
      card_mod:
        style:
          .: |
            h1 {
              font-size: 18px;
              padding: 2px 15px 2px 15px
            }
          statistics-chart$ha-chart-base$: |
            .chartLegend { 
              display: none;
            }
    attributes:
      label: Temperature
  - card:
      type: statistics-graph
      chart_type: line
      period: hour
      days_to_show: 2
      entities:
        - sensor.fridge_sensor_humidity
      stat_types:
        - mean
        - min
        - max
      card_mod:
        style:
          .: |
            h1 {
              font-size: 18px;
              padding: 2px 15px 2px 15px
            }
          statistics-chart$ha-chart-base$: |
            .chartLegend { 
              display: none;
            }
    attributes:
      label: Humidity

Would it be possible to add the History explorer card as an exeption? It allows moving the graphs by dragging it left/right which also triggers the swipe.

https://github.com/alexarch21/history-explorer-card

We should have a maximum swipe duration. If the time between touchstart and touchend exceeds the threshold, we ignore the swipe.

Originally posted by @dbuezas in https://github.com/zanna-37/hass-swipe-navigation/issues/20#issuecomment-1302008563

The configuration should be reloaded when...

• [ ] ...changing between dashboards with different configurations
• [ ] ...changing the configuration with the "Raw configuration editor"

Hello

I really like the idea of this app but what I want to do is simply swipe to go back to the dispay I came from, not the one next to the one I'm in. Is that possible to integrate as an option?

Enhancements

Provide a way to bypass the default hard-coded exceptions

This could be easily done with a flag use_default_exceptions which defaults to true.

swipe_nav:
  use_default_exceptions: false

This flag would be quite useless alone, therefore the user should be able to add custom exceptions.

Provide a way for the user to add exceptions via CSS selectors

swipe_nav:
  custom_exceptions:
    - div.class1.class2
    - special-tag
    - g.my-special-class

Drawbacks

In this implementation, when setting use_default_exceptions to false the user needs to manually copy the hard-coded exception list and put them as custom_exceptions. And although it is suboptimal, it is not that uncommon. Home Assistant default configuration works in the same way. I think that creating a system of inclusions/exclusions would only complicate things with little gain since I suspect that use_default_exceptions would only be used in rare circumstances.

See also:

• mayker comment on the home assistant community.