@CoMPaTech wrote:

If you aren’t shy to try beta software, have an Adam, Anna or P1 Smile for your climate and/or power monitoring and anxious to get it working in Home-Assistant we (@bouwew and @CoMPaTech) present the beta and custom_component for plugwise. Difference with the currently upstreamed and HA-core available plugwise component is we support a much bigger range of Plugwise devices.

If you’re less confident have some patience, we are working towards a PR against HA-core to update the existing component so everyone can enjoy. Installing this custom_component involves configuring HACS and/or manual tinkering.

To get started, review the README on https://github.com/plugwise/plugwise-beta version 0.1.0. and share your experiences here and your issues at that repo!

If you’re unsure how to start, if you already use the HA-core component or a previous version:

• You are not using Anna or Adam yet in HA: make yourself familiair with HACS if you have that installed you’ll be able to add the component in mere seconds
• You are using the HA component: prepare HACS as per above, note that you’ll have to remove your current plugwise config by removing those lines from you configuration.yaml
• You are using the downloaded version of the old Anna-HA or bouwes repositories, you’ll have to remove that custom component and remove the plugwise config from your configuration.yaml . You can decide to either download the component yourself or go the HACS-way indicated above.

The new custom_component is configured through the web-interface as shown a in this post up. We can’t urge you enough to read the README file that is included in the repository and obviously help eachother to get things up and running. Current things we - based on input of fellow owners testing - support are (v as in firmare major version): Adam v2/v3, Anna v1/v3/v4 and P1 v2/v3.

On behalf of @bouwew and myself big thanks to @riemers and @Tane for their support and all our testers over the last week(s) who dealt our typos and challenges.

Posts: 1

Participants: 1

Read full topic

@jazzmonger wrote:

I’ve tried pretty much every spacing option presented in the docs and this forum that I can find of but keep getting this error when I do a CHECK CONFIGURATION. I’ve dumbed it down completely.

Invalid config for [telegram_bot]: expected int @ data['telegram_bot'][0]['allowed_chat_ids'][0]. Got None. (See /config/configuration.yaml, line 52). 

Here’s my exact entries in configuration.yaml

notify:
  - platform: telegram
    name: telegram
    chat_id: xxxxx
telegram_bot:
  platform: webhooks
  api_key: xxxxx
  allowed_chat_ids:
    - xxxxx    

Any ideas? I have the iOS app working with a BotFather created bot.

Jeff

Posts: 4

Participants: 2

Read full topic

@brian1917 wrote:

@bachya - did a somewhat recent change (something between 0.106.* and 0.107.7) switch the SimpliSafe API to WebSocket from polling?

I’ve noticed quicker response time to state changes (awesome!), but I’ve also seen more frequent times when Home Assistant doesn’t pick up the state change at all. For example, I shut my alarm off this morning and Home Assistant still sees it as in Home while the SimpliSafe app shows it correctly as Off.

I know you were experimenting with using SimpliSafe WebSocket so wondering if that change went into effect and could explain the new behavior.

If that is the case, is there any way that a user can still configure a periodic poll to catch state changes that might have been missed?

Posts: 1

Participants: 1

Read full topic

@Jaques-Ludwig wrote:

Hi,

I tried to install piVCCU and deconz 2 USB Stick on one Raspberry 3b. I had no success.
I installed first piVCCU as image. The I installed docker, then portrainer. This worked.

After that I installed deconz as docker. With the phoscon app I could turn on and off my zigbee lights. All seemed to be perfect.

But then I searched my zigbee lights in home assistant. Home assistant is installed on another Raspberry Pi 3b. The addon in HA found my zigbee devices but that was all.

When I looked to “entitäten” I saw the zigbee devices but in status it shows “unavailable”. But at the same time I was able to control the lights with the phoscon app.

What is the failure? I can’t find what I have to change.

Thanks,

Jaques-Ludwig

Posts: 1

Participants: 1

Read full topic

@Skye wrote:

Could anyone share with me what to send over mqtt to change the vibration sensor’s sensitivity? Is there any confirmation or way to know it was applied?

Posts: 1

Participants: 1

Read full topic

@jeffreykog wrote:

Hi, i have a really weird problem which started around 3 weeks ago.

At random moments in the day (Not more than once a day, some days not), all my tradfri (around 15) bulbs and outlet switches strobe very fast for a second or two, turn on, then they fully lose connection to zigbee2mqtt after which i cannot control them any more. My Hue bulbs do not show this behavior.

I just caught it happening again at 18:30 local time, and i grabbed the zigbee2mqtt log around that moment. This is all logging that happened directly after this event:

zigbee2mqtt:info  2020-04-03 16:26:50: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"bedlamp_<redacted>"}}'
zigbee2mqtt:info  2020-04-03 16:29:03: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw03"}}'
zigbee2mqtt:info  2020-04-03 16:29:03: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw01"}}'
zigbee2mqtt:info  2020-04-03 16:29:03: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw04"}}'
zigbee2mqtt:info  2020-04-03 16:29:03: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw04"}}'
zigbee2mqtt:info  2020-04-03 16:29:04: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"werkkamer_jeffrey_bureau_links"}}'
zigbee2mqtt:info  2020-04-03 16:29:04: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw04"}}'
zigbee2mqtt:info  2020-04-03 16:29:04: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw02"}}'
zigbee2mqtt:info  2020-04-03 16:29:04: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"werkkamer_jeffrey_bureau_links"}}'
zigbee2mqtt:info  2020-04-03 16:29:04: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw01"}}'
zigbee2mqtt:info  2020-04-03 16:29:05: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw01"}}'
zigbee2mqtt:info  2020-04-03 16:29:05: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw03"}}'
zigbee2mqtt:info  2020-04-03 16:29:05: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw03"}}'
zigbee2mqtt:info  2020-04-03 16:29:06: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw01"}}'
zigbee2mqtt:info  2020-04-03 16:29:06: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"werkkamer_jeffrey_bureau_rechts"}}'
zigbee2mqtt:info  2020-04-03 16:29:06: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw04"}}'
zigbee2mqtt:info  2020-04-03 16:29:07: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw01"}}'
zigbee2mqtt:info  2020-04-03 16:29:07: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"werkkamer_jeffrey_bureau_rechts"}}'
zigbee2mqtt:info  2020-04-03 16:29:08: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"werkkamer_jeffrey_bureau_rechts"}}'
zigbee2mqtt:info  2020-04-03 16:29:09: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"tsw04"}}'

Now this shows that the bulbs/switches have probably powercycled and are re-announcing to the network. After each event, maybe one or two becomes responsive again, the others i have to re-pair to the network after which they work fine (until the next time this happens).

I have tested a lot of things. I run on the latest version of zigbee2mqtt (1.12). I have tried a different CC2531 stick, have upgraded the firmware on it, even tried the source routing firmware which also had the same problem. I have tried starting from scratch with zigbee2mqtt repairing all devices in the house. I have checked and my zigbee channel is the zigbee2mqtt default channel, and this does not overlap with my 2.4GHz wifi networks. My house has 3 layers of brick so interference from neighbors should not have much of an effect, while inside the house i receive no other wifi networks as my own, though there may be other kinds of interference, but that would be difficult to detect.

I did not yet try moving to another zigbee channel, but i wanted to check here first. Is there anyone who has experienced the same or something similar? This setup has worked for a year without any problems. I maybe suspect some kind of power issue in my area, but here in the Netherlands the power is really reliable and i never have outages or weird brownouts. Voltage is always around 230V, at least always between 220V and 240V. I hope anyone can give more insight on this as i’m afraid i am not going to find the cause on my own.

Posts: 3

Participants: 2

Read full topic

@Dayve67 wrote:

How can I go about trouble shooting these warnings? My log file is filled with them.

Image may be NSFW.
Clik here to view.

Posts: 1

Participants: 1

Read full topic

@mprimog wrote:

Hello,

I am testing deepply Modbus integration.

TCP integration works well.

I am now with “serial” and i am getting an error in the configuration:

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/setup.py”, line 170, in _async_setup_component
hass, processed_config
File “/config/custom_components/modbus/init.py”, line 102, in async_setup
hub_collect[client_config[CONF_NAME]] = ModbusHub(client_config, hass.loop)
File “/config/custom_components/modbus/init.py”, line 174, in init
self._config_delay = client_config[CONF_DELAY]
KeyError: ‘delay’

Any clue?

This is my configuration

modbus:
  name: hub1
  type: serial
  method: rtu
  port: /dev/ttyUSB0
  baudrate: 9600
  stopbits: 1
  bytesize: 8
  parity: N

Thanks a lot.
Marcos.

Posts: 2

Participants: 2

Read full topic

@Skye wrote:

Would like to add a siren sound to my Sqeezelite setup when the alarm goes off.

I couldn’t find in the LMS api what function to call to play a local file, stored in the LMS server’s library.
Could anyone post the configuration for this service call?

Thanks

Posts: 2

Participants: 2

Read full topic

@xion2000 wrote:

I have 2 solar setups each giving production figures via sensors, can I combine 2 (or more) sensors together to create a completely new sensor giving the total solar of the 2 systems combined.

currentcost_garage_solar:
        entity_id: sensor.current_cost
        unit_of_measurement: 'W'
        value_template: '{{ state_attr("sensor.current_cost", "Appliance 1")[:-2]  }}'
        friendly_name: CurrentCost Garage Solar

currentcost_shed_solar:
        entity_id: sensor.current_cost
        unit_of_measurement: 'W'
        value_template: '{{ state_attr("sensor.current_cost", "Appliance 2")[:-2]  }}'
        friendly_name: CurrentCost Shed Solar

Posts: 2

Participants: 2

Read full topic

@flyingsubs wrote:

Has anyone gotten scene triggers to work from their zooz light switch? I have the dimmer one (ZEN27).

I’ve successfully gotten inovelli to work, but not this one. I’m running the latest home assistant and have successfully added the devices to home assistant.

Thanks!
Flyingsubs

Posts: 1

Participants: 1

Read full topic

@balazs wrote:

I have a Honeywell QuietSet 16inch stand fan and I can control this via broadlink.
The fan has 5 speed levels, my goal is to use level 1 from 20°C to 23°; level 2 from 23°C to 27°C; level 3 from 27°C to 30°C etc etc.
I have just one button to control the speed, one push, one level up. That means if I want to go from level 3 to level 2 down, I have to push the button 4x (1. level 3->level 4; 2. level 4->level 5; 3. level5->level 1; 4. level1->level2).
How should look like the automation for this?
My first idea was to create a “dummy” entity with 5 “temperature zones”=5 states. The entity should set the status from 1 to 5 depending on the temperature. After that I can use this entity as a trigger. For example from level 3 to level 2 should trigger an action “push 4x the speed button”
How can I create such a dummy entity? Would this work? Any other ideas?

Posts: 1

Participants: 1

Read full topic

@Mastiff wrote:

I have a Popp with a power supply. In the manual it says that it has to be run with two batteries even with the PSU, which I have found to be bull. The only thing is that with the PSU only Hass shows a battery level at 0. Does anybody else have this running with a PSU?

Also since battery consumption isn’t an issue, I would like to hve it wake up a lot more often. The standard is 604800, I assume that’s ms. Which means ten minutes. So on a reboot of Hass it takes up to ten minutes before this thing actually shows up as anything but “intializing”. But when I try to set the interval to one minute (6000 ms) in node configuration, it doesn’t seem to stick. Does that mean that the interval is fixed in this device, or do I need to do anything else?

I had to press the door bell button to wake it up before I set the wake-up interval! It didn’t get queed for some reason. One problem solved. Partly. Because it doesn’t go from “initialized (cache load)” any faster, I actually have to wake it up by pressing the door bell button to do that

Posts: 1

Participants: 1

Read full topic

@koni wrote:

Hi everybody,

i try to use my smart-me switch which has a rest-api:
https://smart-me.com/swagger/ui/index#!/Actions/Actions_Post

i got so far to use the sensor to connect to the api and not throw an error, but the value are not available in the overview (or rather they are undefined):

sensor:
  - platform: rest
    name: smartmesensor
    json_attributes:
        - Id
        - Name
        - Serial
        - DeviceEnergyType
        - FamilyType
        - ActivePower 
        - ActivePowerUnit
        - CounterReading
        - CounterReadingUnit
        - CounterReadingT1
        - CounterReadingImport
        - SwitchON
        - Voltage
        - VoltageL1
        - Current
        - PowerFactor
        - PowerFactorL1
        - Temperature
        - ValueDate
    resource: https://smart-me.com:443/api/Device/***DEVICE-ID***
    authentication: basic
    username: ***my_username***
    password: ***my_passwort***
    value_template: 'ok'
  - platform: template
    sensors:
      sm_activepower:
        value_template: '{{states.sensor.smartmesensor.attributes["ActivePower"] }}'
        device_class: power
        unit_of_measurement: 'kWh'
      sm_voltage:
        value_template: '{{states.sensor.smartmesensor.attributes["Voltage"] }}'
        unit_of_measurement: 'V'
      sm_counterreading:
        value_template: '{{states.sensor.smartmesensor.attributes["CounterReading"] }}'
        device_class: power
        unit_of_measurement: 'kWh'
      sm_current:
        value_template: '{{states.sensor.smartmesensor.attributes["Current"] }}'
        unit_of_measurement: 'A'
      sm_switchon:
        value_template: '{{states.sensor.smartmesensor.attributes["SwitchON"] }}'

the answer of the rest-api is:

{
  "Id": "string",
  "Name": "string",
  "Serial": 0,
  "DeviceEnergyType": "MeterTypeUnknown",
  "MeterSubType": "MeterSubTypeUnknown",
  "FamilyType": "MeterFamilyTypeUnknown",
  "ActivePower": 0,
  "ActivePowerL1": 0,
  "ActivePowerL2": 0,
  "ActivePowerL3": 0,
  "ActivePowerUnit": "string",
  "CounterReading": 0,
  "CounterReadingUnit": "string",
  "CounterReadingT1": 0,
  "CounterReadingT2": 0,
  "CounterReadingT3": 0,
  "CounterReadingT4": 0,
  "CounterReadingImport": 0,
  "CounterReadingExport": 0,
  "SwitchOn": true,
  "SwitchPhaseL1On": true,
  "SwitchPhaseL2On": true,
  "SwitchPhaseL3On": true,
  "Voltage": 0,
  "VoltageL1": 0,
  "VoltageL2": 0,
  "VoltageL3": 0,
  "Current": 0,
  "CurrentL1": 0,
  "CurrentL2": 0,
  "CurrentL3": 0,
  "PowerFactor": 0,
  "PowerFactorL1": 0,
  "PowerFactorL2": 0,
  "PowerFactorL3": 0,
  "Temperature": 0,
  "ActiveTariff": 0,
  "DigitalOutput1": true,
  "DigitalOutput2": true,
  "AnalogOutput1": 0,
  "AnalogOutput2": 0,
  "DigitalInput1": true,
  "DigitalInput2": true,
  "ValueDate": "2020-04-03T19:15:18.557Z",
  "AdditionalMeterSerialNumber": "string",
  "FlowRate": 0
}

Additionally i try to use the switch feature:

switch:
  - platform: rest
    name: smartme
    resource: https://smart-me.com:443/api/Actions
    username: ***username***
    password: ***passwort
    body_on:  '{"DeviceID": "***device-id****","Actions": [{"ObisCode": "***obiscode***","Value": 1}]}'
    body_off: '{"DeviceID": "***device-id***","Actions": [{"ObisCode": "***obiscode***","Value": 0}]}'
    headers:
      Content-Type: application/json
      authentication: basic

with the message being:

{
  "DeviceID": "string",
  "Actions": [
    {
      "ObisCode": "string",
      "Value": 0
    }
  ]
}

i get the following error about the switch function:
2020-04-03 21:08:17 ERROR (MainThread) [homeassistant.components.rest.switch] Got non-ok response from resource: 405

Thanks for helping

Posts: 1

Participants: 1

Read full topic

@Canedje wrote:

I’m just wondering but can not find the answers on internet.
I know that for conbee the connected end device limit is 32.
Does anyone know what the limit is for the conbee II and deCONZ?

Posts: 1

Participants: 1

Read full topic

@RickyTheCat wrote:

Hi all.

I want to use smart bulbs (Philips Hue) with regular non-smart light switches (for appearance and usability).

I want somebody pressing the switch to toggle the lights on and off.

I also want to be able to operate the Hue bulbs via Home Assistant, so I’d like them to be receiving power permanently so I can turn them on remotely.

What is the best solution?

I had a look at the Shelly but I’m unsure whether this would work.

Thanks in advance!

Posts: 2

Participants: 2

Read full topic

@merkelbeek wrote:

Hi Everyone,

I added a wake on lan switch but its not showing up, if i add it into another place it shows up.
I think i am forgeting something at the end of my codes/entities:

#------------------------------------------------------------------------------------------
# WEER VOORSPELLING
#------------------------------------------------------------------------------------------
      - entity: weather.thuis
        theme: Teal
        type: weather-forecast
      - detail: 2
        entity: sensor.buienalarm_precipitation
        graph: line
        hours_to_show: 2
        name: Buienalarm
        theme: Teal
        type: sensor
      - platform:
#------------------------------------------------------------------------------------------
# Wake on Lan
# ------------------------------------------------------------------------------------------
      - entity: switch.donny_pc
        type: entities
        title: Wake on Lan
        show_header_toggle: false
        entities:
          - entity: switch.donny_pc
            name: Donny PC
#------------------------------------------------------------------------------------------
# Yeelight - Game Kamer
#------------------------------------------------------------------------------------------
        type: custom:light-entity-card
        entity: light.game_kamer
        show_slider_percent: true
        smooth_color_wheel: true
        effects_list: true
        full_width_sliders: true
#------------------------------------------------------------------------------------------

This is my whole lovelace config:

title: Thuis
#----------------------------------------------------------------------------------------
background: url("/local/background3.jpg")
#----------------------------------------------------------------------------------------
resources:
  - url: /community_plugin/compact-custom-header/compact-custom-header.js
    type: module
  - url: /community_plugin/decluttering-card/decluttering-card.js
    type: module
  - url: /community_plugin/calendar-card/calendar-card.js
    type: js
  - url: /community_plugin/light-entity-card/light-entity-card.js
    type: js
  - url: /community_plugin/lovelace-gui-sandbox/gui-sandbox.js
    type: module
  - url: /community_plugin/garbage-collection-card/garbage-collection-card.js
    type: module
  - url: /community_plugin/lovelace-github-entity-row/github-entity-row.js
    type: js
  - url: /community_plugin/banner-card/banner-card.js
    type: module
  - url: /community_plugin/vertical-stack-in-card/vertical-stack-in-card.js
    type: js
  - url: /community_plugin/light-entity-card/light-entity-card.js
    type: js
views:
#------------------------------------------------------------------------------------------
  - badges:
      - entity: person.donny
    cards:
#------------------------------------------------------------------------------------------
# EDIT GUI MODE
#------------------------------------------------------------------------------------------
#       - entity: editmode
#         type: custom:gui-sandbox
#------------------------------------------------------------------------------------------
# WEER VOORSPELLING
#------------------------------------------------------------------------------------------
      - entity: weather.thuis
        theme: Teal
        type: weather-forecast
      - detail: 2
        entity: sensor.buienalarm_precipitation
        graph: line
        hours_to_show: 2
        name: Buienalarm
        theme: Teal
        type: sensor
      - platform:
#------------------------------------------------------------------------------------------
# Wake on Lan
# ------------------------------------------------------------------------------------------
      - entity: switch.donny_pc
        type: entities
        title: Wake on Lan
        show_header_toggle: false
        entities:
          - entity: switch.donny_pc
            name: Donny PC
#------------------------------------------------------------------------------------------
# Yeelight - Game Kamer
#------------------------------------------------------------------------------------------
        type: custom:light-entity-card
        entity: light.game_kamer
        show_slider_percent: true
        smooth_color_wheel: true
        effects_list: true
        full_width_sliders: true
#------------------------------------------------------------------------------------------
#  TAB 1-----------------------------------------------------------------------------------
#------------------------------------------------------------------------------------------
    icon: 'mdi:shield-home'
    theme: synthwave
    title: Thuis
  - badges: []
    cards:
      - entity: editmode
        type: custom:gui-sandbox
      - platform:

        type: custom:light-entity-card
        entity: light.game_kamer
        show_slider_percent: true
        smooth_color_wheel: true
        effects_list: true
        full_width_sliders: true


    icon: 'mdi:home-floor-2'
    theme: synthwave
    title: Thuis2
#------------------------------------------------------------------------------------------
# Compact Custom Header
#------------------------------------------------------------------------------------------
cch:
  menu: overflow
  header: true
  background: rgba(155, 155, 155, 0.25)
  clock_format: 24
  notifications: Show
  options: clock
  swipe_animate: fade
  swipe_prevent_default: true
  swipe: true

Posts: 1

Participants: 1

Read full topic

@Marco_Simon wrote:

I’m trying to make a picture card with my picture, when @home i want it to be in colour and when away i’d like it to be grayed out.

I’m using the last example of https://www.home-assistant.io/lovelace/picture-glance/
but i only get a error.

’
aspect_ratio: 0%
entities:

• device_tracker.marco_tado_s9
  entity: person.marco_simon
  hold_action:
  action: none
  image: local/marco_kleur.jpg
  state_image:
  afwezig: /local/marco_zwart.jpg
  thuis: /local/marco_kleur.jpg
  tap_action:
  action: none
  title: Marco
  type: picture-glance
  ’

the received error is:
Expected a value of type undefined for state_image but received {"afwezig":"/local/marco_zwart.jpg","thuis":"/local/marco_kleur.jpg"}.

i get the same error when i just copy past the example from the page Image may be NSFW.
Clik here to view.

i also tried the grayscale option

’
type: picture-glance
title: steven
entities: []
image: /local/steven_kleur.jpg
state_filter:
thuis: grayscale(0%);
afwezig: grayscale(100%);
home: grayscale(0%);
away: grayscale(100%);
entity: device_tracker.steven
’

who’s got the solution for me ??

Posts: 1

Participants: 1

Read full topic

@Da9L wrote:

I have some trouble getting some JSON response into a card in my Lovelace

I have the following in my configuration yaml

sensor:
  - platform: rest
    name: totalkredit
    resource: http://cba.today/oilburner/scraping/totalkredit.php    
    json_attributes:
      - OneFive
      - One
      - ZeroFive        
    
sensor:
  - platform: template
    sensors:
      onefive:
        friendly_name: "1.5%"
        entity_id: sensor.totalkredit        
        value_template: "{{ state_attr('sensor.totalkredit', 'OneFive') }}"
      one:
        friendly_name: "1.0%"
        entity_id: sensor.totalkredit        
        value_template: "{{ state_attr('sensor.totalkredit', 'One') }}"
      zerofive:
        friendly_name: "0.5%"
        entity_id: sensor.totalkredit        
        value_template: "{{ state_attr('sensor.totalkredit', 'ZeroFive') }}"

The url in th rest sensor returns the following response:

{"OneFive":"99,1340","One":"94,2230","ZeroFive":"91.8890"}

And when i do not use the template sensor and only have the rest sensor in my config i can get the following from the totalkredit sensor

Image may be NSFW.
Clik here to view.

And as you can see it seems that it does get the attributes, but i just don’t know how to correctly get them out so that i can add them individually to a card Image may be NSFW.
Clik here to view. If i use the above template sensors i get the following

Image may be NSFW.
Clik here to view.

Posts: 3

Participants: 2

Read full topic

@snaiperr wrote:

Dear All, I have the following config:

sensor:
  - platform: mqtt
    state_topic: "home/studio/esp/st"
    value_template: "{{ value_json.dht_t }}"
    name: "dht_t"
    unit_of_measurement: "°C"
    expire_after: 60

switch:
  - platform: mqtt
    command_topic: "home/studio/esp/set/1"
    state_topic: "home/studio/esp/st"
    value_template: "{{ value_json.b1 }}"

as you can see the state_topic is the same for the both devices.
The problem is the following:
when device performed switch action, the device must to reply to the HA a new state, The reply must to include the all sensors data, in other case the state in HA immediately will be changed to the N/A for not received sensors.

In my case, when switch action performed, the electromagnetic noise is very big and device cannot read sensor thus reply does not contain the sensor data.

Example:
Here the standard status/state report from device:
home/studio/esp/st : b'{ "T_0053":25.00,"b1":1,"b2":1,"b3":1,"b4":1,"b5":0,"b6":0,"b7":0,"b8":0,"dht_t":25.70,"dht_h":42.00 }'

Here command to switch:
home/studio/esp/set/5 : b'1'

And in reply is missing dht_t and dht_h parameters:
home/studio/esp/st : b'{ "T_0053":25.00,"b1":1,"b2":1,"b3":1,"b4":1,"b5":1,"b6":0,"b7":0,"b8":0 }'

After 5 seconds in the next status report the dht parameters will be present and value will be propertly displayed.

The problem N1: the extra “N/A” state will be logged
The problem N2: as the parameter "expire_after: 60 " defined, the state N/A should be applied only in two scenarios: 1: time is expired, 2: the state N/A received from the device like
{ "dht_t" : null, "dht_h": none }

Posts: 6

Participants: 2

Read full topic