Hello,
I have an Ikea Symfonisk rotary button (E1744 model) - (SYMFONISK white, Sound remote - IKEA).
This button is integrated into my HomeAssistant via deconz (Conbee II stick). I have recently observed an issue: any action on this button (click, double click, triple click) is reported twice as a deconz_event with just a few ms time difference.

This is the event log for a double-click - see the event (1004) being reported twice at a 50ms interval.

Événement 15 déclenché 11:55:
{
    "event_type": "deconz_event",
    "data": {
        "id": "symfonisk_controller",
        "unique_id": "84:2e:14:ff:fe:b1:e2:7f",
        "event": 1004,
        "device_id": "cb2408579ca737d345bdcb4bd7bb3541"
    },
    "origin": "LOCAL",
    "time_fired": "2021-06-05T09:55:10.222381+00:00",
    "context": {
        "id": "41884d08b42d3b5e9282c207237664d5",
        "parent_id": null,
        "user_id": null
    }
}
Événement 14 déclenché 11:55:
{
    "event_type": "deconz_event",
    "data": {
        "id": "symfonisk_controller",
        "unique_id": "84:2e:14:ff:fe:b1:e2:7f",
        "event": 1004,
        "device_id": "cb2408579ca737d345bdcb4bd7bb3541"
    },
    "origin": "LOCAL",
    "time_fired": "2021-06-05T09:55:10.178372+00:00",
    "context": {
        "id": "99ab15b1320c9573c7b695169b9e072a",
        "parent_id": null,
        "user_id": null
    }
}

It obviously results in unwanted behavior with my automations.

However, there is no issue with my Tradfri ON/OFF Switches (model E1743), which are integrated with deconz too. All events are reported only once with these devices.
Has anyone experienced this problem before ? Could it be a problem with the button itself ? Or a recent update of the Deconz ?

Thanks for your support !

1 post - 1 participant

Read full topic

Hello,
I have created some sensors and templates previously that rounds values for the Lovelace cards for example.

Now I tried to create a sensor from the temperature attribute of a device, a xiaomi plug or in particular “chuangmi” plug, which you can see here

HA - sensor missing876×95 26.5 KB

The code I used before in such cases did not create an error but also does not show a result except the new sensor shows “unknown” but not the temperature figure. I tried it even without round in case could have been a string and not an integer.

  - platform: template
    sensors:
      temperatur_drucker_xiaomi:
        friendly_name: "TEMPERATUR - DRUCKER am 'Xiaomi Socket'"
        value_template: "{{ state_attr ( 'sensor.switch.chuangmi_plug_m1' , 'temperature' | round(0) ) }}"

What am I missing ?
thx

1 post - 1 participant

Read full topic

I have a lovelace entity card with custom-buttons that I want to align horizontally. I have been able to achieve this when I use a horizontal-stack card(below) however I want to do this within an entity card with other entities. I am sure it is just a formatting issie, but I cannot seem to get this to work. Any help would me much appreciated.

This is what my entity card looks like

This is my code for the entity card

type: entities
entities:
  - cards:
      - content: '## Front Yard'
        style: |
          ha-card {
            background: rgba(0, 0, 0, 0);
            box-shadow: none;
          }
          .markdown {
            padding-left: 0px;
          }
        type: markdown
      - entity: script.sprinkler_zone_front
        layout: icon_name
        name: Run Now
        size: 30px
        state:
          - icon: 'mdi:play-circle'
            value: 'off'
          - icon: 'mdi:autorenew'
            spin: true
            styles:
              card:
                - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
            value: 'on'
        styles:
          card:
            - border-radius: 10px
            - background-color: '#333'
        tap_action:
          action: call-service
          service: script.toggle
          service_data:
            entity_id: script.sprinkler_zone_front
        type: 'custom:button-card'
    layout: horizontal
    min_columns: 2
    type: 'custom:layout-card'
  - conditions:
      - entity: script.sprinkler_zone_front
        state: 'on'
    name: Zone currently running
    row:
      entity: sensor.sprinkler_current_zone
      icon: 'mdi:numeric'
    type: conditional
  - conditions:
      - entity: script.sprinkler_zone_front
        state: 'on'
    row:
      entity: sensor.sprinkler_zone_front_time_remaining
      icon: 'mdi:progress-clock'
    type: conditional
  - type: divider
  - entity: input_number.station1_run_time
    icon: 'mdi:sprinkler'
    name: Zone 1
  - entity: input_number.station2_run_time
    icon: 'mdi:sprinkler'
    name: Zone 2
  - entity: input_number.station3_run_time
    icon: 'mdi:sprinkler'
    name: Zone 3
  - type: divider
  - type: 'custom:button-card'
    color_type: card
    state:
      - icon: 'mdi:cancel'
        value: 'off'
        styles:
          card:
            - color: '#F8390A'
      - icon: 'mdi:check-circle'
        styles:
          card:
            - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
            - color: '#2AB81E'
        value: 'on'
    styles:
      name:
        - size: 5px
        - color: yellow
        - font-size: 15px
      card:
        - width: 40px
        - height: 40px
        - background-color: blue
        - border-radious: 10px
        - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
    entity: input_boolean.station1_mon
    name: Mon
    icon: 'mdi:check-circle'
  - type: 'custom:button-card'
    color_type: card
    state:
      - icon: 'mdi:cancel'
        value: 'off'
        styles:
          card:
            - color: '#F8390A'
      - icon: 'mdi:check-circle'
        styles:
          card:
            - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
            - color: '#2AB81E'
        value: 'on'
    styles:
      name:
        - size: 5px
        - color: yellow
        - font-size: 15px
      card:
        - width: 40px
        - height: 40px
        - background-color: blue
        - border-radious: 10px
        - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
    entity: input_boolean.station1_tue
    name: Tue
    icon: 'mdi:check-circle'
show_header_toggle: false

This is what my horizontal-stack card looks like. This is the look I am trying to achieve

This is the code for my horizontal-stack card

type: horizontal-stack
color: blue
cards:
  - type: 'custom:button-card'
    color_type: card
    state:
      - icon: 'mdi:cancel'
        value: 'off'
        styles:
          card:
            - color: '#F8390A'
      - icon: 'mdi:check-circle'
        styles:
          card:
            - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
            - color: '#2AB81E'
        value: 'on'
    styles:
      name:
        - size: 5px
        - color: yellow
        - font-size: 15px
      card:
        - width: 40px
        - height: 40px
        - background-color: blue
        - border-radious: 10px
        - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
    color: Black
    entity: input_boolean.station1_mon
    name: Mon
    icon: 'mdi:check-circle'
  - type: 'custom:button-card'
    color_type: card
    state:
      - icon: 'mdi:cancel'
        value: 'off'
        styles:
          card:
            - color: '#F8390A'
      - icon: 'mdi:check-circle'
        styles:
          card:
            - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
            - color: '#2AB81E'
        value: 'on'
    styles:
      name:
        - size: 5px
        - color: yellow
        - font-size: 15px
      card:
        - width: 40px
        - height: 40px
        - background-color: blue
        - border-radious: 10px
        - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
    color: Black
    entity: input_boolean.station1_tue
    name: Tue
    icon: 'mdi:check-circle'
  - type: 'custom:button-card'
    color_type: card
    state:
      - icon: 'mdi:cancel'
        value: 'off'
        styles:
          card:
            - color: '#F8390A'
      - icon: 'mdi:check-circle'
        styles:
          card:
            - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
            - color: '#2AB81E'
        value: 'on'
    styles:
      name:
        - size: 5px
        - color: yellow
        - font-size: 15px
      card:
        - width: 40px
        - height: 40px
        - background-color: blue
        - border-radious: 10px
        - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
    color: black
    entity: input_boolean.station1_wed
    name: Wed
    icon: 'mdi:check-circle'
  - type: 'custom:button-card'
    color_type: card
    state:
      - icon: 'mdi:cancel'
        value: 'off'
        styles:
          card:
            - color: '#F8390A'
      - icon: 'mdi:check-circle'
        styles:
          card:
            - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
            - color: '#2AB81E'
        value: 'on'
    styles:
      name:
        - size: 5px
        - color: yellow
        - font-size: 15px
      card:
        - width: 40px
        - height: 40px
        - background-color: blue
        - border-radious: 10px
        - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
    color: black
    entity: input_boolean.station1_thu
    name: Thu
    icon: 'mdi:check-circle'
  - type: 'custom:button-card'
    color_type: card
    state:
      - icon: 'mdi:cancel'
        value: 'off'
        styles:
          card:
            - color: '#F8390A'
      - icon: 'mdi:check-circle'
        styles:
          card:
            - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
            - color: '#2AB81E'
        value: 'on'
    styles:
      name:
        - size: 5px
        - color: yellow
        - font-size: 15px
      card:
        - width: 40px
        - height: 40px
        - background-color: blue
        - border-radious: 10px
        - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
    color: black
    entity: input_boolean.station1_fri
    name: Fri
    icon: 'mdi:check-circle'
  - type: 'custom:button-card'
    color_type: card
    state:
      - icon: 'mdi:cancel'
        value: 'off'
        styles:
          card:
            - color: '#F8390A'
      - icon: 'mdi:check-circle'
        styles:
          card:
            - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
            - color: '#2AB81E'
        value: 'on'
    styles:
      name:
        - size: 5px
        - color: yellow
        - font-size: 15px
      card:
        - width: 40px
        - height: 40px
        - background-color: blue
        - border-radious: 10px
        - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
    color: black
    entity: input_boolean.station1_sat
    name: Sat
    icon: 'mdi:check-circle'
  - type: 'custom:button-card'
    color_type: card
    state:
      - icon: 'mdi:cancel'
        value: 'off'
        styles:
          card:
            - color: '#F8390A'
      - icon: 'mdi:check-circle'
        styles:
          card:
            - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
            - color: '#2AB81E'
        value: 'on'
    styles:
      name:
        - size: 5px
        - color: yellow
        - font-size: 15px
      card:
        - width: 40px
        - height: 40px
        - background-color: blue
        - border-radious: 10px
        - box-shadow: 0 0 4px 2px var(--paper-item-icon-active-color)
    color: black
    entity: input_boolean.station1_sun
    name: Sun
    icon: 'mdi:check-circle'

1 post - 1 participant

Read full topic

Hey, I installed home assistant for the first time, and I’m a bit confused. I use zigbee2mqtt (on another machine), mosquitto and enabled the MQTT binding in HA. I enabled the HA support in the zigbee2mqtt config, and every device immediately showed up in HA with all data I wanted to see (which was quite impressive so far!).

But now I have two problems, and I’m not sure if I’m doing something wrong or if this is the intended way:

1. If I restart, all mqtt entities are gone, while all non mqtt devices are still present. I have to restart zigbee2mqtt to see all entities again.
2. While I can see all sensor data, I cannot interact with the light (HG06104A). If I toggle the switch on the dashboard, nothing happens, and it just will go back to off.

The z2mqtt device documentation site mentions a manual configuration; when I use this, everything works, and I can toggle the switch, and it also stays after a restart. Is this the way to go, or should all this work “out of the box” with the auto-discovery?

My confusion comes because the site states “Although Home Assistant integration through MQTT discovery is preferred, manual integration is possible with the following configuration”. So it sounds like it should “just work” with the auto-discovery. I’m fine with configuring it through the configuration.yaml, but right now, I have the feeling that something is broken in my setup. Could someone bring some insight, if everything works as intended or where I could start looking for errors?

About my setup:

Home Assistant:
Docker Latest (Home Assistant 2021.6.0)
Just started it with the basic configuration and added mqtt as well as an ikea gateway.

Zigbee2mqtt: 1.19.0, running on a different raspberry pi, added homeassistant: true and friendly names to the configuration
C2531 firmware: 20201127

Mosquttio: Docker latest (2.0.10)

Devices:
Some Lidl HG06104A, Xiaomi WSDCGQ11LM and Xiaomi MCCGQ11LM devices

1 post - 1 participant

Read full topic

since a sort time my dwd_weather_warnings sensor is always unavailable. I already changed the warncallid without any success. Has anybody an idea what’s wrong with dwd?
My current sensor look like this

platform: dwd_weather_warnings
region_name: Kreis Vulkaneifel

I can not find any log error’s or warning’s.

3 posts - 1 participant

Read full topic

Hi Guys, have darkSky stopped access to their API, if so what alternative you using?

Thanks

1 post - 1 participant

Read full topic

Hello everyone,

I’m totally new to HA and Yaml. I’m on Raspberry, home assistant os 5.13, core-2021.6.2
I’m trying to set-up a simple automation related to Sun integration. I’ve copy-pasted some examples, set as “working code”, I found on the forum but I’m always getting different errors like

Message malformed: extra keys not allowed @
or
Message malformed: not a valid value for dictionary value @
or
Message malformed: expected dictionary

I’ve tryied to pay attention to indentation as some posts suggested but i’m still having troubles.

Could somebody give me an example to automate an entity id “light.led” to turn on at sunset with an offset?

Thank you

1 post - 1 participant

Read full topic

Lovelace can not format values so I need to create new sensors with rounded values instead of 24,22 nicer looking 24. I do not wanna change it manually through the interface cause that is unreliable if you change the sensor title later.

I tried this but got an error “invalid option” or so.

  - platform: template
    sensors:
      temperature_printer_via_xiaomi_plug:
        icon: 'mdi:thermometer-lines'
        value_template: "{{ state_attr('switch.chuangmi_plug_m1', 'temperature') | round(0) }}"

Hope someone finds the point I can not see right now. thx

1 post - 1 participant

Read full topic

I am trying to create some automations with homematic thermostats.
I know how to set the temperature with an automation, but my problem is that I am unable to get the temperature of a thermostat.
I want to use the temperature as a trigger, but somehow it is not working.

platform: numeric_state
entity_id: climate.leq0862257
above: '20'
attribute: temperature

My other problem is that I want to send the temperature via a notification, but with this code I only receive “Auto” instead of a temperature value.

service: notify.mobile_app_ipad_von_raphael
data:
  title: Test
  message: Temperatur {{state('climate.leq0862930') }} °C

Has anyone some experience what I need to fix?
Thanks in advance

1 post - 1 participant

Read full topic

Hi,

since 2021.6.2 my sensor to read the log file doesn’t work anymore.

I get:

Error adding entities for domain sensor with platform file
Error while setting up file platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 383, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 588, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 615, in add_to_platform_finish
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 368, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 494, in _async_write_ha_state
    self.hass.states.async_set(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1218, in async_set
    state = State(
  File "/usr/src/homeassistant/homeassistant/core.py", line 906, in __init__
    raise InvalidStateError(
homeassistant.exceptions.InvalidStateError: Invalid state encountered for entity ID: sensor.log_tail. State max length is 255 characters.

This is my configuration on the sensor.yaml

 - platform: file
    file_path: /config/home-assistant.log
    name: Log tail
    value_template: >
      {{value|truncate(255,True)}}

1 post - 1 participant

Read full topic

Hello!

Can someone tell me what is the difference between these two lines?

{{ states.sensor_newma_activation.state }}
{{ states("sensor_newma_activation") }}

I know that the lines could act different in some situations, but why?! What’s the purpose of each line?

Thank you!

1 post - 1 participant

Read full topic

Hello,

I have been using Hassio with my Xiaomi Gateway for a while now. Everything was fine until yesterday, my gateway suddenly couldn’t connect to hassio, as well as all my other xiaomi components (lights, sensors, etc…).
I noticed on the xiaomi app itself, the gateway wasn’t detected anymore. So i did the pairing again with my phone, using the mainland china server, and i now see it again on my phone. Using the Mi Home app, i can see them and control them fine.
However, it seems like hassio still can’t connect to either the gateway or the lights. I tried to enable developer mode, but with the new app version there is no “about” section so it’s impossible to activate developer mode. I would like to make sure the key i’m using is still valid but i can’t really know.
I have been pulling my hair over this and this is driving me insane. It used to work perfectly for multiple years, and out of the blue nothing works.
The logs are not helpful:

• Cannot connect to Gateway (super explicit message…)
• Unknown gateway IP 192.168.1.3

When i look at my configuration.yaml file, i didn’t specify the gateway ip. My entry looks like this:

xiaomi_aqara:
  discovery_retry: 5
  gateways:
    - key: XXXXXXXXX

I’m not even getting an error message for the yeelight lights. They show up as disconected, but no trace in the logs…

Thanks for the help, i really need it!

1 post - 1 participant

Read full topic

Hi all!
I’m trying to show a blinking warning notification when a binary sensor is active using an image inside a picture elements. I have the code below but it doesn’t work. Does anyone know how to do it?

type: picture-elements
image: 'https://demo.home-assistant.io/stub_config/floorplan.png'
elements:
  - type: image
    entity: binary_sensor.alarm
    style:
      top: 35%
      left: 49%
      animation: blink 2s linear infinite

    state_image:
      'on': /local/images/icon-alert.png

1 post - 1 participant

Read full topic

The only updates showing in Supervisor are add-ons.

Version

core-2021.5.0

Newest Version

core-2021.5.0

The latest verion is, I believe, 2021.6.

In the log I’m seeing:

21-06-05 09:56:24 WARNING (MainThread) [supervisor.host.network] Can't update connectivity information: Error: Timeout was reached

Does this have anything to do with the problem?

My HA instance is connected as I can update add-ons fine.

1 post - 1 participant

Read full topic

Hi, i own 3 IMOU IP cameras (Cue 2 and Ranger) integrated via Onvif protocol. I read some time ago that there was a problem with the motion sensor created by the integration. As i remember the problem was that the sensor was created, but never updated (basically it was not working).

Now, when i integrate the cameras via Onvif, Home Assistant creates only 2 entities: High and Low definition video streams. It doesn’t create any motion sensor.

Am i missing sometring? I’m using Onvif, ip of the camera, port 80, admin and password…
Thanks

1 post - 1 participant

Read full topic

Dear Hass Community,

I need your help:

I want to calculate currency exchange rates. I am using for this the API of fixer.

Now I want to add a new sensor. The Value of my new sensor “currency_calculated” should be:

1 / sensor value of “currency”

This is my code: What did I do wrong?

Thanks so much for your help!

• platform: fixer
  api_key: XXX
  target: GBP
  name: currency

• platform: template
  sensors:
  currency_calculated:
  value_template: {{ 1 / (states(‘sensor.currency’)) }}

1 post - 1 participant

Read full topic

I must be missing something very simple here:

alarm_control_panel.home_alarm is my real ring alarm panel and works fine i just but need a keypad to disarm for security obviously or anyone that might break in can just hit DISARM on tablet and stop alarm

alarm_control_panel.ha_alarm is manual created panel WITH keypad/code and works great just dont actual control the actual ring integration/mqtt

I have read a few post but cant seem to understand how this works
how would i make the manual created panel control the actual alarm?

This is what i have in configuration.yaml:

alarm_control_panel:

• platform: manual_mqtt
  state_topic: home/alarm
  command_topic: home/alarm/set
  code: 1234
  pending_time: 30
  delay_time: 20
  trigger_time: 4
  disarmed:
  trigger_time: 0
  armed_home:
  pending_time: 0
  delay_time: 0
  triggered:
  pending_time: 0

1 post - 1 participant

Read full topic

Is there a bit torrent integration for home assistant? I have a bunch of torrents already on it and was hoping I could manage it via home assistant somehow.

1 post - 1 participant

Read full topic

I am trying to write this automation to notify me if either my patio or front door has been left opened for more than 65 seconds.

If opened for 65 seconds, send a notification, wait 90 seconds, check if the binary_sensor that triggered the automation is now “off”, rinse and repeat.

The problem is the keeps notifying me even after the binary_sensor(s) are off (verified in Developers Tools).

So it seems there is an issue with this part:

        until:
          # Did it work?
          - condition: template
            value_template: "{{ trigger.to_state.state == 'off'}}"

Entire automation:

id: test-automation
  trigger:
    - platform: state
      entity_id: binary_sensor.patio_door_sensor
      to: 'on'
      for:
        seconds: 65
    - platform: state
      entity_id: binary_sensor.front_door_sensor
      to: 'on'
      for:
        seconds: 65
  action:
    - repeat:
        sequence:
          - service: notify.mobile_app_iphone
            data_template:
              title: "Test"
              message: "Test msg"

          - delay:
              seconds: 90
        until:
          # Did it work?
          - condition: template
            value_template: "{{ trigger.to_state.state == 'off'}}"

1 post - 1 participant

Read full topic

Tried to install ESPHome and then compile the setup i see those errors:

sh: 1: xtensa-lx106-elf-g++: not found

INFO Reading configuration /config/esphome/test.yaml...
INFO Generating C++ source...
INFO Compiling app...
INFO Running:  platformio run -d /config/esphome/test
Processing test (board: d1_mini; framework: arduino; platform: platformio/espressif8266@2.6.2)
--------------------------------------------------------------------------------
HARDWARE: ESP8266 80MHz, 80KB RAM, 4MB Flash
PACKAGES: 
 - framework-arduinoespressif8266 3.20704.0 (2.7.4) 
 - tool-esptool 1.413.0 (4.13) 
 - tool-esptoolpy 1.20800.0 (2.8.0) 
 - toolchain-xtensa 2.40802.200502 (4.8.2)
Library Manager: Installing Update
Library Manager: Already installed, built-in library
Dependency Graph
|-- <ESPAsyncTCP-esphome> 1.2.3
|   |-- <ESP8266WiFi> 1.0
|-- <ESPAsyncWebServer-esphome> 1.2.7
|   |-- <ESPAsyncTCP-esphome> 1.2.3
|   |   |-- <ESP8266WiFi> 1.0
|   |-- <Hash> 1.0
|   |-- <ESP8266WiFi> 1.0
|-- <ESP8266WiFi> 1.0
|-- <ESP8266mDNS> 1.2
|   |-- <ESP8266WiFi> 1.0
|-- <DNSServer> 1.1.1
|   |-- <ESP8266WiFi> 1.0
Compiling /data/test/.pioenvs/test/src/esphome/components/api/api_connection.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
Compiling /data/test/.pioenvs/test/src/esphome/components/api/api_pb2.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
Compiling /data/test/.pioenvs/test/src/esphome/components/api/api_pb2_service.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
*** [/data/test/.pioenvs/test/src/esphome/components/api/api_connection.cpp.o] Error 127
Compiling /data/test/.pioenvs/test/src/esphome/components/api/api_server.cpp.o
*** [/data/test/.pioenvs/test/src/esphome/components/api/api_pb2.cpp.o] Error 127
*** [/data/test/.pioenvs/test/src/esphome/components/api/api_pb2_service.cpp.o] Error 127
sh: 1: xtensa-lx106-elf-g++: not found
*** [/data/test/.pioenvs/test/src/esphome/components/api/api_server.cpp.o] Error 127
========================== [FAILED] Took 3.31 seconds ==========================

Tried many things but cant solve it.

1 post - 1 participant

Read full topic