@AlfaBravoX wrote:
Hi,
is there a way to detect that target thermostat temperature was changed by human by UI?
I use
hass.states.get('climate.danfoss_z_thermostat').attributes['temperature']to get temperature in custom_components controlling script, but i need to get info if this was done by script of UI to be able to override thermostat plan temporary.
Posts: 1
Participants: 1
@jasper1983x wrote:
Howdy! After i finally got my RFXCOM to work and scanned for my devices (4 smoke detectors), i added the identifiers i got into my configuration file. However, only 3 out of 4 devices get loaded by Hassio after a reboot.
It doesn’t matter in which order i stick them in my config, or which devices i leave out, no more than 3 devices will be loaded and show up as available
My configuration looks like this:sensor: platform: rfxtrx devices: 082009048422000650: name: smoke_detector_attic 08200900846b000660: name: smoke_detector_livingroom 0820090201f2000650: name: smoke_detector_upstairs 0820090001f2000650: name: smoke_detector_utilityroomNo error in the logs, but there you can lso see that it just loads 3 of the 4 items above
2019-11-02 15:58:52 INFO (SyncWorker_14) [homeassistant.components.rfxtrx.sensor] Add smoke_detector_attic rfxtrx.sensor 2019-11-02 15:58:52 INFO (SyncWorker_14) [homeassistant.components.rfxtrx.sensor] Add smoke_detector_livingroom rfxtrx.sensor 2019-11-02 15:58:52 INFO (SyncWorker_14) [homeassistant.components.rfxtrx.sensor] Add smoke_detector_upstairs rfxtrx.sensor‘smoke_detector_utilityroom’ is not mentioned in the logs, not even after a complete hassio reboot
Is it just me, or are there more people with this issue? Am i missing something here?
Posts: 1
Participants: 1
@Mark-81 wrote:
I followed the usual procedure to upgrade my virtualenv to the latest version (0.101.2) from 0.95.x if I didn’t recall wrong.
But it upgraded to 0.96.5 only.Is there a way to find out why it didn’t reach the latest one?
Posts: 4
Participants: 2
@comatose_tortoise wrote:
Whenever I access my HA through Nabu Casa, any Grafana graphs I have in my frontend are gone. Is it possible to make them visible also when HA is being accessed through Nabu Casa?
Posts: 1
Participants: 1
@ThePicklenat0r wrote:
I looked for another thread about this, but couldn’t find anyting, so I must be missing something here. On Android, usually the status bar color updates to match the primary color of a theme, but that doesn’t seem to be happening anymore. I noticed this after upgrading to Android 10, not sure if there is a tag that is missing now, or if there is something else going on. Here’s an example, notice the status bar is blue (default theme) but the primary color is green. My theme is also below.
Dark - Green & Gray: ### Main Interface Colors ### primary-color: "#87BF50" light-primary-color: "#C5C5C5" primary-background-color: "#494B58" secondary-background-color: var(--primary-background-color) divider-color: "#343434" accent-color: var(--primary-background-color) ### Text ### primary-text-color: "#FFFFFD" secondary-text-color: "#87BF50" text-primary-color: "#FFFFFF" disabled-text-color: "#A3A3A3" ### Sidebar Menu ### sidebar-icon-color: "#A3A3A3" sidebar-text-color: "#FFFFFD" sidebar-selected-background-color: var(--primary-background-color) sidebar-selected-icon-color: "#87BF50" sidebar-selected-text-color: var(--sidebar-selected-icon-color) ### States and Badges ### state-icon-color: "#87BF50" state-icon-active-color: "#F7AA1C" state-icon-unavailable-color: var(--disabled-text-color) ### Sliders ### paper-slider-knob-color: "#87BF50" paper-slider-knob-start-color: var(--paper-slider-knob-color) paper-slider-pin-color: var(--paper-slider-knob-color) paper-slider-active-color: var(--paper-slider-knob-color) paper-slider-secondary-color: var(--light-primary-color) ### Labels ### label-badge-background-color: "#575757" label-badge-text-color: "#FFFFFD" label-badge-red: "#87BF50" ### Cards ### paper-card-background-color: var(--primary-background-color) paper-listbox-background-color: var(--primary-background-color) card-background-color: var(--paper-card-background-color) ### Toggles ### paper-toggle-button-checked-button-color: "#87BF50" paper-toggle-button-checked-bar-color: "#598330" paper-toggle-button-unchecked-button-color: "#A3A3A3" paper-toggle-button-unchecked-bar-color: "#6F6F6F" ### Table row ### table-row-background-color: var(--primary-background-color) table-row-alternative-background-color: var(--secondary-background-color)
Posts: 1
Participants: 1
@Klagio wrote:
Below the error lo. Tried to revert back to 0.100.3 but it does not. I am stuck. How can I get back a working configuration?
I use proxmox on a NUC and HASSIO
2019-11-02 23:16:29 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for meross which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant. 2019-11-02 23:16:29 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for entity_controller which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant. 2019-11-02 23:16:29 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for shelly which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant. 2019-11-02 23:16:29 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for smartir which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant. 2019-11-02 23:16:30 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for circadian_lighting which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant. 2019-11-02 23:16:39 ERROR (MainThread) [homeassistant.setup] Error during setup of component circadian_lighting Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/setup.py", line 176, in _async_setup_component component.setup, hass, processed_config # type: ignore concurrent.futures._base.CancelledError 2019-11-02 23:16:39 ERROR (MainThread) [homeassistant.setup] Error during setup of component ffmpeg Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/setup.py", line 172, in _async_setup_component hass, processed_config File "/usr/src/homeassistant/homeassistant/components/ffmpeg/__init__.py", line 61, in async_setup await manager.async_get_version() File "/usr/src/homeassistant/homeassistant/components/ffmpeg/__init__.py", line 111, in async_get_version self._version = await ffversion.get_version() File "/usr/local/lib/python3.7/site-packages/haffmpeg/tools.py", line 75, in get_version output, _ = await self._loop.run_in_executor(None, proc_func) concurrent.futures._base.CancelledError 2019-11-02 23:16:39 ERROR (MainThread) [homeassistant.components.alarm_control_panel] Error while setting up platform bwalarm Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 150, in _async_setup_platform await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT) File "/usr/local/lib/python3.7/asyncio/tasks.py", line 435, in wait_for await waiter concurrent.futures._base.CancelledError 2019-11-02 23:16:39 ERROR (MainThread) [homeassistant.setup] Error during setup of component api Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/setup.py", line 176, in _async_setup_component component.setup, hass, processed_config # type: ignore concurrent.futures._base.CancelledError 2019-11-02 23:16:39 ERROR (MainThread) [homeassistant.setup] Error during setup of component shopping_list Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/setup.py", line 172, in _async_setup_component hass, processed_config File "/usr/src/homeassistant/homeassistant/components/shopping_list/__init__.py", line 87, in async_setup yield from data.async_load() File "/usr/src/homeassistant/homeassistant/components/shopping_list/__init__.py", line 171, in async_load self.items = yield from self.hass.async_add_job(load) concurrent.futures._base.CancelledError 2019-11-02 23:16:39 ERROR (MainThread) [homeassistant.setup] Error during setup of component maxcube Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/setup.py", line 176, in _async_setup_component component.setup, hass, processed_config # type: ignore concurrent.futures._base.CancelledError 2019-11-02 23:16:39 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry 192.168.1.12 for mqtt Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 190, in async_setup hass, self File "/usr/src/homeassistant/homeassistant/components/mqtt/__init__.py", line 649, in async_setup_entry result: str = await hass.data[DATA_MQTT].async_connect() File "/usr/src/homeassistant/homeassistant/components/mqtt/__init__.py", line 793, in async_connect self._mqttc.connect, self.broker, self.port, self.keepalive concurrent.futures._base.CancelledError 2019-11-02 23:16:39 ERROR (MainThread) [homeassistant.components.deconz] Error connecting with deCONZ gateway 2019-11-02 23:16:39 ERROR (MainThread) [homeassistant.setup] Error during setup of component pi_hole Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/setup.py", line 172, in _async_setup_component hass, processed_config File "/usr/src/homeassistant/homeassistant/components/pi_hole/__init__.py", line 83, in async_setup await pi_hole.async_update() File "/usr/src/homeassistant/homeassistant/components/pi_hole/__init__.py", line 128, in async_update await self.api.get_data() File "/usr/local/lib/python3.7/site-packages/hole/__init__.py", line 37, in get_data response = await self._session.get(self.base_url) File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 483, in _request timeout=real_timeout File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 523, in connect proto = await self._create_connection(req, traces, timeout) File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 859, in _create_connection req, traces, timeout) File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 986, in _create_direct_connection req=req, client_error=client_error) File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 936, in _wrap_create_connection return await self._loop.create_connection(*args, **kwargs) # type: ignore # noqa File "/usr/local/lib/python3.7/asyncio/base_events.py", line 941, in create_connection await self.sock_connect(sock, address) File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 464, in sock_connect return await fut concurrent.futures._base.CancelledError 2019-11-02 23:16:39 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry 127.0.0.1 for adguard Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 190, in async_setup hass, self File "/usr/src/homeassistant/homeassistant/components/adguard/__init__.py", line 71, in async_setup_entry version = await adguard.version() File "/usr/local/lib/python3.7/site-packages/adguardhome/adguardhome.py", line 167, in version response = await self._request("status") File "/usr/local/lib/python3.7/site-packages/adguardhome/adguardhome.py", line 107, in _request ssl=self.verify_ssl, File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 483, in _request timeout=real_timeout File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 523, in connect proto = await self._create_connection(req, traces, timeout) File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 859, in _create_connection req, traces, timeout) File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 986, in _create_direct_connection req=req, client_error=client_error) File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 936, in _wrap_create_connection return await self._loop.create_connection(*args, **kwargs) # type: ignore # noqa File "/usr/local/lib/python3.7/asyncio/base_events.py", line 941, in create_connection await self.sock_connect(sock, address) File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 464, in sock_connect return await fut concurrent.futures._base.CancelledError 2019-11-02 23:16:39 ERROR (MainThread) [homeassistant.setup] Error during setup of component group Traceback (most recent call last): File "/usr/local/lib/python3.7/asyncio/runners.py", line 43, in run return loop.run_until_complete(main) File "/usr/local/lib/python3.7/asyncio/base_events.py", line 579, in run_until_complete return future.result() File "/usr/src/homeassistant/homeassistant/__main__.py", line 302, in setup_and_run_hass log_no_color=args.log_no_color, File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 146, in async_from_config_file config_dict, hass, enable_log=False, skip_pip=skip_pip File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 91, in async_from_config_dict await _async_set_up_integrations(hass, config) File "/usr/src/homeassistant/homeassistant/bootstrap.py", line 372, in _async_set_up_integrations *(async_setup_component(hass, domain, config) for domain in domains_to_load) File "/usr/src/homeassistant/homeassistant/setup.py", line 51, in async_setup_component return await task # type: ignore File "/usr/src/homeassistant/homeassistant/setup.py", line 147, in _async_setup_component hass, config, integration File "/usr/src/homeassistant/homeassistant/config.py", line 736, in async_process_component_config p_validated = component_platform_schema(p_config) File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 272, in __call__ return self._compiled([], data) File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 205, in _run return self._exec(self._compiled, value, path) File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 285, in _exec v = func(path, v) File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 817, in validate_callable return schema(data) File "/usr/src/homeassistant/homeassistant/components/scene/__init__.py", line 46, in _platform_validator return platform.PLATFORM_SCHEMA(config) File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 272, in __call__ return self._compiled([], data) File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict return base_validate(path, iteritems(data), out) File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 386, in validate_mapping cval = cvalue(key_path, value) File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 205, in _run return self._exec(self._compiled, value, path) File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 285, in _exec v = func(path, v) File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 635, in validate_sequence cval = validate(index_path, value) File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict return base_validate(path, iteritems(data), out) File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 386, in validate_mapping cval = cvalue(key_path, value) File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 205, in _run return self._exec(self._compiled, value, path) File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 285, in _exec v = func(path, v) File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 817, in validate_callable return schema(data) File "/usr/src/homeassistant/homeassistant/components/homeassistant/scene.py", line 37, in _convert_states if isinstance(states[entity_id], dict): KeyError: 'group.ceiling_lights' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/setup.py", line 172, in _async_setup_component hass, processed_config File "/usr/src/homeassistant/homeassistant/components/group/__init__.py", line 216, in async_setup await _async_process_config(hass, config, component) File "/usr/src/homeassistant/homeassistant/components/group/__init__.py", line 373, in _async_process_config mode=mode, File "/usr/src/homeassistant/homeassistant/components/group/__init__.py", line 488, in async_create_group await component.async_add_entities([group], True)e 475, in _check_closed
raise RuntimeError(‘Event loop is closed’)
RuntimeError: Event loop is closed
Posts: 20
Participants: 5
@laca75tn wrote:
I deleted by mistake an entity card. How can I restore it from my backups?
Thanks for your help
Posts: 4
Participants: 3
@eric10k93 wrote:
So the latest changes with the MyQ integration did some weird things… first it broke my automations… I have the light set to turn on with the garage door and off after a few minutes when it’s closed… This has not been functioning at all for a week or so.
I finally got into my configs to see what happened and it appears my MyQ device has changed names… the old device named “cover.garage_door_opener” does not exist anymore… now I find it listed as “cover.garage_door_opener_2”
I’m not sure why this happened… but that’s not my immediate concern… my main problem is the light hasn’t been turning off automatically because the automation is looking for the state of “cover.garage_door_opener” to be “closed” but since the device doesn’t exist… it never turns off anymore…
Is there a way to configure an automation to ignore an entity that is either “unavailable” or just doesn’t exist anymore for some reason?
Here’s what my automation looks like now:
- alias: a_garage_inside_light_timer initial_state: True trigger: - platform: state entity_id: cover.garage_door_opener_2 to: 'closed' for: minutes: 7 - platform: state entity_id: binary_sensor.contactgaragesidedoor, binary_sensor.contactgaragehouseentrydoor to: 'off' for: minutes: 7 condition: condition: and conditions: - condition: state entity_id: input_boolean.garage_light_timer_override state: 'off' - condition: state entity_id: binary_sensor.contactgaragesidedoor state: 'off' for: minutes: 7 - condition: state entity_id: binary_sensor.contactgaragehouseentrydoor state: 'off' for: minutes: 7 - condition: state entity_id: cover.garage_door_opener_2 state: 'closed' for: minutes: 7 action: service: homeassistant.turn_off entity_id: switch.garagemainlight
Posts: 1
Participants: 1
@pellle87 wrote:
So the thing i want to do is turn on switch.driveway_socket at different times based on the temperature outside
kinda like this
if temp outside between -1 to -10 turn on 06:00
if temp outside between -11 to -20 turn on 05:00
if temp outside between -21 to -30 turn on 04:00
if temp outside < -31 turn on 03:00Times and temps are just examples but is this possible to achieve?
Posts: 6
Participants: 4
@eric10k93 wrote:
I’ve found a number of resources on integrating existing hard-wired smoke and CO alarms using a relay and a Zwave module. This guide in particular was quite thorough: https://community.smartthings.com/t/integrating-kidde-smoke-co-sensors-into-smartthings-properly/53641
The issue I am having is I have combination smoke/CO alarms that I would like to get distinct signals from… I assume I can connect a single Kidde relay with a Zwave module and I’d get a notification for an alarm whether it is smoke or CO… BUT, if possible I’d like to get a distinct notification depending on the type of alarm… I know Kidde makes both a smoke and a CO relay, but I’m assuming I couldn’t just connect both of these to a single combination detector and hope they trigger individually… I’m operating under the assumption that these relays operate on simple voltage output… but I haven’t played with them myself so I was hoping somebody on these forums has.
Is there an easy way to get a distinct signal to tell the difference between a smoke or a CO alarm? Anyone have any experience playing with this type of setup?
Thanks in advance!
Posts: 2
Participants: 2
@jriker1 wrote:
I currently have a presence setup to make sure if anyone in my home is there.
device_tracker: - platform: ping interval_seconds: 30 consider_home: 1200 hosts: john_iphone: 192.168.0.200 sue_iphone: 192.168.0.201I have added UniFi Controller and it’s parameters thru the Integration option. Devices are showing up under Configuration > Devices.
How would I add these existing UniFi devices to the above?
Thanks.
JR
Posts: 1
Participants: 1
@atterberg wrote:
Hi.
I have a input_number that I want to use to set brightness to a light.
I made a test script that looks like this:'1232334232434': alias: testanumberslider sequence: - data: brightness: "{{ states('input_number.alarmminutes_weekdays') | int }}" entity_id: light.kallaren transition: 10 service: light.turn_onIf I use a fixed number for brightness it works fine. But now a get the following error:
Error executing script script.1232334232434. Invalid data for call_service at pos 1: expected int for dictionary value @ data[‘brightness’]In developer tools / states the input_number.alarmminutes_weekdays have state: 30.0
What I’m a doing wrong?
using Home Assistant 0.100.1
Posts: 4
Participants: 3
@ankycooper wrote:
Just another security housekeeping, secrets for integration via GUI are stored in config/.storage/core.config_entries in clear and not secrets.yaml file. Is there a way to point it to secret file, I have tried changing the entry but HA fails to start.
If this is a missing feature, it is a critical one and needs to be addressed. Happy to raise it as a feature request if it is missing.
Posts: 3
Participants: 2
@Noahma wrote:
I just updated to the newest release, and I noticed something about my scenes. The Lifx bulbs I have called out in the scenes no longer transition their brightness. Any help getting it fixed would be appreciative.
Here is a sample of one of the scenes that no longer transition.
- name: Standard entities: light.family_room_right: state: on color_temp: 280 brightness: 255 transition: 8 light.family_room_left: state: on color_temp: 280 brightness: 255 transition: 8 switch.living_room: state: on switch.dining_switch: state: on switch.kitchen_light: state: on light.living_strip: state: on color_temp: 400 brightness: 255 transition: 8
Posts: 5
Participants: 3
@KCYeoh wrote:
I have integrated Xiaomi Gateway into my Hassio and I want send email/sms notifications when Xiaomi Gateway sounded alarm/led blinking. Anyone has done that before? Any advise or recommendation how can i configure it as such are much appreciated.
Current Mi Home app is not that useful and has delay.
Thanks in advance.
Posts: 2
Participants: 2
@Mark-81 wrote:
To give it a try, here my DarkSky configuration:
- platform: darksky api_key: !secret darksky_password language: it forecast: 0 monitored_conditions: - summary - icon - precip_type - precip_intensity - precip_probability - precip_accumulation - temperature - apparent_temperature - dew_point - wind_speed - wind_gust - wind_bearing - cloud_cover - humidity - pressure - visibility - minutely_summary - daily_summary - temperature_high - temperature_low - apparent_temperature_high - apparent_temperature_low - precip_intensity_max - uv_index - moon_phase - sunrise_time - sunset_time - nearest_storm_distance - nearest_storm_bearing - alerts scan_interval: minutes: 5And here the related group:
weatherGroup: name: Weather entities: - sensor.dark_sky_summary - sensor.dark_sky_icon - sensor.dark_sky_precip_type - sensor.dark_sky_precip_intensity - sensor.dark_sky_precip_probability - sensor.dark_sky_precip_accumulation - sensor.dark_sky_temperature - sensor.dark_sky_apparent_temperature - sensor.dark_sky_dew_point - sensor.dark_sky_wind_speed - sensor.dark_sky_wind_gust - sensor.dark_sky_wind_bearing - sensor.dark_sky_cloud_cover - sensor.dark_sky_humidity - sensor.dark_sky_pressure - sensor.dark_sky_visibility - sensor.dark_sky_minutely_summary - sensor.dark_sky_daily_summary - sensor.dark_sky_temperature_high - sensor.dark_sky_temperature_low - sensor.dark_sky_apparent_temperature_high - sensor.dark_sky_apparent_temperature_low - sensor.dark_sky_precip_intensity_max - sensor.dark_sky_uv_index - sensor.dark_sky_moon_phase - sensor.dark_sky_sunrise_time - sensor.dark_sky_sunset_time - sensor.dark_sky_nearest_storm_distance - sensor.dark_sky_nearest_storm_bearing - sensor.dark_sky_alertsBut some of them are not recognized (“entity not available”):
- sensor.dark_sky_precip_type - sensor.dark_sky_precip_accumulation - sensor.dark_sky_cloud_cover - sensor.dark_sky_temperature_high - sensor.dark_sky_temperature_low - sensor.dark_sky_apparent_temperature_high - sensor.dark_sky_apparent_temperature_low - sensor.dark_sky_precip_intensity_max - sensor.dark_sky_moon_phase - sensor.dark_sky_sunrise_time - sensor.dark_sky_sunset_timeDid I forget something?
Posts: 10
Participants: 3
@klogg wrote:
Does anyone else have a problem with
track_new_devicesnot working?I have:
#=== Bluetooth - platform: bluetooth_tracker new_device_defaults: track_new_devices: falsebut every time a random person (read, junk mail delivery!) comes to my door I get a new entry in
known_devicesthat is tracked:t821: hide_if_away: false icon: mac: BT_00:11:67:XX:XX:XX name: T821 picture: track: true
Posts: 3
Participants: 2
@flavio1 wrote:
Goodmorning everyone,Home assistant error on restart does not find everyone around me, I messed up maybe some command.
I have installed phiton 3.8.0 on my raspberry and home assistant has not recovered from this error and cannot find the page.
What can I do to restore a home assistant?
it may be temporarily unavailable or has been permanently moved to a new web address.
it may be temporarily unavailable or has been permanently moved to a new web address.
impossible to reach the site
I tried to restore the backup image previously saved 2 weeks before but it still doesn’t restartthe web page at https://rom2.duckdns.org:3000/auth/authorize?response_type=code&redirect_uri=https%3A%2F%2rom2.duckdns.org%3A3000%2F%3Fauth_callback%3D1&client_id=https%3A%2F%2From2.duckdns.org%3A3000%2F&state=eyJoYXNzVXJsIjoiaHR0cHM6Ly9mbGF2aW8xLmR1Y2tkbnMub3JnOjMwMDAiLCJjbGllbnRJZCI6Imh0dHBzOi8vZmxhdmlvMS5kdWNrZG5zLm9yZzozMDAwLyJ9 it may be temporarily unavailable or has been permanently moved to a new web address.
ERR_FAILED
I tried to restore the backup image previously saved 2 weeks before but it still doesn’t restart
I had installed version 0.101
Posts: 2
Participants: 2
@Odin wrote:
Hi,
I have a problem adding OpenTherm gateway through Integrations in newest version of HA.When I enter name ‘Boiler’ and path ‘socket://10.0.0.109:6638’ and press ‘Submit’ it take couple of second and fields name and parth are empty and there is no OpenTherm Gateway in integrations.
What could be the problem? Is it necessary to have boiler connected with gateway while adding to HA?
I bought my gateway from nodo-shop.nl, I have version with NodeMCU. After I’ve received gateway I was not able to connect with it to enter my WiFi setting I had to install ESPEasy and configured it, maybe that’s the problem? Below is my NodeMCU configuration:
Thank you
Posts: 1
Participants: 1
@Lipown wrote:
Hi,
I have external soundcard with two active speakers connected to Raspberry PI where Hassio is running. For Kodi, Raspotify and Mopidy I run the automation to switch the power plug of the speakers On or Off based on playback.
I would like to automate the same also when somebody is ussing the Raspberry PI as an bluetooth receiver through blueman. Is there any possibility how to do that?
Posts: 1
Participants: 1
