@flippaz wrote:

Hello. Fairly new to Home Assistant. I am trying to add a simple button to the dashboard so when I click on it, a TTS message is sent over to my Google home. I have tried using the input_boolean but it doesn’t seem to work with the automation script:

configuration.yaml

input_boolean:
  dad_busy_status:
    name: Dad Busy Status
    icon: mdi:human-male

automations.yaml

- alias: Dad is in a meeting
  trigger:
  - entity_id: input_boolean.dad_busy_status
    platform: state
    to: 'on'
  action:
  - data:
      message: Dad is in a meeting.
    service: tts.google_translate_say

Any help is much appreciated!

Posts: 1

Participants: 1

Read full topic

@jeppper wrote:

I would like to turn off my Synology NAS together with all my lights when I go to bed.
Is this somehow possible to to so with HA?

Posts: 1

Participants: 1

Read full topic

@brondum wrote:

Hi Guys.
I have run into a small problem that i cant seem to get my head around.
I am trying to resize an icon within a markdown card.

original content:

- type: 'custom:hui-markdown-card'
  content: >
   <ha-icon icon="mdi:{{ states('sensor.weather_icon') }}"></ha-icon>

I have tried by adding style to the element, but it ignores when rendering.

- type: 'custom:hui-markdown-card'
  content: >
   <ha-icon icon="mdi:{{ states('sensor.weather_icon') }}" style="width: 45px;"></ha-icon>

Any ideas on how i can change this ?

Posts: 5

Participants: 2

Read full topic

@Imperial-Guard wrote:

Since a few days I switched over from Amplifi to my new Unifi Equipment (USG, 2x AC-LR 1x AC-Mesh)

Somehow my Chromcast devices where unavailable in Home Assistant and since I removed them I couldn’t add them via “Integrations”.

The message what I will get is:

Aborted

No Google Cast devices found on the network.

I can add them via the configuration.yaml, but then I don’t see my groups what I have created.

cast:
  media_player:
    - host: 192.168.1.36
    - host: 192.168.1.37
    - host: 192.168.1.70
    - host: 192.168.1.120
    - host: 192.168.1.150
    - host: 192.168.1.165
    - host: 192.168.1.180
    - host: 192.168.1.181

Posts: 3

Participants: 2

Read full topic

@ds1707 wrote:

Hello guys,

I have problems with my senic bridge, after installation of hoppe window handle sensor, the senic bridge stopped working.
That’s why i decided to try to implement my nuimo click switches directly to hassio.

I added the USB 300 to my config, this works fine.
After that i read the ID’s of my sensors with Dolphinview.
Now i get this debug message:

2020-04-14 08:58:31 DEBUG (Thread-2) [homeassistant.components.enocean] Received radio packet: 00:35:BD:C8->FF:FF:FF:FF (-91 dBm): 0x01 ['0xf6', '0x10', '0xID1', '0xID2', '0xID3', '0xID3', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x5b', '0x0'] OrderedDict()

The 0x10 is for button 1, 0x30 = button 1, 0x50 button 3, 0x70 button 5.

I created the switch in the config:

  - platform: enocean
    name: enocean_nuimo_click_kuche
    id: [0xID1,0xID2,0xID3,0xID4]

Now i wanted to create a automation for each button, but could not get it working.

event_data:
  id:
    - ID1
    - ID2
    - ID3
    - ID4
  onoff: 0
  pushed: 1
  which: 10

Can anyone help me with the automation?
That would be awesome, so i can get rid of the senic bridge…
Best regards,
Dominik

Posts: 1

Participants: 1

Read full topic

@jonassam wrote:

Hi!
I have two templated Binary Sensors to track two persons presence (person1_home_sensor and person2_home_sensor), and a third one (away_mode) depending on the state of the two first. Like this:

binary_sensor:
  - platform: template
    sensors:
      person1_home_sensor:
        friendly_name: Person1 Home
        device_class: occupancy
        value_template: '{{ is_state("device_tracker.person1_iphone", "home") }}'
      person2_home_sensor:
        friendly_name: Person2 Home
        device_class: occupancy
        value_template: '{{ is_state("device_tracker.person2_iphone", "home") }}'
      away_mode:
        friendly_name: Away Mode
        device_class: occupancy
        value_template: >-
          '{{ "on" if (is_state("binary_sensor.person1_home_sensor", "off") and 
          is_state("binary_sensor.person2_home_sensor", "off")) else "off" }}'

The two first works just like they should, but the away_mode sensor does not update correctly. Testing the templates in the Developer Tools, everything works as I would like, but not with the actual sensors.

Is it not possbile to have a template sensor dependent on other template sensors like this? It would of course be possible with an automation, but this would be much more elegant…

Best regards,
Jonas

Posts: 1

Participants: 1

Read full topic

@HansHassio wrote:

Within automations.yaml I have placed this code:

- alias: Fan
  trigger:
    platform: state
    entity_id: light.bathroom
    to: 'off'
  action:
    service: switch.turn_on
    entity_id: switch.sonoff218

When the state of the light in the batroom (Philips Hue) changes to OFF the fan (Sonoff) starts running. So far so good but I did not succeed adding a timer function so the fan stops after a certain time.

Can someone help me to add this timer function?

Posts: 3

Participants: 2

Read full topic

@deltabert wrote:

Hello all,
I am new to Home Assistant. Try to switch from openhab to ha. But I was very much confused by the various install methods of HA!
I tried the HASSOS version, but that leaves me with an OS with which i could not do anything else. I wanted HA installed in docker and on a USB SSD drive, so i chose the Supervisory install method.
Installed on two RPI’s, one RPi4 and one RPi2. Installation went on both systems without problems.
Installation of Samba, Mosquitto File Editor all went very well. But then i got problems with the installation of node-RED add-on.

node-RED problem.
I installed node-RED add-on and configured the admin and user. Then i start nod-RED. When i try to access the node-RED interface it stops!!
I receive this message “502: Bad Gateway” and looking at node-RED is has stopped.

Hopefully anyone can help with this?
Kind regards, Bert
BTW, this is my node-RED config:

credential_secret: ''
dark_mode: false
http_node:
  username: admin
  password: ******
http_static:
  username: user
  password: ******
ssl: true
certfile: fullchain.pem
keyfile: privkey.pem
require_ssl: false
system_packages: []
npm_packages: []
init_commands: []

Posts: 1

Participants: 1

Read full topic

@Mariusthvdb wrote:

using this automation:

  - alias: 'GitHub repo update installed'
    trigger:
      platform: event
      event_type: state_changed
    condition:
      - condition: template
        value_template: >
          {{trigger.event.data.new_state.entity_id.startswith('input_boolean.github')}}
      - condition: template
        value_template: >
          {{trigger.event.data.new_state.state == 'off' and
            trigger.event.data.old_state.state  == 'on'}}
    action:
      service: persistent_notification.dismiss
      data_template:
        notification_id: >
          {{trigger.event.data.new_state.object_id}}

dismisses the persistent_notification when the input_boolean is turned off.

Id like to add an automation to do the exact same in reverse: turn_off the input_boolean, when the persistent_notification is dismissed.
but I am puzzled which service to use as trigger (for starters…) Can I use an event trigger on the call-service?

if so, what would be the way to get the correct trigger service-data so I can pass the notification-id over to the input_boolean to dismiss it…

  - alias: 'Persistent notification dismissal turns off boolean'
    trigger:
      platform: event
      event_type: call_service
      event_data:
        domain: persistent_notification
        service: dismiss
    condition:
      #check for 'github' so this only fires for selected notification dismissals
      condition: template
      value_template: >
        {{'github' in trigger.event.data.new_state.object_id}}
    action:
      service: input_boolean.turn_off
      data_template:
        entity_id: >
          input_boolean.{{trigger.event.data.new_state.object_id}}
        

would this be close?
thanks for having a look.

extra reason I seek your assistance is this cant very easily be tested, because only very nice in a while a new GitHub repo update occurs… I need some keen eyes to check if I made no syntax or logic errors.

also, in the events list on developer-tools/event, the dismiss isn’t listed. only see this:

Posts: 1

Participants: 1

Read full topic

@Razer wrote:

Trying to set up a scene to have warm light, everything seems to work fine, i set up the color in the scene, but as soon as i exit the lightbulb changes color to a cold light, testing the scene gives the same result

Using 2 lightbulbs flashed with Tasmota

These devices are also RGB, i think that may be causing the issue, seems like they go plain white color instead of setting the light to warm

Posts: 1

Participants: 1

Read full topic

@Jokerigno wrote:

Hi,

I just noticed today that my Home Assistant istance is reporting wrong day and week day.

Today we are tuesday but in HA I read monday.

How can I fix this?

Ty in advance

Posts: 4

Participants: 2

Read full topic

@xbmcnut wrote:

Running 0.108.3 but been doing this as far as I can tell for the last 3 or 4 weeks so maybe popped up in 107??

I have a notification that triggers on a sun elevation event and turns my PTZ so it looks at the sunset then it sends the picture to my Android TV. I know…very cool aye

Problem is, it triggers at sunset like it supposed to and it just triggered again at 1156 pm! Anyone see an issue with the trigger?

  - alias: 'Take sunset snapshot and send to TV'
    initial_state: true    
    trigger:
      platform: numeric_state
      entity_id: sun.sun
      value_template: "{{ state_attr('sun.sun', 'elevation') }}"
      below: 0.3
    condition:
      - condition: template
        value_template: >-
          {% set season = states('sensor.season') %}
          {{ season == 'autumn' or season == 'summer' }}      
    action:
      - service: rest_command.move_to_preset_05_07s # view preset defined in #
      - delay: '00:00:05'    
      - service: camera.snapshot
        data:
            entity_id: camera.proxy_deck_720_2fps
            filename: '/config/www/images/sunset.jpg'
## Adds a condition inside actions. More info here https://www.home-assistant.io/docs/automation/action/ 
      - condition: state
        entity_id: media_player.sony_bravia_tv
        state: 'on'            
      - delay: 00:00:02
      - service: rest_command.androidtv_sunset_view 

Image shows an approximate time when HA retriggered the automation.

Posts: 1

Participants: 1

Read full topic

@CBG wrote:

hi
I use ESP32-CAM with PIR sensor
So i want to save image file when motion detected.
but there was an error like ‘Could not read camera Local File image from file: /config/www/images/image.jpg’

homeassistant:
  # HA접속시 표시되는 이름
  name: LAB2
  whitelist_external_dirs:
  - /config/www/images


# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
 
#local_file_update_file_path:
    #file_path: /config/www/images/cam_snapshot.jpg


camera:
  - platform: local_file
    #name: lubacam_snapshot
    file_path: /config/www/images/image.jpg


# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Text to speech
tts:
  - platform: google_translate

#group: !include groups.yaml
#automation: !include automations.yaml
#script: !include scripts.yaml
#scene: !include scenes.yaml

thank you and sorry for my english

Posts: 1

Participants: 1

Read full topic

@Joebinator wrote:

Hi there! New to Home Assistant

I wanted to add my lupusec alarm system https://www.home-assistant.io/integrations/lupusec/

it can’t be found in the integrations.

when i add the lupusec section to my configuration.yaml i get

Invalid config

The following integrations and platforms could not be set up:

* [lupusec](https://www.home-assistant.io/integrations/lupusec)

Please check your config.

what am i doing wrong?

Posts: 1

Participants: 1

Read full topic

@tungmeister wrote:

Hi Guys, I’m having issues getting the utility monitor to return correct results. I’ve fed it both KW and KWh sensors however the actual consumption is much less than the utility monitor is reporting. e.g. when feeding it Kw I’d consumed 1.2KWh however the utility meter reported 3.1KWh and when feeding it the live consumption over a test period I’d consumed .388KWh and the utility meter reported .676KWh.
I’ve tried the below sensors to feed the data. they combine the readings provided by my smart plugs to current KWh or Combined Daily KWh.

      combined_live_consumption:
        friendly_name: "Live Consumption"
        unit_of_measurement: "KW"
        value_template: "{{ ((states('sensor.sofa_plug_energy_temp_wattage') | float + states('sensor.pc_avr_plug_energy_temp_wattage') | float + states('sensor.readyroom_plug_energy_temp_wattage') | float) / 1000) | round(4)}}"
      combined_day_consumption:
        friendly_name: "Daily Consumption"
        unit_of_measurement: "KWh"
        value_template: "{{ ((states('sensor.sofa_plug_energy_temp_total_daily_energy') | float + states('sensor.pc_avr_plug_energy_temp_total_daily_energy') | float + states('sensor.readyroom_plug_energy_temp_total_daily_energy') | float)) | round(4)}}"

Any suggestions on where I’m going wrong?

Posts: 2

Participants: 2

Read full topic

@membersound wrote:

I have the problem that my device_tracker.membersound remains in home state forever. Even if I switch my phone off, or walk around in my town.

I think at least the fact that my phone is then not connected to my home wifi anymore should be signal enough to tell HA that I’m not in zone.home anymore. But that never happens. What could be the cause?

In fact the HA UI still shows my mobile phone being connected to my wifi (in the sensor.membersound_wifi_connection state), although it is not. Is it because the HA app cannot report to raspberry when out of home? And thus HA still shows some kind of cached state?

I did not set up any device tracking myself. Just using the default one that is created when installing the HA mobile app.

Posts: 1

Participants: 1

Read full topic

@dsonenberg wrote:

I have two switches that I always use together, and was wondering if it’s possible to make a custom entity that is both switches together?

Posts: 5

Participants: 2

Read full topic

@daveLeiser wrote:

The Goal
Im in the process of setting up Homeassistant so I can manage all my zigbee devices through HA. I want to use zigbee2mqtt in combination of the mosquitto broker addon available in the addon store.

What is done so far
After some research I ended up buying a cc2531 usb sniffer and flashed it with the right firmware. I also installed the mosquitto broker addon using anonymous mode with the following configuration:

logins: []
anonymous: true
customize:
  active: true
  folder: mosquitto
certfile: fullchain.pem
keyfile: privkey.pem
require_certificate: false

I also did create the accesscontrolllist file with the following content:

topic readwrite # 

I also installed the zigbee2mqtt addon from the addon store and configured it:

data_path: /share/zigbee2mqtt
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://192.168.1.145'
serial:
  port: /dev/ttyACM0
advanced:
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blacklist: []
ban: []
whitelist: []
queue: {}
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false

These are mostly standard values except for the setting of the mqtt server. I was able to pair a xiaomi contact sensor and i see the state reported in the zigbee2mqtt log:

zigbee2mqtt:info  2020-04-14 12:33:24: MQTT publish: topic 'zigbee2mqtt/Haustür', payload '{"contact":true,"linkquality":68,"battery":100,"voltage":3005}'

I then went in HA GUI to Settings -> Integrations and added the mqtt integration. it automatically detected mosquitto broker with the right settings (not much to set up there) and i ticked the box “enable autodiscovery” before saving. So far so good…

The problem
My problem is, even though I can see the state of the sensor reporting to zigbee2mqtt and zigbee2mqtt says its connected to the mosquitto server (I will show you the logs later in this post), the devices do not show up on the mqtt integration page in HA. I just feel like there is a small piece missing but i can’t figure out what it is…

Let me show you the logs when i restart the both the addons “mosquitto broker” and then “zigbee2mqtt”:

Log of Mosquitto broker:

[12:49:13] INFO: Setup mosquitto configuration
[12:49:13] WARNING: SSL not enabled - No valid certs found!
[12:49:13] INFO: No local user available
[12:49:14] INFO: Initialize Hass.io Add-on services
[12:49:14] INFO: Initialize Home Assistant discovery
[12:49:14] INFO: Start Mosquitto daemon
1586868554: Loading config file /share/mosquitto/acl.conf
1586868554: mosquitto version 1.6.3 starting
1586868554: Config loaded from /etc/mosquitto.conf.
1586868554: Loading plugin: /usr/share/mosquitto/auth-plug.so
1586868554:  ├── Username/password checking enabled.
1586868554:  ├── TLS-PSK checking enabled.
1586868554:  └── Extended authentication not enabled.
1586868554: |-- *** auth-plug: startup
1586868554: Opening ipv4 listen socket on port 1883.
1586868554: Opening ipv6 listen socket on port 1883.
1586868554: Opening websockets listen socket on port 1884.
1586868554: Warning: Mosquitto should not be run as root/administrator.
1586868554: New connection from 172.30.32.1 on port 1883.
1586868554: New client connected from 172.30.32.1 as mqttjs_d4862366 (p2, c1, k60).
1586868557: New connection from 172.30.32.1 on port 1883.
[INFO] found homeassistant on local database
1586868558: New client connected from 172.30.32.1 as auto-587D268B-DFF3-7213-BA3D-EEB3596202EF (p2, c1, k60, u'homeassistant').

The log of the zigbee2mqtt addon:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
./run.sh: line 17: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
[Info] Socat is DISABLED and not started
2020-04-14T13:02:36: PM2 log: Launching in no daemon mode
2020-04-14T13:02:36: PM2 log: App [npm:0] starting in -fork mode-
2020-04-14T13:02:36: PM2 log: App [npm:0] online
> zigbee2mqtt@1.12.2 start /zigbee2mqtt-1.12.2
> node index.js
zigbee2mqtt:info  2020-04-14 13:02:42: Logging to console and directory: '/share/zigbee2mqtt/log/2020-04-14.13-02-42' filename: log.txt
zigbee2mqtt:info  2020-04-14 13:02:43: Starting zigbee2mqtt version 1.12.2 (commit #unknown)
zigbee2mqtt:info  2020-04-14 13:02:43: Starting zigbee-herdsman...
zigbee2mqtt:info  2020-04-14 13:02:45: zigbee-herdsman started
zigbee2mqtt:info  2020-04-14 13:02:45: Coordinator firmware version: '{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190109}}'
zigbee2mqtt:info  2020-04-14 13:02:45: Currently 6 devices are joined:
zigbee2mqtt:info  2020-04-14 13:02:45: Haustür (0x00158d0002e9d384): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
zigbee2mqtt:info  2020-04-14 13:02:45: 0x00158d0002ea0a02 (0x00158d0002ea0a02): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
zigbee2mqtt:info  2020-04-14 13:02:45: 0x00158d0002e2bcdf (0x00158d0002e2bcdf): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
zigbee2mqtt:info  2020-04-14 13:02:45: 0x00158d0002e6e87a (0x00158d0002e6e87a): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
zigbee2mqtt:info  2020-04-14 13:02:45: 0x00158d0002f38b2c (0x00158d0002f38b2c): WXKG02LM - Xiaomi Aqara double key wireless wall switch (EndDevice)
zigbee2mqtt:info  2020-04-14 13:02:45: 0x00178801062cc88d (0x00178801062cc88d): 9290022169 - Philips Hue white ambiance E27 with Bluetooth (Router)
zigbee2mqtt:warn  2020-04-14 13:02:45: `permit_join` set to  `true` in configuration.yaml.
zigbee2mqtt:warn  2020-04-14 13:02:45: Allowing new devices to join.
zigbee2mqtt:warn  2020-04-14 13:02:45: Set `permit_join` to `false` once you joined all devices.
zigbee2mqtt:info  2020-04-14 13:02:45: Zigbee: allowing new devices to join.
zigbee2mqtt:info  2020-04-14 13:02:45: Connecting to MQTT server at mqtt://192.168.1.145
zigbee2mqtt:info  2020-04-14 13:02:45: Connected to MQTT server
zigbee2mqtt:info  2020-04-14 13:02:45: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
zigbee2mqtt:info  2020-04-14 13:02:45: MQTT publish: topic 'zigbee2mqtt/Haustür', payload '{"contact":true,"linkquality":68,"battery":100,"voltage":3005}'
zigbee2mqtt:info  2020-04-14 13:02:45: MQTT publish: topic 'zigbee2mqtt/0x00158d0002ea0a02', payload '{"contact":false,"linkquality":0,"battery":97,"voltage":2995}'
zigbee2mqtt:info  2020-04-14 13:02:45: MQTT publish: topic 'zigbee2mqtt/0x00158d0002e2bcdf', payload '{"temperature":23.13,"linkquality":63,"humidity":36.84,"battery":100,"voltage":3005}'
zigbee2mqtt:info  2020-04-14 13:02:45: MQTT publish: topic 'zigbee2mqtt/0x00158d0002e6e87a', payload '{"temperature":23.26,"linkquality":81,"humidity":36.51,"battery":100,"voltage":3005}'
zigbee2mqtt:info  2020-04-14 13:02:45: MQTT publish: topic 'zigbee2mqtt/0x00158d0002f38b2c', payload '{"battery":100,"voltage":3035,"linkquality":68}'
zigbee2mqtt:info  2020-04-14 13:02:45: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.12.2","commit":"unknown","coordinator":{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190109}},"log_level":"info","permit_join":true}'

After that there are a lot of messages for what I understand reporting the current state of the paired devices.

I just checked the mosquitto broker log again after restarting the zigbee2mqtt addon and i can see the following error:

1586869348: Socket error on client mqttjs_d4862366, disconnecting.
1586869365: New connection from 172.30.32.1 on port 1883.
1586869365: New client connected from 172.30.32.1 as mqttjs_36963777 (p2, c1, k60).

I don’t know if this is related to my problem. For me it’s not clear what this “client mqttjs_d4862366” is…

But so for me it seems like zigbee2mqtt is able to talk to the mosquitto broker and HA also was able to detect the mosquitto broker when I added the MQTT integration. I just don’t know what triggers HA to add the devices which are already paired… I hope someone can clear this up for me.

At this point: Thanks for reading through all of this and i wish you great day!

Posts: 2

Participants: 2

Read full topic

@darryl12123 wrote:

Hi all,

I’ve a question regarding the the ‘recorder’ integration in the config.yaml file. So my database is getting quite big (5GB) so I started to implement some rules on which entities are important te recorder and which ones are useless to record.

Now my situation: I’ve a smart energy meter (for gas and power) which I’m reading into my Home Assistant. Ofcourse this is important information for me as I can recall my usage and can compare to like last month or year. So it is important to save these entities for maybe 5 years or so?

Most other entities like states of lights etc I would like to keep for a few days, but most definitely not for years.

How can I make a difference in retention days between entities?

Many thanks!

Posts: 6

Participants: 3

Read full topic

@Brightspark wrote:

Hi all, I’ve searched but am so new to HA that I may have even misunderstood what I am really looking for. ng up and running and have all my Nest products working with BadNest. The are all there in the entity section but when I come to do an automation I cannot find the Thermostat as a device.

I want to be able to turn the heating to ECO when the back door is open but to do this in automations I need a device and not an entity.

Im sure I’ve just asked a stupid question but for the life of me I have been going round in circles for a couple of days so I feel its time to ask.

Hope you can help.

Posts: 3

Participants: 3

Read full topic