@tmchow wrote:

I installed the Unifi integration and it added a crazy amount of device tracking entities that are completely useless to me… for example, it’s enumerated device tracker entities for stuff like my network switches and stationary devices like my internet-connected HDMI switcher.

I’ve tried to go into the HA Dashboard through Configuration > Entities and no way to delete these. I get the message:

This entity does not have a unique ID, therefore its settings cannot be managed from the UI.

How can I delete these entities completely? There’s probably 50 of them.

Posts: 1

Participants: 1

Read full topic

@ladaowner wrote:

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

# 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: 192.168.0.21
  discovery: true
  discovery_prefix: homeassistant

In HomeAssistant GUI under dev tools/MQTT I can see loads of devices

Message 214 received on shellies/shellyswitch25-E66DB8/overtemperature at 19:57:
0
QoS: 0 - Retain: false
Message 213 received on shellies/shellyswitch25-E66DB8/temperature_f at 19:57:
137.61
QoS: 0 - Retain: false
Message 212 received on shellies/shellyswitch25-E66DB8/temperature at 19:57:
58.67
QoS: 0 - Retain: false
Message 211 received on shellies/shellyswitch25-E66DB8/input_event/1 at 19:57:
{
    "event": "",
    "event_cnt": 0
}
QoS: 0 - Retain: false
Message 210 received on shellies/shellyswitch25-E66DB8/input/1 at 19:57:
1
QoS: 0 - Retain: false
Message 209 received on shellies/shellyswitch25-E66DB8/input_event/0 at 19:57:
{
    "event": "",
    "event_cnt": 0
}
QoS: 0 - Retain: false
Message 208 received on shellies/shellyswitch25-E66DB8/input/0 at 19:57:
1
QoS: 0 - Retain: false
Message 207 received on shellies/shellyswitch25-E66DB8/relay/1/energy at 19:57:
1049
QoS: 0 - Retain: false
Message 206 received on shellies/shellyswitch25-E66DB8/relay/1/power at 19:57:
0
QoS: 0 - Retain: false
Message 205 received on shellies/shellyswitch25-E66DB8/relay/1 at 19:57:
off
QoS: 0 - Retain: false
Message 204 received on shellies/shellyswitch25-E66DB8/relay/0/energy at 19:57:
429
QoS: 0 - Retain: false
Message 203 received on shellies/shellyswitch25-E66DB8/relay/0/power at 19:57:
0
QoS: 0 - Retain: false
Message 202 received on shellies/shellyswitch25-E66DB8/relay/0 at 19:57:
off
QoS: 0 - Retain: false
Message 201 received on shellies/shellyswitch25-0082FD/overtemperature at 19:57:
0
QoS: 0 - Retain: false
Message 200 received on shellies/shellyswitch25-0082FD/temperature_f at 19:57:
153.05
QoS: 0 - Retain: false
Message 199 received on shellies/shellyswitch25-0082FD/temperature at 19:57:
67.25
QoS: 0 - Retain: false
Message 198 received on shellies/shellyswitch25-0082FD/input_event/1 at 19:57:
{
    "event": "",
    "event_cnt": 0
}
QoS: 0 - Retain: false
Message 197 received on shellies/shellyswitch25-0082FD/input/1 at 19:57:
0
QoS: 0 - Retain: false
Message 196 received on shellies/shellyswitch25-0082FD/input_event/0 at 19:57:
{
    "event": "",
    "event_cnt": 0
}
QoS: 0 - Retain: false
Message 195 received on shellies/shellyswitch25-0082FD/input/0 at 19:57:
0
QoS: 0 - Retain: false
Message 194 received on shellies/shellyswitch25-0082FD/relay/1/energy at 19:57:
23070
QoS: 0 - Retain: false
Message 193 received on shellies/shellyswitch25-0082FD/relay/1/power at 19:57:
38.38
QoS: 0 - Retain: false
Message 192 received on shellies/shellyswitch25-0082FD/relay/1 at 19:57:
on
QoS: 0 - Retain: false
Message 191 received on shellies/shellyswitch25-0082FD/relay/0/energy at 19:57:
5140
QoS: 0 - Retain: false
Message 190 received on shellies/shellyswitch25-0082FD/relay/0/power at 19:57:
0
QoS: 0 - Retain: false
Message 189 received on shellies/shellyswitch25-0082FD/relay/0 at 19:57:
off
QoS: 0 - Retain: false
Message 188 received on shellies/shelly1-2278B2-11/input_event/0 at 19:57:
{
    "event": "",
    "event_cnt": 0
}
QoS: 0 - Retain: false
Message 187 received on shellies/shelly1-2278B2-11/input/0 at 19:57:
0
QoS: 0 - Retain: false
Message 186 received on shellies/shelly1-2278B2-11/relay/0 at 19:57:
off
QoS: 0 - Retain: false
Message 185 received on shellies/shelly1-227CA3/input_event/0 at 19:57:
{
    "event": "",
    "event_cnt": 0
}
QoS: 0 - Retain: false
Message 184 received on shellies/shelly1-227CA3/input/0 at 19:57:
0
QoS: 0 - Retain: false

MQTT explorer can see loads of devices

Screenshot 2020-06-03 at 19.59.49734×806 106 KB

But nothing is discovery in HomeAssistant. I have reset docker, its using the same network as the host? I have re-installed mosquito

Posts: 1

Participants: 1

Read full topic

@olafvs wrote:

Hi,

I’m trying to modify my first card, but I’m a bit confused. Although I think I’ve set everything correct it still does not filter.

I don’t want to see the entity when the state is False. With below code I still see the entity. I checked the state actually is False by changing the operator to ‘==’ and switch between true and false. That part works.

I just can’t find a way to use the ‘!=’ not equal or ‘not in’ It seems like when the editor comes across a equal sign operator it skips the rest.

type: entity-filter
entities:
  - entity: sensor.synology_below_min_remaining_life_sda
state_filter:
  - operator: '!='
  - value: 'False'

Posts: 2

Participants: 2

Read full topic

@SupremeSports wrote:

Hi everyone, I’m getting a bit annoyed by the templates, effect lists, etc. showing up in my cards in lovelace. I don’t mind it gives me the icon_color result, that’s even great, but the template code is useless and irrelevant for anyone else in my house…

Untitled802×616 42.7 KB

Is there a way to hide those as they are not needed information and it gets pretty annoying especially on a cell phone app. It’s also not good for WAF…

Thank you

Posts: 2

Participants: 1

Read full topic

@ced1442 wrote:

Hi,
It seems that the optionnal commit_interval for recorder is not working.
I tried to set it to 10, 30, 50 and my sensor keep publishing every second.
My DB is growing too fast and I don’t know how to slow down it.
Anybody saw this option working ?

Example state changed time recorded:
2020-06-03 20:00:21.234360
2020-06-03 20:00:21.242900
2020-06-03 20:00:21.786608
2020-06-03 20:00:22.675126
2020-06-03 20:00:22.684792
2020-06-03 20:00:23.226622
2020-06-03 20:00:24.023969
2020-06-03 20:00:24.038115
2020-06-03 20:00:24.122900
2020-06-03 20:00:24.132024
2020-06-03 20:00:25.567267

Posts: 1

Participants: 1

Read full topic

@c0revin wrote:

Given the following API return string in XML from MQTT:
<?xml version="1.0" ?><vs><ac>127</ac><cl>211</cl><cl>117</cl><cl>255</cl><cs>0</cs><cs>0</cs><cs>0</cs><ns>0</ns><nr>1</nr><nl>0</nl><nf>1</nf><nd>60</nd><nt>0</nt><fx>0</fx><sx>128</sx><ix>128</ix><fp>0</fp><wv>0</wv><ws>0</ws><ps>0</ps><cy>0</cy><ds>WLED</ds><ss>0</ss></vs>

What would be the proper template to get the value for <fx> ?

Posts: 1

Participants: 1

Read full topic

@Humphaz wrote:

I’m trying to run the Lightwave Proxy service (Lightwave-TRV) but it seems almost impossible to run it through Home Assistant in the flashed Raspberry version.

Any ideas?

If I run AppDaemon, can I use pip3 install xxxx?

I want to install the service so that I can read out the broadcast TRV responses, but without it, I’m stuffed.

I’m startnig to think that installing a developer version might be a much easier way to use than the docker version.

Posts: 1

Participants: 1

Read full topic

@jimford wrote:

I’m having problems setting up a colour Yeelight (model YLDP06YL)

I’ve copied and pasted the recommended lines for Automatic Detection into the configuration.yaml file:

light.yeelight_color2_XXXXXXXXXXXX:
friendly_name: Living Room

But get the following error:
“Setup failed for light.yeelight_color2_XXXXXXXXXXXX: Integration not found.”

Additionally, I get an entry on the Lovelace ‘Living Room’ card, but instead of showing a light switch I get ‘Home’.

I was hoping to get a switch and also sliders to change the brightness and colour!

I’ve no idea where to look now - and a web search shows that several people have had problems in setting up this light but their solutions have not helped me. I could do with some advice, please!
Jim

Posts: 1

Participants: 1

Read full topic

@At3 wrote:

Don’t know if this is the right place to ask.

I’m trying nabu casa to see if itcan make my life easier. Looking good except for 1 thing. My TV and Sonos speakers are “switches” in Google home and not media players. While in HA they are definitely media players. Doesn’t this work or do I need to do something extra?

Posts: 1

Participants: 1

Read full topic

@jdknox wrote:

I’m having a terrible time getting very basic stuff to work in python. For example:

File "color_temp.py", line 22, in calc_color
NameError: name '_inplacevar_' is not defined

All line 22 does is a -= 1, where a is just a float.

I’m being serious. As soon as I changed the line to a = a - 1 the script works. This is unacceptable by even the lowest standards! I also can’t use map, nor starred expressions in function calls. What am I doing wrong?

Posts: 1

Participants: 1

Read full topic

@NMe84 wrote:

I upgraded my NAS and as such moved all my Docker containers over from the old one to the new one. I had no issues whatsoever with Mosquitto and Zigbee2MQTT but I can’t for the life of me seem to get Home Assistant itself running anymore.

Symptoms:

• The Docker container is running and keeps running. Doesn’t crash.
• When I go to the UI in a browser that previously visited it through the old server or with the Android app, it either keeps trying to load for a few minutes followed by “Unable to connect to Home Assistant.” and the retry button, or it shows that screen right away.
• When I go to the UI in a browser that has not previously used it, I get a login screen. When I log in with my actual credentials I get the same error as above, and if I purposefully use bad credentials I get directed back to the login screen to try again, so something seems to be running.
• None of my automations work, so nothing much else seems to be running.

This is my log file:

2020-06-04 01:44:45 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-06-04 01:44:45 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for zigbee2mqtt_networkmap which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-06-04 01:44:47 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for discord_game which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-06-04 01:44:54 ERROR (SyncWorker_6) [homeassistant.components.octoprint] Endpoint: printer Failed to update OctoPrint status. Error: 409 Client Error: CONFLICT for url: http://octopi-cr-x:80/api/printer
2020-06-04 01:44:56 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed client session
2020-06-04 01:44:56 ERROR (MainThread) [homeassistant.core] Error doing job: Unclosed connector
2020-06-04 02:03:40 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from ***.***.***.***

Funnily enough that last line only gets added when I use the correct credentials, actual bad login attempts don’t get logged.

I should probably add that I’m using a reverse proxy for SSL termination, this is my config for that:

http:
  server_host: 127.0.0.1
  use_x_forwarded_for: true
  trusted_proxies: 127.0.0.1
#  base_url: https://sub.domain.tld

I tried it both with and without the base_url option but the result is the same.

In case it helps, this shows my Docker setup:

CONTAINER ID        IMAGE                                 COMMAND                  CREATED             STATUS                 PORTS                                                                                                        NAMES
1805ea6bc601        homeassistant/home-assistant:latest   "/init"                  About an hour ago   Up 40 minutes                                                                                                                       HomeAssistant
8daf0012a85b        koenkk/zigbee2mqtt                    "./run.sh"               3 hours ago         Up 3 hours                                                                                                                          Zigbee2MQTT
264e74fdd0c3        eclipse-mosquitto:latest              "/docker-entrypoint.…"   3 hours ago         Up 3 hours             0.0.0.0:1883->1883/tcp, 0.0.0.0:9001->9001/tcp                                                               Mosquitto

Home Assistant and Zigbee2MQTT both were started with --net=host, which is why the ports section is empty.

Does anyone know what I can do to get past this?

Posts: 1

Participants: 1

Read full topic

@trireme32 wrote:

(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Posts: 1

Participants: 1

Read full topic

@pashdown wrote:

I have a Tasmota sensor with “SensorRetain 1” set. I also have “recorder” set in my configuration.yaml. Every time I restart Home Assistant, the binary_sensor reverts to off, even though it is on.

What am I missing here?

Posts: 1

Participants: 1

Read full topic

@timvancann wrote:

I’m using a template sensor to calculate total energy consumption and production in my house, as well as net energy usage.

Here’s my setup:

sensor:
  - platform: dsmr
    dsmr_version: 5
    port: /dev/ttyUSB0

  - platform: template
    sensors:
      energy_production_total:
        value_template: >
          {{ (states('sensor.energy_production_tarif_1') | float + states('sensor.energy_production_tarif_2') | float) | round(1) }}
        unit_of_measurement: 'kWh'

      energy_consumption_total:
        value_template: >
          {{ (states('sensor.energy_consumption_tarif_1') | float + states('sensor.energy_consumption_tarif_2') | float) | round(1) }}
        unit_of_measurement: 'kWh'

      net_energy:
        value_template: >
          {{ (states('sensor.energy_consumption_total') | float - states('sensor.energy_production_total') | float) | round(1) }}
        unit_of_measurement: 'kWh'

The problem is that energy_consumption_total remains unknown, it also doesn’t show any unit_measurement. The template developer tools can parse the template just fine and calculates it as it should.

Screenshot 2020-06-04 at 08.09.551832×576 99.4 KB

As a result, any derivative sensor using the utility_meter component also fails. I can’t find anything in the logs that indicates a failure in the template. What could be going on here?

Posts: 1

Participants: 1

Read full topic

@dreamzboy wrote:

I’ve been trying to connect to my Home Assistant Android Mobile App with SSL certificate enabled but I couldn’t figure it out. It does; however, work by typing https://mydomain.com:8123 over web browser on both desktop and phone. It’s just the app that couldn’t connect. I have my own DNS service and is using Docker for my setup. I’m getting the following error.

Unable to connect to Home Assistant

Unable to communicate with Home Assistant because of an SSL error. Please ensure your certificate is valid

I’ve tried the following as suggested by other threads:

• Upgraded the Home Assistant app
• Reinstall the app
• Removed all cache data
• Copy the full URL after login in from browsers
• Tried with https://mydomain.com:8123/, https://mydomain.com, https://mydomain.com:8123

Configuration.yaml:

http:
  #base_url: https://kenmain.asuscomm.com:8123   <--- Makes no difference
  base_url: https://kenmain.asuscomm.com  #<--- Same results as above
  ssl_certificate: /config/fullchain.pem
  ssl_key: /config/privkey.pem

Reference threads:

• Issue with new android app
• Mobile App can't connect after enabling SSL
• Cannot connect with local address

My guess would be because the Certificate is Self-Signed (using this method) and so the App cannot access the certificate key. Then again, why did the browser work but not the app?

Posts: 1

Participants: 1

Read full topic

@henrik.klang wrote:

Hi guys,

I am using OpenZWave (beta) integration with the OpenZwave plugin (0.3.0) and a MQTT broker (@Raspberry Pi 4). I would say it works fairly stable except that there’s no control panel YET.

Anyhow. I recently moved my Aeotec ZWave Gen5 stick and I am seriously suspecting that nodes far away from the base unit are not able to communicate with the USB stick anymore.

So I want to execute a heal network command. In lack of a easily installable control panel(?) does anyone know how I can send a heal command to OpenZwave plugin by publishing it to the MQTT broker?

Thank you

/ Henrik

Posts: 1

Participants: 1

Read full topic

@bessarabov wrote:

I need to send data about cpu load, memory and disk usage from windows computer to Home Assistant.

I’ve tried IOTLink, it does exactly what I need, but this soft is unreliable. I’ve tried it with two different computers, at first it works fine, but in some time it stop sending data.

Can you recommend some windows software that can be used to gather metrics from windows computer, that can be send to Home Assistant.

Posts: 2

Participants: 2

Read full topic

@bmistry3 wrote:

I have read few old topics on this subject but still cannot get my AEOTEC USB stick to work on my HA (Home Assistant Core on Docker) on PI CM3+

Could someone please help me, advice on how to resolve

This is my config.

image737×783 29.5 KB

Hers is the OZW Log.
2020-06-04 07:54:52.179 Always, OpenZwave Version 1.4.3469 Starting Up
2020-06-04 07:55:00.819 Info, Setting Up Provided Network Key for Secure Communications
2020-06-04 07:55:00.820 Info, mgr, Added driver for controller /dev/zwave
2020-06-04 07:55:00.820 Info, Opening controller /dev/zwave
2020-06-04 07:55:00.820 Info, Trying to open serial port /dev/zwave (attempt 1)
2020-06-04 07:55:00.821 Info, Serial port /dev/zwave opened (attempt 1)
2020-06-04 07:55:00.823 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-04 07:55:00.823 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-06-04 07:55:00.823 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-06-04 07:55:00.823 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-06-04 07:55:00.824 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-06-04 07:55:00.824 Detail,
2020-06-04 07:55:00.824 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-04 07:55:00.828 Detail, contrlr, Received: 0x01, 0x10, 0x01, 0x15, 0x5a, 0x2d, 0x57, 0x61, 0x76, 0x65, 0x20, 0x34, 0x2e, 0x35, 0x34, 0x00, 0x01, 0x93
2020-06-04 07:55:00.828 Detail,
2020-06-04 07:55:00.828 Info, contrlr, Received reply to FUNC_ID_ZW_GET_VERSION:
2020-06-04 07:55:00.828 Info, contrlr, Static Controller library, version Z-Wave 4.54
2020-06-04 07:55:00.829 Detail, Node045, Expected reply was received
2020-06-04 07:55:00.829 Detail, Node045, Message transaction complete
2020-06-04 07:55:00.829 Detail,
2020-06-04 07:55:00.829 Detail, contrlr, Removing current message
2020-06-04 07:55:00.829 Detail,
2020-06-04 07:55:00.829 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-06-04 07:55:01.829 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-04 07:55:01.830 Detail, contrlr, Removing current message
2020-06-04 07:55:01.830 Detail, contrlr, Notification: Notification - TimeOut
2020-06-04 07:55:01.831 Detail,
2020-06-04 07:55:01.831 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-06-04 07:55:02.333 Warning, WARNING: 500ms passed without reading the rest of the frame…aborting frame read
2020-06-04 07:55:02.333 Warning, WARNING: Out of frame flow! (0x28). Sending NAK.
2020-06-04 07:55:02.334 Warning, WARNING: Out of frame flow! (0x04). Sending NAK.
2020-06-04 07:55:02.339 Detail, contrlr, Received: 0x01, 0x04, 0x01, 0x05, 0x28, 0xd7
2020-06-04 07:55:02.339 Detail,
2020-06-04 07:55:02.339 Info, contrlr, Received reply to FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES:
2020-06-04 07:55:02.339 Info, contrlr, There is no SUC ID Server (SIS) in this network.
2020-06-04 07:55:02.339 Info, contrlr, The PC controller is a primary controller.
2020-06-04 07:55:02.339 Detail, Node215, Expected reply was received
2020-06-04 07:55:02.340 Detail, Node215, Message transaction complete
2020-06-04 07:55:02.340 Detail,
2020-06-04 07:55:02.340 Detail, contrlr, Removing current message
2020-06-04 07:55:02.340 Detail,
2020-06-04 07:55:02.340 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-06-04 07:55:02.341 Detail, Unsolicited message received while waiting for ACK.
2020-06-04 07:55:02.342 Detail, contrlr, Received: 0x01, 0x01, 0x00
2020-06-04 07:55:02.342 Warning, contrlr, WARNING: Checksum incorrect - sending NAK
2020-06-04 07:55:02.343 Warning, WARNING: Out of frame flow! (0x00). Sending NAK.
2020-06-04 07:55:02.343 Warning, WARNING: Out of frame flow! (0x00). Sending NAK.
2020-06-04 07:55:02.345 Detail, Unsolicited message received while waiting for ACK.
2020-06-04 07:55:02.350 Detail, contrlr, Received: 0x01, 0x2b, 0x01, 0x07, 0x01, 0x01, 0x00, 0x86, 0x00, 0x01, 0x00, 0x5a, 0xfe, 0x81, 0xff, 0x88, 0x4f, 0xfb, 0x67, 0x00, 0x00, 0x80, 0x00, 0x00, 0x00, 0x00, 0x60, 0x00, 0x00, 0xfa, 0x88, 0x4f, 0x1f, 0x00, 0x9f, 0x7d, 0xa0, 0x00, 0x80, 0x86, 0x00, 0xe8, 0x73, 0x0e, 0x00
2020-06-04 07:55:02.350 Warning, contrlr, WARNING: Checksum incorrect - sending NAK
2020-06-04 07:55:02.351 Warning, WARNING: Out of frame flow! (0x81). Sending NAK.
2020-06-04 07:55:02.352 Warning, WARNING: Out of frame flow! (0x7d). Sending NAK.
2020-06-04 07:55:02.353 Warning, WARNING: Out of frame flow! (0x00). Sending NAK.
2020-06-04 07:55:02.353 Warning, WARNING: Out of frame flow! (0x00). Sending NAK.
2020-06-04 07:55:03.354 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-04 07:55:03.354 Detail, contrlr, Removing current message
2020-06-04 07:55:03.354 Detail, contrlr, Notification: Notification - TimeOut
2020-06-04 07:55:03.354 Detail,
2020-06-04 07:55:03.355 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-06-04 07:55:13.355 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-04 07:55:13.355 Detail, contrlr, Removing current message
2020-06-04 07:55:13.355 Detail, contrlr, Notification: Notification - TimeOut

Posts: 1

Participants: 1

Read full topic

@powo wrote:

Hi,
1)
I just discovered HA and in three days, I tried HA in Hassio AllInOne version.
All work well, about Z-wave, Zigbee, Hue, Hank, Camera ONVIF, Camera usb with Eyemotion, etc …
https://gyazo.com/5c9044a8da83282eed9b194bb4d81f48
but all Add-ons not work well. For example, Samba. Do not want to start, and when I change the smallest detail in the configuration, when saving it, I am always entitled to the same error.
In this example, i use the defaults sets and mod only the password of NULL to 0000. But when i save … (see the Gyazo for the error received)
https://gyazo.com/8b398b10dc307d0f30b4848b1764f658
In addition, many Add-ons that are supposed to start with a restart do not. As with Samba, SSH does not start.
So I have no way to add Hacs or any other Repositories I need.

So I wanted to try HA by installing it on Raspberry PI OS Buster.
And there, Big surprise !! I don’t have a Supervisor.
So no Add-ons possible.
And ONVIF did not want to settle, despite a first attempt, and the following attempts, always lead to the return to the beginning of the list of choices after having clicked on ONVIF.

I know that in this message, I am in demand on many points at the level of installation and configuration.
In addition, on two of the possible ways of installing HA.
But I wish I could get there in both ways and learn to master them.
Because my objective is to have a version reserved only for HA use (Hassio) and another version, more open to adding other functionalities depending on Raspberry PI OS, while making HA work on it at the same time.

I hope I have been clear enough, and my apologies for my English.
Thanks for your help and don’t hesitate to ask me for other Gyazos just in case.
Powo
P.S:
Both version installed are done on two Raspberry PI 3 B+

Posts: 1

Participants: 1

Read full topic

@pawael wrote:

Hello everybody,

is it possible to configure the default lovelace ui (moving around some objects) but leaving the automatic entity generation active? I created a second page and I hoped the default page with automatic management is still on. Now I have the problem for example that entities won’t be generated automatically. One case are the switches if shelly firmware updates are available. I cannot see them and when I create them manually I will get an “missing entity” error when I start the firmware update.

Thanks in advance

Cheers
Rick

Posts: 1

Participants: 1

Read full topic