@HansHassio wrote:

After updating my HA installation to the latest version it keeps on warning “Login attempt or request with invalid authentication from 192.168.2.xxx”, even if the request came from within my local home network.

I know it has something to do with trusted network settings in configuration.yaml but I prefer disabling this warning message completely. Is this possible and if so, can anyone explain me how?

Posts: 1

Participants: 1

Read full topic

@pawelka wrote:

I just integrated HA (my first addon) with SofarSolar KTL-X inverter, maybe it will work with other brands.

All the brands like SofarSolar, Omnik, iGen, Solarman, Hosola, Goodwe, Solax, Ginlong, Samil may used similar protocol, not confirmed.

Result is here:https://github.com/pawelka/hassio-addons and it’s installed as add-on in hass.io and integrates over mqtt.

My WiFi Logger serial number start with 17xxx and it uses v5 protocol which is not public, so all work is reveres engineering of the protocol.

Posts: 1

Participants: 1

Read full topic

@zerg wrote:

Hello ,

Text I have been using for a while HA from hassio image for Raspberry Pi 4. There is RPC shutdown official add-in. I never used it but liked the idea. I have moved to HA installed on docker, so no option to use official add-ins, but I need this functionality. I have Raspberrry Pi4 with 4G RAM with raspbian buster.

Can you please recommend if I can use same functionality ? I am not sure how the official plugin works and how to re-create the functionality on Docker environment . I have seen few topics in the forum, but non of them is referring to the official plugin architecture.

Thank you in advance !

Posts: 1

Participants: 1

Read full topic

@fsa317 wrote:

I’m curious to how people have configured getting notified if something isn’t working in their setup. I have automations that can detect if some systems in my house are down or not updating promptly, however I only see that when I login to my HASS. I used to have html5 notifications setup but that broke at somepoint and before I try to fix it I was curious about how others get notified about the status of their system changing.

Posts: 4

Participants: 2

Read full topic

@Danny9029 wrote:

Hi guys after the restart failed from Hass.io i’ve to try from Putty and it works.To find the issue i’ve controled the log with Putty and find this problem.

s6-svwait: fatal: timed out
[s6-finish] sending all processes the TERM signal.
2020-03-31 19:20:18 INFO (MainThread) [homeassistant.core] async_stop called twice: ignored
s6-svscanctl: fatal: unable to control var/run/s6services: supervisor not listening
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] udev.sh: executing…
[19:20:23] INFO: Update udev information
[cont-init.d] udev.sh: exited 1.
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

Anyone can help me? Because i don’t know what to do to solve this problem.

Posts: 1

Participants: 1

Read full topic

@jorgenn wrote:

Hi I have this “Develco Products A/S EMIZB-132” adapter for reading my energy meter off the type Norwegian AMS.

This is a Zigbee adapter, but doesn’t have an device handler in ZHA. Can any one explain to me how to make one ?

I understand this is some sort off ZHAquirk, I have the information on which zigbee clusters it uses. But I don’t know how to connect this attributes to variables that are displayable in Home assitant in the correcct way.

Posts: 1

Participants: 1

Read full topic

@velkrosmaak wrote:

After a recent upgrade to 107.7 all of my groups have disappeared from the lovelace UI. I found some changes in the changelog about groups, but don’t see how they relate to my setup.

I define groups in groups.yaml manually, and then use those entities in the UI. Are there any other config changes I need to do to make these work? From reading it seems like the manual definition in the groups.yaml file is an old school way of doing it, but I can’t find a way to create groups in the UI.

I read this thread which sounded related despite being for a much older version, but it didn’t help.

image924×227 10.3 KB

Thanks for any help!

Posts: 2

Participants: 2

Read full topic

@Robert_Shaw wrote:

Hi,

So I’ve been trying to work out what I did wrong, but can’t seem to work it out I installed hasos_rpi4-3.12 but there is no has . io tab in home assistant. I first thought I may have just installed home assistant with no has.os, but I retraced my steps and checked my install and it seems to be the correct has . io version.

Being a systems admin I tried to login via ssh(and did) but it is not really a linux system or at least not like what i’ve ever dealt with. I’m starting to think I should just install debian or ubuntu and then has.io and home assist, but I thought the native one would run better.

I’m just trying to work out how to diagnose whats going on.

Posts: 3

Participants: 2

Read full topic

@RYNO wrote:

Hi all, I was attempting to get back into Hassio in my down time with a fresh VM install on EXSI. I seem to be having issuse connecting to tuya and sense power monitor components. From the VM cli I can login with root and then the command “login” I am able to ping external connections like www.google.com and so on. Im not sure whats up, but I did see this in the logs. Have you came accross this error? Let me know what other details you might need.
I removed my info and put in Xs but you can check the config for sense and tuya. Do you think the error below is my issue?
Thanks in advance!

1850×310 17.9 KB

20-03-31 23:21:54 WARNING (MainThread) [supervisor.tasks] Watchdog found a problem with CoreDNS plugin!
20-03-31 23:21:54 ERROR (MainThread) [supervisor.tasks] CoreDNS plugin is in fails state / Reset config
20-03-31 23:21:54 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
20-03-31 23:21:54 INFO (SyncWorker_32) [supervisor.docker.interface] Clean hassio_dns application
20-03-31 23:21:54 INFO (SyncWorker_32) [supervisor.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - 172.30.32.3
20-03-31 23:22:14 WARNING (MainThread) [supervisor.tasks] Watchdog found a problem with CoreDNS plugin!
20-03-31 23:22:14 ERROR (MainThread) [supervisor.tasks] CoreDNS plugin is in fails state / Reset config
20-03-31 23:22:14 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
20-03-31 23:22:14 INFO (SyncWorker_10) [supervisor.docker.interface] Clean hassio_dns application
20-03-31 23:22:14 INFO (SyncWorker_10) [supervisor.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - 172.30.32.3
20-03-31 23:22:34 WARNING (MainThread) [supervisor.tasks] Watchdog found a problem with CoreDNS plugin!
20-03-31 23:22:34 ERROR (MainThread) [supervisor.tasks] CoreDNS plugin is in fails state / Reset config
20-03-31 23:22:34 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
20-03-31 23:22:34 INFO (SyncWorker_10) [supervisor.docker.interface] Clean hassio_dns application
20-03-31 23:22:35 INFO (SyncWorker_10) [supervisor.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - 172.30.32.3
20-03-31 23:22:54 WARNING (MainThread) [supervisor.tasks] Watchdog found a problem with CoreDNS plugin!
20-03-31 23:22:54 ERROR (MainThread) [supervisor.tasks] CoreDNS plugin is in fails state / Reset config
20-03-31 23:22:54 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
20-03-31 23:22:54 INFO (SyncWorker_6) [supervisor.docker.interface] Clean hassio_dns application
20-03-31 23:22:54 INFO (SyncWorker_6) [supervisor.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - 172.30.32.3
20-03-31 23:23:14 WARNING (MainThread) [supervisor.tasks] Watchdog found a problem with CoreDNS plugin!
20-03-31 23:23:14 ERROR (MainThread) [supervisor.tasks] CoreDNS plugin is in fails state / Reset config
20-03-31 23:23:14 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
20-03-31 23:23:14 INFO (SyncWorker_0) [supervisor.docker.interface] Clean hassio_dns application
20-03-31 23:23:14 INFO (SyncWorker_0) [supervisor.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - 172.30.32.3
20-03-31 23:23:34 WARNING (MainThread) [supervisor.tasks] Watchdog found a problem with CoreDNS plugin!
20-03-31 23:23:34 ERROR (MainThread) [supervisor.tasks] CoreDNS plugin is in fails state / Reset config
20-03-31 23:23:34 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
20-03-31 23:23:34 INFO (SyncWorker_18) [supervisor.docker.interface] Clean hassio_dns application
20-03-31 23:23:35 INFO (SyncWorker_18) [supervisor.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - 172.30.32.3
20-03-31 23:23:54 WARNING (MainThread) [supervisor.tasks] Watchdog found a problem with CoreDNS plugin!
20-03-31 23:23:54 ERROR (MainThread) [supervisor.tasks] CoreDNS plugin is in fails state / Reset config
20-03-31 23:23:54 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
20-03-31 23:23:54 INFO (SyncWorker_13) [supervisor.docker.interface] Clean hassio_dns application
20-03-31 23:23:54 INFO (SyncWorker_13) [supervisor.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - 172.30.32.3
20-03-31 23:24:14 WARNING (MainThread) [supervisor.tasks] Watchdog found a problem with CoreDNS plugin!
20-03-31 23:24:14 ERROR (MainThread) [supervisor.tasks] CoreDNS plugin is in fails state / Reset config
20-03-31 23:24:14 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
20-03-31 23:24:14 INFO (SyncWorker_23) [supervisor.docker.interface] Clean hassio_dns application
20-03-31 23:24:15 INFO (SyncWorker_23) [supervisor.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1 - 172.30.32.3

Posts: 4

Participants: 3

Read full topic

@kamacarzi wrote:

Hi All,

I am just wondering if anyone has had success setting up a Kogan SmarterHome™ 5-Stage Air Purifier 3S with H13 Filter via the Tuya app to HA.
I have set up the app and my lights and switches show but not the Air Purifier. I can see the Air Purifier in my Google home so its synced, just not to HA.

Also if possible to get the fan control and the PM2.5 sensor that would be great to automate it.

Thanks All.

Posts: 1

Participants: 1

Read full topic

@dthporro wrote:

Hi! i’ve been reading a lot, and learning a lot, but i’m stuck right now, and a little desperate!

I have home assistant installed on my rpi3b, official mosquitto broker add-on and official zigbee2mqtt add-on. Everything looks fine, log of both add-ons looks ok, pairing zigbee devices seems to be ok (got 3 devices paired already), but i can’t see them on home assistant. I think it’s something related with discovery, but i’ve tried several configurations with no success.

My HA 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

My zigbee2mqtt configuration.yaml

{ “devices”: “devices.yaml”,
“groups”: “groups.yaml”,
“homeassistant”: true,
“permit_join”: false,
“mqtt”: {
“base_topic”: “zigbee2mqtt”,
“server”: “mqtt://core-mosquitto”,
“user”: “HEREIHAVEMYUSER”,
“password”: “HEREIHAVEMYPASSWORD”
},
“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”: {}
}

My MQTT broker config.

logins:

• username: HEREIHAVEMYUSER
  password: HEREIHAVEMYPASSWORD
  anonymous: true
  customize:
  active: true
  folder: mosquitto
  certfile: fullchain.pem
  keyfile: privkey.pem
  require_certificate: false

What am i missing?

Posts: 2

Participants: 2

Read full topic

@el97 wrote:

Hi! I am trying to set up the recently added Minecraft integration. But I can’t connect to any servers outside LAN. For every time I’m trying, i get the following error: Failed to connect to server. Please check the host and port and try again. Also ensure that you are running at least Minecraft version 1.7 on your server.
I have doubled checked that I’m using the right port for every server I’m trying with so that’s not the issue here I think. Is the integration only for LAN servers or am I doing something wrong?

Posts: 3

Participants: 2

Read full topic

@vormsty wrote:

Hello, I try to install the usb module RFXCOM or RFXTRX
I try to une the rfxmngr windows software an was able to receive and send order to my T6 protocol blind.

I connect the usb cable on the Home Assistant linux machine.
I list usb device and find the name of the usb connection is:
device: /dev/serial/by-id/usb-RFXCOM_RFXtrx433XL_DO462ESY-if00-port0

I add the following line in the configuration.yaml file:

rfxtrx:
  device: /dev/serial/by-id/usb-RFXCOM_RFXtrx433XL_DO462ESY-if00-port0
  debug: true
         
cover:
      - platform: rfxtrx
        signal_repetitions: 8
        automatic_add: true

If I use my remote control no device are added in the config file.
I change the usb name by: device: /dev/ttyUSB2 but nothing bette appear.

Can anybody help me to connect the module to home assistant ?

Many thanks for your very appreciated help.

Best regards

Posts: 1

Participants: 1

Read full topic

@ajobbins wrote:

I have a few battery powered Z-Wave devices. I’ve tried monitoring their battery levels to know when they are getting low, but finding they die at random levels. For example, My Aoetec PIR went flat but was still showing batteries at 74%.

The issue really, is that I don’t actually know it’s gone flat, as HA still sees the device per it’s last state. I’ve also had recessed door sensors go flat and I don’t notice until some automation doesn’t fire.

Does anyone have an easy way to detect if a Z-Wave device has not sent an update in X period, which I could then feed into an automation? Devices usually check in once an hour or so (depending on config), but there doesn’t seem to be a built in way to deal with devices that have gone ‘stale’

Posts: 1

Participants: 1

Read full topic

@ianadd wrote:

Is it possible to define a mouse-over event to display user-chosen bits of text.
I want to get a more verbose explanation of what a switch does to appear if I roll my mouse over it - in the same way, for example, that a history graph shows more info if you mouse-over a part of it.
Is this possible?

Posts: 2

Participants: 2

Read full topic

@Dennis_Smith wrote:

Due to lack of time we are looking for a HA expert for a paid job in the Netherlands.

Extent/improve current setup;

For our small office we have a Raspi 4 with zwave.me dongle under docker running HA.With around 5 fibaro dimmers. This is working but is instable.

-this is not a ‘learn on the job assignment’

-work has to be documented with screenshots and uploaded, so the community can also benefit from it.

Goals;

1-Determine if docker still the best solution in this case, possible reinstall

2-Enable putty SSH access

3-Add two fibaro motion sensors to the setup

4-Install and enable 3rd party Sectigo certificate

5-Enable connection to the P1 power meter

6-Enable control of our three Toshiba airco units using IntesisHome

Especially goals 4,5 and 6 are important.

Contact me; info at gourami dot eu, state your price estimation when contacting…

After a face to face meeting in Blaricum, the Netherlands (no handshaking, and with 1.5 distance of course), and signing a NDA, work can be done remotely.

Posts: 1

Participants: 1

Read full topic

@kkangg1 wrote:

I just switch to MariaDB. But after that, all my entities on Homekit Controller have a delay for updating the state. Does anyone know the reason?

I use Homekit Controller to control the aqara gateway, the motion sensor will be triggered in aqara app immediately, but it takes over 20s to respond on HA.

Posts: 2

Participants: 2

Read full topic

@Phobos wrote:

Hey,
im running home assistant on a QNAP TS-453be inside container station, got it running.
However, Im trying to add a conbee2 stick and cant get it to work.
Ive installed deconz also as container, I can access the web interface, however the firmware shows as not connected - meaning, the stick cant be found. I tried mounting the container with both ACM Usb and TTY privileges under advanced settings/devices.

The problem is, im pretty much a linux-newb. I can follow tutorials pretty well and so far ive got several things to work if only I had something to follow…

However this time, i have no idea what to do.

I found the advice to use “sudo usermod -a -G dialout admin”, however I get the response " usermod: group “dialout” does not exist

Soooo. What can I do?

Any help is appreciated!

Thanks in advance

Posts: 1

Participants: 1

Read full topic

@Retroknut wrote:

Edit/TLDR: main problem: all nodes in Zwave2MQTT appears as “dead” after some time. Everything seems to be working up until then, despite some error messages in the log.

Running Rpi 3b+, with Aeotec stick gen 5. Memory card recently fried, so I’m starting over, and was adviced to use Zwave2MQTT.

My z-wave network consist of 19 fibaro dimmers, 4 heatit termostats, 8 aeotec multisensors and some wall plugs, a total of 44 nodes.

I’ve attatched several screenshots of the zwave2mqtt configuration, a screenshot of the log from the zwave2mqtt add-on, and some screenshots from the node list in zwave2mqtt and home assistant.

I followed this tutorial setting it up: ZWAVE2MQTT add-on simple tutorial

As I’ve understood it, the z-wave network config is located on the z-stick, and is what zwave2mqtt is using to populate the list of nodes in the web UI.

1. My first question is how long does it take to fully populate the list after the add-on is started? It seems it takes far longer than it use to when I had all the nodes in home assistant.

2. When the add-on is started/restarted, the process often freezes, and I have to restart the add-on. Then it might populate the entire list of nodes with names. After a restart I can see the list of 44 nodes, but at first it’s empty, then it fills our with either “unknown” or dimmers/multisensor etc. The “unknowns” are later updated to dimmer/multisensors. But like I said, this freezes form time to time. Normally the population process stops half way through.

3. I have been able to control some of the entities from home assistant, like one of the wall plugs. But it is slow. It is as slow/random like it was in home assistant after a reeboot and the z-wave network was starting. Sometimes the command goes through at once, sometimes after 5-6 seconds. Sometimes nothing happens.

4. home assitant is populated, but never with all of the nodes. The most I’ve had is 14 of 18 dimmers. I delete the device_registry and entity_registry after each attemt, and delete the mqtt integration and do a restart of home assitant to start fresh.

5. Several entities are missing from home assitant.

6. So I figure I need to give the add-on time to connect to all nodes and figure out the network. So I leave it for a couple of hours and come back, but then everything has froze, and the nodes/entities are unavailable or unresponsive in home assitant.

7. update: most recent observation: after being away for 15 minutes, I saw the entire list populate with names in zwave2mqtt, but upon refresh the entire list was empty except for the z-stick. (last image). The log still updates with similar lines as shown in other screenshot. Is there some way to export the log somehow?

What am I doing wrong?

zwqve2mqtt config zwave and mqtt875×788 36.9 KB

zwqve2mqtt config gateway808×559 23.8 KB

zwqve2mqtt log start988×885 129 KB

zwqve2mqtt log after some minutes1304×861 290 KB

zwqve2mqtt control panel node list1736×957 41.2 KB

zwqve2mqtt after refresh, all nodes are dead and gone1686×897 13 KB

Posts: 1

Participants: 1

Read full topic

@Jon87 wrote:

Hi there,

I’m having trouble with setting up push notifications which send an image using information from a sensor attribute in the url.

It’s for a image based off a camera event so the image event ID needs to be passed into the url so that the correct image is picked up.

Here’s my automation which doesn’t work;

data:
  image: >-
    http://domain.com/?view=image&eid={{state_attr('sensor.front_garden_alerts',
    'eventid')}}&fid=objdetect
message: 'Motion Detected {{state_attr(''sensor.front_garden_alerts'', ''name'')}}'
title: Motion Detected

No the odd thing is, the message section comes through ok, the attribute is resolved correctly and I get the camera info.
Also, If I change the attribute info in the url to a static eventID I get the picture through with the message.
Also, also, in the developer template if I copy my url there with the sensor attribute in, it resolves correctly and give me the correct url which when I visit, gives me the camera image.

So a lot of things are working as they should be, but I get no image when I have the sensor attribute to resolve the eventID in the url. I don’t get any errors in the logs either.

Anyone done something similar and worked around this?

Thanks for the help!
Jon

Posts: 1

Participants: 1

Read full topic