New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turning on MQTT services breaks HomeAssistant image retrieval #638

Open
daj102 opened this Issue Aug 12, 2018 · 101 comments

Comments

Projects
None yet
@daj102
Copy link

daj102 commented Aug 12, 2018

I have a WyzeCam v2 that I've just flashed with the most recent version of the firmware (PR #629 seems to be the latest that was merged in on Aug 9th). Things are fine when I start the camera, connect to wifi and then use the HomeAssistant guide to set up an ffmpeg camera. HA shows the camera fine using the rtsp address, VLC works, the camera website is working - all good.

Except, when I turn on either the MQTT Control or Status services, the HA camera stops working and I get the dreaded "Timeout reading image" message in the HA log. I'm sure I've correctly set up the HA configuration because when the Control and Status services are on, I can control the camera from HA, and HA can see the MQTT messages about motion (even the snapshot is shown correctly in HA). The issue is the main ffmpeg camera ... I can still see the feed fine from the camera website, and I've used VLC to stream it directly and it works great. For some reason, though, the HA timeout message occurs whenever the MQTT services are on. I've turned them off and rebooted the camera, and HA starts working again - I can reliably replicate the issue.

I don't know what logs to post though; none of the ones that I can see in the camera website seem to even mention MQTT. My HA config is here if you want to check it over: https://github.com/daj102/homeassistant/tree/miller_hill_cleanup/homeassistant

Thanks for all your work on this - I really appreciate the ability to integrate the camera into HomeAssistant!

@shreram

This comment has been minimized.

Copy link

shreram commented Aug 13, 2018

I have the same issue. In my case, HomeAssistant discovered only the camera entity.

From Home Assistant log file: (edit: additional information)

2018-08-12 20:28:04 DEBUG (MainThread) [haffmpeg.core] Start FFmpeg with ['ffmpeg', '-rtsp_transport', 'tcp', '-i', 'rtsp://192.168.1.2:8554/unicast', '-an', '-frames:v', '1', '-c:v', 'mjpeg', '-f', 'image2pipe', '-']

2018-08-12 20:28:19 WARNING (MainThread) [haffmpeg.core] Timeout while waiting of FFmpeg

2018-08-12 20:28:19 WARNING (MainThread) [haffmpeg.tools] Timeout reading image..
@johansvenson

This comment has been minimized.

Copy link

johansvenson commented Aug 15, 2018

Same issue here...

@jmtatsch

This comment has been minimized.

Copy link
Collaborator

jmtatsch commented Aug 15, 2018

I have exactly the same timeouts in HA, but also for other ffmpeg cameras. I guess my old home server is too slow to deal with several of these streams at the same time.

@daj102

This comment has been minimized.

Copy link
Author

daj102 commented Aug 15, 2018

@bachya

This comment has been minimized.

Copy link

bachya commented Aug 16, 2018

Same here. Running HASS in a Docker container on a more-than-powerful NUC.

For what it's worth, I've tried running the same FFmpeg command used by HASS in the container (with debug-level logging); I don't get much back that would explain what the feed is hanging:

root@hub:/usr/src/app# ffmpeg -rtsp_transport tcp -i rtsp://garage-camera:8554/unicast -an -frames:v 1 -c:v mjpeg -f image2pipe - -loglevel debug
ffmpeg version N-91594-g00ae349 Copyright (c) 2000-2018 the FFmpeg developers
  built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516
  configuration: --prefix=/usr/src/app/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/usr/src/app/ffmpeg_build/include --extra-ldflags=-L/usr/src/app/ffmpeg_build/lib --extra-libs='-lpthread -lm' --bindir=/usr/local/bin --enable-gpl --enable-libass --enable-libfreetype --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree
  libavutil      56. 19.100 / 56. 19.100
  libavcodec     58. 22.101 / 58. 22.101
  libavformat    58. 17.101 / 58. 17.101
  libavdevice    58.  4.101 / 58.  4.101
  libavfilter     7. 26.100 /  7. 26.100
  libswscale      5.  2.100 /  5.  2.100
  libswresample   3.  2.100 /  3.  2.100
  libpostproc    55.  2.100 / 55.  2.100
Successfully parsed a group of options.
Parsing a group of options: input url rtsp://garage-camera:8554/unicast.
Successfully parsed a group of options.
Opening an input file: rtsp://garage-camera:8554/unicast.
[tcp @ 0x5587e10f4c80] No default whitelist set
@shreram

This comment has been minimized.

Copy link

shreram commented Aug 18, 2018

@bachya I just upgraded to HA to 0.76.0 and now the camera is working again with MQTT (Status Server and Control Server). I am not sure if something was fixed in latest HA release. Btw, I kept my Wyze in the garage too. :)

2018-08-18 00:48:37 DEBUG (MainThread) [haffmpeg.core] Start FFmpeg with ['ffmpeg', '-rtsp_transport', 'tcp', '-i', 'rtsp://192.168.86.248:8554/unicast', '-an', '-frames:v', '1', '-c:v', 'mjpeg', '-f', 'image2pipe', '-']
@bachya

This comment has been minimized.

Copy link

bachya commented Aug 18, 2018

@shreram Unfortunately, mine is still sporadic: sometimes it works right away, but other times, I have to disable MQTT on the camera, restart HASS, wait for the image to show up, the re-enable MQTT.

@goermezer

This comment has been minimized.

Copy link

goermezer commented Aug 18, 2018

I don`t know, if it is a bit too heavy to send the whole image file through MQTT. I had a similar problem with mqttfx, whenever motion happened. So I decided to comment out the image transfer through MQTT in /system/sdcard/scripts/detectionOn.sh :

 #if [ "$save_snapshot" = true ] ; then
        #/system/sdcard/bin/mosquitto_pub.bin -h "$HOST" -p "$PORT" -u "$USER" -P "$PASS" -t "${TOPIC}"/motion/snapshot ${MOSQUITTOOPTS} ${MOSQUITTOPUBOPTS} -f "$save_dir/$filename"
 #fi
@shreram

This comment has been minimized.

Copy link

shreram commented Aug 18, 2018

@bachya Yes, I spoke too soon. I noticed the same issue. Camera displays in HA for a few minutes then images disappears then appears back again after some time. Do you have any automation to trigger if the image is not shown in HA?

Btw, apart from camera.garage_camera (defang) entity, I noticed another entity 'camera.dafang_motion_snapshot'. What's the use of this?

{
  "access_token": "##hash##",
  "friendly_name": "dafang motion snapshot",
  "entity_picture": "/api/camera_proxy/camera.dafang_motion_snapshot?token=##hash##",
  "supported_features": 0
}
@daj102

This comment has been minimized.

Copy link
Author

daj102 commented Aug 18, 2018

@bachya

This comment has been minimized.

Copy link

bachya commented Aug 18, 2018

@goermezer That same effect can be achieved by setting save_snapshot=false in /system/sdcard/config/motion.conf. I have this setting in place and unfortunately, the same flakiness occurs.

@shreram

Do you have any automation to trigger if the image is not shown in HA?

Negative; I supposed I could, but I would rather just have a consistent image. 😆On top of that, my previous comment makes it sound like it's easy to re-establish the feed by switching off MQTT, restarting HASS, and re-enabling MQTT, but even that isn't consistent.

@goermezer

This comment has been minimized.

Copy link

goermezer commented Aug 18, 2018

@bachya Not exactly. I leave this line activated:

/system/sdcard/bin/mosquitto_pub.bin -h "$HOST" -p "$PORT" -u "$USER" -P "$PASS" -t "${TOPIC}"/motion ${MOSQUITTOOPTS} ${MOSQUITTOPUBOPTS} -m "ON"

Then I still get the motion message, but no more images transfered through MQTT.

@bachya

This comment has been minimized.

Copy link

bachya commented Aug 18, 2018

@goermezer Ah, got it. Are you finding that helps with stability?

@goermezer

This comment has been minimized.

Copy link

goermezer commented Aug 18, 2018

@bachya I don`t use Homeassistant. In my case the image transfer via mqtt caused mqttfx to crash. So I thought, this could probably the reason for the issue of @daj102.

@daj102

This comment has been minimized.

Copy link
Author

daj102 commented Aug 27, 2018

Just to close this thread out; I've recently upgraded my HomeAssistant Docker container to 0.77.0b1 ... and I can enable both MQTT services with no problem on the camera. I haven't updated the firmware, so I guess this was an HA problem rather than the camera. Thanks to all for the suggestions!

@daj102 daj102 closed this Aug 27, 2018

@bachya

This comment has been minimized.

Copy link

bachya commented Aug 27, 2018

@daj102 Seems a little premature to close this out, especially since you're running a HASS beta (and considering my comment above, in which FFmpeg itself seemed to hang); might be a good idea to leave it open until (a) 0.77 proper is released and (b) a few others (myself included) have a chance to test and confirm?

@daj102

This comment has been minimized.

Copy link
Author

daj102 commented Aug 27, 2018

@bachya OK fair enough; I am trying a few versions and this worked on 0.76.2 as well ... but I'll reopen for comments. Thanks.

@daj102 daj102 reopened this Aug 27, 2018

@bachya

This comment has been minimized.

Copy link

bachya commented Aug 30, 2018

Just upgraded to Home Assistant 0.77 and this issue is still present.

@daj102

This comment has been minimized.

Copy link
Author

daj102 commented Aug 30, 2018

I've just upgraded to 0.77.0 too ... and it is still working :-/ Am getting the live image through, as well as the MQTT status information such as light level, control settings, etc.

@bachya - what version of the camera firmware are you running? I updated maybe a week ago; I've been trying to find a version or build number from the camera but blowed if I can track it down. The footer does not have a version number, and the dmesg is somewhat overwhelming to someone not used to developing in Linux. If you have any pointers, am willing to send debug info either from the camera or HA to see if that helps track it down ...

@bachya

This comment has been minimized.

Copy link

bachya commented Aug 30, 2018

@daj102: So strange. I'm using 2018-08-27T16:45:55Z on a Wyze V2.

EDIT: apologies, didn't fully read your message. If you can FTP/SSH into the camera, you can find the version here: /system/sdcard/.lastCommitDate

@bachya

This comment has been minimized.

Copy link

bachya commented Aug 31, 2018

More information – very localized, but maybe it'll help.

I've noticed that with MQTT turned on, sometimes, I am unable to SSH into the Wyze V2 from within my Home Assistant Docker container. Turn MQTT services off, reboot, and suddenly SSH works again.

@daj102

This comment has been minimized.

Copy link
Author

daj102 commented Aug 31, 2018

The strange gets worse; when I remote in to my camera, I get this:

[root@WyzeCamera_FamilyRoom:~]# more /system/sdcard/.lastCommitDate
more: /system/sdcard/.lastCommitDate: No such file or directory

so I can't tell you which version I have :) I was wondering why the version is blank in all the UI places I was checking ...

I've also noticed that while the main camera feed is working, motion detection is not sending anything to the MQTT topic. I'll try updating the firmware to the latest (looks like it updates motion detection, interestingly) and report back.

UPDATE: I SSHed in and ran the autoupdate.sh, and now I have version 2018-08-27T16:45:55Z. And pleased/sorry to say that it is still working with HA. I also realized I hadn't updated motion.conf with the latest firmware application, so set the publish_mqtt_message to true - viola, working.

@bachya

This comment has been minimized.

Copy link

bachya commented Aug 31, 2018

@daj102 Thanks for walking through this with me. To confirm: you have Wyze v2?

Only alterations I can think of:

@daj102

This comment has been minimized.

Copy link
Author

daj102 commented Aug 31, 2018

@bachya

This comment has been minimized.

Copy link

bachya commented Aug 31, 2018

I hate to say it, but it sounds like I need to work my way through all three of these and confirm/deny them as the culprit. Will follow up once I have more.

@guandalf

This comment has been minimized.

Copy link

guandalf commented Sep 11, 2018

Hi,

I've got the same issue here.
I run hassos 1.10 (32 bit) on an RPi 3b+. HA version 0.77.3.
As soon as I turn on mqtt_control and mqtt_status, the image retrieval from homeassistant breaks. Switching them off fixes the issue.
Let me know if I can help in some way. TY

@jmtatsch

This comment has been minimized.

Copy link
Collaborator

jmtatsch commented Sep 11, 2018

Likely related to #675

@alexdelifer

This comment has been minimized.

Copy link

alexdelifer commented Nov 30, 2018

edit: nope, still failed with --net=host when I checked in the morning.
Both zoneminder and home assistant aren't able to load the rtsp stream.

Looks like --net=host mode has been running for ~4 hours with no fail, gonna leave it overnight and see. I don't have all my camera's on this container though, keeping some on the pi as a "control". I've also played with the motor controls + ir led through mqtt to try to spam mqtt messages.

I'm still getting lots of connect/disconnect messages being spammed to the mosquitto.log, not sure if that's how it's supposed to be.


1543549142: New connection from 10.10.10.26 on port 1883.
1543549142: New client connected from 10.10.10.26 as mosqpub|23522-DAFANG (c1, k60, u'alex').
1543549142: Client mosqpub|23522-DAFANG disconnected.
1543549142: New connection from 10.10.10.26 on port 1883.
1543549142: New client connected from 10.10.10.26 as mosqpub|23527-DAFANG (c1, k60, u'alex').
1543549142: Client mosqpub|23527-DAFANG disconnected.
1543549142: New connection from 10.10.10.26 on port 1883.
1543549142: New client connected from 10.10.10.26 as mosqpub|23534-DAFANG (c1, k60, u'alex').
1543549142: Client mosqpub|23534-DAFANG disconnected.
1543549142: New connection from 10.10.10.26 on port 1883.
1543549142: New client connected from 10.10.10.26 as mosqpub|23537-DAFANG (c1, k60, u'alex').
1543549142: Client mosqpub|23537-DAFANG disconnected.
1543549142: New connection from 10.10.10.26 on port 1883.
1543549142: New client connected from 10.10.10.26 as mosqpub|23539-DAFANG (c1, k60, u'alex').
1543549142: Client mosqpub|23539-DAFANG disconnected.
1543549142: New connection from 10.10.10.26 on port 1883.
1543549142: New client connected from 10.10.10.26 as mosqpub|23542-DAFANG (c1, k60, u'alex').
1543549142: Client mosqpub|23542-DAFANG disconnected.
1543549142: New connection from 10.10.10.26 on port 1883.
1543549142: New client connected from 10.10.10.26 as mosqpub|23547-DAFANG (c1, k60, u'alex').
1543549142: Client mosqpub|23547-DAFANG disconnected.
1543549142: New connection from 10.10.10.26 on port 1883.
1543549142: New client connected from 10.10.10.26 as mosqpub|23550-DAFANG (c1, k60, u'alex').
1543549142: Client mosqpub|23550-DAFANG disconnected.
1543549142: New connection from 10.10.10.26 on port 1883.
1543549142: New client connected from 10.10.10.26 as mosqpub|23557-DAFANG (c1, k60, u'alex').
1543549142: Client mosqpub|23557-DAFANG disconnected.
1543549143: New connection from 10.10.10.26 on port 1883.

@daj102

This comment has been minimized.

Copy link
Author

daj102 commented Nov 30, 2018

@bachya I think you might be on to something ... I just restarted my Docker containers with the host network mode for both HA and Mosquitto. I can now enable the MQTT Status and Control services and I'm still seeing the picture come through ... however, I am getting the constant MQTT disconnect/reconnect too (similar to @alexdelifer ) and none of the sensors and switches are coming through. I've tried rebooting the camera, restarting the containers multiple times ... picture still good, controls not so much.

@GerardRibas

This comment has been minimized.

Copy link

GerardRibas commented Dec 5, 2018

I'm having the same problem, after a few hours running ok, then it starts to hang. Only message strange in HA logs is: WARNING (MainThread) [haffmpeg.tools] Timeout reading image. but nothing in the Dafang Side.

Restarting rtsp-h264 service HA then shows the image again.

I'm running HA in docker (with network mode host) and mosquitto on the same machine (i5-6500 with 16GB of ram)

@guandalf

This comment has been minimized.

Copy link

guandalf commented Dec 8, 2018

Don't ask me how it happened but now I can see the rtsp streaming on HA (hassos) v0.83.3 on RPi3b+ Dafang hacks: : 2018-12-01T10:13:24Z

@RolfKoenders

This comment has been minimized.

Copy link

RolfKoenders commented Dec 9, 2018

@guandalf With MQTT enabled? The issue is that its not showing the stream when MQTT options are enabled. Without it the stream works fine.

@guandalf

This comment has been minimized.

Copy link

guandalf commented Dec 10, 2018

@RolfKoenders

This comment has been minimized.

Copy link

RolfKoenders commented Dec 10, 2018

@guandalf Thanks for the update. Will try it again as well. Lets see!

@RolfKoenders

This comment has been minimized.

Copy link

RolfKoenders commented Dec 10, 2018

I can confirm that after enabling MQTT status and Control the streams are after 12 hours still working smooth on Hass.io v0.83.3 RPi3b+.
@guandalf 👍

@pullaf

This comment has been minimized.

Copy link

pullaf commented Dec 14, 2018

Are you guys running Mosquitto or something else?
I'm on HASSIO 0.84.1 with the Mosquitto add-on and I'm getting the failed video+image thing
Which settings are you using on the camera?

@cristimi

This comment has been minimized.

Copy link

cristimi commented Dec 27, 2018

Hi, I am running 0.83.3 and mosquitto add-on and I am having the issue as well. Plus, I am not getting any information over mqtt. Are you getting info over mqtt when having this issue? I am thinking that they are related somehow. When I changed the broker to a public broker for test purposes, the image refresh started again but still no success in getting Mqtt information.

@guandalf

This comment has been minimized.

Copy link

guandalf commented Dec 28, 2018

@winterscar

This comment has been minimized.

Copy link

winterscar commented Jan 2, 2019

Just my 2c:
I'm having the same issue with the same configuration (hass + mosquitto in docker)

I'm struggling to think how an mqtt message received in one docker container could mess with ffmpeg in another container.

It seems to me like the problem is more likely to be on the wyze cam side of things, and maybe how that interacts with the mqtt server specifically when its running in docker.

@funkypenguin

This comment has been minimized.

Copy link

funkypenguin commented Jan 2, 2019

My issue may be different to yours, but I've noticed that when it happens, although I can ping the camera from hassio, I can't establish any TCP connection. No SSH banner on port 22, no response to curl, nothing. If I change the camera's IP (I know, right?), or reboot hassio, TCP connectivity sometimes recovers, but I still get timeouts using either ffmpeg or generic still images in hassio.

@UYKV878ogfvkhc

This comment has been minimized.

Copy link

UYKV878ogfvkhc commented Jan 5, 2019

Same issue. turning on MQTT crashes camera feed. It has been going since I got the Wyze cams. I am connecting using the generic camera in home assistant. I have also used the platform: ffmpeg camera with RTSP feed and had the same problem.

Current setup = hassio 1.13 64bit + mosquitto + HA 0.84.6 + Wyze v2 Dafang Version: 2018-12-30T20:06:37Z

- platform: generic
    name: DaFang0
    username: root
    password: ismart12
    authentication: basic
    still_image_url: https://dafang.local/cgi-bin/currentpic.cgi
    verify_ssl: false
    scan_interval: 5

also using mqtt option on the camera
MOSQUITTOOPTS="-V mqttv311"

@mon3y78

This comment has been minimized.

Copy link

mon3y78 commented Jan 6, 2019

I nave the same issue with rasbian + hass.io

@winterscar

This comment has been minimized.

Copy link

winterscar commented Jan 6, 2019

Might this have anything to do with #675 ? Possibly the reading of incoming messages is breaking something.

I'll try flash this pull requesttomorrow to see if that helps.

@alex-phillips

This comment has been minimized.

Copy link

alex-phillips commented Jan 10, 2019

I have this issue as well. It seems to not just affect image retrieval, but accessing the web server at all, SSH, and rtsp. It seems to affect only SOME devices at a single time, i.e., my server isn't able to connect but at the same time my laptop is.

It looks like disabling mqtt completely fixes the problem?

@radinsky

This comment has been minimized.

Copy link

radinsky commented Jan 16, 2019

Is there anything new on this issue?
Validated now on Version: 2019-01-05T19:32:18Z it still exist, once I start the mqtt service (status) I can't retrieve the image from the homeassistant and actually i can't connect to the camera from the HA server at all. Once restarted without mqtt the image retrieving, ssh and web from HA server work fine (until i turn on the mqtt status server again).

@jmtatsch

This comment has been minimized.

Copy link
Collaborator

jmtatsch commented Jan 16, 2019

Maybe someone can try to transplant a new mqtt binary from openfang.

@asifma

This comment has been minimized.

Copy link

asifma commented Jan 25, 2019

Also have the same issue...

@ravensteijn

This comment has been minimized.

Copy link

ravensteijn commented Jan 26, 2019

My setup :hassio 0.84 and mosquitto, Xiaofang.
I had the same issue with mqtt. I added the hassio addon motioneye removed the rtsp stream directly to hassio and the problems were gone. Mqtt status and control are now back on. Mqtt Motion detection and mqtt images are off.
I use motioneye for motiondetection and autorecording on motion and use picturestream in homeassistant through motioneye. Benefit of motioneye is the local recording. It's super easy install thanks to hassio community add-ons from frenk
I used this curl line in motioneye for motion detection in home assistant
https://community.home-assistant.io/t/motioneye-home-assistant-camera-motion-automation/41712/62

@UYKV878ogfvkhc

This comment has been minimized.

Copy link

UYKV878ogfvkhc commented Jan 28, 2019

I have upgraded to HA 0.86.3 and Dafang Hacks Version: 2019-01-05T19:32:18Z
and all the mqtt is working with motion snapshot too.

I have several Wyze v2 cams with Dafang Hacks. When I turn on mqtt on more than one camera at a time then the second camera is breaking. Having mqtt on one camera working seems like progress. Does this mean that there is some issue with duplicate mqtt messages from multiple cameras?

- platform: generic
    name: DaFang0
    username: root
    password: ismart12
    authentication: basic
    still_image_url: https://dafang.local/cgi-bin/currentpic.cgi
    verify_ssl: false
    scan_interval: 5

also using mqtt option on the camera
MOSQUITTOOPTS="-V mqttv311"

Current setup = hassio 1.13 64bit + mosquitto + HA 0.86.3 + Wyze v2 Dafang Version: 2019-01-05T19:32:18Z

@jmtatsch

This comment has been minimized.

Copy link
Collaborator

jmtatsch commented Jan 28, 2019

@UYKV878ogfvkhc do your cameras have different camera names defined in mqtt.confs?

@UYKV878ogfvkhc

This comment has been minimized.

Copy link

UYKV878ogfvkhc commented Jan 28, 2019

@jmtatsch yes they are all named differently in mqtt.conf. I did wonder if the snapshot function has a independent config for calling mosquitto_pub? The snapshot mqtt seems to work sometimes when mqtt control and server are off.

@jmtatsch

This comment has been minimized.

Copy link
Collaborator

jmtatsch commented Jan 28, 2019

@UYKV878ogfvkhc then you should connect to your broker with mosquitto_sub and listen if all cameras are separated properly.
I have a feeling this might have to do with the recent enabling of device registries in home assistants mqtt. Please also check if the autoconf ids for all your devices are different.

@UYKV878ogfvkhc

This comment has been minimized.

Copy link

UYKV878ogfvkhc commented Feb 2, 2019

@jmtatsch mosquitto_sub shows the topics are uniquely named for each camera.
puttyputtyputty is shown at the end of the snapshot mqtt message and does not line break before the next message of motion off.

YPuTTYPuTTYPuTTYPuTTYPuTTYhome0/dafang/motion OFF

in home assistant the core.entity_registry file entry for snapshot has "device_id": null, when the other mqtt entities all have "device_id": "camera's id" associated with them. I edited the core.entity_registry file to add the device_id for each camera to the snapshot section, home assistant changes it back to null on reboot.

other than snapshot every mqtt entry from the cameras seems to be populated and has unique unique_id numbers.

@jmtatsch

This comment has been minimized.

Copy link
Collaborator

jmtatsch commented Feb 2, 2019

In our autodiscovery setup Script, the Unique id is probably missing. Try adding it and it could work.

@UYKV878ogfvkhc

This comment has been minimized.

Copy link

UYKV878ogfvkhc commented Feb 2, 2019

After a few reboots of home assistant all the cameras are working for me.

@jmtatsch

This comment has been minimized.

Copy link
Collaborator

jmtatsch commented Feb 2, 2019

Was the unique id missing from the autodiscovery Script? If yes please prepare a pull request to fix the issue.

@UYKV878ogfvkhc

This comment has been minimized.

Copy link

UYKV878ogfvkhc commented Feb 3, 2019

The snapshot entity in the core.entity_registry file still has a device_id as null, but does not seem to be a problem as there is a unique_id for snapshot. I think the update and reboot of home assistant solved the mqtt issues. I would agree the "recent enabling of device registries in home assistants mqtt" seems to be the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment