@yoni wrote:

Anyone having issues with TTS? I have a bunch of automations that stopped working with TTS… anything happening with Google and HA?

Posts: 2

Participants: 2

Read full topic

@Bryan_Zapata wrote:

I want to use the screen of the tablet to be able to manipulate homeasistant what methods are there to do it?

Posts: 3

Participants: 3

Read full topic

@biiiink wrote:

I just upgraded to 107.5 and now the Ecobee thermostat is not working.

This is on the log. I have confirmed that the API is correct. Not sure what else to try.

Log Details (ERROR)
Logger: homeassistant.config_entries
Source: components/ecobee/__init__.py:105
First occurred: 10:19:19 PM (1 occurrences)
Last logged: 10:19:19 PM

Error setting up entry ecobee for ecobee
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/pyecobee/__init__.py", line 513, in _request
    response.raise_for_status()
  File "/usr/local/lib/python3.7/site-packages/requests/models.py", line 941, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://api.ecobee.com/token?grant_type=refresh_token&refresh_token=XXXX&client_id=XXXX

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 216, in async_setup
    hass, self
  File "/usr/src/homeassistant/homeassistant/components/ecobee/__init__.py", line 58, in async_setup_entry
    if not await data.refresh():
  File "/usr/src/homeassistant/homeassistant/components/ecobee/__init__.py", line 105, in refresh
    if await self._hass.async_add_executor_job(self.ecobee.refresh_tokens):
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/pyecobee/__init__.py", line 148, in refresh_tokens
    auth_request=True,
  File "/usr/local/lib/python3.7/site-packages/pyecobee/__init__.py", line 522, in _request
    "ecobee tokens invalid; re-authentication required"
pyecobee.errors.InvalidTokenError: ecobee tokens invalid; re-authentication required

Posts: 2

Participants: 2

Read full topic

@linuxguy322 wrote:

Hello,
I am trying to migrate to HA from hubitat. My Zwave motion sensor works perfectly in Hubitat , but when i move it over to HA, the motion detection is not reflected in the HA. It works once if i restart but then no updates even when motion is detected in the HA.

Any advice or pointers in the right direction please ?

Posts: 1

Participants: 1

Read full topic

@ipjaeger wrote:

OK, I’ve read a ton of threads about the whole DuckDNS/NGINX not being able to access from the outside. And while some of them sound similar, none of them seem to be exactly what I’m seeing (although as a noob with this stuff, I could be very wrong, and I apologize for that up front!)

From the start, I was never able to access HA via the hassio.local:8123 address… always had to go via the direct IP at 192.168.1.X:8123. What I didn’t look for at the time was whether that gave me a secure connection or not BEFORE I tried the DuckDNS stuff for remote access.

Went through the setups in the following two threads that proved to be helpful… except it still doesn’t work:
DuckDNS - It's not just me - it's you!
https://help.konnected.io/support/solutions/articles/32000023964-set-up-hass-io-with-secure-remote-access-using-duckdns-and-nginx-proxy

The Konnected link shows a log from the NGINX app that shows it creating dhparams and a snakeoil certificate. My logs just say “INFO: Running nginx…” and it doesn’t change when I hit refresh.

.
.

So I’ve done a few other things to see what’s going on:

• Port Forwarding works because when I use an outside (i.e. iphone) access and pull up the actual ip address of my router with the X.X.X.X:443 I get the HomeAssistant welcome page but it’s “Not Secure.”
• FROM EXTERNAL: I can ping the XXX.duckdns. org address and get a return (averages about 55ms) and it shows that it’s going to the correct IP address
• FROM EXTERNAL: When I tracert / traceroute the duckDNS address or direct IP address, it always goes dead at the same node: agg1.rcsntxiw01m.tx.rr. com
• FROM INTERNAL: I cannot ping or Traceroute either the DuckDNS or direct IP address.

I’m probably missing something simple, but I’ve been at this for 1.5 days now and it’s driving me crazy!

Halp!

Posts: 2

Participants: 2

Read full topic

@Three wrote:

Been using the manual mqtt alarm control panel platform happily for nearly going on a year now.

Last week I update Home Assistant from 0.104.5 to the fastest 0.107.5 which broke the code that counts door and windows that are open.

I read on the release notes for 0.105 that view and control features of Groups was removed 0.107 but the code I use doesn’t use this and can’t seem to figure out why it won’t load since 0.107

This is my alarm code

#################################################################
#                                                               #
#                    Packages/Alarm System                      #
#                                                               #
#################################################################

#################################################################
#                                                               #
#                          Customize                            #
#                                                               #
#################################################################

homeassistant:
  customize:
    alarm_control_panel.ha_alarm:
      icon: mdi:shield-home
    binary_sensor.door_window_sensor_hiddenb9:
      friendly_name: Sliding Door
      device_class: door
    binary_sensor.door_window_sensor_hidden16:
      friendly_name: Front Door
      device_class: door
    binary_sensor.door_window_sensor_hiddena4:
      friendly_name: Laundry Door
      device_class: door
    binary_sensor.door_window_sensor_hidden13:
      friendly_name: Garage Door
      device_class: door
    binary_sensor.door_window_sensor_hiddenc0:
      friendly_name: Bathroom Window
      device_class: window
    binary_sensor.motion_sensor_hidden1f:
      friendly_name: Porch Motion Sensor
    binary_sensor.motion_sensor_hiddene9:
      friendly_name: Lawn Motion Sensor
    binary_sensor.motion_sensor_hidden3e:
      friendly_name: Woodpile Motion Sensor
    binary_sensor.motion_sensor_hidden8f:
      friendly_name: Garage Motion Sensor
#    binary_sensor.smoke_sensor_hiddenba:
#     friendly_name: Upstairs Smoke Detector
#     device_class: smoke

#################################################################
#                                                               #
#                           Group                               #
#                                                               #
#################################################################

group:
  security:
    name: Security
    icon: mdi:security-home
    view: yes
    entities:
      - group.alarms
      - group.doors
      - group.windows
      - group.motion
      
  alarms:
    name: Alarms
    icon: mdi:security
    view: no
    entities:
      - alarm_control_panel.ha_alarm
      
  motion:
    name: Motion
    icon: mdi:walk
    view: no
    entities:
      - binary_sensor.motion_sensor_hidden8f
      - binary_sensor.motion_sensor_hiddene9
      - binary_sensor.motion_sensor_hidden3e
      - binary_sensor.motion_sensor_hidden8f
      
  doors:
    name: Doors
    icon: mdi:door
    view: no
    entities:
      - binary_sensor.door_window_sensor_hiddenb9
      - binary_sensor.door_window_sensor_hidden16
      - binary_sensor.door_window_sensor_hiddena4
      - binary_sensor.door_window_sensor_hidden13
      
  windows:
    name: Windows
    icon: mdi:window
    view: no
    entities:
      - binary_sensor.door_window_sensor_hiddenc0
      
#################################################################
#                                                               #
#                     MQTT Control Panel                        #
#                                                               #
#################################################################

alarm_control_panel:
  - platform: manual_mqtt
    code: 1402
    state_topic: home/alarm
    command_topic: home/alarm/set
    code_arm_required: false
    pending_time: 30
    delay_time: 10
    trigger_time: 300
    disarmed:
      trigger_time: 0
    armed_home:
      pending_time: 15
      delay_time: 5
    armed_away:
      pending_time: 30
      delay_time: 5
    triggered:
      pending_time: 10
    
#################################################################
#                                                               #
#                      Template Sensors                         #
#                                                               #
#################################################################

sensor:
  - platform: template
    sensors:
      door_count:
        value_template: >-
           {{ states | selectattr('entity_id','in',state_attr('group.doors','entity_id')) | selectattr('state','eq','on') | list | count | int}}
      window_count:
        value_template: >-
           {{ states | selectattr('entity_id','in',state_attr('group.windows','entity_id')) | selectattr('state','eq','on') | list | count | int}}
           
#################################################################
#                                                               #
#                       Binary Sensors                          #
#                                                               #
#################################################################

### For Lovelace UI ###

#################################################################
#                                                               #
#                       Booleans Sensors                        #
#                                                               #
#################################################################
input_boolean:
  garage_armed:
    name: Arm garage
    initial: off
  backdoors_armed:
    name: Arm backdoors
    initial: off

####################################################
#                                                  #
#             Binary Sensor - Template             #
#                                                  #
####################################################
# This area sets the icon type for each group open/closed or missing

binary_sensor:
  - platform: template
    sensors:
## Door Sensors
      doors:
        friendly_name: Doors
        device_class: door
        entity_id: group.doors
        value_template: "{{ is_state('group.doors', 'on') }}"
        icon_template: >-
          {% if is_state('group.doors', 'on') %}
            fas:door-open
          {% elif is_state('group.doors', 'off') %}
            fas:door-closed         
          {% else %}
            mdi:alert
          {% endif %}
## Window Sensors
      windows:
        friendly_name: Windows
        device_class: window
        entity_id: group.windows
        value_template: "{{ is_state('group.windows', 'on') }}"
        icon_template: >-
          {% if is_state('group.windows', 'on') %}
            mdi:window-open
          {% elif is_state('group.windows', 'off') %}
            mdi:window-closed       
          {% else %}
            mdi:alert
          {% endif %}
## Alarm Panel
      alarm:
        friendly_name: Alarm
        entity_id: alarm_control_panel.ha_alarm
        value_template: >-
          {% if is_state('alarm_control_panel.ha_alarm', 'armed_home') %}
            on
          {% elif is_state('alarm_control_panel.ha_alarm', 'armed_away') %}
            on
          {% elif is_state('alarm_control_panel.ha_alarm', 'pending') %}
            on
          {% elif is_state('alarm_control_panel.ha_alarm', 'triggered') %}
            on
          {% else %}
            off
          {% endif %}
        icon_template: >-
          {% if is_state('alarm_control_panel.ha_alarm', 'armed_home') %}
            mdi:shield-home
          {% elif is_state('alarm_control_panel.ha_alarm', 'armed_away') %}
            mdi:shield-lock
          {% elif is_state('alarm_control_panel.ha_alarm', 'pending') %}
            mdi:security
          {% elif is_state('alarm_control_panel.ha_alarm', 'triggered') %}
            mdi:shield-close
          {% elif is_state('alarm_control_panel.ha_alarm', 'disarmed') %}
            mdi:shield-home
          {% else %}
            mdi:alert
          {% endif %}

Posts: 4

Participants: 2

Read full topic

@rolandow wrote:

When I started with my Home Assistant configuration, Area’s didn’t exist yet. Then when this was introduced, I started putting the devices in the right area; but previously I had already created groups for this.

So now with my new shelly mqtt devices, I have a group called “Livingroom” and an area called “Livingroom”. What is the best way to merge them? As far as I can see I cannot manually put entities in area’s.

I can put them in groups, by configuring the entities in groups.yaml. But then; how do I ‘hide’ the area with the same name?

Also I have two yeelights which don’t have an unique id (that’s what HA tells me). So I cannot add them to an area with the UI. So I guess I can only add these devices in groups; not in area’s?

At the moment area’s and groups are really confusing. Too bad there isn’t more documentation about this.

Posts: 1

Participants: 1

Read full topic

@MyKE wrote:

Hi,

According to https://www.home-assistant.io/blog/2020/03/18/release-107/#breaking-changes

Groups - Groups are NOT being removed, but the configuration options, services, and service options related to the (previously deprecated and now removed) States UI are now removed in this release.

I used to have a group of people where was check the state if this group is On/Off and according to this automation was initiated.

/config/groups.yaml

group_people:
  name: People
  icon: mdi:human-male-female
  entities:
    - input_boolean.personA_present
    - input_boolean.personB_present
    - binary_sensor.dt_router_personA
    - binary_sensor.dt_router_personB

Could you please explain how to use it in 0.107 version? Should I check manually all of these entities in my automation?

I used to have:

{% if trigger.to_state.state == “on” and trigger.entity_id == “group.group_people” %}

Should I use this instead:

{% if trigger.to_state.state == “on” and (trigger.entity_id == “input_boolean.personA_present” or trigger.entity_id == “input_boolean.personB_present” or trigger.entity_id == “binary_sensor.dt_router_personA” or trigger.entity_id == “binary_sensor.dt_router_personB”) %}

?

Thank you for explanation.

Posts: 4

Participants: 3

Read full topic

@Tom7320 wrote:

Hi

I use Tankerkönig platform to get and display gas prices. The platform does work as expected but it is very ugly. The main problem is, that I can not set friendly names for the created entities:

Also, the representation on the map is very ugly:

Is there a way to set a friendly name? The GUI does not let me change the name? Is it possible to show the fill up stations on the map with an icon like mdi-gas-station for example?

Stay healthy!

Posts: 2

Participants: 2

Read full topic

@ideal2545 wrote:

Hi All,

Was curious how I could enable the S31 Relay to be immediately on when it comes up, right now its defaulting into the off state.

# Device Specific Config

uart:
  rx_pin: RX
  baud_rate: 4800
  
binary_sensor:
  - platform: gpio
    pin:
      number: GPIO0
      mode: INPUT_PULLUP
      inverted: True
    name: "Dishwasher S31 Button"
    on_press:
      - switch.toggle: relay

switch:
  - platform: gpio
    name: "Dishwasher S31 Relay"
    pin: GPIO12
    id: relay

sensor:
  - platform: cse7766
    update_interval: 2s
    current:
      name: "Dishwasher S31 Current"
    voltage:
      name: "Dishwasher S31 Voltage"
    power:
      name: "Dishwasher S31 Power"

status_led:
  pin:
    number: GPIO13

Posts: 2

Participants: 2

Read full topic

@boneheadfraggle wrote:

I have a sensor that show all entities that are unavailable. Mostly to track any zigbee devices not responding or that someone switched off physically. That sensor works great. Thanks to @petro for that one!

   unavailable:
     friendly_name: 'Enheter utan data'
     value_template: >
       {{ states | selectattr('state', 'in', ['unavailable', 'unknown', 'none']) | list | length }}
     entity_id: sensor.time
     attribute_templates:
       entities: >
         {{ states | selectattr('state', 'in', ['unavailable', 'unknown', 'none']) | map(attribute='entity_id') | list | join('\n') }}

Now I’d like track unused automations the same way, with a sensor, counting the number of automation whose last_triggered is for example “now() - 6 weeks”. With the automations fulfilling this criteria in an attribute to that sensor.

Any suggestions?

Posts: 2

Participants: 2

Read full topic

@Roberto69 wrote:

Continuing the discussion from How to configure more than 1 application-id in TTN:

This issue is becoming more and more popular, as number of growing nodes and consequentially number of TTN apps growing up.
Is there any solution to use more than one TTN app in Home assistant?

Thank You!

Posts: 1

Participants: 1

Read full topic

@Stejo wrote:

Hi,

I got a strange problem after upgrading to 0.107.5. 2 of my views only display one column of cards in the middle instead of auto making 3 columns. (It don´t use the whole width) I can´t see any differences between the views and I use the cards in different views.

Somebody have any ideas, I tried also with the lovelace-layout-card
to force more columns, I got more but still not the whole width of the screen.

Capture1253×194 22.8 KB

!
Tried With layout-card

Capture11202×593 30.7 KB

!
A view that don´t use the whole width

Capture21229×246 41 KB

!
A view still working correct

Posts: 1

Participants: 1

Read full topic

@opmaniaopmania wrote:

오피 매니 아 닷 넷 수원오피 인천오피 인천풀사롱 강남풀싸롱 동탄휴게텔 강남안마 동탄오피 판교오피 성남ㅇ오피 분당오피

Posts: 1

Participants: 1

Read full topic

@opmaniaopmania wrote:

오피매니아 닷 넷 오피매니아주소변경 강남안마 강남오피 강남오피걸 강남풀싸롱 강남휴게텔 강남스파 역삼오피 부천오피 인천오피

Posts: 1

Participants: 1

Read full topic

@opmaniaopmania wrote:

오~피~매니아 닷 넷- 오피사이트 강남스파 수원오피매니아 인천오피매니아 동탄오피매니아 대구오피매니아 광주오피매니아 구미오피매니아오~피~매니아오~피~매니아 닷 넷- 오피사이트 강남스파 수원오피매니아 인천오피매니아 동탄오피매니아 대구오피매니아 광주오피매니아 구미오피매니아오~피~매니아오~피~매니아 닷 넷- 오피사이트 강남스파 수원오피매니아 인천오피매니아 동탄오피매니아 대구오피매니아 광주오피매니아 구미오피매니아오~피~매니아오~피~매니아 닷 넷- 오피사이트 강남스파 수원오피매니아 인천오피매니아 동탄오피매니아 대구오피매니아 광주오피매니아 구미오피매니아오~피~매니아

Posts: 1

Participants: 1

Read full topic

@Vikes34 wrote:

Disclaimer, I am new to playing with Home Assistant, about 2 weeks into it. I have been able to get various switches, dimmers and wall outlets up and running. That being said, I am having problems with the Honeywell ZW3107 Dimmer.

It is exhibiting the exact same behavior as described in this thread:

I cannot get it to turn fully off. It will turn off, but the light is left on with a very low modulation, so very dim.

This product is made by Jasco. Who also makes the GE Enbrighten product that is mentioned in the above thread.

Based on the manuals, the configuration parameters for the GE and Honeywell are identical:
GE: http://manual.zwave.eu/backend/make.php?lang=en&sku=28167%20(ZW3104)&cert=ZC10-15080013
Honeywell: {Sorry, being a new user I cannot add a third link to my post. }

But when I follow the directions in the thread, there are no “Node Config Options” available through the GUI to configure.

Here would be a list of questions:

1. How can I fix this problem?

2. When you add a node, where do the options and defaults for the product come from? I tried looking through the Home Assistant Repo, but didn’t have any luck.

Any help would be appreciated. Thanks

Posts: 1

Participants: 1

Read full topic

@grossmann wrote:

Hi, I have a long Jeedom experience, but once I’ve seen what HA permits, I decided to switch to HA
I’m a really newbie in HA.
I have a lot of mysensors Nodes, and all the temperatures nodes got to work : they appear in the Entities …
But, I cannot see the other ones : for example, I have a 8 relay switch, which appears nowhere, except in the logs :

2020-03-23 12:38:52 ERROR (MainThread) [mysensors.handler] Node 10 is unknown, will not add child 1
2020-03-23 12:38:52 DEBUG (MainThread) [mysensors.handler] n:0 c:255 t:3 s:9 p:154361 TSF:MSG:READ,10-10-0,s=2,c=0,t=3,pt=0,l=0,sg=0:

The sketch is this one :

#define MY_DEBUG 
#define MY_RADIO_NRF24
#define MY_REPEATER_FEATURE
#define MY_NODE_ID 10

#include <SPI.h>
#include <MySensors.h>

#define RELAY_1  3  // Arduino Digital I/O pin number for first relay (second on pin+1 etc)
#define NUMBER_OF_RELAYS 4 // Total number of attached relays
#define RELAY_ON 0  // GPIO value to write to turn on attached relay
#define RELAY_OFF 1 // GPIO value to write to turn off attached relay
#include <DallasTemperature.h>
#include <OneWire.h>
#define ONE_WIRE_BUS 7 // Pin where dallas sensor is connected
#define MAX_ATTACHED_DS18B20 1
#define TEMPERATURE_PRECISION 12

unsigned long SLEEP_TIME = 60000L*10L; // Sleep time between reads (in milliseconds)  10 MINUTES
  
OneWire oneWire(ONE_WIRE_BUS);
DallasTemperature sensors(&oneWire);
DeviceAddress tempDeviceAddress; // We'll use this variable to store a found device address
float lastTemperature;
int numSensors=0;
unsigned long prevMillis=0;
boolean receivedConfig = false;
boolean metric = true;
MyMessage tempMsg(0,V_TEMP);



void before() { 
  // Startup up the OneWire library
  sensors.begin();
  
  for (int sensor=1, pin=RELAY_1; sensor<=NUMBER_OF_RELAYS;sensor++, pin++) {
    // Then set relay pins in output mode
    pinMode(pin, OUTPUT);    
    digitalWrite(pin, RELAY_OFF);
  }
}

void setup() {
    // requestTemperatures() will not block current thread
  sensors.setWaitForConversion(false);
  analogReference(INTERNAL);
  if(sensors.getAddress(tempDeviceAddress, 0))   //0 car 1ère sonde DS18B20 trouvée
      {
        Serial.print("Device found: ");
        Serial.println(TEMPERATURE_PRECISION, DEC);
        sensors.setResolution(tempDeviceAddress, TEMPERATURE_PRECISION);
      } else {
        Serial.print("Found ghost device at ");
        Serial.print(1, DEC);
        Serial.print(" but could not detect address. Check power and cabling");
      }
}

void presentation()  
{   
  // Send the sketch version information to the gateway and Controller
  sendSketchInfo("VoletsNodeGrenier", "1.0");
  wait(2000);   //Nécessaire ????

    // Fetch the number of attached temperature sensors  
  numSensors = sensors.getDeviceCount();

  // Present all sensors to controller
  for (int i=0; i<numSensors && i<MAX_ATTACHED_DS18B20; i++) {   
     present(i, S_TEMP);
  }

  //for (int sensor=1, pin=RELAY_1; sensor<=NUMBER_OF_RELAYS;sensor++, pin++) {
  for (int sensor=1, pin=RELAY_1; sensor<=10;sensor++, pin++) {
    // Register all sensors to gw (they will be created as child devices)
    present(sensor, S_LIGHT);
  }
}


void loop() 
{
  unsigned long currMillis=millis();
  if (currMillis-prevMillis>=SLEEP_TIME)  {
      prevMillis=currMillis; // update
      sensors.requestTemperatures();
      // Fetch and round temperature to one decimal
      float temperature = static_cast<float>(static_cast<int>(sensors.getTempCByIndex(0) * 10.)) / 10.;
      if (lastTemperature != temperature && temperature != -127.00 && temperature != 85.00) {
          send(tempMsg.setSensor(0).set(temperature,1));
          lastTemperature=temperature;
      }
  }
  
}

  


void receive(const MyMessage &message) {
  if (message.type==V_LIGHT) {
     Serial.print("Incoming change for sensor:");
     Serial.print(message.sensor);
     Serial.print(", New status: ");
     Serial.println(message.getBool());
     //Ouverture/fermeture simple - 1 seconde appui
     if (message.sensor<=4) {
        digitalWrite(message.sensor-1+RELAY_1, RELAY_ON);     
        delay(500);
        digitalWrite(message.sensor-1+RELAY_1, RELAY_OFF);
     }
     //Ouverture/fermeture longue - 5 secondes appui
     if ((message.sensor>4) and (message.sensor<=8)) {
        digitalWrite(message.sensor-5+RELAY_1, RELAY_ON);     
        delay(5000);
        digitalWrite(message.sensor-5+RELAY_1, RELAY_OFF);
     }
          //Ouverture/fermeture longue - 5 secondes appui
     //STOP Volets roulants 1 
     if (message.sensor==9) {
        digitalWrite(RELAY_1, RELAY_ON);
        digitalWrite(RELAY_1+1, RELAY_ON);     
        delay(200);
        digitalWrite(RELAY_1, RELAY_OFF);
        digitalWrite(RELAY_1+1, RELAY_OFF);
     }
     //STOP Volets roulants 2 
     if (message.sensor==10) {
        digitalWrite(RELAY_1+2, RELAY_ON);
        digitalWrite(RELAY_1+3, RELAY_ON);     
        delay(200);
        digitalWrite(RELAY_1+2, RELAY_OFF);
        digitalWrite(RELAY_1+3, RELAY_OFF);
     }

   } 
}

Here the part of my config file :

mysensors:
  gateways:
    - device: '/dev/ttyUSB0'
      nodes:
        67:
          name: 'Citerneo'
        10:
          name: 'Grenier'
        40:
          name: 'Piscine' 
        2:
          name: 'Parents'
          
  debug: true
  persistence: true
  optimistic: true

I have no switch.yaml file. I don’t know why : it is a new install. I really need help …

Posts: 1

Participants: 1

Read full topic

@Steen67 wrote:

I have a problem with a binary sensor

I have make this 2 rules i tasmota

Rule1 on switch1#state do publish stat/sonoff_rf/RESULT {"POWER1":"%value%"} endon
Rule2 on switch2#state do publish stat/sonoff_rf/RESULT {"POWER2":"%value%"} endon

It works fine, I get this topic

13:28:01 MQT: stat/sonoff_rf/RESULT = {"POWER1":"1"}
13:28:04 RUL: SWITCH1#STATE performs "publish stat/sonoff_rf/RESULT {"POWER1":"0"}"
13:28:04 MQT: stat/sonoff_rf/RESULT = {"POWER1":"0"}
13:28:05 RUL: SWITCH1#STATE performs "publish stat/sonoff_rf/RESULT {"POWER1":"1"}"
13:28:05 MQT: stat/sonoff_rf/RESULT = {"POWER1":"1"}

13:28:12 RUL: SWITCH2#STATE performs "publish stat/sonoff_rf/RESULT {"POWER2":"0"}"
13:28:12 MQT: stat/sonoff_rf/RESULT = {"POWER2":"0"}
13:28:13 RUL: SWITCH2#STATE performs "publish stat/sonoff_rf/RESULT {"POWER2":"1"}"
13:28:13 MQT: stat/sonoff_rf/RESULT = {"POWER2":"1"}

But how do I make a binary sensor ?
This does not work

  - platform: mqtt
    state_topic: "stat/sonoff_rf/RESULT" 
    name: 'Dor'
    value_template: '{{value_json.POWER1.Data}}'
    payload_on: '1'
    payload_off: "0" 
    device_class: door
    qos: 1

Posts: 1

Participants: 1

Read full topic

@Javier_Gomez wrote:

Hello
I want to change the color of the temperature in lovelace.
Depending on whether the heating is working but I don’t get it.
I have tried a lot of things but I have not managed to make it work for me.
This code does not give me an error but it does not change the color either green or red.
Have if you can lend me a hand
Thank you

       - type: state-label
          entity: climate.nombre_calefaccion_01
          attribute: current_temperature
          suffix: ' ºC'
          style:
            top: 65%
            left: 22%
            color: >
             if (states('switch.rele_calefaccion_01') == 'heat') return 'red'; else return 'green';

Posts: 1

Participants: 1

Read full topic