@LarsAC wrote:
Hello,
I seem to have lost a couple of ZWave nodes in HA. Under entities tab, the ZWave controller pretends to have following neighbours:
neighbors: 4,6,8,10,16,17,18,19,20,21,22,23,24,25whereas I can only see entity information for 16, 17, 19, 21 in UI or entities list.
Any ideas what might have happened ? I also found a new zwcfg_xxx.xml in my /config directory - could this be related ?
I am running 0.105.3 as a docker container.
Lars
Posts: 1
Participants: 1
@jjross wrote:
Just upgraded to 0.108 and I’m loving it so far.
Once I upgraded HA detected my printer so I added it right away but I’ve noticed that the status says “printing” even those the printer isn’t actually printing. Is this a bug or something I need to configure on my printer?
Posts: 1
Participants: 1
@HavartiBard wrote:
I have been troubleshooting an issue with my google calendar lovelace card for the past few weeks and I am just not knowledgeable on all of the home assist backend to figure out whats going wrong here:
Following the update to 0.107.1 ( and subsequent point releases ) my atomic-calendar lovelace card was unable to load my calendar data with the following error:
Cannot assign to read only property ‘0’ of object ‘[object Array]’
My assumption was that my google calendar integration was broken and started poking around and did the following:
- Attempted using the calendar-card plugin ( similar results of an error suggesting no data )
- Scorched earth deleted google calendar configs and regenerated
- regenerated a google oath key and updated hassio config
- Verified that the calendar integration is working by examining the calendar entities directly
So now I am troubleshooting with the calendar-card and running on 0.107.7. In the lovelace card I see a 400 response code error. Looking at the requests I can see that the Bearer authentication header is being sent properly but getting an error on the internal API call for calendars:
Request URL: http://192.168.86.25:8123/api/calendars/calendar.family_calendar?start=2020-04-08T00:00:00Z&end=2020-04-15T00:00:00Z Request Method: GET Status Code: 400 Bad Request Remote Address: 192.168.86.25:8123 Referrer Policy: same-origin Response Headers Content-Length: 0 Content-Type: application/octet-stream Date: Wed, 08 Apr 2020 21:20:15 GMT Server: Python/3.7 aiohttp/3.6.1 Request Headers Accept: 3./* Accept-Encoding:gzip, deflate Accept-Language: en-US,en;q=0.9 authorization:Bearer <redacted> Connection: keep-alive Host: 192.168.86.25:8123 Referer: http://192.168.86.25:8123/lovelace/home User-Agent:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.163 Safari/537.36 Query String Parameters start: 2020-04-08T00:00:00Z end: 2020-04-15T00:00:00ZTesting other api paths such as http://192.168.86.25:8123/api/config with the same Bearer key returns results as expected, but nothing for the calendar entities. Anyone more familiar with the REST API that can point me in the right direction?
Posts: 1
Participants: 1
@amkochaki wrote:
Hello people
I’m trying to connect an Arduino Mega Wemos with Wifi (esp8266-01) to ESPHome. I can connect the wifi of the card to EspHome but I would like to know if there is the possibility of Esp8266 making the interface so that ESPHome can control all 54 pins of the Arduino Mega card. If anyone can help I appreciate it.
Posts: 1
Participants: 1
@dirtdiver1977 wrote:
So I finally figured out how to cast some info on our Google cast device yet i’d like to know how to get it to actually read the sensor. This is what I have so far:
- alias: Climate Notification initial_state: true trigger: platform: state entity_id: sensor.livingroom_temperature condition: - condition: numeric_state entity_id: sensor.livingroom_temperature above: 80.0 action: - service: tts.google_say data: entity_id: media_player.bedroom_speaker message: "It's 80°F now in the living room. Close all doors and windows and turn on the AC."So where it says 80°F I try and place the sensor as so {{ states.sensor.livingroom_temperature.state }}°F and its not actually telling me the temp. Am I coding it wrong?
Posts: 3
Participants: 2
@JohnGalt1717 wrote:
Anyone know how to fix this?
I have the following:
- id: "1568290217758" alias: Websites are down and can't get back up again! trigger: - entity_id: device_tracker.web for: 00:07:00 from: home platform: state to: not_home condition: [] action: - data: message: Web server is down and can't get back up! title: Web server is down! service: notify.mobile_app_james_hancock_s_pixel_3_xlWhen this automation is executed now (it used to work) I get the following in the logs and no notification:
Logger: homeassistant.components.automation Source: components/mobile_app/notify.py:135 Integration: Automation ([documentation](https://www.home-assistant.io/integrations/automation), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+automation%22)) First occurred: 9:27:03 PM (1 occurrences) Last logged: 9:27:03 PM Router's Down and can't get back up!: Error executing script. Unexpected error for call_service at pos 1: 0, message='Attempt to decode JSON with unexpected mimetype: text/plain; charset=utf-8', url='https://us-central1-ha-client-c73c4.cloudfunctions.net/sendPushNotification Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 154, in _async_step self, f"_async_{cv.determine_script_action(self._action)}_step" File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 624, in _async_call_service_step *self._prep_call_service_step(), blocking=True, context=self._context File "/usr/src/homeassistant/homeassistant/core.py", line 1232, in async_call await asyncio.shield(self._execute_service(handler, service_call)) File "/usr/src/homeassistant/homeassistant/core.py", line 1255, in _execute_service await handler.func(service_call) File "/usr/src/homeassistant/homeassistant/components/notify/__init__.py", line 119, in async_notify_message await notify_service.async_send_message(**kwargs) File "/usr/src/homeassistant/homeassistant/components/mobile_app/notify.py", line 135, in async_send_message result = await response.json() File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 1031, in json headers=self.headers) aiohttp.client_exceptions.ContentTypeError: 0, message='Attempt to decode JSON with unexpected mimetype: text/plain; charset=utf-8', url='https://us-central1-ha-client-c73c4.cloudfunctions.net/sendPushNotificationWhat am I doing wrong?
Posts: 1
Participants: 1
@2ndchanceor wrote:
I have an orphaned Shelly HT sensor stuck in my 108.0 Hassio device list. I’m not seeing any apparent way to delete it.
(forgive my mask muffled voice)
Posts: 1
Participants: 1
@scpowered wrote:
Hello all,
Hopefully this is in the correct location. I have searched with no luck finding anyone with a similar issue.
Anytime I use the UI to setup/edit an automation or a script I am not able to scroll down in the drop-down menu to select an entity. It jumps back to the top. It seems to be a problem ONLY with the “call service” action type.
Example,
Action type = call service
Service = switch.turn_on
Name of entities = switch.bathroom_fan (this is the menu that has the problem)Has anyone else had this issue?
Running Ubuntu / Docker / Hassio
Thank you,
Sam
Posts: 1
Participants: 1
@stevemann wrote:
About a month ago I moved my Home Assistant to an Intel NUC. (Native in a docker container on Ubuntu). With some help, I got everything running. It looks great.
So, since everything appears to be working, I had no reason to look at the log files. But, today I did, and was surprised to see this:
“Error adding event: (sqlite3.DatabaseError) database disk image is malformed…message first occurred at April 2, 2020… and shows up 34079 times”
Is the fix as simple as just to delete home-assistant_v2.db from the config directory and restart HA?
Posts: 3
Participants: 2
@stevemann wrote:
Home Assistant 0.107.7
I added a panel_iframe: to my config.yaml, and when I went to CHECK CONFIGURATION, I got an error in another section that had been fine for months:
# Discover some devices automatically ("New Devices Discovered") discovery: ignore: - plex_mediaserver - google_castThe error is:
“Invalid config for [discovery]: value is not allowed @ data[‘discovery’][‘ignore’][0]. Got ‘plex_mediaserver’. (See /config/configuration.yaml, line 42).” [Line 42 is “discovery:”]So, what changed in “discovery” that I missed?
Posts: 4
Participants: 2
@aristosv wrote:
With version 0.108 released we saw plenty more integrations available to set up from the UI.
We also saw the Unifi manual integration being deprecated.
I was wondering if Home Assistant is gradually moving away from manual (yaml) configurations, to UI configurations?
I’m sure that’s fine for the majority of users, but some of you will agree that manual configuration is a much more satisfying learning experience, providing a lot more inside on how the integration’s options work, and perhaps giving a more granular way of configuring the integration.
Then again, I’m guessing the UI integrations also save their configurations in a file (xml?) that can be reviewed and tinkered with?
Anyway, I’m just thinking out loud here.
Two questions in this post, if you know their answers.
Thanks.
Posts: 1
Participants: 1
@Kamal_Krishna wrote:
Hi Guys,
I have Xiaomi sensors and Smartlife Switches at home currently integrated and working alright.
So i was looking at the recommened hardware and bought a Nortek HUSBZB-1 USB Hub
Now i can’t find a tutorial or a video to integrate it or use it to better my setup, could you please direct me toa tutorial, iam a noob so i will have to follow a step by step tutorial if there is one, please help. thanks.
Posts: 2
Participants: 2
@stevemann wrote:
Home Assistant 0.107.7
I added a panel_iframe for motioneye to my config.yaml:
panel_iframe: nodered: title: Node-RED icon: mdi:sitemap url: http://192.168.1.54:1880 motioneye: title: Motion Eye icon: mdi:cctv url: http://192.168.1.54:8123/hassio/ingress/a0d7b954_motioneyeWhy am I getting two sidebars?
Posts: 1
Participants: 1
@Tom7320 wrote:
Hi
I have a problem with the telegram bot. This message is in the log approximately two times per minute:
2020-04-09 07:22:54 ERROR (updater) [telegram.ext.updater] Error while getting Updates: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running (409)I do not have Node-RED running! I configured Telegram bot like this:
telegram_bot: - platform: polling api_key: !secret telegram_api_key allowed_chat_ids: - !secret telegram_chat_id notify: - platform: telegram name: telegram chat_id: !secret telegram_chat_idI send messages from automations.yaml like this:
action: - service: notify.telegram data: message: "Test message"So there should be really only one instance running! How can I fix that (HASS 0.108)?
Thx a lot!
Posts: 1
Participants: 1
@fribse wrote:
I’ve had NUT set up for a while as a sensor, I’ve even built a nice card for it, it has worked without a problem.
Now with 0.108 it’s moved to an integration, and that doesn’t work for the NUT service on the qnap, so what has changed in the way the integration is done?
Also I seem to be missing ups.mfr and ups.model from the features list (which I used in my card).The config as a sensor:
- platform: nut name: UPS Battery backup host: 1.2.3.4 username: qnapups password: 123456 resources: - ups.status.display - ups.load - ups.realpower.nominal - ups.mfr - ups.model - input.voltage - battery.charge - battery.runtimeIf I enter this into the integration, I just get a Failed to connect, please try again
As I only have one UPS connected to the QNAP, I haven’t set the alias.
Posts: 1
Participants: 1
@Gerlad wrote:
After installing homeassistant to a pi4 and adding the Somfy stuff, I can not see the sun/light detector and neither the szenario player and the smoove switches.
What can I do or are those sensors and switches not implemented ?
Posts: 1
Participants: 1
@fr00kt wrote:
Can I connect the Xiaomi Mijia 1C Sweeping Vacuum Cleaner (white) (STYTJ01ZHM) to the Home Assistant?
Posts: 1
Participants: 1
@gezuka77 wrote:
Hi,
I am trying to add some of my cameras with picture card and I am getting the following error:
Picture Entity Card Configuration
ChunkLoadError: Loading chunk 73 failed. (error: http://192.168.107.79:8123/frontend_latest/chunk.56383f1c825b131b8bf1.js)
SHOW VISUAL EDITOR
Anyone seen such a thing?
Posts: 1
Participants: 1
@iz3man wrote:
I use Tasmota for ages now, upgraded them some time ago to fw v8.x and since then it shows THREE values for total power on my Sonoff POWs.
You see ENERGY Today is totally fine, showing today’s kWh.
But the line below has 3 Values of which the first one is TOTAL POWER, but what are the other two. I searched a lot, but can’t find that info.I guess showing the first value needs some value_template sensor, correct?
Posts: 1
Participants: 1
@Kalenden wrote:
Hi,
I am trying to get a message to play on a Google Home Mini Speaker through a script.
If I manually trigger the script in the lovelace interface, I hear a bell/chime sound on my Google Mini Speaker but it does not play the .mp3 file. If I look at the state of the speaker in Developer Tools, it shows the .mp3 file url. I can play this mp3 file using my browser on my laptop (internal network) and smartphone (through 4G external network).
I use duckdns and am behind a VPN but have configured it so that the port 8123 is forwarded through, hence all other google assistant/home commands work.
Anyway, I have no clue why it works. Could you help?I have the following configuration in configuration.yml
http: #api_password: !secret http_password # from file secrets.yaml base_url: https://<DUCKDNS_NAME>.duckdns.org:8123 ssl_certificate: /ssl/fullchain.pem ssl_key: /ssl/privkey.pem # Text to speech tts: - platform: google_translate service_name: google_say cache: true cache_dir: /tmp/tts time_memory: 300 base_url: https://<DUCKDNS_NAME>.duckdns.org:8123And the following script:
playlist_announce: sequence: - service: tts.google_say data_template: entity_id: media_player.office_speaker message: "this is message6"After executing the script, the state of my media_player.office_speaker is as follows:
volume_level: 0.5 is_volume_muted: false media_content_id: >- https://<DUCKDNS_NAME>.duckdns.org:8123/api/tts_proxy/a19166c06d9c49f401b6b3799c84fcd130fe45bc_en_-_google_translate.mp3 media_position: 0 media_position_updated_at: '2020-04-09T09:43:58.559710+00:00' app_id: CC1AD845 app_name: Default Media Receiver entity_picture_local: null friendly_name: Office Speaker supported_features: 21391The above media_content_id can be played on both laptop and smartphone.
So I am flabbergasted what the issue might be. Any help?
Posts: 1
Participants: 1
I have an orphaned Shelly HT sensor stuck in my 108.0 Hassio device list. I’m not seeing any apparent way to delete it. 
