I’m obviously missing something crucial here. The logic works fine in the Developer tools, and have based the rest of it on the templating docs. But I can’t figure out why HA throws a wobbly at this.

What am I doing wrong?! Suggestions gratefully received…

- platform: template
  sensors:
    awc_status:
        friendly_name: 'AWC Status'           
        value_template: >
              {% if is_state('switch.tapo_10', 'on') 
                 and is_state('switch.tapo_13', 'on') %}
                Overflow
              {% elif  is_state('switch.tapo_10', 'off')  
                 and is_state('switch.tapo_13', 'off') %}
                Standby
              {% elif  is_state('switch.tapo_10', 'on')  
                 and is_state('switch.tapo_13', 'off') %}
                Drain
              {% elif  is_state('switch.tapo_10', 'off')  
                 and is_state('switch.tapo_13', 'on') %}
                Fill
              {% else %}
                Error
              {% endif %}

Actually appears to break HA in some way (won’t restart / check config without throwing errors).

The logs show:

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/config.py”, line 895, in async_process_component_config
p_validated = platform.PLATFORM_SCHEMA(p_config) # type: ignore
File “/usr/local/lib/python3.9/site-packages/voluptuous/validators.py”, line 218, in call
return self._exec((Schema(val) for val in self.validators), v)
File “/usr/local/lib/python3.9/site-packages/voluptuous/validators.py”, line 337, in _exec
v = func(v)
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 272, in call
return self._compiled([], data)
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 817, in validate_callable
return schema(data)
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 272, in call
return self._compiled([], data)
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 594, in validate_dict
return base_validate(path, iteritems(data), out)
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 386, in validate_mapping
cval = cvalue(key_path, value)
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 817, in validate_callable
return schema(data)
File “/usr/src/homeassistant/homeassistant/helpers/config_validation.py”, line 489, in verify
return cast(dict, schema(value))
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 272, in call
return self._compiled([], data)
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 594, in validate_dict
return base_validate(path, iteritems(data), out)
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 386, in validate_mapping
cval = cvalue(key_path, value)
File “/usr/local/lib/python3.9/site-packages/voluptuous/validators.py”, line 215, in _run
return self._exec(self._compiled, value, path)
File “/usr/local/lib/python3.9/site-packages/voluptuous/validators.py”, line 339, in _exec
v = func(path, v)
File “/usr/local/lib/python3.9/site-packages/voluptuous/schema_builder.py”, line 817, in validate_callable
return schema(data)
File “/usr/src/homeassistant/homeassistant/helpers/config_validation.py”, line 750, in validator
if key in config:
TypeError: argument of type ‘NoneType’ is not iterable

1 post - 1 participant

Read full topic

Hi,

I’m using a blueprint so automate the double press of the ON button on my inovelli switch. Now i wanted to add that when the sun is below horizon the color temp of the light bulb is set.

here is what i got:

- id: '1635288344964'
  alias: Light Louis On/Off
  description: ''
  use_blueprint:
    path: jerelabs/zwave-js-inovelli-lzw31-sn-red-series-dimmer.yaml
    input:
      inovelli_switch: d4dcdd870e75a7b85d619c0908b8ddfb
      button_a2:
      - service: light.turn_on
        target:
          entity_id: light.ampoule_a_louis
        data:
          color_temp: >-
            {% if is_state('sun.sun','below_horizon') %}
              color_temp: 461
            {% else %}
              color_temp: '{{ range(40, 600) | random }}'
      button_b2:
      - service: light.turn_off
        target:
          entity_id: light.ampoule_a_louis
        data: {}

But the color_temp is not set. I have search in the forum and documentation and didn’t find anything to help me out. What is the correct format to add an IF statement ?

Thanks

1 post - 1 participant

Read full topic

Hey,

need you’re advise/help.
I have integrated my air ventilation system with this guide as templated sensor
Integrate Poloplast PoloAir ventilation systems using Modbus integration.

is it possible (how) to appear this system as consumer in the energy dashboard?. currently the sensor doesn’t appear in the config.

Thank you very much!

cheers

1 post - 1 participant

Read full topic

Hi

I’m a newbie to HA and Home Automation in general and I’m 73 years of age and been working with things Computer for 52 years now so forgive me if some of my terminology is a little dated.

I don’t think Saswell have a concise name for this system and it is sold on Amazon as

SASWELL TUYA WiFi Heating TRV Radiator Thermostat with Hot Water Control,Smart Radiator Thermostat, Dual Channel Wireless Receiver(Starter Kit), Compatible with Alexa, Google Assistance.

and comprises an SASWG-04-RF-WIFI(TY) Gateway, a single SEA802-DF TRV and an SAS2016DE2 Receiver. The receiver is effectively a 2 channel switch turning on and off the Central Heating and Water Heating functions of the boiler.

The system does work (though certain components appear to go on and offline randomly) but its implementation in the SmartLife app is extremely poor and I would say unstable.

In addition 2 this I also have a single SmartHome smart breaker which is wi-fi controlled.

Tuya recognises all these components in both SmartLife and in the IoT Platform but when I add the Tuya integration, only the TRV’s are discovered and the SmartHome breaker and the Saswell Receiver are not brought across. Conversley when I add Local Tuya only the Gateway and the Smart Breaker are discovered and if I try to add the Gateway I get the error message .

Failed to authenticate with device. Verify that device id and local key are correct.

The Smart breaker does add in properly

Am I doing something wrong or is it that the Saswell Gateway and Receiver are not implemented in Tuya Local

Can anyone help please

1 post - 1 participant

Read full topic

Since core update to 2021.11 the entities in my homebridge instance are no longer available.
Set up a complete new instance, it got detected, but when configuring I get “Flow not found”.
Any help is appreciated.

1 post - 1 participant

Read full topic

I have a really simple button showing the status and I want to display a custom field underneath but as you see the text is aligning right. Can anyone suggestion how I can make it centre, underneath the name?

type: custom:button-card
size: 80px
tap_action:
  action: call-service
  service: automation.trigger
  service_data:
    entity_id: automation.heating_on_if_temp_low_in_morning_duplicate
show_name: true
show_label: false
name: |
  [[[
    var sta = states['climate.hall'].attributes.hvac_action;
    return 'Status: ' + "" + sta + ""   ;
  ]]]
icon: mdi:fire
styles:
  grid:
    - grid-template-areas: '"i" "n" "s"'
    - grid-template-columns: 100%
    - grid-template-rows: min-content min-content 1fr
  card:
    - background-color: '#fff'
    - border-radius: 10%
  name:
    - font-size: 14px
    - color: black
  icon:
    - color: |
        [[[
          if (states['climate.hall'].attributes.hvac_action == 'off') return 'blue';
          else return 'orange';
        ]]]
  custom_fields:
    boost:
      - color: black
      - justify-self: end
custom_fields:
  boost: |
    [[[
      return `<ha-icon
        icon="mdi:thermometer"
        style="width: 12px; height: 12px; color: yellow;text-align:center">
        </ha-icon><span>${states['sensor.timer_60minutes_remaining'].state}</span>`
    ]]] 

2 posts - 2 participants

Read full topic

I don’t have a whole house monitoring system, but I do have a stack of Kasa individual wifi plugs. Instead of adding each device individually into the energy ‘electricity grid’ section using its total kWh consumption, I have created a sum of all of the devices in a group I wish to mostly monitor. I wanted to have 3 or 4 different groups and then add them into the ‘electricity grid’ section.

I can get the total of devices added up fine with a template but I am missing the one critical element… “state_class: total_increasing”. How do I add this to the sensor.yaml file?

      nats_total_current_consumption:
        friendly_name: "Nats Consumption Total"
        unit_of_measurement: 'kWh'
        icon_template: 'mdi:flash'
        device_class: 'energy'
        value_template: >-
          {% if not is_state('sensor.nats_subwoofer_current_consumption', 'unknown') %}
            {{ 
            ((states('sensor.nats_room_air_conditioning_total_consumption')|float) + 
            (states('sensor.nat_s_laptops_total_consumption')|float) + 
            (states('sensor.nat_s_bedroom_dyson_total_consumption')|float) +
            (states('sensor.nat_s_audio_equip_total_consumption')|float) +
            (states('sensor.nat_s_tv_unit_total_consumption')|float) +
            (states('sensor.nats_subwoofer_total_consumption')|float) +
            (states('sensor.nat_s_fridge_total_consumption')|float) +
            (states('sensor.nat_s_bedroom_side_table_total_consumption')|float) +
            (states('sensor.nat_s_bedroom_tv_total_consumption')|float))
             }}
          {%endif %}          

1 post - 1 participant

Read full topic

I cannot Get the Simplisafe webapp to do anything past the signon it never opens a second page with the Code as described in the Documentation. any help would be appreciated. Everything worked fine in 2021.10.06 but not 2021.11.0 or the Betas.

1 post - 1 participant

Read full topic

hi,
I have a sensor that monitors the consumption of two pzem:

    consumo_totale_watts:
      friendly_name: "Consumo totale Watts"
      value_template: "{{ states('sensor.pzem_016_energy_power') | float + states('sensor.pzem_016_2_energy_power') | float }}"
      unit_of_measurement: 'W'

in the logs i can see:

**Template warning: 'float' got invalid input 'unknown' when rendering template '{{ states('sensor.pzem_016_energy_power') | float + states('sensor.pzem_016_2_energy_power') | float }}' but no default was specified. Currently 'float' will return '0', however this template will fail to render in Home Assistant core 2022.1**

could you advise me how to eliminate the error?


thank you so much in advance for your help

2 posts - 2 participants

Read full topic

I did yesterday update to the newest ZwaveJS2Mqtt version. And made a re-interview of all the nodes.
After that I figured out that my Fibaro Wally Double Switch FGWDSEU-221 doesn’t transfer the On/Off states from the node to HA anymore.
I did try to play around with associations, but couldn’t figure how to fix it.

zwavejs2mqtt: 5.10.1
zwave-js: 8.6.1

That’s from the log:

{
  "id": 10,
  "name": "Double Switch WC/VMC",
  "loc": "Corridor",
  "values": [
    {
      "id": "10-134-0-libraryType",
      "nodeId": 10,
      "commandClass": 134,
      "commandClassName": "Version",
      "endpoint": 0,
      "property": "libraryType",
      "propertyName": "libraryType",
      "type": "number",
      "readable": true,
      "writeable": false,
      "label": "Library type",
      "stateless": false,
      "list": true,
      "states": [
        {
          "text": "Unknown",
          "value": 0
        },
        {
          "text": "Static Controller",
          "value": 1
        },
        {
          "text": "Controller",
          "value": 2
        },
        {
          "text": "Enhanced Slave",
          "value": 3
        },
        {
          "text": "Slave",
          "value": 4
        },
        {
          "text": "Installer",
          "value": 5
        },
        {
          "text": "Routing Slave",
          "value": 6
        },
        {
          "text": "Bridge Controller",
          "value": 7
        },
        {
          "text": "Device under Test",
          "value": 8
        },
        {
          "text": "N/A",
          "value": 9
        },
        {
          "text": "AV Remote",
          "value": 10
        },
        {
          "text": "AV Device",
          "value": 11
        }
      ],
      "value": 3,
      "newValue": 3
    },
......
 "groups": [
    {
      "text": "Lifeline",
      "endpoint": 0,
      "value": 1,
      "maxNodes": 1,
      "isLifeline": true,
      "multiChannel": true
    },
    {
      "text": "On/Off (1)",
      "endpoint": 0,
      "value": 2,
      "maxNodes": 5,
      "isLifeline": false,
      "multiChannel": true
    },
    {
      "text": "Dimmer (1)",
      "endpoint": 0,
      "value": 3,
      "maxNodes": 5,
      "isLifeline": false,
      "multiChannel": true
    },
    {
      "text": "On/Off (2)",
      "endpoint": 0,
      "value": 4,
      "maxNodes": 5,
      "isLifeline": false,
      "multiChannel": true
    },
    {
      "text": "Dimmer (2)",
      "endpoint": 0,
      "value": 5,
      "maxNodes": 5,
      "isLifeline": false,
      "multiChannel": true
    },
    {
      "text": "Lifeline",
      "endpoint": 1,
      "value": 1,
      "maxNodes": 1,
      "isLifeline": true,
      "multiChannel": true
    },
    {
      "text": "On/Off (1)",
      "endpoint": 1,
      "value": 2,
      "maxNodes": 5,
      "isLifeline": false,
      "multiChannel": true
    },
    {
      "text": "Dimmer (1)",
      "endpoint": 1,
      "value": 3,
      "maxNodes": 5,
      "isLifeline": false,
      "multiChannel": true
    },
    {
      "text": "Lifeline",
      "endpoint": 2,
      "value": 1,
      "maxNodes": 1,
      "isLifeline": true,
      "multiChannel": true
    },
    {
      "text": "On/Off (2)",
      "endpoint": 2,
      "value": 2,
      "maxNodes": 5,
      "isLifeline": false,
      "multiChannel": true
    },
    {
      "text": "Dimmer (2)",
      "endpoint": 2,
      "value": 3,
      "maxNodes": 5,
      "isLifeline": false,
      "multiChannel": true
    }

1 post - 1 participant

Read full topic

Hi,

is it possible to manually trigger a refresh of a restful sensor? According to the docs, there is no command for rest sensors. Only rest.refresh what I guess is to reload the configuration.

Background is: I have a template switch which is based on a rest sensor. If you toggle the switch, the command is sent. But the switch still shows the old state, until the next refresh of the rest sensor. This is confusing…

1 post - 1 participant

Read full topic

I have a bedtime timer that will turn off the tv and set a boolean when completed. The automation is set to restart the timer if I click it again. Im trying to figure out a way to send an “android TV notification” to the tv when there is 1 minute in case I want to add more time.

I have not been able to figure this out. I think its crazy that the the real time countdown you see in the frontend cannot be used as an attribute. Im wondering if I have to bite the bullet and use Node Red for this.

3 posts - 2 participants

Read full topic

Hi Guys, I hope anybody can help me. I’m pretty new to HA.

What I try to to achieve is:
Turning on my receiver when I stream from a Google Home to a Chromecast. And when I stop streaming to turn off the receiver. In both cases I need to change the source.

Turning OFF and changing the AV3 works like a charm. But turning does not work at all and I have no glue whats going wrong.

Below is what I created with the Assistent for Automations.

Thanks in advance.

- id: '1636028526076'
  alias: Receiver turn on and change source
  description: when Chromecast is activ
  trigger:
  - platform: state
    entity_id: media_player.wohnzimmer
    from: off
    to: playing
    for:
      hours: 0
      minutes: 0
      seconds: 2
      milliseconds: 0
  condition: []
  action:
  - service: media_player.turn_on
    target:
      entity_id: media_player.yamaha_receiver
  - service: media_player.select_source
    target:
      entity_id: media_player.yamaha_receiver
    data:
      source: HDMI4
  mode: single
- id: '1636029055909'
  alias: Turn off receiver when Chromecast stops
  description: ''
  trigger:
  - platform: state
    entity_id: media_player.wohnzimmer
    from: playing
    to: off
    for:
      hours: 0
      minutes: 0
      seconds: 2
      milliseconds: 0
  condition: []
  action:
  - service: media_player.select_source
    target:
      entity_id: media_player.yamaha_receiver
    data:
      source: AV3
  - service: media_player.turn_off
    target:
      entity_id: media_player.yamaha_receiver
  mode: single

1 post - 1 participant

Read full topic

The 2021.11.0 update provides a new way to integrate with SimpliSafe including step-by-step instructions outlining the proper integration method. Unfortunately, my results do not match the instructions. After receiving the verification email from SimpliSafe, I do not receive an error page but rather a verification successful page. There is no code on the first web page as per the instructions. There is a code on the second web page, however, entering this code in the HA integration page results in a verification failed message.

I’ve tried this from my desktop browser as well as my Android phone with the same results.

I’ve restored my 2021.10.7 environment as that continues to work with SimpliSafe.

1 post - 1 participant

Read full topic

I reported a bug, in a separate post, which turned out not to be a bug but needing some intervention. The “sense” integration provides sensors from Sense (Solar). The only sensors you could configure in the energy panel were things like “Daily from Grid” etc. Theoretically these work, but they only get updated once an hour (either Sense or the integration). These updates don’t always happen exactly on the hour and often are registered in the next hour. This causes corresponding energy bars to be shifted in the hr interval after the one they actually correspond to.

The solution I found is to create a few new template sensors using the provided sensor.energy_production and sensor.energy_usage, both in W and changing more frequently. It starts with:

- sensor:
  # Sensor that returns instantaneous power (W) taken from grid (>= 0), or put to grid (< 0)
  - name: net_power_from_grid
    unique_id: net_power_from_grid
    device_class: power
    unit_of_measurement: W
    availability: >-
      {{ true if states.sensor.energy_production and states.sensor.energy_usage }}
    state: >-
      {{ states.sensor.energy_usage.state | float - states.sensor.energy_production.state | float }}

This produces a more frequently update sensor for net_grid_power. From that we derive two others:

  # Sensor that returns instantaneous power (W) taken from grid (>= 0), or 0 if not taking
  - name: power_from_grid
    unique_id: power_from_grid
    device_class: power
    unit_of_measurement: W
    availability: >-
      {{ true if states.sensor.net_power_from_grid }}
    state: >-
      {{ max(states.sensor.net_power_from_grid.state | float, 0) }}

  # Sensor that returns instantaneous power (W) put to grid (>= 0), or 0 if not putting any
  - name: power_to_grid
    unique_id: power_to_grid
    device_class: power
    unit_of_measurement: W
    availability: >-
      {{ true if states.sensor.energy_production and states.sensor.energy_usage }}
    state: >-
      {{ max(-(states.sensor.net_power_from_grid.state | float), 0) }}

These separately track power to and from the grid, both expressed as positive values. Finally, define the following “integral” sensors to integrate power into energy (kWh):

- platform: integration
  name: home_energy_consumed
  source: sensor.energy_usage
  round: 5
  unit_prefix: k
  unit_time: h
  
- platform: integration
  name: solar_energy_produced
  source: sensor.energy_production
  round: 5
  unit_prefix: k
  unit_time: h
  
- platform: integration
  name: energy_from_grid
  source: sensor.power_from_grid
  round: 5
  unit_prefix: k
  unit_time: h
 
- platform: integration
  name: energy_to_grid
  source: sensor.power_to_grid
  round: 5
  unit_prefix: k
  unit_time: h

You now have all the sensors you need to properly configure the energy panel, but the sensors don’t show up there. You need some customizations that set things you cannot do directly in the above. Put these in customizations.yaml:

sensor.home_energy_consumed:
  device_class: energy
  friendly_name: Energy Consumed by Home
sensor.solar_energy_produced:
  device_class: energy
  friendly_name: Solar Energy Produced
sensor.energy_to_grid:
  device_class: energy
  friendly_name: Energy Sent to Grid
sensor.energy_from_grid:
  device_class: energy
  friendly_name: Consumed from Grid
sensor.power_to_grid:
  friendly_name: Power to Grid
sensor.power_from_grid:
  friendly_name: Power from Grid
sensor.net_power_from_grid:
  friendly_name: Net Power from Grid

So then, finally, you can:

The new sensors update much more frequently, and while there could be still one update that straddles the hour boundary, the difference is now minute and most everything shows up in the right 1 hr interval. Hope this helps somebody!

1 post - 1 participant

Read full topic

Hello!
First of all, im pretty noob with HA. This is like my 2nd week on this.
So I’m try to accompolish the folowing… a custom card with a slider. The left icon and the slider controls the bulb itself (It’s working). The power icon (custom button) “controlls” the smart outlet (Not working).
I know the integration works because I have a separate button and i’ve try on the SCRIPTS in the DEVELOPER TOOLS as well.
Is it this card? Is it incompatible with what im trying toi achive.
Thanks in advance

1 post - 1 participant

Read full topic

Hi all, apologies if this is the wrong place to post this…I’m new here…

Anyways, I’ve got an old Lutron Homeworks Series 8 system installed and I’ve managed to integrate it into Home Assistant using this integration: Lutron Homeworks - Home Assistant.

I’m using a Moxa NPort Serial to Ethernet adapter connected to the Homeworks processer.

When I first start up HA, everything works fine. Lights turn on and off and everything functions like normal. After a while (the time varies, sometimes it’s 10 seconds, sometimes it’s 10 hours) the Lutron lights stop responding in HA. The keypads and physical dimmers still work fine, but when a light is turned on either via HA or a physical switch, HA does not update that light so it remains “off” in Home Assistant. Other devices still work fine in HA. Only Lutron lights stop responding.

Sometimes HA can still control the light (ie dimming and turning on) but the light is stuck in the “Off” position on my dashboard & everywhere else in HA, so I can’t actually turn it off from Home Assistant. Other times, HA cannot control the light or see its on/off status.

I’m running Home Assistant 2021.11.0 on an Intel NUC as HomeAssistant OS. (ie, not through docker - the NUC boots into HA & has nothing else on it)

This also happened when I was using a RasPi 4.

Does anyone know how to fix this so the lights update reliably?

1 post - 1 participant

Read full topic

This is still work in progress, but I prefer continuing the discussion here rather than on a git issue .

The monit tool is generally used for monitoring services on a machine and restart them when necessary. For instance, I use it to monitor apache2, mysql, proprietary services, applications, etc. on servers, embedded systems using *nix, etc.

I discovered it can be installed on HA OS/Core using the “Terminal + SSH” add-on. I haven’t configured it yet, but in order to document it for the community, I started writing a script.

To enable monit in “Terminal + SSH”, you have to add it to the ‘apks’ of the “Terminal + SSH” configuration like so, the example also includes nmap:

authorized_keys:  []
apks:
  - monit
  - nmap
password: ''
server:
  tcp_forwarding: false

After saving the configuration and restarting the add-on, monit should be available in the terminal.
You can verify that monit is running and accessible from CLI:

monit summary

The script below is work in progress and not tested at all at this time.
What it will be doing when tested/finished:

• Create /etc/monit.d to put the configurations into in separate files.
• Modify monitrc to include the files in that directory.
• Add some configurations for monitoring services, including home assistant.
• Add some monitoring to monitor cpu load (and restart HA).
• Reload the configuration to include the new configurations.
• Report a status (which will correspond to “Initializing”) to check that monit is ok.

# Script (adjust some variables to correspond to your setup):

mkdir -p /etc/monit.d

# TODO: python/perl/sed - change line with uncomment include of monit.d 

HA_HTTPS_HOST=PUBLIC_HOST_NAME_FOR_HA_ON_HTTPS
cat > /etc/monit.d/ha <<EOHA
check process apache2
    # with pidfile PATHTOPIDFILE
    start program = "/usr/bin/ha core restart"
    stop program  = "/usr/bin/ha core stop"
    if failed host $HA_HTTPS_HOST port 443 protocol https
       # with size <10
       with content = ""
       with timeout 20 seconds
       then restart
    group ha
EOHA

# Its possible to set up mail alerts.
# Example for server using TLS on port 587:

EMAILLOGIN="YOUREMAILLOGIN"
EMAILPASSWORD="YOUREMAILLOGIN"
MAILSERVER=YOURMAILSERVER
cat > /etc/monit.d/mailserver <<EOMS
set mailserver
      $MAILSERVER port 587 username "$EMAILLOGIN" password "$EMAILPASSWD" using tlsv1
EOMS

monit reload
monit summary

1 post - 1 participant

Read full topic

I’m a newbie attempting to enable my Tapo plug based on fishbigger’s example:

I have pasted the folder from GitHib into my custom components folder and the code into configuration.yaml, when I run Check Configuration I get the following error:

Platform error switch.tapo_p100_control - Integration ‘tapo_p100_control’ not found.

So, what am I doing wrong?

2 posts - 2 participants

Read full topic

I have multiple 1wire sensors (DS2438 + DS18B20) and they work fine most of the time in HA. But two of the DS2438 sporadically disappear from the bus - probably because of the long bus length. This was never a problem with my old home automation system as this happens seldom and only for a few seconds. But HA removes these devices and then adds them again with all configurations like enabled entities lost. What can I do to avoid this? I do not want to reconfigure this devices regularly.

1 post - 1 participant

Read full topic