@lseufer wrote:
Hi guys,
I have tried updating to Openzwave and now I have the following issue which also affects the regular zwave integration. My switches can turn on lights but the state of the light isn’t recorded, consequently the light is on but the home assistant switch reverts back on its own to off.
Any idea what could cause this?Thanks!
Posts: 1
Participants: 1
@Alon wrote:
Hi,
With hass.io on rpi and latest 0.110.01 and HassOS 3.13 I have the following works:camera: - platform: ffmpeg name: kitchen input: rtsp://[user]:[pass]@192.168.2.11:14896/profile1now after reading the news on onvif on 110 release I tried to run the onvif integration from the integrations panel - it failed and on the log I saw this message:
Log Details (ERROR) Logger: aiohttp.server Source: components/onvif/config_flow.py:195 First occurred: 8:12:28 PM (1 occurrences) Last logged: 8:12:28 PM Error handling request Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start resp = await task File "/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle resp = await handler(request) File "/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/real_ip.py", line 39, in real_ip_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 73, in ban_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 127, in auth_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 125, in handle result = await result File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 145, in post return await super().post(request, flow_id) File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 54, in wrapper result = await method(view, request, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 103, in post result = await self._flow_mgr.async_configure(flow_id, data) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 153, in async_configure result = await self._async_handle_step(flow, cur_step["step_id"], user_input) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 201, in _async_handle_step result: Dict = await getattr(flow, method)(user_input) File "/usr/src/homeassistant/homeassistant/components/onvif/config_flow.py", line 170, in async_step_auth return await self.async_step_profiles() File "/usr/src/homeassistant/homeassistant/components/onvif/config_flow.py", line 195, in async_step_profiles await device.update_xaddrs() File "/usr/local/lib/python3.7/site-packages/onvif/client.py", line 277, in update_xaddrs capabilities = await self.devicemgmt.GetCapabilities({"Category": "All"}) File "/usr/local/lib/python3.7/site-packages/zeep/asyncio/bindings.py", line 13, in send options["address"], envelope, http_headers File "/usr/local/lib/python3.7/site-packages/zeep/asyncio/transport.py", line 107, in post_xml response = await self.post(address, message, headers) File "/usr/local/lib/python3.7/site-packages/zeep/asyncio/transport.py", line 95, in post proxy=self.proxy, File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 504, in _request await resp.start(conn) File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 847, in start message, payload = await self._protocol.read() # type: ignore # noqa File "/usr/local/lib/python3.7/site-packages/aiohttp/streams.py", line 591, in read await self._waiter aiohttp.client_exceptions.ServerDisconnectedError: Noneis this something I can fix?
thanks!
Posts: 1
Participants: 1
@pixelrogue wrote:
Walking away from Wink.
On a Mac-mini, running Wink + Homebridge for HomeKit.Thinking of returning to a z-wave stick and installing Home Assistant. Happen to have a z-wave Wayne Dalton z-wave stick handy. Think that will work? Is’t actual app only works w/Flash, and hoping not to install Flash just for this need. Would Home Assistant access and work w/Wayne Dalton Z-Wave Stick?
Posts: 1
Participants: 1
@MDLefevere wrote:
Hi All.
I’ve been using Custom Header for some time to hide that big massive bar at the top.
Since the last update and upgrade of HACS it’s not working anymore.All resources that used to be on top of the raw editor have been moved but i can’t figure out how to get Custom Header working again.
Any ideeas?. If i go to HACS on the sidebar and then Frontend; the custom header is activated
Posts: 2
Participants: 1
@silver323 wrote:
Dear,
I’ve updated my raspberry Pi with Home assistant to version 110.1
But now I see messages about deprecated. But the messages are not saying me anything.
These are the errors:2020-05-22 13:22:52 WARNING (MainThread) [homeassistant.components.switch] SwitchDevice is deprecated, modify RfxtrxSwitch to extend SwitchEntity
2020-05-22 13:22:53 WARNING (MainThread) [homeassistant.components.cover] CoverDevice is deprecated, modify RfxtrxCover to extend CoverEntity
2020-05-22 13:22:54 WARNING (MainThread) [homeassistant.components.light] Light is deprecated, modify RfxtrxLight to extend LightEntity
2020-05-22 13:22:55 WARNING (MainThread) [homeassistant.components.binary_sensor] BinarySensorDevice is deprecated, modify RfxtrxBinarySensor to extend BinarySensorEntity
2020-05-22 13:23:06 WARNING (MainThread) [homeassistant.components.binary_sensor] BinarySensorDevice is deprecated, modify MindBinarySensor to extend BinarySensorEntityI don’t see what’s changed in the release notes. So can somebody tell me where to look or what is changed?
Posts: 2
Participants: 2
@MsbS wrote:
I just updated my installation to 0.110.1 and I noticed that some scripts/automations stopped working. After some investigation I noticed that once you set the volume_level of a media_player (in my case, a Squeezebox player) to zero, the attribute volume_level is disappearing from the entity (I checked using developer tools --> states). Can anyone confirm this?
Posts: 1
Participants: 1
@superwizbang wrote:
Thanks for looking. I have a doorbell set up in HA (OS 110). I would like to trigger playing an mp3 (WAV or any format which will work) through the 3.5mm jack on an intel NUC and routing through my whole-home audio amps.
For this task, I have tried using Mopidy, creating my own custom addon, using media extractor, everything I can possibly find–without success. As a n00b, can anyone assist with getting this configured? Thanks in advance.
Posts: 1
Participants: 1
@mcfarlde wrote:
(topic withdrawn by author, will be automatically deleted in 24 hours unless flagged)
Posts: 1
Participants: 1
@mcfarlde wrote:
The LCRs lost their names and all show with the same name “Lutron LZL4BWHL01 Remote” within ZHA. Not found as a Device or Entity anymore so no very usefull for naything. Removed, repaired, renamed while adding and thought things were improving until a reboot where they are all back to having the same name and not visible outside of ZHA. Anyone else?
Posts: 1
Participants: 1
@CorneliousJD wrote:
I have automations trigger tts.google_translate_say with an entity ID of a speaker (or speaker group) and a message.
The .mp3 file is generated successfully in the tts folder, but my Google home devices make a sound like they’re about to say something (e.g. play the mp3 file from the tts folder) but it never actually plays now.
It just makes the noise like it’s about to then nothing.
Any advice is appreciated here.
Posts: 2
Participants: 2
@f00dagi wrote:
Hi!
I am lost, please help.
I had a perfectly working setup where I used custom cards: layout-card, button-card, slider-entity-row, card-tools which I had installed manually. To facilitate management (updates, …) I moved to HACS some time ago. I used a stepwise approached and replaced card by card from manual install to HACS and everything seemed to work fine (even after reboot). Now, suddenly everything came crashing down and I cannot get the custom cards to load anymore. I really want the cards to load by using HACS and don’t want to move back to manual installation.
My HACS custom-cards got installed here:
\\192.168.1.242\config\www\community\button-card\ \\192.168.1.242\config\www\community\lovelace-card-tools\ \\192.168.1.242\config\www\community\lovelace-layout-card\ \\192.168.1.242\config\www\community\lovelace-slider-entity-row\Question 1: How do I get Home Assistant to look in these folders when trying to find the custom cards?
My manual installation were in different folders that I had created based on instructions I found.
Question 2: To get the manual installations working I also had to have these resources in ui-lovelace.yaml. Do I need these when using HACS and what should the path look like?
resources: - url: /community_plugin/button-card/button-card.js type: module - url: /local/plugins/layout-card.js?v=1 type: js - url: /local/slider-entity-row.js type: module - url: /local/plugins/card-tools.js?v=1 type: jsThe error message I get for all my cards are like the picture below. Custom element doesn’t exist: button-card.
Question 3: Any thought on why I did not get the error messages right away? Browser cache? Different types of home assistant reboot? I reboot from UI.
Thanks!
Posts: 2
Participants: 2
@thanksmister wrote:
After the last update, I tried to update my alarm panel to use some of the new parameters listed in the MQTT Manual Alarm Panel documentation. However, I consistently receive configuration errors for some of the new params.
The following params are not allowed:
code_template
code_arm_requiredThe error thrown in the Configuration validation is as follows:
Invalid config for [alarm_control_panel.manual_mqtt]: [arming_time] is an invalid option for [alarm_control_panel.manual_mqtt]. Check: alarm_control_panel.manual_mqtt->arming_time. (See ?, line ?).Also, after the latest update, I would expect the Manual MQTT (Alarm Panel) to share the same configuration and params as the Manual (Alarm Panel). This was mentioned as a breaking change in the recent release of Home Assistant 0.110, yet those changes for the Manual Alarm Panel are not reflected in the documentation for the MQTT Manual Alarm Panel. It’s a bit confusing since the MQTT Manual is based on the Manual.
I would expect that I could do this in my configuration file for the platform manual_mqtt:
alarm_control_panel: - platform: manual_mqtt state_topic: home/alarm command_topic: home/alarm/set trigger_time: 1800 disarm_after_trigger: false delay_time: 30 arming_time: 60 command_template: "{\"action\":\"{{action}}\",\"code\":\"{{code}}\"}" code_arm_required: false code_disarm_required: true code: 1234Has anyone encountered this issue and perhaps knows if this is just a temporary oversight in the documentation? I am the maintainer of an open source MQTT Alarm Panel for Android based on the MQTT Manual Alarm Panel, so it would be nice to use some of these new updates such as the command template and arming and disarming states.
Thanks!
Posts: 1
Participants: 1
@Mrianphill wrote:
Hi,
Does anyone know if it is possible to find if an LG TV (webos) is in HDR or Dolby Vision Mode? I’d like to display it on my dashboard.
Many thanks
Ian
Posts: 1
Participants: 1
@AdrianGarside wrote:
I’m in the middle of setting up a bunch and noticed huge variation in the listed delay from sub-minute to 30+ minutes even when the sensor is still showing up on the raspberry pi as a w1 bus device. In at least one case, the raw value shown in the home assistant page didn’t match the raw value in the w1_slave file for quite a long period before eventually updating again and getting back in sync.
Is it maybe that if the sensor doesn’t observe a change in temperature it doesn’t generate an event thus the timestamp of the last temperature read doesn’t change? Although holding the sensor to heat it up doesn’t seem to reliably trigger home assistant to update it’s value in the UX. And I’ve seen a case where a sensor was still updating it’s value but the file timestamp on the w1_slave file (and others) was still from the previous day. While at other times, the timestamps update when the reading gets updated. So if there is some kind of eventing going on, it’s not reflected in the file timestamps for the devices in the linux filesystem.
Posts: 1
Participants: 1
@PPatou wrote:
Hello,
I have the same problem as described in this post
https://community.home-assistant.io/t/input-date-time-format/34838
Unfortunately the solution given in this post (dec 2017) does not work actually with latest Hassio version.{{states('input_datetime.start6')}} {{ states('sensor.time')}}1 gives format : HH:MM:SS
2 gives format HH:MM
So impossible to compare the 2 states
How can I format the input_datetime to HH:MM ?
Thanks in advance for your attention
Patou
Posts: 3
Participants: 2
@toon1uk wrote:
Am complete NOOB and am just dabbling on HASSIO.I have a full Micro Sd card install, which ties up the whole PI.Did setup a Google Drive Snapshot backup…So is this possible ?
Like to run Berry Boot and OS like Raspbian X on SSD (looks like Windows) but install CURL docker for Hassio (like App) but then user my orginal Google Drive snapshot to reinstall my Configs to the Hassio docker and other setups i have refined.
Also over clock to 2Ghz CPU and 600 GPU.Basically get more from RPI4B.I have the approaite cooling fan.
Posts: 2
Participants: 2
@taimur wrote:
Hi, I am trying to stream video from my cctv in the Home Assistant so I can view it on the dashboard.
However I have searched high and low and tried all possible combinations to stream it. I can stream the camera in VLC using the link rtsp://admin:***@10.107.1.:00554/ch01/0 and it loads the stream fine.
Without adding the camera component and adding the following code
stream: camera: - platform: generic still_image_url: http://10.107.1.***:00085/Streaming/Channels/101/picture stream_source: rtsp://admin:*******@10.107.1.***:00554/ch01/0 username: "admin" password: "******" authentication: digestI get the error
Once I install the custom camera component I get this error
All I am trying to do is play the stream. or even play it in a iframe or anyway possible. Or is this something not possible? Any help will be appreciated.
Posts: 1
Participants: 1
@Benouzao wrote:
Hello,
I’m trying to figure out a simple way to enable a view/tab when the current user is home but always on for others users?
Basically I want to enable a view/tab with cameras for our Nanny to monitor our kids sleeping, but only when she’s home. I will always be activate for my wife and I. Our Nanny will also have access to other views to control other devices in the house.
Thanks for your inputs,
Ben
Posts: 1
Participants: 1
@toon1uk wrote:
I have Broadlink Pro plus and have NOOBed experimented with Broadlink APPS (what frustrating APP to work with !!).
Now I did see some write ups but where Not very clear too follow as I would Like to Use NODE-RED to fine tune Broadlink Device Pro plus 3 ,say for instance , a toggled power button on a remote, can leave the state in the wrong position and Off being ON and so on.I thought I could use NODE RED to use Broadlink nodes and ping command to sence say TV on or off state.This would give a more accurate responce every time.Is it Possible ? RPI>HA>Google Home>Node RED>IR Codes
I know the Broadlink App can do it but NODE RED would give it a virtual ability.
Posts: 1
Participants: 1
@grh6u5zp04kd wrote:
After the 0.110 update, I’m getting blank icons all over HA: dashboards, sidebar, menu’s etc. This is what I’m getting in Firefox:
In Chrome, I get what I’d normally expect:
Has anyone else experienced this? I’ve tried clearing the Firefox cache, but no luck.
Posts: 1
Participants: 1
