Quantcast
Channel: ESPHome - Home Assistant Community
Viewing all 1486 articles
Browse latest View live

Use state of mqtt topic to override physical button press action?!

$
0
0

Hi… i have tid in my ESPHome yaml

binary_sensor:
- platform: gpio
id: manual_open_switch
internal: true
pin:
number: GPIO33
mode: INPUT
inverted: true
filters:
- delayed_on_off: 20ms
on_press:
then:
- switch.toggle: relay_toggle
switch:
- platform: gpio
id: relay
pin: GPIO27
internal: true
- platform: template
id: relay_toggle
internal: true
turn_on_action:
- switch.turn_on: relay
- delay: 1s
- switch.turn_off: relay

and in Home Assistant i have defined a MQTT switch like this

switch:
- platform: mqtt
unique_id: big_garagedoor_lockout
name: Deaktiver fysisk bryter til garasjeport
command_topic: 'MH/BigGaragedoor/Lockout'
state_topic: 'MH/BigGaragedoor/Lockout'
payload_on: 'on'
payload_off: 'off'
retain: true

I somehow want the state of the mqtt topic to override the input of the physical switch. like if the topic has the payload of on, i dont want the relay_toggle template switch to be run. Anyone got any clever solutions?

This is so i can disable the physical openswitch of my garagedoor :stuck_out_tongue:

2 posts - 2 participants

Read full topic


IR Transmitter raw signal issue

$
0
0

Hi,

I got an IR receiver which translate command to zwave device. I was hoping to connect directly to the data output and send signal from ESP32 using IR transmitter module with raw commands but no luck so far. I hooked up oscilloscope to check IR receiver response to normal remote controller (pic below) and pattern is different (opposite) to what I can see from ESP GPIO32. Has anybody tried something like that before any advice?

1 post - 1 participant

Read full topic

Using ZMCT103C Current Transformer with ESPHome to Monitor AC Power Usage

$
0
0

I’m trying to set up a power meter to measure watts using one of these ZMCT103C modules. I have been trying to find online sources that could help me to get it working, but so far I haven’t been successful. The board is like the one in this listing: https://id.aliexpress.com/item/32862297933.html

The board has these pins:
GND
GND
OUT
VCC

I connected one of the GND pins to ground, the OUT to A0 on my ESP8266, and VCC to 5v. I tried using this example provided here https://esphome.io/components/sensor/ct_clamp.html

sensor:
  - platform: ct_clamp
    sensor: adc_sensor
    name: "Measured Current"
    update_interval: 60s

  - platform: adc
    pin: A0
    id: adc_sensor

The code runs without errors, and the sensor appears in HA. But I can’t get a correct reading from the sensor. Even without any load turned on it shows some random value instead of 0, and when I turn on my load for testing which is a light bulb, the reading changes but to a value that is incorrect. I tried calibrating it but I am still unable to get a correct reading. Did I improperly connect it? Do I need to add a resistor somewhere in the circuit? Or did I just not calibrate it right?

Has anyone ever had any experience using this sensor with ESPHome? Or maybe someone could point me to a link (website or forum) that could show how to correctly set this up? Any suggestions would be very appreciated. Thanks!

1 post - 1 participant

Read full topic

Help Implementing Sun Solar Tracker

$
0
0

Hi, I have a DIY large solar sun tracker that i need some help with.
All the hardware is up and running. I am moving the software from “Blynk Local Server” to Home assistant and Esphome.
Hardware: Two linear actuators controlled by 4 relays.
Controller: ESP32 and sensor MPU6050

Current manual control code.

esphome:
  name: solar_tracker
  platform: ESP32
  board: esp-wrover-kit


wifi:
  ssid: "##########"
  password: "###########"


  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Solar Tracker Fallback Hotspot"
    password: "lZEGI44isCwX"

captive_portal:

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:

i2c:
  sda: 21
  scl: 22
  scan: True

sensor:
  - platform: mpu6050
    address: 0x68
    update_interval: 100ms
    
    accel_x:
      name: "MPU6050 Accel X"
      filters:
       - sliding_window_moving_average:
          window_size: 10
          send_every: 5 
       - calibrate_linear:
          # Map 0.0 (from sensor) to 0.0 (true value)
          - -10.0 -> 270.0
          - 10.0 -> 90.0           

    accel_y:
      name: "MPU6050 Accel Y"
      filters:
       - sliding_window_moving_average:
          window_size: 10
          send_every: 5 
       - calibrate_linear:
          # Map 0.0 (from sensor) to 0.0 (true value)
          - 0.0 -> 90.0
          - -10.0 -> 0.0   
          
          
    accel_z:
      name: "MPU6050 Accel z"
      filters:
       - sliding_window_moving_average:
          window_size: 10
          send_every: 5 
    gyro_x:
      name: "MPU6050 Gyro X"
      filters:
       - sliding_window_moving_average:
          window_size: 10
          send_every: 5 
    gyro_y:
      name: "MPU6050 Gyro Y"
      filters:
       - sliding_window_moving_average:
          window_size: 10
          send_every: 5 
    gyro_z:
      name: "MPU6050 Gyro z"
      filters:
       - sliding_window_moving_average:
          window_size: 10
          send_every: 5 
    temperature:
      name: "MPU6050 Temperature"
      filters:
       - sliding_window_moving_average:
          window_size: 10
          send_every: 5 
          

#relay bank Manual Switching
switch:
  - platform: gpio
    pin: 23
    id: relayUp
    name: "Solar Up"
    inverted: yes
  

  - platform: gpio
    pin: 19
    id: relayDown
    name: "Solar Down"
    inverted: yes
    
    
  - platform: gpio
    pin: 5
    id: relayEast
    name: "Solar East"
    inverted: yes
   

  - platform: gpio
    pin: 17
    id: relayWest
    name: "Solar West"
    inverted: yes

I need help!
I need to compare sun azimuth and sun elevation (from Home Assistant) with my MPU6050 data X and Y

I think the following code will expose the azimuth and elevation, but im new to coding in YAML and cant figure out how it implement this.




  - platform: template
    sensors:
      sun_elevation:
        friendly_name: "Sun Elevation"
        unit_of_measurement: 'degrees'
        value_template: "{{ state_attr('sun.sun', 'elevation') }}"

  - platform: template
    sensors:
      sun_azimuth:
        friendly_name: "Sun Azimuth"
        unit_of_measurement: 'degrees'
        value_template: "{{ state_attr('sun.sun', 'azimuth') }}"

The automation needs to be on the ESP32 as we do get power cuts and the WIFI goes off.
I really would appreciate any help as I love the esphome and home assistant platforms.
Many thanks

1 post - 1 participant

Read full topic

ESPHome Font Tester

ESP32-CAM stability

$
0
0

Hello, i have 2 camera on my local homeAssistant installation, and i have a real stability problem. The device is unavailable 15-30% overall time.

Device history:

Also using http picture capture via:
http://127.0.0.1:8123/api/camera_proxy/camera.camara_X
And fails really often.

Please help :frowning:

Installation:
Debian GNU/Linux 10 (buster) on a OrangePiOne. Armbian
Connected via cable to Wifi router.
ESP32-cam no usb version, powered via 5v using 2Amp phone chargers.
Hass downloaded via pip
Pyhton 3.8
Ram: 56% usage, hdd: 46%

YAML:

esphome:
  name: camara3
  platform: ESP32
  board: esp32cam

wifi:
  ssid: "MyWifi"
  password: "Octagon"

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Camara3 Fallback Hotspot"
    password: "T7T67sdfsdfsdfjS1"

captive_portal:

# Enable logging
logger:

# Enable Home Assistant API
api:
  password: "B1exdfgsdfRz"

ota:
  password: "B1exsdfgdfsg"

esp32_camera:
  name: Camara 3
  external_clock:
    pin: GPIO0
    frequency: 20MHz
  i2c_pins:
    sda: GPIO26
    scl: GPIO27
  data_pins: [GPIO5, GPIO18, GPIO19, GPIO21, GPIO36, GPIO39, GPIO34, GPIO35]
  vsync_pin: GPIO25
  href_pin: GPIO23
  pixel_clock_pin: GPIO22
  power_down_pin: GPIO32
  resolution: 1280x1024
  jpeg_quality: 10
switch:
  - platform: gpio
    pin: GPIO4

2 posts - 2 participants

Read full topic

ESPHome/Inkplate Calendar Display

Esp8266 joining two 3.3v sensors on one pin

$
0
0

I have an esp8266, ESP-12F to which I need to connect 4 sensors, all 3.3v power needed but the board only has 3 x 3.3v pins.
My question is, can I join two sensor’s positive cables together and connect them to the same 3.3v pin on the board or do they need to be separate?

3 posts - 2 participants

Read full topic


Couldn't complie any ESPHome yaml

$
0
0

Could you please help me in the following issue?

I couldn’t compile any of my ESPHome yamls. These have worked up till now. The current version of the HA is 2021.2.3. I get the following error message when I click to the compile button:

INFO Reading configuration /config/esphome/basementlamp.yaml...
INFO Generating C++ source...
INFO Compiling app...
Traceback (most recent call last):
  File "/usr/local/bin/esphome", line 11, in <module>
    load_entry_point('esphome', 'console_scripts', 'esphome')()
  File "/opt/esphome/esphome/__main__.py", line 557, in main
    return run_esphome(sys.argv)
  File "/opt/esphome/esphome/__main__.py", line 544, in run_esphome
    rc = POST_CONFIG_ACTIONS[args.command](args, config)
  File "/opt/esphome/esphome/__main__.py", line 286, in command_compile
    exit_code = compile_program(args, config)
  File "/opt/esphome/esphome/__main__.py", line 149, in compile_program
    return platformio_api.run_compile(config, CORE.verbose)
  File "/opt/esphome/esphome/platformio_api.py", line 94, in run_compile
    return run_platformio_cli_run(config, verbose)
  File "/opt/esphome/esphome/platformio_api.py", line 90, in run_platformio_cli_run
    return run_platformio_cli(*command, **kwargs)
  File "/opt/esphome/esphome/platformio_api.py", line 79, in run_platformio_cli
    import platformio.__main__
  File "/usr/local/lib/python3.6/dist-packages/platformio/__main__.py", line 21, in <module>
    from platformio import __version__, exception, maintenance, util
  File "/usr/local/lib/python3.6/dist-packages/platformio/maintenance.py", line 22, in <module>
    from platformio import __version__, app, exception, fs, telemetry
  File "/usr/local/lib/python3.6/dist-packages/platformio/app.py", line 29, in <module>
    from platformio.project.helpers import get_default_projects_dir, get_project_core_dir
ImportError: cannot import name 'get_default_projects_dir'

1 post - 1 participant

Read full topic

ESPhome addon not showing latest update

$
0
0

Hello, perhaps I am missing something here, but I see that the latest version of esphome is 1.16.1. My addon shows that I am running version 1.15.3. In the past I have been given the option to update but it is not showing up this time. What am I missing? Auto update is turned on as well.

Thanks!

3 posts - 2 participants

Read full topic

ESP32 DHCP IP-Hostname official Bugfix 1.0.5-rc7

$
0
0

Hi, can I update it manually? or use it like

arduino_version: espressif32@1.0.5-rc7



1 post - 1 participant

Read full topic

Message malformed: Service esphome.esp-buzzer_unit_keep_buzzer does not match format

$
0
0

Dear friends
thanks for hearing my problem, please give me the solution for the following issue
First: I´m very new to HA, and I have no experience in programming. But I like to think I´m slowly improving. Anyways, please keep any answers as simple as possible.

Problem: I’m using ESP32s boar, with that, I connected buzzer and motion sensor… it is working great, but when I set automation to buzzer it is giving error.
ERROE : Message malformed: Service esphome.esp-buzzer_unit_keep_buzzer does not match format . for dictionary value @ data[‘action’][0][‘service’]

But when I call service in Developer Tools - the buzzer is working



–> Automation

alias: New Automation
description: ‘’
mode: single
trigger:

  • platform: state
    entity_id: binary_sensor.pir_sensor
    to: ‘on’
    condition: []
    action:
  • service: esphome.esp-buzzer_unit_keep_buzzer
    data: {}

–>IN ESPHOME–> this is the program that I compiled in ESP32s board

esphome:
name: esp-buzzer_unit
platform: ESP32
board: nodemcu-32s

wifi:
ssid: “xxx”
password: “xxx”
manual_ip:
static_ip: 192.168.10.9
gateway: 192.168.10.1
subnet: 255.255.255.0
dns1: 192.168.10.1
dns2: 192.168.10.1

Enable fallback hotspot (captive portal) in case wifi connection fails

ap:
ssid: “Esp-Buzzer Unit Fallback Hotspot”
password: “bYWd6djiF7pq”

captive_portal:

Enable logging

logger:

Enable Home Assistant API

ota:
password: “123456”

api:
password: “123456”

services:
- service: keep_buzzer
then:
- rtttl.play: “beep:d=16,o=5,b=100:b”
- service: kep_buzzer
then:
- service: play_rtttl
variables:
song_str: string
then:
- rtttl.play:
rtttl: !lambda ‘return song_str;’

sensor:

  • platform: wifi_signal
    name: “WiFi Signal Sensor buzzer”
    update_interval: 5s
    id: esp32s_buzzer_wifi

binary_sensor:

  • platform: gpio
    pin: 14
    name: “PIR Sensor”
    device_class: motion

output:

  • platform: ledc
    pin: 5
    id: rtttl_out

rtttl:
output: rtttl_out
on_finished_playback:
- logger.log: ‘Song ended!’

2 posts - 2 participants

Read full topic

ERROR Error while reading incoming messages: Error while receiving data: [Errno 9] Bad file descriptor

$
0
0

The strangest thing is happening with one of my esp8266 12-F boards where it disconnects randomly (it is right beside the wifi router) and also throws some errors even when I disabled all the sensors connected to it:

The config

esphome:
  name: living_room
  platform: ESP8266
  board: nodemcuv2

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_pw
  fast_connect: true
  power_save_mode: none
  reboot_timeout: 0s
  manual_ip:
    static_ip: 192.168.0.179
    gateway: 192.168.0.1
    subnet: 255.255.255.0
    dns1: 192.168.0.1

# Enable logging
logger:
  level: VERY_VERBOSE

# Enable Home Assistant API
api:

ota:

# uart:
#   rx_pin: GPIO3
#   tx_pin: GPIO1
#   baud_rate: 9600

#sensor:
  # - platform: mhz19
  #   id: living_room_mhz19c
  #   co2:
  #     name: "Living Room CO2"
  #   temperature:
  #     name: "Living Room MH-Z19C Temperature"
  #   update_interval: 60s
  #   automatic_baseline_calibration: true
  # - platform: dht
  #   pin: D7
  #   model: dht22
  #   temperature:
  #     name: "Living Room Temperature"
  #     filters:
  #     - offset: -2.3
  #   humidity:
  #     name: "Living Room Humidity"
  #   update_interval: 60s
  # - platform: adc
  #   pin: A0
  #   name: "Living Room LUX"
  #   unit_of_measurement: lx
  #   update_interval: 60s
  #   filters:
  #     - lambda: |-
  #         return (x / 10000.0) * 20000000.0;

# binary_sensor:
#   - platform: gpio
#     pin: D5
#     name: "Living Room PIR Sensor"
#     device_class: motion 

I tried setting the IP to static, no change, power_save_mode: none, the same, fast_connect: true, no change.
Funny thing is I have another of these boards with the same sensors and it is rock solid.
Tried multiple power supplies without any difference.
Anyone got any suggestions? What that error might be about?

2 posts - 1 participant

Read full topic

Esphome: hallsensor on ESP8266

$
0
0

hello,

i ve a external hall sensor
image

how can i use it with esphome?
i had try this:

sensor:
  - platform: esp32_hall
    pin: 2
    name: "ESPhome_Gaszaehler"
    unit_of_measurement: 'm^3'

but dont work

INFO Reading configuration /config/esphome/gaszaehler.yaml...
Failed config

sensor.esp32_hall: [source /config/esphome/gaszaehler.yaml:19]
  
  Component sensor.esp32_hall doesn't support ESP8266

1 post - 1 participant

Read full topic

Ultra low power MQTT ESPHome sensor

$
0
0

Hello, I would like to share my experience with building low power alert sensor based on ESPHome. I achieved deep sleep current 12μA with plain ESP8266 module ESP-12F. Full code is below.

I wanted to build a sensor, that regularly (every 10min) checks if the LED on my washing mashine turns ON so I know when it ended washing cycle end then notify me over telegram. The automation and telegram integration are pretty standard things so I will not describe it here. I have solved following challenges:

  • Sleep between measurements: this is easily achievable, as the ESPHome directly support deep sleep. I used mqtt and disabled ESPHome api.
  • Use WiFi only if alert is needed, otherwise do not attemp to start wifi. This shortens wake time to fraction of second. This was a bit tricky, because ESPHome always turns wifi ON. However, there is a moment when sensor is initialized, but wifi not started. I had to use that moment to check the sensor and go to deep sleep before wifi is started. I tried to use on_boot: with various priorities, but it did not work because priorities did not catch the right moment. However, on_loop: worked. It looks like before starting the loop sensor is initialized and wifi starts only after first loop. If you put sensor condition to on_loop:, then you can check sensor and send ESPhome to sleep before wifi.
  • No residual current in voltage divider: I check light by photo resistor. To check its value, I needed to create voltage divider from one resistor and photo resistor, put it between 3.3V and GND and then measure voltage on junction of resistors. However, this schema will create permanent current draw. So I connected the voltage divider beween GPIOs and I create the voltage difference only during measurement.

There were few catches. After I turn on voltage on GPIO, I had to add 100ms delay. Also, when I send ESPHome to deep sleep before it does it on its own, the ESPHome thinks it crashed and after 10 such reboots it would start OTA access point and discharge the battery. Luckily, this behavior can be turned off by safe_mode: false. I want to turn GPIO power up as early as possible, so I give it priority 900.

Sensor works fine. When wasing mashine LED is off, it measures less than 0.5V, when LED is on, it measures more than 0.5V and only in that case it connects to wifi and reports the value to Home Assistant. There you can catch it with automation and perform actions.

The code:

esphome:
  name: mqtt_pracka
  platform: esp8266
  board: esp12e
  on_boot:
    priority: 900
    then:
      - lambda: |-
          pinMode(14, OUTPUT);
          pinMode(12, OUTPUT);
          digitalWrite(14, HIGH);
          digitalWrite(12, LOW);
          delay(100);

  on_loop:
    then:
      - lambda: |-
          if (id(pracka2_pr).state < 0.5) {
            ESP.deepSleep(600*1E6);
            }


wifi:
  ssid: "IoT"
  password: "...."
  manual_ip:
    static_ip: 10.0.0.46
    gateway: 10.0.0.138
    subnet: 255.255.255.0
    dns1: 8.8.8.8
    dns2: 8.8.4.4

  ap:
    ssid: "MQTT Pracka Hotspot"
    password: ""
  fast_connect: on

captive_portal:

logger:

# Do not enable Home Assistant API
#api:

ota:
  safe_mode: false

sensor:
  - platform: adc
    id: pracka2_pr
    pin: A0
    name: "Pracka2 Photo Resistor"
    retain: true
    update_interval: 30s
    accuracy_decimals: 3

deep_sleep:
  id: deep_sleep_1
  run_duration: 4s
  sleep_duration: 10min

mqtt:
  broker: 10.0.0.54
  username: ...
  password: ...
  birth_message:
    topic: mqtt_pracka2/status
    payload:
    qos: 2
  will_message:
    topic: mqtt_pracka2/status
    payload:
  on_message:
    - topic: mqtt_pracka2/ota_mode
      payload: 'ON'
      then:
        - deep_sleep.prevent: deep_sleep_1
    - topic: mqtt_pracka2/sleep_mode
      payload: 'ON'
      then:
        - deep_sleep.enter: deep_sleep_1

The only last challenge I have is how to measure analog input on A0 pin and battery VCC. It looks like ESPHome only supports one or other method, but not both together. There is only one mqtt message received when I create two adc sensors, one on A0 pin and second on VCC pin. When I had older version that I programmed completely in C++, I could use both and send message based on critical battery level.

It s possible to OTA flash the sensor even if it goes to deep sleep before wifi. I just need to force it to think that light is on - by shortening the photo resistor, and restart it. Then it turns on wifi for 3 seconds and in that moment I can trigger OTA from PC.

1 post - 1 participant

Read full topic


Device not listed in Intergration tab

$
0
0

I’ve some strange behaviour with one of my ESPHome intergrations: The device and all its entities ARE visible on the Devices AND Entities tabs in Home Assistant but the device ISN’T listed on the Intergration tab.

If I add the device manualy once again I get the error messages “Platform esphome does not generate unique IDs” in the HA log. The error makes sense because, like I said, the device and the entities allready is listed in the Device and Entities tab.

Im scratching my head figuring out why this happned and, more important, how to fix this. I’ve looked in my .storage folder and removed all related lines/files, but after a core start or rebuild the entities will pop-up afterwards.

Does anyone have an idea how to fix this?

1 post - 1 participant

Read full topic

Esp8266 newbie

$
0
0

Just a very newbie question.
So I finally got my ESP8266 to be discovered as a device in home assistant.
My question : Why do we need to upload a yaml binary file in the ESP home web ui interface and also upload a sketch via the Arduino IDE ? How does this mechanism work? My goal to create a switch and use MQTT to talk to other devices on my HomeAssistant.

3 posts - 2 participants

Read full topic

ESP32s and ESPHome

$
0
0

Hello friends!
A few days ago I bought an ESP32 development board. It must be a different version than the ones I see in tutorials to install ESPHome (ESP32S ??) I have a usb ttl board to connect it to the PC and flash it but I don’t know how the cables are placed. Could you tell me how to install ESPHome on this board?
Thanks in advance!

1 post - 1 participant

Read full topic

ESPHome on wemos D1 mini lite losing its brains

$
0
0

Hi All,

I have many ESPHome devices all over my house that have been working flawlessly for years… except one.

The one that monitors my doorbell, a PIR sensor and a DS18S20 temperature sensor loses it’s brains every few weeks. Just resetting it doesn’t bring it back. It needs to be reflashed over USB.

At first I thought it was the inductive kick from the doorbell coil, but I finally got around to testing for this, and I can’t find any signs that thats a problem.

I also think it probably lost it’s brains at least once when there were no button presses, but I can’t guarantee that.

I’m going to try reinstating it without the doorbell button connected at all and see what happens, but since it can be weeks before it dies, it’s worth asking the question;

Has anyone seen this problem before that ESPHome can brick itself?

Code below:

esphome:
  name: doorbell
  platform: ESP8266
  board: esp8285

wifi:
  ssid: '#######'
  password: '#######'

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:

binary_sensor:
  - platform: gpio
    name: "button"
    pin:
      number: GPIO16
      inverted: True
      #mode: INPUT_PULLUP

  - platform: gpio
    name: "Doorbell"
    pin:
      number: GPIO4
      inverted: False
      #mode: INPUT_PULLUP
  - platform: gpio

    name: "PIR Entry"
    pin:
      number: GPIO0
      inverted: True
      #mode: INPUT_PULLUP


switch:
  - platform: gpio
    pin:
        number: GPIO15
    restore_mode: RESTORE_DEFAULT_OFF
    name: "Spare Output"

dallas:
  - pin: GPIO13

sensor:
  - platform: adc
    pin: A0
    name: "Doorbell Battery"
    update_interval: 60s

  - platform: dallas
    index: 0
    name: "Hallway Temperature"

3 posts - 3 participants

Read full topic

NodeMCU-32s - OTA Successful but loads old config

$
0
0

Hi All,

Context - I have 2 x NodeMCU-32s boards, each one is connected to a 16 way relay board.

I’m having a bit of a mare with a couple of NodeMCU-32s at the moment:

For some unknown reason yesterday, both of my boards started going crazy and the relays on pin’s 17 started going nuts - to the point that ANY action on the board caused the relay to click - doing some research, looks like I had used Pins 16 and 17 without disabling the UART logging…MCU 1 - 0 ME.

I managed to re-write the firmware using the local USB connection - however ever since I have done that, every time I run esphome filename.yaml run - the upload takes about 1 second flat, says its successful, and then the board reboots into the existing config.

Has anyone seen this before? If it helps, these are the pins which I have relays connected to:

04,05,12,13,14,18,19,21,22,25,26,23,32,33

It was all working fine until yesterday when randomly they went nuts.

Thanks
Leacho

3 posts - 2 participants

Read full topic

Viewing all 1486 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>