@mrstanley wrote:

I am new to Home Assistant and still learning. I setup the USB adapter and configured the Z-Wave portion of the stick but am confused on setting up the ZigBee section. I couldn’t find any method to get the ZigBee working. The hardware is showing up both Z-Wave and ZigBee but am puzzled what steps are needed to finish the ZigBee portion of the stick. Any help appreciated.

Posts: 2

Participants: 2

Read full topic

@SylvainGa wrote:

So from time to time, when launching HA from my phone through the mobile app configured with Nabu Casa, I get a

Login attempt or request with invalid authentication from 127.0.0.1

Although I never get an access denied when accessing HA so I know it’s not a bad password and always seems to happen at the same time as I launch the app.

Anyway I can prevent these? If they were just in the log it wouldn’t bother me but it’s the persistent notification that annoys me.

Thanks.

Posts: 1

Participants: 1

Read full topic

@mchauhan wrote:

Hi I am running HASSOS on two different RPI3B, one is my production env and other one is development. Dev server running latest version 108.2 while prod is running version 101.3. I have below config. using a MQTT broker running on dev server and trying to monitor production HA status. I created a sensor on development server but getting status ‘Unknown’. Could someone guide and advise what is missing in bellows setup:

MQTTSetup21280×720 124 KB

Posts: 1

Participants: 1

Read full topic

@whatisk wrote:

I am looking at getting rid of my current Xiaomi Gateway and have setup Mosquito Broker and Zigbee2MQTT as per the instructions I have found (I have the board configured). And they appear to talk to one another without issue. I also setup the 10min timer for discovering devices as found in the documentation.

When trying to add a new Zigbee device, looking at the logs of Zigbee2MQTT it appears to find the device and it’s details okay, but I cannot find the device as an Entity anywhere.

Have included logs and configuraton below. Not sure why the devices aren’t showing. Running Hass.IO 0.107.7 as a fresh install before doing anything with my currenty running install (using Xiaomi Gateway).
Configuration.yaml

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# 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

mqtt:
  broker: core-mosquitto # This will have to be your mqtt broker, Mosquitto addon is recommended.
  discovery: true

input_boolean:
  zigbee_permit_join:
    name: Allow devices to join
    initial: off
    icon: mdi:cellphone-wireless

timer:
  zigbee_permit_join:
    name: Time remaining
    duration: 600 # Updated this to the number of seconds you wish

sensor:
  - platform: mqtt
    name: Bridge state
    state_topic: "zigbee2mqtt/bridge/state"
    icon: mdi:router-wireless

automation:
  - id: enable_zigbee_join
    alias: Enable Zigbee joining
    trigger:
      platform: state
      entity_id: input_boolean.zigbee_permit_join
      to: 'on'
    action:
    - service: mqtt.publish
      data:
        topic: zigbee2mqtt/bridge/config/permit_join
        payload: 'true'
    - service: timer.start
      data:
        entity_id: timer.zigbee_permit_join
  - id: disable_zigbee_join
    alias: Disable Zigbee joining
    trigger:
    - entity_id: input_boolean.zigbee_permit_join
      platform: state
      to: 'off'
    action:
    - data:
        payload: 'false'
        topic: zigbee2mqtt/bridge/config/permit_join
      service: mqtt.publish
    - data:
        entity_id: timer.zigbee_permit_join
      service: timer.cancel
  - id: disable_zigbee_join_timer
    alias: Disable Zigbee joining by timer
    trigger:
    - platform: event
      event_type: timer.finished
      event_data:
        entity_id: timer.zigbee_permit_join
    action:
    - service: mqtt.publish
      data:
        topic: zigbee2mqtt/bridge/config/permit_join
        payload: 'false'
    - service: input_boolean.turn_off
      data:
        entity_id: input_boolean.zigbee_permit_join

Mosquito Broker config:

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

Mosquito Broker log:

[11:15:32] INFO: Setup mosquitto configuration
[11:15:32] WARNING: SSL not enabled - No valid certs found!
[11:15:32] INFO: No local user available
[11:15:32] INFO: Initialize Hass.io Add-on services
[11:15:32] INFO: Initialize Home Assistant discovery
[11:15:32] INFO: Start Mosquitto daemon
1586567732: mosquitto version 1.6.3 starting
1586567732: Config loaded from /etc/mosquitto.conf.
1586567732: Loading plugin: /usr/share/mosquitto/auth-plug.so
1586567732: |-- *** auth-plug: startup
1586567732:  ├── Username/password checking enabled.
1586567732:  ├── TLS-PSK checking enabled.
1586567732:  └── Extended authentication not enabled.
1586567732: Opening ipv4 listen socket on port 1883.
1586567732: Opening ipv6 listen socket on port 1883.
1586567732: Opening websockets listen socket on port 1884.
1586567732: Warning: Mosquitto should not be run as root/administrator.
1586567733: New connection from 172.30.33.1 on port 1883.
[INFO] found mqtt on Home Assistant
1586567733: New client connected from 172.30.33.1 as mqttjs_dd849d93 (p2, c1, k60, u'mqtt').
1586567806: New connection from 172.30.32.1 on port 1883.
[INFO] found homeassistant on local database
1586567806: New client connected from 172.30.32.1 as auto-A0E17B1C-B4F5-BCF7-3F5D-4D41789B3C14 (p2, c1, k60, u'homeassistant').

Zigbee2MQTT config:

data_path: /share/zigbee2mqtt
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto'
  user: <user>
  password: <password>
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

Zigbee2MQTT log:

zigbee2mqtt:info  2020-04-11 11:05:46: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_removed","message":"left_network","meta":{"friendly_name":"0x00158d0001dc0a1a"}}'
zigbee2mqtt:info  2020-04-11 11:05:53: Device '0x00158d0001dc0a1a' joined
zigbee2mqtt:info  2020-04-11 11:05:53: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_connected","message":{"friendly_name":"0x00158d0001dc0a1a"}}'
zigbee2mqtt:info  2020-04-11 11:05:53: Starting interview of '0x00158d0001dc0a1a'
zigbee2mqtt:info  2020-04-11 11:05:53: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_started","meta":{"friendly_name":"0x00158d0001dc0a1a"}}'
zigbee2mqtt:info  2020-04-11 11:05:54: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"0x00158d0001dc0a1a"}}'
zigbee2mqtt:info  2020-04-11 11:05:54: Successfully interviewed '0x00158d0001dc0a1a', device has successfully been paired
zigbee2mqtt:info  2020-04-11 11:05:54: Device '0x00158d0001dc0a1a' is supported, identified as: Xiaomi Mi power plug ZigBee (ZNCZ02LM)
zigbee2mqtt:info  2020-04-11 11:05:54: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_successful","meta":{"friendly_name":"0x00158d0001dc0a1a","model":"ZNCZ02LM","vendor":"Xiaomi","description":"Mi power plug ZigBee","supported":true}}'
zigbee2mqtt:info  2020-04-11 11:05:55: MQTT publish: topic 'zigbee2mqtt/0x00158d0001dc0a1a', payload '{"state":"OFF","power":0,"voltage":null,"consumption":25.42,"temperature":25,"linkquality":92}'
zigbee2mqtt:info  2020-04-11 11:05:56: MQTT publish: topic 'zigbee2mqtt/0x00158d0001dc0a1a', payload '{"state":"OFF","power":0,"voltage":null,"consumption":25.42,"temperature":25,"linkquality":92}'
zigbee2mqtt:info  2020-04-11 11:05:56: MQTT publish: topic 'zigbee2mqtt/0x00158d0001dc0a1a', payload '{"state":"OFF","power":0,"voltage":null,"consumption":25.42,"temperature":25,"linkquality":89}'

So, if I am understanding the log correctly, the device (in this case a Xiaomi power plug) is being recognised/discovered without issue. So, not sure why it is not showing up. When I look at the Mosquite integration and devices, it lists none. If I check the System Options within the Integration it has ‘enable newly added entities’ enabled.

This is running in a VM on an Intel Nuc. A while back I also briefly tried on a RPi and had devices there add and show successfully. My preference is to use the NUC (where my current Hass.IO install is) and a VM to keep all my machines together.

Posts: 3

Participants: 2

Read full topic

@msahar wrote:

I want to listen jingle bells at 9 AM every Friday, Saturday, and Sunday. Below are the code spinets from configuration and automation files. I am not able to achieve this despite several attempts. I would be grateful if anybody point out what is wrong with my code. Thanks

configuration.yaml

binary_sensor:
  - platform: workday
    country: AU
    workdays: [fri, sat, sun]

automation.yaml

#################### Jingle Music ####################
- alias: 'Jingle Bells'
  trigger:
     platform: time
     at: '09:00:00'
  condition:
      condition: state
      entity_id: 'binary_sensor.workday_sensor'
      state: 'on'
  action:
   - data:
       entity_id: "media_player.sahar_google_mini"
       media_content_id: "https://incompetech.com/music/royalty-free/mp3-royaltyfree/Jingle%20Bells%203.mp3"
       media_content_type: "music"
     service: media_extractor.play_media
   - data:
       entity_id: media_player.sahar_google_mini
       volume_level: '0.7'
     service: media_player.volume_set

Best Regards,
Sahar

Posts: 4

Participants: 3

Read full topic

@sanmane wrote:

Hi!

My Z-Wave network seems to be broken somehow. It has been running flawlessly for the past few months. I’m not sure what as gone wrong, and I don’t want to make things worse. My hassio install in running on a Dell Optiplex running Windows 10 as the host OS with VirtualBox running Ubuntu Server with a Hassio on Docker. The USB is passed though to the VM for the stick. I have had no issues with this setup until recently. I cloned the hard drive as I migrated to an SSD recently, I have no idea if that is related. I am using a Z Stick gen5 with three Zooz dImmers and two of the new Inovelli dimmers (fantastic dimmers).

Currently, on the home page of HA, all my devices show as “unavailable,” however in the Z-Wave section, Z-Wave appears to be started.

I am running HA v0.108.3.

Thanks in advance for your help.

here is my config:

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# 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

#Thermostat
climate 1:
  - platform: honeywell
    username: hidden
    password: hidden
    region: us
    scan_interval: 600

# Example for Z-Wave
homekit:
  auto_start: false

discovery:
  enable:
    - homekit

switch:
  - platform: command_line
    switches:
      aeotec_zstick_disco_light:
        friendly_name: 'Aeotec Z-Stick Disco Light'
        command_on: 'echo -e -n "\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50" > /dev/serial/by-id/usb-0658_0200-if00'
        command_off: 'echo -e -n "\x01\x08\x00\xF2\x51\x01\x00\x05\x01\x51" > /dev/serial/by-id/usb-0658_0200-if00'

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

My OZW_Log file can be found at https://pastebin.com/gAgKm8js

Posts: 1

Participants: 1

Read full topic

@GrahamS wrote:

Now at HA 0.108.3
As discussed here, sensor values are plotted as a staircase of values. I converted some sensors to input_number to retain their values after HA restart. I was surprised to discover the input_number values are plotted in a spline. I do not see a Lovelace option to control the plotting style so I created a template sensor for plotting based on the input_number value. This works.

  - platform: template
    sensors:
      furnace_power_plot:
        friendly_name: 'Furnace Power Plot'
        unit_of_measurement: 'kW'
        value_template: '{{ states.input_number.furnace_power.state}}'

Some people want to see the spline plot for a sensor. I do not see a template input_number for a similar workaround.

Posts: 1

Participants: 1

Read full topic

@Faramir wrote:

I am a little stuck on how to create triggers and conditions for an automation I’d like that is depending on temperatures of two sensors.

In pseudo-code I’d like the automation to be triggered when:

IF [inside temperature] > 24 AND 
   [outside temperature] < [inside temperature] AND 
   [clerestory window state] = 'Closed'

What I’ve currently got is as below. However the second condition is where I’d like to compare the inside temperature to the outside temperature so that the second condition is only satisfied when outside is cooler than inside.

Any ideas, help, pointers to more reading / examples would be very much appreciated

- id: '1586585163400'
  alias: Clerestory - Auto - In over 24 and outside less
  trigger:
  - above: '24'
    entity_id: sensor.dining_temperature
    platform: numeric_state
  condition:
  - condition: and
    conditions:
    - condition: state
      entity_id: input_select.clerestory_window
      state: Closed
    - below: '24'
      condition: numeric_state
      entity_id: sensor.outside_temperature
  action:
  - data: {}
    entity_id: switch.openclerestory
    service: switch.turn_on

Posts: 1

Participants: 1

Read full topic

@cinquemic wrote:

Hi all,

I have a problem with a button card I’m running on hassio 0.108.1.
When I set assumed_state: false in customize, the button switch to on and then to off, if I re-press the button it work normally and it stay on.
the code for the switch:

- platform: command_line
    switches:
      irrigazione:
        command_on: 'python3 /config/python_scripts/irrig_on.py'
        command_off: 'python3 /config/python_scripts/irrig_off.py'

If I use an entity card and don’t use assumed_state: false the switch works normally.
Any ideas?
thanks

Posts: 1

Participants: 1

Read full topic

@Mariusthvdb wrote:

Checking my groups I now notice all groups still show ‘order’ in the developer-tools/states

Sorry for the tag, but please let me ask @frenck, is this still used and undocumented, or an oversight when all other state related aspects where taken out lately?

107.5 Hassio here.
Thanks for having a look

Posts: 1

Participants: 1

Read full topic

@Markg wrote:

Hello, I have an owl cm180 energy monitor that I’ve setup with a rfxtrx433e. Every now and then I get a Total usage stat of 0 which is throwing off my calculations for cost for the previous hour. It doesn’t reflect on the owl monitor itself, only within home assistant. Has anybody else come across this? My gut feeling is that it’s the reading from one of the other phase inputs from the transmitter (I only have 1 connected) but I only see one input in home assistant.
The total use stat is also slightly off compared to what I see on the owl monitor, if anybody has any advice on that I’d appreciate it too!

Posts: 1

Participants: 1

Read full topic

@dvbit wrote:

I have the following issue:
I cannot customize any feature of zwave entities.
If I just change even just an icon although they are still listed under the controller I cannot do anything anymore with them.
They are ready in the zwave section of the settings but have no component anymore under them.
Does anyone have the same?is there a solution not requiring to remove and reinclude the nodes (f…k)

Posts: 1

Participants: 1

Read full topic

@sean.mcgrath wrote:

Hi all,

I would like to get state_topic working on my switch, and would love some feedback.

I have an MQTT switch that sends messages to my ESP32 Arduino board to turn irrigation valves on and off – this works fine. I would like to make it a closed loop system: have the switch receive a message that the action has been carried out, and only then would the HA dashboard show the change in state.

I have set it up so that the ESP32 sends out the MQTT confirmation when it receives the command – this also works fine. However, the HA dashboard does not react to the message at all. Here’s the part of my config:

switch:
# Arduino switches for four garden valves
  - platform: mqtt
    name: 'In1'
    state_topic: 'garden/state'
    command_topic: 'garden/valve1'
    retain: true
    state_on: '{"valve": "In1", "value": 1}'
    state_off: '{"valve": "In1", "value": 0}'
    payload_on: '{"valve": "In1", "value": 1}'
    payload_off: '{"valve": "In1", "value": 0}'
    icon: mdi:water

I’ve tried with and without the state_on / _off lines, and have restarted HA, but no luck. I’m not even sure where to look. Does anyone have tips on how to debug this?

cheers,
Sean

Posts: 4

Participants: 3

Read full topic

@ryan.mccartney wrote:

Hi,

Has anyone had any success trying to integrate a Mi-Light 5 in 1 LED controller with Home Assistant?

They use the closed 2.4GHz RF communications to work with remotes and bridges. They also connect directly to Wi-Fi and appear to act as their own single channel bridge.

Being in the mi-light eco system I’m assuming it can be added in the same way as a bridge using he limitlessLED integration.

Here’s my configuration;

#Mi-Light Configuration
light:
  platform: limitlessled
  bridges:
    - host: 192.168.0.55
      version: 4
      port: 8899
      groups:
      - number: 1
        name: Stairs
        type: white
        fade: true

I’ve been able to interrogate the device which is connected to my network using the tools here;

https://github.com/BKrajancic/LimitlessLED-DevAPI

I can even control the light from web browser using port 8899 and some of the commands documented in the link above.

When integrated with Home Assistant the new entity is added with no configuration errors raised, but as far as I can tell no UDP messages are ever sent from HA. The light doesn’t respond to commands through Home Assistant.

Update

Some investigation using Wireshark seems to show that Home Assistant never sends any data to the controller’s IP address. When using the web browser the traffic sent to the controller can be seen.

Posts: 1

Participants: 1

Read full topic

@AlphaSupreme wrote:

I started using the stream component this morning.
The camera’s seem to work, but if I look at the live view of the camera, it has a 1 minute and 52 second delay. Tried multiple camera streams (direct to camera and via synology) but all the same result.

Camera config:

camera:
  - platform: synology
    url: https://[ip]:5001
    username: !secret synology_username
    password: !secret synology_password
    verify_ssl: false
  - platform: generic
    name: carport
    still_image_url: "http://[ip]/cgi-bin/snapshot.cgi"
    stream_source: "rtsp://username:password@[ip]:554/cam/realmonitor?channel=1&subtype=00"
    username: !secret camera_username
    password: !secret camera_password
  - platform: generic
    name: carport_synology_rtsp
    still_image_url: "http://[ip]/cgi-bin/snapshot.cgi"
    stream_source: "rtsp://syno:[token]@[ip]:554/Sms=5.unicast"

picture entity config:

aspect_ratio: 66%
camera_image: camera.carport
camera_view: live
entity: camera.carport
show_name: true
show_state: true
type: picture-entity

Any idea how I can get the live image?

Posts: 2

Participants: 2

Read full topic

@rch1708 wrote:

Hello Experts,

To begin, I’m new to HA - attempting to move over from OpenHAB. In my current config, I have a ‘switch’ entity that has a (power consumption) value associated with it. I want to extract the power consumption value and make it a ‘sensor’ entity so that I can graph it. To this end I have setup the following configuration in “sensor.yaml”, after having checked it in the Template Editor:

sensor:
  - platform: template
    sensors:
      american_fridge_power:
        friendly_name: "American Fridge Power"
        unit_of_measurement: 'Watt'
        value_template: "{{ states.switch.americanfridge.attributes.current_consumption }}"

Sensor.yaml is hooked into configuration.yaml with an include. The Template Editor gives the following result:

sensor:
  - platform: template
    sensors:
      american_fridge_power:
        friendly_name: "American Fridge Power"
        unit_of_measurement: 'Watt'
        value_template: "90.1"

The problem is that I have no evidence that this configuration results in a sensor being created. I don’t see a sensor called ‘american_fridge_power’ appear anywhere ie not in the ‘Entities’ list. But neither do I have any evidence that the sensor is not being created - ie there’s nothing in the log file to indicate a problem.

So what am I doing wrong? Have I missed a step out somewhere? Or has the sensor been created and I’ve not yet found it.

Many thanks.

Posts: 3

Participants: 3

Read full topic

@Denny_d wrote:

Hi everyone, these days I have been working on automating cooling fans based on the CPU temperature of the RPI4.
I created this automation which based on a certain temperature that I set with input_text as the minimum and maximum value increases or decreases the fan speed.
This is one of the automations:

  - alias: ventole_bassa_velocita_s1
    trigger:
      platform: state
      entity_id: sensor.cpu_temperature
    condition:
      condition: and
      conditions:  
        - condition: template
          value_template: >
            {{ trigger.to_state.state|float   >= states('input_text.velocita_bassa_sopra_s1')|float and 
               trigger.from_state.state|float <=  states('input_text.velocita_bassa_sotto_s1')|float }}
        - condition: state
          entity_id: input_boolean.attivazione_automazione_s1
          state: 'on'
        - condition: state
          entity_id: input_boolean.bassa_velocita_s1
          state: 'off'
    action:
    - service: light.turn_on
      data:
        entity_id: light.tutte_le_ventole_s1
        brightness: 255
    - delay: 00:00:05
    - service: light.turn_on
      data_template:
        {"brightness": "{{ states('input_number.velocita_bassa_s1')|int }}","entity_id": "light.tutte_le_ventole_s1"}
    - service: input_boolean.turn_on
      entity_id: input_boolean.bassa_velocita_s1
    - service: input_boolean.turn_off
      entity_id:
        - input_boolean.ventole_spente_s1
        - input_boolean.media_velocita_s1
        - input_boolean.alta_velocita_s1

It all works only that by doing tests I realized that many times the CPU temperature exceeds the set parameters for a few seconds and the speed changes very often.

My goal is that if the minimum and maximum CPU temperature

        - condition: template
          value_template: >
            {{ trigger.to_state.state|float   >= states('input_text.velocita_bassa_sopra_s1')|float and 
               trigger.from_state.state|float <=  states('input_text.velocita_bassa_sotto_s1')|float }}

it goes back in those values for 5 minutes then everything starts without being instantaneous.
how can i do it? thanks

Posts: 1

Participants: 1

Read full topic

@Boogs77 wrote:

Hi to all!
I got this error several weeks ago, but I’m not able to solve it.

image858×534 41.6 KB

systemmonitor: Error on device update!
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 324, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 476, in async_device_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/systemmonitor/sensor.py", line 151, in update
    self._state = round(psutil.disk_usage(self.argument).free / 1024 ** 3, 1)
  File "/usr/local/lib/python3.7/site-packages/psutil/__init__.py", line 2013, in disk_usage
    return _psplatform.disk_usage(path)
  File "/usr/local/lib/python3.7/site-packages/psutil/_psposix.py", line 121, in disk_usage
    st = os.statvfs(path)
FileNotFoundError: [Errno 2] No such file or directory: ''

Hassio on PI3+ 0.108.3

Thanks in advance
Boogs

Posts: 2

Participants: 2

Read full topic

@PeetsHome wrote:

Hello all, iám rather new on HA and having some questions about MQTT sensor readings / formatting
In the template editor it works ok

{{ states(‘sensor.DB199_OB098’) | round(0) }}
{{ (states(‘sensor.DB199_OB097’)|float * 1 / 1000) | round(3)}}

But when i put this in my configuration.yaml .is not diplaying getting any data, also no error message.

• platform: mqtt
  state_topic: ‘DB199-OB098’
  name: “db199-ob098”
  value_template: ‘{{ states(sensor.db199_ob098) | round(0) }}’
  unit_of_measurement: ‘Watt’

• platform: mqtt
  state_topic: ‘DB199-OB097’
  name: “db199-ob097”
  value_template: ‘{{ ( states(sensor.db199_ob097)|float * 1 / 1000) | round(3)}}’
  unit_of_measurement: ‘kWh’

If i remove the value_template the unformatted values are dislayed like +0.3062391E+03 Watt

Posts: 2

Participants: 2

Read full topic

@BullFrog wrote:

Updated HA from 107.6 to 108.3 around 11:10~

WLED integration started to act strange, Unavailable -> ON -> Unavailable -> ON.
Even when when I turned OFF it became unavailable and from OFF it turns back ON.

Reverted back to 107.3 and it is working fine without error. Log says nothing usefull, like there is no problem at all.

Device is Weemos D1 with WLED 0.9.1
Anyone else has the same issue? WLEDs connection is stable I can control it from UI and works good from HA 107

Posts: 3

Participants: 2

Read full topic