@dinth wrote:

Im trying to set up HA to download a PNG image, process it by cropping and use the cropped version within UI.
Ive done this package:

  camera:
  - platform: generic
    name: 'Thinkbroadband monitor uncropped'
    still_image_url: !secret thinkbroadband_url
  - platform: proxy
    name: 'Thinkbroadband monitor'
    entity_id: camera.thinkbroadband_monitor_uncropped
    mode: crop
    image_top: 85
    image_left: 85
    max_image_width: 628
    max_image_height: 208

Unfortunately it doesnt work - the image doesnt get cropped and both camera.thinkbroadband_monitor_uncropped and camera.thinkbroadband_monitor entities contain same image.
What am i doing wrong here?

Posts: 1

Participants: 1

Read full topic

@redflag237 wrote:

Good Morning,
I’ve got a question regarding Tasmota (Option 19 Autodiscovery: On) and Autodiscovery with Home Assistant. My Tasmota is latest Release 8.2.0 from March. Home-Assistant is 0.108.3. The Device is a ESP-01 with Binary Switch (ON/OFF) on GPIO0, configured as “Switch 1(9)”. There is another Temperature Sensor, DS18b20, on GPIO2.

On Home-Assistant side MQTT Connection is configured and running. There are several other Sensors configured on fixed topics. Autodiscovery is enabled. Enabling Autodiscovery Option 19 on Tasmota immadiately shows the device in lovelace. There are two Bullets showing up: In one hand there is the Status Button, that contains RSSI, Built, IP-Address, etc. In other hand there is the Temperature Sensor DS18b20, that shows current temp in lovelace. But the binary switch is not showing up, whatever i try to get it running.

Watching the Console on Tasmota i can see the Pin changes and sending it to telemetry topic. Can anyone help me on that?

Best,
redflag237

Posts: 1

Participants: 1

Read full topic

@joselito1 wrote:

I really love HA with the last updates, it is becoming user friendly. Integration in GUI are perfect, but there is a catch! Sometimes integration fails on reboots, and this is a nightmare, because you can not start HA! This is happening with WLED and ESPHOME, and this should be fixed!!! Sensor/light lose wifi or something and you can not start HA - this take long time to inspect these and you get mad.
Also NETATMO integration failes few times during the day.
Please fix that or enable safe mode for failed integration!
THANK YOU!

Posts: 4

Participants: 3

Read full topic

@phrozenpenguin wrote:

I have just flashed a CC2531 and was going to try using ZHA or Zigbee2Mqtt but am having issues.

I add the ZHA integration, use the USB path /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018E2EBB4-if00 which seems to work (i.e. I can add the device), but then I can’t seem to see how to add a sensor device? The help says " Click on ADD DEVICES to start a scan for new devices." but there is no obvious “Add Devices” button?

Reviewing my log I also get an error, which may be related?

missing tsn from activeEpRsp, maybe not a reply

Can anybody offer me some help or things to check? I am running the latest 108.4 of Home Assistant.

Posts: 1

Participants: 1

Read full topic

@Caddyblack wrote:

Hi,
I probably did not configure my DSMR reader correct because I do not get data in HA.

image1119×661 74.6 KB

The DSMR reader does send messages (the queue is filled when I reboot my HA / MQTT server.
When it is back online the queue of messages in DSMR is emptied again.
The mosquitto MQTT logging shows connection:

image1014×644 32.9 KB

DSMR reader config:

image887×897 57.1 KB

What can be wrong? How can I debug this issue?

Posts: 1

Participants: 1

Read full topic

@dinth wrote:

Hey. Ive got a couple of question regarding history and recorder components, as i would like to keep my new HA instance clean and performing well.

1. Some integrations are creating their own sensors, for example 17track. Because new sensors are constantly being created and old sensors removed, i cannot exclude those from history/recorder one by one.
   Is there any way of excluding sensors from recorder using a wildcard, like sensor.seventeentrack_* ?

2. Is it possible to exclude sensors from recorder from a package? For example by adding recorder: to packages/package.yaml ?

Posts: 1

Participants: 1

Read full topic

@ramiroasl wrote:

Hi all,

I’ve been playing with the open/close IKEA Tradfri remotes that come with the FYRTUR and KADRILJ blinds for a while to no avail. The blinds, I’ve managed to pair with ZHA just fine and I’m currently controlling them via scripts issuing commands on their WindowCovering clusters.

Now I’d like to be able to issue commands to HA using the open/close controllers as well. I’ve managed to pair them with ZHA but in the Developer Event listener, upon button presses, they issue no event whatsoever. I’ve searched all over for an idea and nobody really seems to be using these 2-button little devices, but the 5-button one.
Am I doing something wrong or is it that these fellas are not supported yet?

Log on device pairing - stripped some parts as they were being detected as link

[0x0000:zdo] ZDO request 0x0036: [60, <Bool.false: 0>]
…
[0x7744] Discovering endpoints
…
[0x7744] Discovered endpoints: [1]
…
[0x7744:1] Manufacturer: KE
[0x7744:1] Model: TRADFRI open/close remote
Checking quirks for KE TRADFRI open/close remote (08:6b:d7:ff:fe:20:17:5e)
Considering <class ‘bellows.zigbee.application.EZSPCoordinator’>
Fail because device_type mismatch on at least one endpoint
Considering <class ‘zhaquirks.gledopto.soposhgu10.SoposhGU10’>
Fail because endpoint list mismatch: {11, 13} {1}
Considering <class ‘zhaquirks.lutron.lzl4bwhl01remote.LutronLZL4BWHL01Remote2’>
Fail because profile_id mismatch on at least one endpoint
Considering <class ‘zhaquirks.netvox.z308e3ed.Z308E3ED’>
Fail because device_type mismatch on at least one endpoint
Considering <class ‘zhaquirks.osram.a19twhite.A19TunableWhite’>
Fail because endpoint list mismatch: {3} {1}
Considering <class ‘zhaquirks.philips.rom001.PhilipsROM001’>
Fail because device_type mismatch on at least one endpoint
Considering <class ‘zhaquirks.philips.rwl021.PhilipsRWL021’>
Fail because endpoint list mismatch: {1, 2} {1}
Considering <class ‘zhaquirks.smartthings.multi.SmartthingsMultiPurposeSensor’>
Fail because device_type mismatch on at least one endpoint
Considering <class ‘zhaquirks.smartthings.tag_v4.SmartThingsTagV4’>
Fail because device_type mismatch on at least one endpoint
Considering <class ‘zhaquirks.xbee.xbee3_io.XBee3Sensor’>
Fail because endpoint list mismatch: {232, 230} {1}
Considering <class ‘zhaquirks.xbee.xbee_io.XBeeSensor’>
Fail because endpoint list mismatch: {232, 230} {1}
Considering <class ‘zhaquirks.xiaomi.mija.smoke.MijiaHoneywellSmokeDetectorSensor’>
Fail because device_type mismatch on at least one endpoint
device - 0x7744:08:6b:d7:ff:fe:20:17:5e entering async_device_initialized - is_new_join: True
device - 0x7744:08:6b:d7:ff:fe:20:17:5e has joined the ZHA zigbee network
[0x7744](TRADFRI open/close remote): started configuration
…
[0x7744](TRADFRI open/close remote): completed initialization

Any help is appreciated!
Chees!

Posts: 1

Participants: 1

Read full topic

@sebk-666 wrote:

Hi,

since the dawn of time, I have configured my hue bridge manually through configuration.yaml:

hue:
  bridges:
    - host: 192.168.x.y
      allow_unreachable: true
      allow_hue_groups: true

Completely ignoring that, the Lovelace UI since a while is always reminding me that it discovered a hue bridge and asks me to configure it.

Also having

discovery:
  ignore:
    - philips_hue

in my config doesn’t seem to do anything.

Anyway, I’m willing to remove my manual config and switch to the discovery mechanism instead, but I’m unsure if that would break stuff.
Will I need to re-authenticate to the bridge (i.e. press the button) or can I use my existing “account”?
Will all the devices that are currently associated with the bridge be discovered again and get new entity names (i.e. will light.hallway be rediscovered as light.hallway_1, forcing me to update all my automations)?

Has anyone switched from “manual” to “automatic” discovery yet and coud shed some light on the experience?

Sebastian

Posts: 1

Participants: 1

Read full topic

@a.palumbox wrote:

when i try to connect to API in this way:
http://192.168.1.XX:8123/api/states/light.camera_da_letto_luce_1_170
i received an error:

401: Unauthorized
why?

Thanks

Posts: 2

Participants: 2

Read full topic

@Cykelpump wrote:

Hey,

I’m running Hassio in docker on a linux machine. I have installed the Zwave2mqtt add-on after getting tired of my zwave network crash every-time i restarted HA.

My zwave network is very smal, I’m running a Aeotec Z-stick gen5 and Aeotec HEM gen5 (Home Energy Meter).

Since the installation of the add-on everything have worked perfectly until last week when my host machine froze after 280days uptime.

After that the HEM had reset the total consumption value and started counting from zero.
In my head the HEM should not be affected by a reboot of the host machine ?

Now i have updated Hassio to 0.108.4 and zwave2mqtt to 0.5.0 (latest).
After that it seemed fine for a while, iv got some values reported to HA, but i missed a lot of sensors.

After a restart of the addon, trying to fix the issues, the HEM status is Dead…
I have tried to everything but i cant get it to work now.

zwave network seems to be very unstable, or am i doing something wrong ?

/Anton

Posts: 1

Participants: 1

Read full topic

@PorreKaj wrote:

Hi,

HACS is really convenient, but every time i install or update a component, there’s a risk that exactly 15 minutes is added to the boot time of HA (I’m guessing waiting for a timeout?). The only solution I’ve found is to uninstall HACS, remove all custom components, install it all again at hope it doesn’t happen this time.

The last line in the log while the 15 minutes passes is.

2020-04-15 12:39:33 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.hacs

Does anyone know of a another solution that may be a bit less time consuming?

Posts: 1

Participants: 1

Read full topic

@Dayve67 wrote:

I have been noticing that the addon is saying it should be upgraded when I open it. Also in the log files it says the same. The main install page does not show it needing the upgrade.

How do I go about upgrading the addon?

image613×524 38.8 KB

---

Hass.io Add-on: Visual Studio Code
Fully featured VSCode experience, to edit your HA config in the browser, including auto-completion!

Add-on version: 2.1.0
There is an update available for this add-on!
Latest add-on version: null
Please consider upgrading as soon as possible.
System: Ubuntu 18.04.4 LTS (amd64 / qemux86-64)
Home Assistant Core: 0.108.3
Home Assistant Supervisor: 217

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

And if I try to upgrade in Visual Studio I get this error:

Posts: 1

Participants: 1

Read full topic

@liamp wrote:

Here are my settings in configuration.yaml

vacuum:
  - platform: xiaomi_miio
    host: my ip
    token: my vacuum's token 

That part is working fine and I see the entity vacuum.xiaomi_vacuum_cleaner

I followed this guide

and added this to configuration.yaml

switch:
  - platform: template
    switches:
      vacuum:
        value_template: "{{ is_state('vacuum.xiaomi_vacuum_cleaner', 'on') }}"
        turn_on:
          service: vacuum.turn_on
          data:
            entity_id: vacuum.xiaomi_vacuum_cleaner
        turn_off:
          service: vacuum.return_to_base
          data:
            entity_id: vacuum.xiaomi_vacuum_cleaner

            
find_vacuum:
  alias: Find Vacuum
  sequence: 
    - service: vacuum.locate
      entity_id:
      - vacuum.xiaomi_vacuum_cleaner

I get an error
Component error: find_vacuum - Integration ‘find_vacuum’ not found.

But the big problem is when I tell Alexa to search for new devices it doesn’t find my vacuum.

Is there something I am missing?

Thank you for any help.

Posts: 1

Participants: 1

Read full topic

@mrkrabs wrote:

Hi, i am trying to use a scrape sensor to get the content of the <meta> tag in the website. the code on the site reads:

<meta property="product:availability" content="in stock">

how do i get the content part using the scrape sensor? i have tried this, and it doesn’t work:

select: "meta [property=product:availability]"

is this even possible with the scrape sensor? thanks in advance!

Posts: 1

Participants: 1

Read full topic

@Mariusthvdb wrote:

New entities are being created for the dimmer and tap switches. Next to the ones created by the Custom integration, I now see new battery_level sensors for my physical tap and dimmer switches.

I can see the latter in the entities overview, but no entity is found for the switches them selves? How than could they be displayed in the frontend? @azogue could you point me to them?

Schermafbeelding 2020-04-15 om 17.51.382036×1172 159 KB

they are visible in the devices:

Schermafbeelding 2020-04-15 om 17.55.212444×554 24.4 KB

I wonder how we can create automations on the clicks of these new entities, if we cant read the click (state) of them. The custom integration is very clear on that, do hope we are not solely allowed to do so in the device UI editor?
thanks for having a look!

Posts: 1

Participants: 1

Read full topic

@helfm wrote:

Dear colleagues,

has anyone already integrated the Switch Actuator “HmIP-FSI16” from HomeMaticIP in his hassio environment?

The switch can be easily integrated into the HomeMatic CCU. RaspberryMatic CCU version 3.51.6.20200229, but then it will not be integrated in my hassio system.
All previous components of HomeMatic can be integrated without any problems (Shutter Actuator etc.)

I don’t know if more information about my question is needed, I would be happy about answers.

With thanks in advance
help

Posts: 1

Participants: 1

Read full topic

@Christophe_Beaucourt wrote:

Hi all,

I have added a new sensor (using template).

When my HA received a new specific email (imap integration works fine with HA) from a provider, I set the sensor value to “PersonInside”. This email contains the alarm sensor that just switch to “PersonInside” state.

Unfortunnetly, the alarm system is not able to send “NoPersonInside” state later…

So, I would like to set the state “NoPersonInside” after 3 ou 5 minutes for example.

Can you provide me the “setState” piece of code ? I’m not able to find an automation service to set the value of a sensor.

The sensor is defined as follow with the value “PersonInside” defined when an email is received :

presence_couloir:
friendly_name: “Présence Couloir”
value_template: >
{% if state_attr(‘sensor.tahoma_mail’, ‘body’)
| replace (’\n’,’’) | replace (’"’,’’) | replace ("=","")
| regex_match (‘TaHoma alerte : .*, votre condition Pr Couloir’, ignorecase=FALSE) %}
PersonInside
{% endif %}

I know that is possible to trigger a change in automation after a specific period of time, but my problem is that I don’t have the line to set the state of “presence_couloir” to “NoPersonInside”.

Many thanks for your help.

Christophe

Posts: 1

Participants: 1

Read full topic

@Da9L wrote:

How do i add that? It seems that it is possible, but it isn’t showing when i go to the switch pane and select add. Only those two are shown

deconz1116×779 41 KB

Posts: 1

Participants: 1

Read full topic

@ob2s wrote:

I am just trying to create a card with an entity(?) that has an on off button for a simple esp8266 relay. The URLs are http://relay/?S=On and http://relay/?S=Off Both return
{ “POWER” : “ON”} or { “POWER” : “OFF”}. I was able to hack my way through to create a circular widget on the dashboard that shows status via the Rest Sensor (http://relay/status) which has the same json returned as above.

I am struggling with translating this rest switch example into on-off control of my esp8266. I don’t want to use the esp8266 integration, it is over my head, though I can write code for esp8266, etc.

switch:
  - platform: rest
    resource: http://relay/?S=
    body_on: '{"POWER": "ON"}'
    body_off: '{"POWER": "OFF"}'
    is_on_template: '{{ value_json.POWER }}'
    headers:
      Content-Type: application/json

I know I am missing something, also will I see the ‘switch’ as an entity that I can add to a card once I have it correct ? I have looked at many videos and web pages and it just eludes me.
Thanks

Posts: 2

Participants: 2

Read full topic

@honikos wrote:

Hi there !
Some changes in mqtt sensor auto-detection made my homeassistant losing the state of a binary sensor (reed switch on sonoff-basic, GPIO 14) after hass restarts. When restarting hass, the sensors status is always OFF ( garage door open), even if the real sonoff-sensor is ON (garage door closed). Test on sonoff- Tasmota CLI;

19:07:00 MQT: stat/sonoff-garage-1/STATUS10 = {“StatusSNS”:{“Time”:“2020-04-15T19:07:00”,“Switch1”:“ON”}}

Perfect. I tried 2 solutions. Mqtt - platform and template-platform. Both work well, but both don’t recognize the real sensor state after reboot.

Do I have any chance to fetch the state for homeassistant. Is there a command to achieve this? (mqtt ?)
Unfortunately the mqtt teleperiod delivers the right sensor state every 5 minutes.

19:11:48 MQT: tele/sonoff-garage-1/SENSOR = {“Time”:“2020-04-15T19:11:48”,“Switch1”:“ON”}

But as I mentioned at the beginning, hass doesn’t take notice anymore.

Maybe I can save the last state somewhere. Tried a lot (rules, mqtt commands …)

Thanks
Horst

Posts: 2

Participants: 2

Read full topic