@denham wrote:

Does anyone how I can get make a sensor from the device info? In the screenshot below I’d like to get the firmware version as a sensor, so I can make a notification when there is a new firmware version on Github.

Posts: 1

Participants: 1

Read full topic

@Gamester17 wrote:

Sonoff ZBBridge by by ITead is a new new Sonoff branded Zigbee Bridge / Gateway/Hub

It contains an ESP8266 WiFi MCU/SoC and a very powerful Silicon Labs MCU/SoC with Zigbee 3.0 radio combo, so could possible run Tasmota on it and either use the Zigbee chip directly or act as a pass-through adapter bridge to third-party software like Zigbee2mqtt or ZHA / Zigpy / Bellows

It’s very early days however I think that will be interesting to follow development of that hacking effort.

The MCU with Zigbee radio inside it is based on EFR32MG21 (EFR32 Mighty Gecko) from Silicon Labs.

Posts: 1

Participants: 1

Read full topic

@kjelle392 wrote:

Sorry guys if I post this in the wrong category, but now I’m stuck.

After running HA flawlessly a long time, I upgraded the system today (new system upgrade). After upgrading, I noticed that I couldn’t access HA anymore. Nor, did it show up in the network.

After work, I connected my Pi to the TV to see what is happening during bootup. Everything seems normal until this message comes:

A start job is running for wait Until Kernel Time Synchronized (1 min 48s /no limit).

The boot never gets beyond this point. What do I do now?

Posts: 1

Participants: 1

Read full topic

@rednas wrote:

I have these errors in Lovelace:
Custom element doesn't exist: mini-graph-card.
Custom element doesn't exist: simple-thermostat.

Both are installed using HACS. I just updated HA to see whether this would fix these errors, but they remain.
What am I doing wrong?

Posts: 1

Participants: 1

Read full topic

@juan wrote:

HI.

I have a new problem with my Z-Wave Controller. Since the last update, I have this issue:

2020-06-02 03:27:39.441 Always, OpenZwave Version 1.4.3469 Starting Up
2020-06-02 03:27:57.636 Info, Setting Up Provided Network Key for Secure Communications
2020-06-02 03:27:57.636 Info, mgr,     Added driver for controller /dev/ttyAMA0
2020-06-02 03:27:57.636 Info,   Opening controller /dev/ttyAMA0
2020-06-02 03:27:57.637 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2020-06-02 03:27:57.638 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2020-06-02 03:27:57.639 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-02 03:27:57.639 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-06-02 03:27:57.639 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-06-02 03:27:57.639 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-06-02 03:27:57.639 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-06-02 03:27:57.639 Detail,
2020-06-02 03:27:57.639 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-02 03:27:57.639 Detail, contrlr, Notification: DriverFailed

System: HassOS 4.8
Supervisor: 225

What is happening? I’ve never had a problem with my Razberry controller

Posts: 1

Participants: 1

Read full topic

@chris-mac wrote:

Hi, I would greatly appreciate if someone could clarify for me the below (in HA v. 0.110.4):

1. In most of HA documentation there are references to YAML configuration files, for example MQTT docs here

2. Yet, when in my HA GUI I went to Configuration -> Integrations and added MQTT the only place where I was able to find reference to my MQTT broker is .storage/core.config_entries The file configuration.yaml remains unchanged and there is no new key mqtt present.

Why is that? Does YAML applies only when one configures HA by editing config files? And .storage/core.config_entries JSON file is being used when configuration is done via Web UI ? Does one format has precedence over another?

What will happen if I already have mqtt settings in .storage/core.config_entries and I will add it to configuration.yaml ? which one will take priority over another?

Any pointers to docs explaining the above much appreciated.

Best regards,
Chris

Posts: 2

Participants: 2

Read full topic

@klogg wrote:

I have a template sensor for which I cannot get the picture to display even though the attribute appears correct.
I have tried using a picture used in another template that does work so it can’t be the actual picture itself.

What can be going on to stop it showing?

Sensor that doesn’t show its picture:

image966×118 5.88 KB

Sensor that does show its picture:

image932×196 7.28 KB

---

Just in case, here are the picture details:

113.png

Bakerloo_roundel_outline.png

Posts: 1

Participants: 1

Read full topic

@jasin81 wrote:

I have roughly 14 NuTone In-wall Zwave switches throughout my house that I’m looking at replacing slowly over time. These switches aren’t Zwave+ and do not send status updates when manually turned on/off, so unless I setup polling or use them on SmartThings, they show inconsistent states. I have a Pi running zigbee deCONZ and zwave2mqtt, so all options are possible. I would like local control (reason for ditching smartthings) and MQTT is a plus. Here’s a list of options:

1. Replace with Inovelli ZWave switches (https://www.amazon.com/dp/B07T2416D8/ref=cm_sw_em_r_mt_dp_U_JnN1EbMTJAHW4) - Currently have one and it works great.

2. Replace with Enbrighten Zigbee In-wall switch (https://www.amazon.com/dp/B08428GHM8/ref=cm_sw_em_r_mt_dp_U_vkN1EbD7N5VH5) - New product and not sure if it works with deCONZ.

3. Put back original switches and use Shelly 1 modules (UL Version?)

4. Put back original switches and use Sonoff Mini modules flashed w/ Tasmota

I have a couple Sonoff Mini’s I use for cabinet lighting which I like. However, the Shelly 1 UL rated modules look intriguing and would like to try them out. My only concern is having too many Wifi devices. I have 3 ubiquiti access points spread out, but like the idea of low frequency zwave/zigbee. Just want some opinions…I’m leaning towards the Sonoff/Shelly due to costs, but I may buy one of those zigbee switches to play around with. Some of the electrical boxes are already pretty full so I’m not sure adding the Shelly/mini would be possible everywhere, which is fine. What would you do?

Posts: 1

Participants: 1

Read full topic

@emerout wrote:

Hello,

I’m brand new to Home Assistant, coming from jeedom.

I have setup HA on a k8s cluster : https://github.com/helm/charts/tree/master/stable/home-assistant

I’m trying to configure RFLink and devices.

The configuration :

# 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

rflink:
  host: 192.168.1.13
  port: 1234
  
sensor:
  - platform: rflink

logger:
  default: error
  logs:
    rflink: debug
    homeassistant.components.rflink: debug

data is received from RFLink gateway but devices are never added to the UI.

The log:

INFO (MainThread) [homeassistant.components.rflink] Initiating Rflink connection                                                              
DEBUG (MainThread) [rflink.protocol] connected
INFO (MainThread) [homeassistant.components.rflink] Connected to Rflink                                                                       
DEBUG (MainThread) [rflink.protocol] received data: 20;00;Nodo RadioFrequencyLink - RFLink Gateway V1.1 - R46;
DEBUG (MainThread) [rflink.protocol] received data: 20;01;Auriol V3;ID=0C01;TEMP=00e2;HUM=62;                                                 
DEBUG (MainThread) [rflink.protocol] received data:
DEBUG (MainThread) [rflink.protocol] received data: 20;02;Auriol V3;ID=0C01;TEMP=00df;HUM=62;                                                 
DEBUG (MainThread) [rflink.protocol] received data:
DEBUG (MainThread) [rflink.protocol] received data: 20;03;Auriol V3;ID=0C01;TEMP=00df;HUM=62;                                                 
...

Any help appreciated !

Posts: 1

Participants: 1

Read full topic

@Hellis81 wrote:

I want an automation that triggers when I switch source on the receiver.
When you switch between two sources it’s not uncommon that the volume is too high for the source you switch too.

What can I do to trigger on the attribute source change?

  trigger:
  - platform: template
    value_template: '{{ states.media_player.yamaha_receiver.attributes.source }}'
  condition:
  - condition: state
    entity_id: media_player.yamaha_receiver
    state: 'On'
  - condition: template
    value_template: '{{ states.media_player.yamaha_receiver.attributes.volume_level
      > 0.72 }}'
  action:
  - data:
      volume_level: 0.65
    entity_id: media_player.yamaha_receiver
    service: media_player.volume_set

The attribute source has the following options so making one automation per change is not really ideal:
source_list: AUDIO, AV1, AV2, AV3, AV4, AV5, AV6, AirPlay, HDMI1, HDMI2, HDMI3, HDMI4, NET RADIO, SERVER, TUNER, USB, V-AUX, iPod (USB)

Posts: 2

Participants: 2

Read full topic

@membersound wrote:

I want to trigger an automation based on an attribute that is not always present.
In the following example, the rain attribute might be missing, or is present and numeric.

How can add a check to the condition that it should only trigger if “rain is present” and “rain > 2”?

condition:
  - above: '2'
    condition: numeric_state
    value_template: '{{ state_attr("sensor.my_weather", "rain") }}'

Posts: 1

Participants: 1

Read full topic

@Makis wrote:

I just noticed a strange bug with my LG TV but not sure if it is only me or not. I am on version 0.110.4
When I restart HA it is working ok and in Live source displays the channel is playing (Star - in the following pic) After sometime it won’t display it. it is just blank.
Right now, I have no logs because I restarted HA. will report back when it happens again.
Anybody else with this issue?

Posts: 1

Participants: 1

Read full topic

@IOIIOOO wrote:

I have two workshop hanging lights controlled by MQTT wifi smart plugs. These are grouped together currently.

group:
  workshop_lights:
    name:  Workshop Lights
    entities:
      - switch.workshop_east_hanging_lights
      - switch.workshop_west_hanging_light
    icon: mdi:ceiling-light

On my dashboard, I have these showing where I can switch them on and off, but I’d also like the icon to change when turned on to be yellow like the “lights” that are on. Is there a way to do this?

Overview_-_Home_Assistant756×746 40.9 KB

Posts: 1

Participants: 1

Read full topic

@chris-mac wrote:

Hi, I am running Home Assistant 0.110.4 on Raspberry PI 4 installed in Python virtual env. Got Aeotec WallMote Quad added as a Device using OpenZWave along with Aeotec Switch 7.

Got simple automation setup where WallMote button is toggling Aeotec Switch 7 state (and turning desk lamp on/off). The problem is when toggling from off -> on state it is pretty instant (1-2 sec.) but often (70% of cases) toggling from on -> off state take a long time, up to 10 sec. See relevant logs below:

WallMote button pressed:

2020-06-02 19:49:40 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on OpenZWave/1/node/27/instance/1/commandclass/91/value/281475435380756/: b'{
    "Label": "Scene 1",
    "Value": {
        "List": [
            {
                "Value": 0,
                "Label": "Inactive"
            },
            {
                "Value": 1,
                "Label": "Pressed 1 Time"
            },
            {
                "Value": 2,
                "Label": "Key Released"
            },
            {
                "Value": 3,
                "Label": "Key Held down"
            }
        ],
        "Selected": "Pressed 1 Time",
        "Selected_id": 1
    },
    "Units": "",
    "ValueSet": false,
    "ValuePolled": false,
    "ChangeVerified": false,
    "Min": 0,
    "Max": 0,
    "Type": "List",
    "Instance": 1,
    "CommandClass": "COMMAND_CLASS_CENTRAL_SCENE",
    "Index": 1,
    "Node": 27,
    "Genre": "User",
    "Help": "",
    "ValueIDKey": 281475435380756,
    "ReadOnly": false,
    "WriteOnly": false,
    "Event": "valueChanged",
    "TimeStamp": 1591123780
}'

triggers automation:

2020-06-02 19:49:40 INFO (SyncWorker_14) [custom_components.hello_mqtt] Received message VALUE: ["Pressed 1 Time"]
2020-06-02 19:49:40 INFO (MainThread) [homeassistant.components.automation] Executing Office Light Toggle
2020-06-02 19:49:40 INFO (MainThread) [homeassistant.components.automation] Office Light Toggle: Running script
2020-06-02 19:49:40 INFO (MainThread) [homeassistant.components.automation] Office Light Toggle: Executing step device automation

which sends MQTT message to the Switch:

2020-06-02 19:49:40 DEBUG (MainThread) [homeassistant.components.mqtt] Transmitting message on OpenZWave/1/command/setvalue/: {"ValueIDKey": 441008144, "Value": false}
2020-06-02 19:49:40 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on OpenZWave/1/command/setvalue/: b'{"ValueIDKey": 441008144, "Value": false}'
2020-06-02 19:49:41 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on OpenZWave/1/event/setvalue/: b'{\n    "status": "ok",\n    "TimeStamp": 1591123781\n}'

so far, so good, we are under 1 sec. but the actual switch state (and my desk lamp) changes 8 seconds later:

2020-06-02 19:49:49 DEBUG (MainThread) [homeassistant.components.mqtt] Received message on OpenZWave/1/node/26/instance/1/commandclass/37/value/441008144/: b'{
    "Label": "Switch",
    "Value": false,
    "Units": "",
    "ValueSet": false,
    "ValuePolled": false,
    "ChangeVerified": false,
    "Min": 0,
    "Max": 0,
    "Type": "Bool",
    "Instance": 1,
    "CommandClass": "COMMAND_CLASS_SWITCH_BINARY",
    "Index": 0,
    "Node": 26,
    "Genre": "User",
    "Help": "Turn On/Off Device",
    "ValueIDKey": 441008144,
    "ReadOnly": false,
    "WriteOnly": false,
    "Event": "valueChanged",
    "TimeStamp": 1591123789
}'

All devices (PI, USB Stick, WallMote button and Switch 7 are on my desk within 2m radius).

Would anyone have an idea how to troubleshoot and fix this ?

Best regards,
Chris

Posts: 1

Participants: 1

Read full topic

@evilmouse wrote:

Hi,

I am trying to get Emulated Hue to work within my Alexa app but I am unable to see any new devices when scanning.

I am trying with a single device to see if it works ( I know there are possible issues when over 50 devices )

emulated_hue:
  host_ip: 192.168.0.252
  listen_port: 80
  expose_by_default: false
  entities:
    switch.fibaro_system_fgs213_switch_switch_2:
      name: "Ceiling Fan"
      hidden: false

I can confirm port 80 is open on HA and is assessable from a computer on the network.

Daniels-MacBook-Pro:~ daniel$ nc -vz 192.168.0.252 80
Connection to 192.168.0.252 port 80 [tcp/http] succeeded!
Daniels-MacBook-Pro:~ daniel$ 

http://192.168.0.252/description.xml returns the following

<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.0.252:80/</URLBase>
<device>
<deviceType>urn:schemas-upnp-org:device:Basic:1</deviceType>
<friendlyName>Home Assistant Bridge (192.168.0.252)</friendlyName>
<manufacturer>Royal Philips Electronics</manufacturer>
<manufacturerURL>http://www.philips.com</manufacturerURL>
<modelDescription>Philips hue Personal Wireless Lighting</modelDescription>
<modelName>Philips hue bridge 2015</modelName>
<modelNumber>BSB002</modelNumber>
<modelURL>http://www.meethue.com</modelURL>
<serialNumber>001788FFFE23BFC2</serialNumber>
<UDN>uuid:2f402f80-da50-11e1-9b23-001788255acc</UDN>
</device>
</root>

http://192.168.0.252/api/pi/lights returns the following

{"32": {"manufacturername": "Home Assistant", "modelid": "HASS123", "name": "Ceiling Fan", "state": {"bri": 254, "mode": "homeautomation", "on": false, "reachable": true}, "swversion": "123", "type": "Dimmable light", "uniqueid": "00:44:8f:fe:78:dc:a8:64-b5"}}

I have tried both “Philips Hue V1 Bridge (Circular shape)” and just the “Other” to scan for devices, both result in the same “No new devices found.” message being shown.

Posts: 1

Participants: 1

Read full topic

@Humphaz wrote:

Hi,

I’m creating a new topic for this and would recommend that many of the old posts be deprecated as they are no longer relevant.

But hey, it still doesn’t work.

I’m using the flashed version for raspberry pi 4b - Version 4.8 (32bit recommended)

If I specify file_path I get this error:

Invalid config for [rpi_camera]: not a file for dictionary value @ data['rpi_camera']['file_path']. Got '/tmp/image.jpg'. (See /config/configuration.yaml, line 45).

These are the relevant lines from the configuration.yaml

45 rpi_camera:
46     name: Office Camera
47     timelapse: 1000
48     file_path: /tmp/image.jpg

If I don’t specify a file_path it does not error, and I get a UI camera, but no content:

image768×180 3.87 KB

I’ve tried every bloody combination, not geting frustrated, only been at it for, 4 hours, so you know.

Any assistance would be greatful!

Posts: 1

Participants: 1

Read full topic

@Zevin_Mars wrote:

Okay, before we start:

• Unraid User
• Running Home Assistant Core installed on Docker
  • v0.110.4
• Using sorccu/ADB docker installed from Docker Hub as my ADB server.

I’ve been trying to set up the Android Fire TV integration through the ADB Server implementation (the python thing didn’t work). I’m having a lot of trouble getting it to work. My ADB server container can connect to my Fire TV 4k fine and I can use the terminal in Unraid to send commands to it (power on/off, open the Plex app, etc.) so that end of things seems to be working as intended. Home Assistant just doesn’t want to send commands to my ADB server?

I used BurnsHA’s Video about the subject as the basis for how I set everything up, (even though I didn’t use Docker compose, just Unraid’s docker container tools). Here’s how my containers are set up.

Home Assistant
Name: Home Assistant Core
Repository: homeassistant/home-assistant
Network Type: Host
Console Shell Command: Shell
Privileged: Off
Config Directory: /mnt/user/appdata/Home-Assistant-Core
ttyACM0: /dev/ttyACM0 (this is my Z-Wave controller)

ADB
Name: adb
Repository: Sorccu/adb
Network Type: Bridge
Console Shell Command: Shell
Privileged: Off
Config Directory: /mnt/user/appdata/adb
Time: /etc/timezone
Local: /etc/localtime
Host Port: 5037

Here’s my config for the Android TV Device:

#Amazon Fire TV 4K
media_player:
  - platform: androidtv
    name: Zack's Fire TV 4K
    host: 192.168.1.23
    adb_server_ip: 192.168.1.17
    adb_server_port: 5037

I realize I could be formatting my commands in Home Assistant wrong. My goal is to be able to use this touch interface on my tablet to control my media devices (video source switchers, HDTV, etc) and I want to be able to press the app icons at the bottom and have the Fire TV open the app (yeah I know HBO Max isn’t on Firestick’s yet, I’m future proofing.)

I tried using the media_player.select_source service but I know there is also an androidtv.adb_command service. Does the androidtv.adb_command service have better results here? And if so, does anyone have any good resources to help me learn how to format those commands? I know up top I mentioned being able to send commands via terminal, but I did have some trouble parsing out how to do that based on the stuff I was reading online. I did eventually get a few figured out but I have a lot to learn.

Anyway, I’ve been digging at this for about a week and nothing I’m finding online gets me any closer, so I finally resigned to asking here for help. Thanks in advance for any direction you can offer! If you need anymore info from my end feel free to ask, I tried to be as comprehensive as possible.

Posts: 1

Participants: 1

Read full topic

@roelandpollet wrote:

Hi everyone,

Would be really grateful if someone can point me in the right direction, been struggling with the most simple template in my scripts.yaml.
Alarm_sound_loop is called as an action when my alarm control panel is triggered. As long as my alarm is in pending state it needs to loop a beeping sound, once triggered it needs to loop the burglar sound.
The script fully works without the data template, so something must be wrong there. Also cannot seem to get the template for the delay to work, that is now commented.

Anybody any input!

alarm_sound_loop:
  alias: Alarm Triggered Sound Loop
  sequence:
    - condition: or
      conditions:
        - condition: state
          entity_id: alarm_control_panel.security_system
          state: 'triggered'
        - condition: state
          entity_id: alarm_control_panel.security_system
          state: 'pending'
    - service: script.turn_on
      entity_id: script.alarm_sound
alarm_sound:
  alias: Alarm Triggered Sound
  sequence:
    - service: media_player.volume_set
      data:
        entity_id: media_player.sonos_beam
        volume_level: 0.2
    - service: media_player.play_media
      data_template:
        entity_id: media_player.sonos_beam
        media_content_type: "music"
        media_content_id: >
          {% if is_state('alarm_control_panel.security_system','pending') %}
            !secret pending_beep_url
          {% else %}
            !secret burglar_alarm_sound_url
          {% endif %}
    - delay: "00:00:05" #>
#        {% if is_state('alarm_control_panel.security_system','pending') %}
#          "00:00:01"
#        {% elif is_state('alarm_control_panel.security_system','triggered') %}
#          "00:00:20"
#        {% else %}
#          "00:00:05"
#        {% endif %}
    - service: script.turn_on
      entity_id: script.alarm_sound_loop

Thanks a lot!

Posts: 1

Participants: 1

Read full topic

@DougAmes wrote:

I’ve had an issue for a long time where HA will not restart successfully, requiring me to log in with SSH, manually stop the HA service, wait 2 minutes for it to report stopped, and then start it again.

The service status report looks like this:

Jun 02 14:00:57 aml hass[14549]: AttributeError: 'NoneType' object has no attribute 'transport_id'
Jun 02 14:00:58 aml hass[14549]: 2020-06-02 14:00:58 ERROR (Thread-21) [pychromecast.socket_client] [192.168.0.72:8009] Failed to connect. No retries.
Jun 02 14:00:58 aml hass[14549]: 2020-06-02 14:00:58 ERROR (Thread-14) [pychromecast.socket_client] [192.168.0.71:8009] Failed to connect. No retries.
Jun 02 14:00:59 aml hass[14549]: 2020-06-02 14:00:59 ERROR (Thread-17) [pychromecast.controllers] Exception thrown when calling cast status listener
Jun 02 14:00:59 aml hass[14549]: Traceback (most recent call last):
Jun 02 14:00:59 aml hass[14549]:   File "/srv/homeassistant/lib/python3.6/site-packages/pychromecast/socket_client.py", line 1048, in _report_status
Jun 02 14:00:59 aml hass[14549]:     listener.new_cast_status(self.status)
Jun 02 14:00:59 aml hass[14549]:   File "/srv/homeassistant/lib/python3.6/site-packages/pychromecast/socket_client.py", line 381, in new_cast_status
Jun 02 14:00:59 aml hass[14549]:     new_channel = self.destination_id != cast_status.transport_id
Jun 02 14:00:59 aml hass[14549]: AttributeError: 'NoneType' object has no attribute 'transport_id'

The IP addresses specified in the error messages (192.168.0.71 and .72) are my Sonos One speakers, which I know appear to have Chromecast capabilties to many apps, but they do not - it’s an illusion.
After this error, HA startup freezes forever, and needs the manual stop/restart.
But this error does not happen all of the time. Sometimes at random HA will restart successfully, and in fact it tends to restart successfully if several restarts in a row are needed because other devices don’t initialize correctly.

Posts: 1

Participants: 1

Read full topic

@Knottyboy wrote:

Evening All,

I had an issue with my emulated_hue component and the fix was to:

1. Delete the emulated_hue_ids.json
2. Delete all the deviced on alexa.amazon.com

The above two steps have generally fixed the issue for me in the past. This time I had to do carry out a third step.

3. Stop the “offending” amazon devices.

Now my question is about the last point “Stop “offending” amazon devices.”. For some reason, although I deleted all the devices shown at alexa.amazon.com, some of the echo dots are still retaining the lights and sending requests to my pi.:

> 2020-06-02 21:00:40 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 31 not found in emulated_hue_ids.json
> 2020-06-02 21:00:40 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 22 not found in emulated_hue_ids.json
> 2020-06-02 21:00:40 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 34 not found in emulated_hue_ids.json
> 2020-06-02 21:00:40 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 34 not found in emulated_hue_ids.json
> 2020-06-02 21:00:40 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 48 not found in emulated_hue_ids.json
> 2020-06-02 21:00:40 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 48 not found in emulated_hue_ids.json
> 2020-06-02 21:00:40 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Unknown entity number: 48 not found in emulated_hue_ids.json

This was stopping the emualted_hue from working. I tried removing the devices and adding them again (as others have suggested in the cominuty) however this did not work for me. I ended up unplugging all the amazon devices and leaving one which I hopped wasn’t one of the *“offending” devices. I got lucky as when I rebooted the pi I didn’t get the above errors. I then scanned for devices and added all my lights again. A new emulated_hue_ids.json was created (the “offending” devices were stopping this from happenign it seems).

I’ve since plugged them back in and I am getting the errors again. The lights do work, however if my emulated_hue breaks again it would be nice to know how to properlly “flush” the amazon devices so I don’t have to go round unplugging all my dots & echos.

Posts: 1

Participants: 1

Read full topic