Camera feed not detected after setup.

I am working with a wired doorbell, T8200. After the installation, three new entities were added, person detector sensor, battery & wifi ssid power. The battery entity was unavailable, as it makes sens with the wired doorbell, there is no battery. wifi ssid sensor was unavailable too. And I had no luck getting the stream from the doorbell camera.

Some log lines:

2021-07-18 12:16:49 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Exception in websocket - process_messages : 'battery' - traceback: Traceback (most recent call last): File "/config/custom_components/eufy_security/websocket.py", line 55, in process_messages await self.on_message(msg) File "/config/custom_components/eufy_security/websocket.py", line 66, in on_message await self.message_callback(message) File "/config/custom_components/eufy_security/coordinator.py", line 165, in on_message self.async_set_updated_data(self.data) File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 287, in async_set_updated_data update_callback() File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 325, in _handle_coordinator_update self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 419, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 453, in _async_write_ha_state state = self._stringify_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 425, in _stringify_state state = self.state File "/config/custom_components/eufy_security/sensor.py", line 86, in state return self.entity[self.key] KeyError: 'battery'

2021-07-18 12:12:43 ERROR (MainThread) [homeassistant.components.camera] Error while setting up eufy_security platform for camera Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 250, in _async_setup_platform await asyncio.shield(task) File "/config/custom_components/eufy_security/camera.py", line 34, in async_setup_entry _LOGGER.debug(f"{DOMAIN} - camera setup entries - {entities}") File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 803, in __repr__ return f"<Entity {self.name}: {self.state}>" File "/config/custom_components/eufy_security/camera.py", line 74, in state self.is_streaming = self.entity["rtspStream"] KeyError: 'rtspStream'

yes, i am working on it, let's follow from here, i will publish an update tonight in EU time :)
https://github.com/fuatakgun/eufy_security/issues/6

ops, let's reopen it to track battery and WIFI sensors

Sure thing. Thank you, will keep an eye on this issue.

Just installed it today with the custom integration.  Two cameras were detected and one doorbell.  All of them have various sensors, etc.  None of them show as having an entity ID as camera.XXX
BTW...excellent progress!  Happy that I don't need to install a Docker.

Same here; was happy to see that my 2k Floodlight cam was detected along with my cams, but no camera entities for any of them.
Still though; following the directions given, the install went great and the progress is amazing.  Thanks for the work! Hoping this will replace ioBroker for my setup!

I tried installing everything fresh again after your recent commit and followed the instruction there. The problem with the camera not being detected is still there along with wifi_rssi sensor being unavailable and the doorbell_battery sensor unavailable as well. (I have a wired version - T8200)
The only sensor that seems to populate after the installation of the integration is the Person Detection Sensor.
Here are my log files.
2021-07-22 08:33:00 ERROR (MainThread) [homeassistant.components.camera] Error while setting up eufy_security platform for camera
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 250, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/eufy_security/camera.py", line 76, in async_setup_entry
_LOGGER.debug(f"{DOMAIN} - camera setup entries - {entities}")
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 803, in __repr__
return f"<Entity {self.name}: {self.state}>"
File "/config/custom_components/eufy_security/camera.py", line 124, in state
self.entity["rtspStream"] == True
KeyError: 'rtspStream'

2021-07-22 08:33:00 ERROR (MainThread) [homeassistant.components.sensor] Error adding entities for domain sensor with platform eufy_security
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 383, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 588, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 666, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 419, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 453, in _async_write_ha_state
state = self._stringify_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 425, in _stringify_state
state = self.state
File "/config/custom_components/eufy_security/sensor.py", line 86, in state
return self.entity[self.key]
KeyError: 'battery'

2021-07-22 08:33:00 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up eufy_security platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 258, in _async_setup_platform
await asyncio.gather(*pending)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 383, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 588, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 666, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 419, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 453, in _async_write_ha_state
state = self._stringify_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 425, in _stringify_state
state = self.state
File "/config/custom_components/eufy_security/sensor.py", line 86, in state
return self.entity[self.key]
KeyError: 'battery'
2021-07-22 08:33:01 ERROR (MainThread) [custom_components.eufy_security] eufy_security - Exception - process_messages : 'battery' - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/websocket.py", line 65, in process_messages
await self.on_message(msg)
File "/config/custom_components/eufy_security/websocket.py", line 81, in on_message
await self.message_callback(message)
File "/config/custom_components/eufy_security/coordinator.py", line 170, in on_message
self.async_set_updated_data(self.data)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 287, in async_set_updated_data
update_callback()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 325, in _handle_coordinator_update
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 419, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 453, in _async_write_ha_state
state = self._stringify_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 425, in _stringify_state
state = self.state
File "/config/custom_components/eufy_security/sensor.py", line 86, in state
return self.entity[self.key]
KeyError: 'battery'

2021-07-22 08:33:01 ERROR (MainThread) [homeassistant.components.binary_sensor] eufy_security: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 432, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 601, in async_device_update
await task
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 336, in async_update
await self.coordinator.async_request_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 141, in async_request_refresh
await self._debounced_refresh.async_call()
File "/usr/src/homeassistant/homeassistant/helpers/debounce.py", line 78, in async_call
await task
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 165, in async_refresh
await self._async_refresh(log_failures=True)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 265, in _async_refresh
update_callback()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 325, in _handle_coordinator_update
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 419, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 453, in _async_write_ha_state
state = self._stringify_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 425, in _stringify_state
state = self.state
File "/config/custom_components/eufy_security/sensor.py", line 86, in state
return self.entity[self.key]
KeyError: 'battery'

Adding some log data to this.   Eufy 2k indoor cameras
Logger: homeassistant.components.stream.worker
Source: components/stream/worker.py:215
Integration: Stream (documentation, issues)
First occurred: 3:55:58 PM (42 occurrences)
Last logged: 4:05:54 PM

Error opening stream None

No stream under any circumstances, including when start stream service command is issued.

Adding some log data to this. Eufy 2k indoor cameras
Logger: homeassistant.components.stream.worker
Source: components/stream/worker.py:215
Integration: Stream (documentation, issues)
First occurred: 3:55:58 PM (42 occurrences)
Last logged: 4:05:54 PM

Error opening stream None

No stream under any circumstances, including when start stream service command is issued.

can you confirm that you have enabled rtsp stream from camera? i believe supports rtsp.

Adding some log data to this. Eufy 2k indoor cameras
Logger: homeassistant.components.stream.worker
Source: components/stream/worker.py:215
Integration: Stream (documentation, issues)
First occurred: 3:55:58 PM (42 occurrences)
Last logged: 4:05:54 PM

Error opening stream None

No stream under any circumstances, including when start stream service command is issued.

can you confirm that you have enabled rtsp stream from camera? i believe supports rtsp.

Confirmed
Setting screenshot: https://i.imgur.com/j51XPp4.png

if you can enable excessive logging for the integration and share the logs, i could have a deep dive investigation.
logger:
  default: warning
  logs:
    custom_components.eufy_security: debug
    haffmpeg.core: debug
    ffmpeg: debug

See attached logs
logs.txt

See attached logs
logs.txt

Can you confirm you have the latest codebase?

Installed everything 21 July...certainly can update to make sure code is current.

Latest codebase here (f948623)  please see attached log.
Issued the service call to start streams on all devices at 2021-07-23 10:38:26.   Something very obviously changed when that was issued as the logging blew up (truncated the log slightly after that for size), but still no livestream.
log:
home-assistant.txt

Installed everything 21 July...certainly can update to make sure code is current.

ancient history by fuat's coding speed :D   i think theres been three revs since then.

Finally, with the latest update, I was able to get the camera entity along with Motion Sensor, Person Detector Sensor, Ringing Sensor. But, the camera entity fails to start the live stream. I do get a still image when there is an event, but unable to start the live feed.
There seem to be tons of eufy_security strings in the log file.

File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
BrokenPipeError: [Errno 32] Broken pipe
2021-07-23 11:50:43 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:43 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:43 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:43 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (stream_worker) [homeassistant.components.stream.worker] Error opening stream eufy_security-T8200N001939068F.m3u8
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:44 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (Thread-22) [pychromecast.socket_client] [Play Area speaker(<IP_ADDRESS>):8009] Failed to connect to service ServiceInfo(type='mdns', data='Google-Home-Mini-53650d3cd8b0a82b5c01e1e7b6d47b9b._googlecast._tcp.local.'), retrying in 5.0s
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:45 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:46 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:46 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:46 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:46 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:46 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:46 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:46 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:46 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:46 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:47 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:47 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:47 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:47 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:47 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:47 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file
2021-07-23 11:50:47 ERROR (MainThread) [custom_components.eufy_security] eufy_security Exception in video : I/O operation on closed file - traceback: Traceback (most recent call last):
File "/config/custom_components/eufy_security/camera.py", line 240, in process_frames
self.ffmpeg.process.stdin.write(frame_bytes)
ValueError: I/O operation on closed file

The log goes on and on with similar data, I am assuming whenever I am trying to start the stream, this is happening.
Please let me know if I am doing anything wrong, or if I need to do anything on my end to help identify and solve the bug if it is one.

Will confirm...latest update shows cameras (and static images).  Live stream fails.  All-in-all, excellent progress!

Seconded @dsjackson findings - same here.  Also same on progress - getting from no cameras to semi working was fast!

Please confirm you have enabled ffmpeg in your setup.

FFMPEG is a required integration to make this thing working, double check your configuration.yaml file if it is enabled. More information: https://www.home-assistant.io/integrations/ffmpeg/
give me more information about your home assistant setup (os, installation method), as live stream functionality is creating a file on main directory of home assistant, it might be related to your setup.
as a last resort, i am ready to spare time to connect your local add on id you can expose your IP address temporarily to me, so we can nail down the issue faster.

Install:  Home Assistant OS 6.1 / core-2021.7.4 / supervisor-2021.06.8  Running on Virtualbox on a dedicated Win10 Pro workstation.  I could provide access to the server via SplashTop if it would help or provide a login to the HA instance.
System Health

version
core-2021.7.4

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

virtualenv
false

python_version
3.9.5

os_name
Linux

os_version
5.10.45

arch
x86_64

timezone
America/New_York

Home Assistant Community Store

GitHub API
ok

Github API Calls Remaining
5000

Installed Version
1.13.2

Stage
running

Available Repositories
856

Installed Repositories
63

AccuWeather

can_reach_server
ok

remaining_requests
42

Home Assistant Cloud

logged_in
true

subscription_expiration
August 16, 2021, 8:00 PM

relayer_connected
true

remote_enabled
true

remote_connected
true

alexa_enabled
true

google_enabled
true

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 6.1

update_channel
stable

supervisor_version
supervisor-2021.06.8

docker_version
20.10.6

disk_total
30.8 GB

disk_used
17.7 GB

healthy
true

supported
true

board
ova

supervisor_api
ok

version_api
ok

installed_addons
Terminal & SSH (9.1.3), ADB - Android Debug Bridge (0.8.0), ESPHome (1.20.0), Visual Studio Code (3.6.0), Let's Encrypt (4.11.0), Node-RED (9.2.1), Home Assistant Google Drive Backup (0.104.3), MariaDB (2.4.0), Check Home Assistant configuration (3.8.0), Glances (0.12.3), Bitwarden (Vaultwarden) (0.12.0), Portainer (1.5.1), Tautulli (2.3.0), phpMyAdmin (0.4.3), php-nginx Docker Image (latest), rest980 Docker Image (20200205), ioBroker (0.8.0), eufy_security_addon (latest)

Lovelace

dashboards
2

resources
48

views
28

mode
storage

I'm using FFMPEG with other cameras (Like Wyze RTSP streams) and they are currently working so I believe I have FFMPEG installed and running correctly.

Also was wondering about this - In the dev service screen, the start/top llivestream service shows targets (devices/entities) as shown here:

but the start/stop RTSP services doesn't show any options for selecting a target at all:

Is this as expected or does this indicate an issue on my end?

Please confirm you have enabled ffmpeg in your setup.

FFMPEG is a required integration to make this thing working, double check your configuration.yaml file if it is enabled. More information: https://www.home-assistant.io/integrations/ffmpeg/
give me more information about your home assistant setup (os, installation method), as live stream functionality is creating a file on main directory of home assistant, it might be related to your setup.
as a last resort, i am ready to spare time to connect your local add on if you can expose your IP address temporarily to me, so we can nail down the issue faster.

Confirmed that ffmpeg is enabled in my configuration.yaml, and installed on my base system.

Home assistant supervised install on debian 10.

If it helps you troubleshoot for everyone, im glad to create a user for you, but you definitely should not feel obligated to offer me personalized tech support

Install: Home Assistant OS 6.1 / core-2021.7.4 / supervisor-2021.06.8 Running on Virtualbox on a dedicated Win10 Pro workstation. I could provide access to the server via SplashTop if it would help or provide a login to the HA instance.
System Health
version	core-2021.7.4
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
virtualenv	false
python_version	3.9.5
os_name	Linux
os_version	5.10.45
arch	x86_64
timezone	America/New_York
Home Assistant Community Store
AccuWeather
Home Assistant Cloud
Home Assistant Supervisor
Lovelace
I'm using FFMPEG with other cameras (Like Wyze RTSP streams) and they are currently working so I believe I have FFMPEG installed and running correctly.
ffmpeg:
is confirmed in my configuration.yaml. Also RTSP is set on all of my compatible eufycams; it has been for months as I was testing out the other options (Fuzzy's custom component, MQTT, ioBroker, etc.). The account I'm using for your component/add on pair are not is use anywhere else. That's about all I can think of off the top of my head.

I have had similar issues on all those other implementations to the issues im having here, did you get streams working on any of them?   The only one i got to work was the webRTC of the actual RSTP stream the cam is spitting out, but CPU usage was way too high even on my i5 NUC to maintain it.

I have had similar issues on all those other implementations to the issues im having here, did you get streams working on any of them?

It's been a while, but I remember getting a couple of cams to work with those components, not 100% reliably but enough times to know that it worked.

I am assuming it is related to the file created in the main directory of the Home Assistant Install. I have re-installed the latest version, most of the prior error logs have vanished, but the stream does not seem to work.
My installation is docker HA installed on the dedicated Ubuntu LTS 20.04 Desktop. ffmpeg: is enabled in my configuration.yaml  file.
Here is the server info:
System Health

version
core-2021.7.4

installation_type
Home Assistant Container

dev
false

hassio
false

docker
true

virtualenv
false

python_version
3.9.5

os_name
Linux

os_version
5.8.0-63-generic

arch
x86_64

timezone
America/Chicago

Home Assistant Community Store

GitHub API
ok

Github API Calls Remaining
4876

Installed Version
1.13.2

Stage
running

Available Repositories
850

Installed Repositories
7

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Lovelace

dashboards
4

resources
1

views
33

mode
storage

The only errors I see on the log file are
2021-07-24 09:48:39 ERROR (stream_worker) [homeassistant.components.stream.worker] Error opening stream None
2021-07-24 09:48:49 ERROR (stream_worker) [homeassistant.components.stream.worker] Error opening stream None
2021-07-24 09:48:52 ERROR (Thread-16) [pychromecast.socket_client] [([::ffff:c0a8:b0d]):8009] Failed to connect to service ServiceInfo(type='host', data=('[::ffff:c0a8:b0d]', 8009)), retrying in 5.0s
2021-07-24 09:48:52 ERROR (Thread-17) [pychromecast.socket_client] [([::ffff:c0a8:b0d]):32133] Failed to connect to service ServiceInfo(type='host', data=('[::ffff:c0a8:b0d]', 32133)), retrying in 5.0s
2021-07-24 09:48:56 ERROR (Thread-22) [pychromecast.socket_client] [Play Area speaker(<IP_ADDRESS>):8009] Failed to connect to service ServiceInfo(type='mdns', data='Google-Home-Mini-53650d3cd8b0a82b5c01e1e7b6d47b9b._googlecast._tcp.local.'), retrying in 5.0s
2021-07-24 09:49:09 ERROR (stream_worker) [homeassistant.components.stream.worker] Error opening stream None
2021-07-24 09:49:39 ERROR (stream_worker) [homeassistant.components.stream.worker] Error opening stream None
2021-07-24 09:50:19 ERROR (stream_worker) [homeassistant.components.stream.worker] Error opening stream None
2021-07-24 09:51:09 ERROR (stream_worker) [homeassistant.components.stream.worker] Error opening stream None

I’ve got the stream to work. Something is wrong when the integration starts with my 2K indoor camera with RTSP enabled.
In order for the stream to work I have to call the Camera Turn Off service followed by the Camera Turn On service. After that, stream starts working properly.
I’ve had a few instances where the stream will stop working due to “demuxing errors” and wasn’t able to recover by itself forcing me to redo the above steps.

I can confirm the same as @fabianluque on my system.  (Brilliant find BTW!  Thanks!!)  Turned off then on and the stream came up right away.

I’ve got the stream to work. Something is wrong when the integration starts with my 2K indoor camera with RTSP enabled.
In order for the stream to work I have to call the Camera Turn Off service followed by the Camera Turn On service. After that, stream starts working properly.
I’ve had a few instances where the stream will stop working due to “demuxing errors” and wasn’t able to recover by itself forcing me to redo the above steps.

Confirmed behavior, calling camera_turnon and off on the camera indicated makes the stream work

So everyone is aware, the turn-off turn-on method is subject to the three minute stream limit, after which you have to execute the function again.   This is an underlying limitation with eufy, and bropat has looked at it before as have fuzzy and a few of the others.

And to elaborate on @jbrukardt's comment, this limitation is how eufy can make their battery life claims as keeping the devices streaming would kill them in short order.  I can't fault them much for this as they last longer than my Arlo or Ring battery devices.
Seems like a trivial thing to script and attach to a button or make part of a tap action though.  (That's what I did back when I was using Fuzzy's implementation.)

@jbrukardt I can also confirm on my 2k wireless doorbell that the live feed seems to break after about the 3 minute mark. Restarting the services live feed will allow me to view it again.

to recap;

we are able to start and stop the livestream for the first time without any issues
if live stream continues more than 3 minutes, it is closed on eufy side but we don't receive the update - action item: at least, we can update the state on our end
to restart live stream after 3 minutes timespan, you need to stop and start the stream.

I prefer not to do anything inside Home Assistant and request to fix this on WS layer, what do you think>

@fuatakgun All bullet points seem accurate. I am not sure if that is possible on the WS layer as I dont fully understand it but it is worth opening a discussion.

For RTSP cameras I guess the 3 minute limit doesn't count. I have been running the stream for days now without stopping.
@fuatakgun Camera turn off/on is a step we have to do with RTSP cameras? Shouldn't they start by themselves by default at least be configurable?

I have created this: https://github.com/bropat/eufy-security-client/issues/30
It is better to fix this from source.

For RTSP cameras I guess the 3 minute limit doesn't count. I have been running the stream for days now without stopping.
@fuatakgun Camera turn off/on is a step we have to do with RTSP cameras? Shouldn't they start by themselves by default at least be configurable?

is it battery powered or mains?

@fuatakgun It’s not battery powered, but USB. Issue is it won’t work from the start until I call manually camera off/on service.

You are right, when initializing at first run, i am not checking if it is already live streaming. This is solvable.

to recap;

we are able to start and stop the livestream for the first time without any issues
if live stream continues more than 3 minutes, it is closed on eufy side but we don't receive the update - action item: at least, we can update the state on our end
to restart live stream after 3 minutes timespan, you need to stop and start the stream.

I prefer not to do anything inside Home Assistant and request to fix this on WS layer, what do you think?

Concur that this is a WS layer issue.   Disagree with item 1 though "we are able to start and stop the livestream for the first time without any issues".   It doesnt work the first time for me on 2k, has to stop and start to get it working at all.

to recap;

we are able to start and stop the livestream for the first time without any issues
if live stream continues more than 3 minutes, it is closed on eufy side but we don't receive the update - action item: at least, we can update the state on our end
to restart live stream after 3 minutes timespan, you need to stop and start the stream.

I prefer not to do anything inside Home Assistant and request to fix this on WS layer, what do you think?

I am not versed in what the services actually do... but the service that works is "Camera: Turn off" and "Camera: Turn on",  not "Eufy Security: Start Live Stream".   Start live stream doesnt solve the problem, and seems to contribute to lockup.

let's put a timeline here:

t0 - camera is not live streaming and home assistant installation started
t1 - live stream started from HA, WS layer keeps track of live stream status and record client id as live stream started
t2 - live stream was timed out, closed by hardware but HA is not aware of this, still in streaming mode
t3 - restarted your HA, we are not checking live stream status at restart now nor we are not receiving any video chunks
t3 - or - you tried to see camera live view but  it was not possible because no new video chunks are coming.
t4 - tried to start live stream and it will not work because WS layer still thinks that it is live streaming.

to recap;

we are able to start and stop the livestream for the first time without any issues
if live stream continues more than 3 minutes, it is closed on eufy side but we don't receive the update - action item: at least, we can update the state on our end
to restart live stream after 3 minutes timespan, you need to stop and start the stream.

I prefer not to do anything inside Home Assistant and request to fix this on WS layer, what do you think?

I am not versed in what the services actually do... but the service that works is "Camera: Turn off" and "Camera: Turn on", not "Eufy Security: Start Live Stream". Start live stream doesnt solve the problem, and seems to contribute to lockup.

camera.turn_on: checks if RTSP attribute exists in camera attributes, if yes, calls start_rtsp if not calls start_livestream
camera.turn_off: same logic to turn off.

to recap;

we are able to start and stop the livestream for the first time without any issues
if live stream continues more than 3 minutes, it is closed on eufy side but we don't receive the update - action item: at least, we can update the state on our end
to restart live stream after 3 minutes timespan, you need to stop and start the stream.

I prefer not to do anything inside Home Assistant and request to fix this on WS layer, what do you think?

I am not versed in what the services actually do... but the service that works is "Camera: Turn off" and "Camera: Turn on", not "Eufy Security: Start Live Stream". Start live stream doesnt solve the problem, and seems to contribute to lockup.

camera.turn_on: checks if RTSP attribute exists in camera attributes, if yes, calls start_rtsp if not calls start_livestream
camera.turn_off: same logic to turn off.

ohhh, thats strange.   I stream everything to BlueIRIS all the time, so i know RSTP is actually working.   Ill have to ensure flipping it on and off doesnt break the Blueiris side of things.

Yes, double check it and let me know the outcome.

flipping it does cause a break in the rstp stream, buts its a 1/2 second or so blip and the stream picks right back up.   Its fine.
Just wonder why the WS library doesnt detect the stream is already live, but thats a bropat question.

Actually, if you are using rtsp, it should work fine and remember the
state. I had issues for p2p cases, i will double check and let you know for
2c cameras.
On Mon, Jul 26, 2021, 19:44 jbrukardt @.***> wrote:

flipping it does cause a break in the rstp stream, buts its a 1/2 second
or so blip and the stream picks right back up. Its fine.
Just wonder why the WS library doesnt detect the stream is already live,
but thats a bropat question.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/eufy_security/issues/10#issuecomment-886900660,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUSN7U7K26XTKC2NA4DL63TZWNIVANCNFSM5ASKXPHQ
.

ok, im glad to run any test needed for usb-powered indoor 2k's as well, but I can verify that they all have an active rstp stream already.   I think most folks (bropat included) have 2c's and design towards those, so there is some odd behavior on indoor 2ks.

ok, im glad to run any test needed for usb-powered indoor 2k's as well, but I can verify that they all have an active rstp stream already. I think most folks (bropat included) have 2c's and design towards those, so there is some odd behavior on indoor 2ks.

+1
I can also test using my 2K indoor cameras.

sent you a message on home assistant forums with a test account tied to one of my 2k cams in a place I dont care about, you can use it for testing in whatever manner you like.

I have updated repository with some fixes, now, it should understand that stream is active when it started running and attach to it. please get latest codebase and let us know

The stream doesn't seem to work for my 2K Wired Doorbell. I have got the following new set of errors in the logs.
This error originated from a custom integration.
Logger: homeassistant
Source: custom_components/eufy_security/camera.py:241
Integration: Eufy Security (documentation, issues)
First occurred: 4:41:55 PM (1 occurrences)
Last logged: 4:41:55 PM

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/camera/__init__.py", line 263, in preload_stream
    stream = await camera.create_stream()
  File "/config/custom_components/eufy_security/camera.py", line 241, in create_stream
    self.hass, stream_source, options=self.stream_options
UnboundLocalError: local variable 'stream_source' referenced before assignment

Your camera should support RTSP, double check if you had enabled it on eufy app and try start_rtsp service and check if camera state is changed as streaming. Later than, click on image to see live stream.

@fuatakgun Updated to latest, my T8400 camera (2K IndoorCam with RTSP enabled) became unavailable. I reinstalled the integration and now my camera entity is gone, I still have all the sensors though. eufy_security_addon also updated to version 0.3.3.

any logs you can share?

@fuatakgun Updated to latest, my T8400 camera (2K IndoorCam with RTSP enabled) became unavailable. I reinstalled the integration and now my camera entity is gone, I still have all the sensors though. eufy_security_addon also updated to version 0.3.3.

Ive had weirdness as well.  The camera entity is only showing up for 2 of my 8 cams (the 2 with SD cards in them, but also rstp enabled).  The other devices are all there, and all their sensors are functioning, but no camera entity.
Same versions.
No errors in logs, and all devices are detected by the addon as shown in the logs.   I think its something with the auto-creation of entities by the integration

@fuatakgun Here are some logs:
2021-07-28 12:45:11 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - set_ws - connect
2021-07-28 12:45:19 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - on_open - executed
2021-07-28 12:45:19 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - process_messages started
2021-07-28 12:45:25 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - WebSocket message sent. {"messageId": "set_api_schema", "command": "set_api_schema", "schemaVersion": 3}
2021-07-28 12:45:25 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - WebSocket message sent. {"messageId": "start_listening", "command": "start_listening"}
2021-07-28 12:45:25 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - check_if_started_listening
2021-07-28 12:45:25 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - check_if_started_listening - 0
2021-07-28 12:45:25 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - on_message - {'type': 'result', 'success': True, 'messageId': 'set_api_schema', 'result': {}}
2021-07-28 12:45:25 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - on_message - {'type': 'result', 'success': True, 'messageId': 'start_listening', 'result': {'state': {'driver': {'version': '0.9.4', 'connected': True, 'pushConnected': True}, 'stations': [{'name': 'Living Room', 'model': 'T8400', 'serialNumber': 'T8400P20203624D8', 'hardwareVersion': 'P2', 'softwareVersion': '<IP_ADDRESS>', 'lanIpAddress': '<IP_ADDRESS>', 'macAddress': '8C85805D80EF', 'currentMode': 1, 'guardMode': 1, 'connected': True}], 'devices': [{'name': 'Living Room', 'model': 'T8400', 'serialNumber': 'T8400P20203624D8', 'hardwareVersion': 'P2', 'softwareVersion': '<IP_ADDRESS>', 'stationSerialNumber': 'T8400P20203624D8', 'enabled': True, 'motionDetected': False, 'personDetected': False, 'personName': '', 'soundDetected': False, 'petDetected': False, 'cryingDetected': False, 'autoNightvision': True, 'ledStatus': True, 'motionDetection': True, 'soundDetection': False, 'petDetection': False, 'rtspStream': True, 'watermark': 1, 'motionDetectionType': 4, 'motionDetectionSensivity': 3, 'soundDetectionType': 1, 'soundDetectionSensivity': 3, 'microphone': True, 'speaker': True, 'speakerVolume': 80, 'audioRecording': True, 'videoStreamingQuality': 3, 'notificationType': 3, 'notificationPerson': False, 'notificationPet': False, 'notificationAllOtherMotion': False, 'notificationCrying': False, 'notificationAllSound': False}]}}}
2021-07-28 12:45:25 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - on_message start_listening
2021-07-28 12:45:25 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - WebSocket message sent. {"messageId": "get_properties", "command": "device.get_properties", "serialNumber": "T8400P20203624D8"}
2021-07-28 12:45:25 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - WebSocket message sent. {"messageId": "get_livestream_status.T8400P20203624D8", "command": "device.is_livestreaming", "serialNumber": "T8400P20203624D8"}
2021-07-28 12:45:25 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data
2021-07-28 12:45:26 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - on_message - {'type': 'result', 'success': True, 'messageId': 'get_properties', 'result': {'properties': {'name': {'value': 'Living Room', 'timestamp':<PHONE_NUMBER>000}, 'model': {'value': 'T8400', 'timestamp':<PHONE_NUMBER>000}, 'serialNumber': {'value': 'T8400P20203624D8', 'timestamp':<PHONE_NUMBER>000}, 'type': {'value': 30, 'timestamp':<PHONE_NUMBER>000}, 'hardwareVersion': {'value': 'P2', 'timestamp':<PHONE_NUMBER>000}, 'softwareVersion': {'value': '<IP_ADDRESS>', 'timestamp':<PHONE_NUMBER>000}, 'stationSerialNumber': {'value': 'T8400P20203624D8', 'timestamp':<PHONE_NUMBER>000}, 'notificationType': {'value': 3, 'timestamp':<PHONE_NUMBER>000}, 'microphone': {'value': True, 'timestamp':<PHONE_NUMBER>000}, 'motionDetectionType': {'value': 4, 'timestamp':<PHONE_NUMBER>000}, 'motionDetectionSensivity': {'value': 3, 'timestamp':<PHONE_NUMBER>000}, 'petDetection': {'value': False, 'timestamp':<PHONE_NUMBER>000}, 'soundDetectionSensivity': {'value': 3, 'timestamp':<PHONE_NUMBER>000}, 'watermark': {'value': 1, 'timestamp':<PHONE_NUMBER>000}, 'speaker': {'value': True, 'timestamp':<PHONE_NUMBER>000}, 'notificationCrying': {'value': False, 'timestamp':<PHONE_NUMBER>000}, 'rtspStream': {'value': True, 'timestamp':<PHONE_NUMBER>000}, 'autoNightvision': {'value': True, 'timestamp':<PHONE_NUMBER>000}, 'enabled': {'value': True, 'timestamp':<PHONE_NUMBER>000}, 'statusLed': {'value': True, 'timestamp':<PHONE_NUMBER>000}, 'notificationAllSound': {'value': False, 'timestamp':<PHONE_NUMBER>000}, 'notificationAllOtherMotion': {'value': False, 'timestamp':<PHONE_NUMBER>000}, 'notificationPet': {'value': False, 'timestamp':<PHONE_NUMBER>000}, 'speakerVolume': {'value': 80, 'timestamp':<PHONE_NUMBER>000}, 'notificationPerson': {'value': False, 'timestamp':<PHONE_NUMBER>000}, 'videoStreamingQuality': {'value': 3, 'timestamp':<PHONE_NUMBER>000}, 'motionDetection': {'value': True, 'timestamp':<PHONE_NUMBER>000}, 'soundDetectionType': {'value': 1, 'timestamp':<PHONE_NUMBER>000}, 'soundDetection': {'value': False, 'timestamp':<PHONE_NUMBER>000}, 'audioRecording': {'value': True, 'timestamp':<PHONE_NUMBER>000}, 'motionDetected': {'value': False, 'timestamp': 0}, 'personDetected': {'value': False, 'timestamp': 0}, 'personName': {'value': '', 'timestamp': 0}, 'petDetected': {'value': False, 'timestamp': 0}, 'soundDetected': {'value': False, 'timestamp': 0}, 'cryingDetected': {'value': False, 'timestamp': 0}}}}
2021-07-28 12:45:26 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data
2021-07-28 12:45:26 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - on_message - {'type': 'result', 'success': True, 'messageId': 'get_livestream_status.T8400P20203624D8', 'result': {'livestreaming': False}}
2021-07-28 12:45:26 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - GET_LIVESTREAM_STATUS_MESSAGE - {'type': 'result', 'success': True, 'messageId': 'get_livestream_status.T8400P20203624D8', 'result': {'livestreaming': False}}
2021-07-28 12:45:26 DEBUG (MainThread) [custom_components.eufy_security] Manually updated eufy_security data
2021-07-28 12:45:27 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - get_device_properties
2021-07-28 12:45:27 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - WebSocket message sent. {"messageId": "poll_refresh", "command": "driver.poll_refresh"}
2021-07-28 12:45:27 DEBUG (MainThread) [custom_components.eufy_security] Finished fetching eufy_security data in 0.001 seconds
2021-07-28 12:45:28 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - camera setup entries - []
2021-07-28 12:45:29 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - WebSocket message sent. {"messageId": "poll_refresh", "command": "driver.poll_refresh"}
2021-07-28 12:45:29 DEBUG (MainThread) [custom_components.eufy_security] Finished fetching eufy_security data in 0.003 seconds
2021-07-28 12:45:30 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - on_message - {'type': 'result', 'success': True, 'messageId': 'poll_refresh', 'result': {}}
2021-07-28 12:45:30 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - on_message - {'type': 'result', 'success': True, 'messageId': 'poll_refresh', 'result': {}}

can you double check that you have enabled notifications with picture? There is no picture URL her to show as a placeholder and I am intentionally skipping these entities. I can try to find another way of doing this but you will have no still image.

Double checked on mine that "thumbnail included" is present on all cameras for notification mode.
I think this a 2c vs 2k thing.  The 2c's all store last thumbnail on the home base.   The 2k's dont store last thumbnail anywhere persistent UNLESS you have an SD card in them.   Id hypothesize thats why my two cameras with sd cards in them are working but the others arent.   In previous versions of the integration I would get no-picture-url placeholders for the cams without sd cards in them, and then as motion events were triggered on that cam, they would update the lovelace card.

ok, let's fix it, I will release a fix tonight

@fuatakgun @jbrukardt Can confirm the thumbnail behavior. Before the update I would get no image until there were some events triggered.

can you share your device for testing purposes with admin rights?
if you are located in EU, use my account<EMAIL_ADDRESS>if you are located in US, use test account<EMAIL_ADDRESS>

be aware that if you're testing on my "basement" device @fuatakgun that one does have an SD card in it, so it may not be good for testing this issue.

be aware that if you're testing on my "basement" device @fuatakgun that one does have an SD card in it, so it may not be good for testing this issue.

which one I should rely? :)

eeek... i dont have any I can share with you that dont have an sd card in em.  Theyre all in my living spaces.
You could eject the card in app i guess?  i think you can do that as an admin.

i can only format but not eject, so you dont have sutaible camera to share. let's wait @fabianluque 's response than

i can only format but not eject, so you dont have sutaible camera to share. let's wait @fabianluque 's response than

Just shared one my 2K cameras with your, admin rights. Let me know if works for you.

please get latest codebase (1 min ago) and you will have camera. There is also one good improvement for you, picture will be updated while streaming automatically. Please resolve if it is done

@fuatakgun Awesome, let me update and test.

waiting for the update to show up in hacs and then ill do it.

@fuatakgun Confirmed, fix works beautifully! Thanks so much! Removing access until next time. :)

Let's hope we dont need it anymore :-) @jbrukardt , can you also validate with your cameras?

can do.  Just waiting for HA.   Its hanging on restart waiting for something :/

Do you see what keeps it hanging? Normally,  it should mention which integration is holding it.

ok, all cameras are detected again and have snapshots.
Streams working too!

Do you see what keeps it hanging? Normally, it should mention which integration is holding it. I hope it is not about this one :-)
Honestly, it is this the integration sometimes :p  but lets let that sleeping dog lie for now.   We'll go for functionality first, then stability.

There are many stuff happening at startup, i can definitely improve them.

After the latest code update (thanks for the frequent updates and improvements), wired doorbell no longer shown (Generates error: This entity is currently unavailable and is an orphan to a removed, changed or dysfunctional integration or device.) and the 2c's I have show the snapshot with RTSP-Streaming (before, just Streaming) but no longer stream.

I know the issue about doorbell but i am not sure about 2c, any luck you can share it?

Great enhancement to add the tag for streaming type.  Thats really handy for troubleshooting the streaming method. All mine show rstp (as they should)

I know the issue about doorbell but i am not sure about 2c, any luck you can share it?
Update: published another version of integration, please check if you have latest version of integration and 0.3.3 version of add on.
I just wanted to separate streaming-rtsp vs streaming-p2p as it is difficult most of the time for users what is happening, so state is fine.

Confirmed that the 2C's now work as expected.  Wired doorbell shows "Streaming - p2p" but no snapshot and no streaming.  An earlier version (a few days ago...I will I had the version number) worked fine...a version before you added the streaming type tag.

@dsjackson please create a separate issue, this became unmanageable. And share logs with it.


header names are needlessly line-wrapped

Even though there is plenty of horizontal space (as can be seen from the width of the "Request-Response-Details" tab bar).

Hi, i had a look into the source but it turns out that they are not needlessly wrapped up but it is intentional to be on the new line. It may not be clear for smaller urls but for longer urls it make the header responses visible which would otherwise be wrapped up.
If you still have any other suggestions, feel free to share them.

I'm not sure I understand what you're saying. Just because header values could be larger, doesn't mean we have to line-wrap the header names when they aren't.

I want to think about this question. Which files can i work on?

The correct fix here is to

Get available space.
Calculate maximum header name length.
Calculate maximum header value length.
Make sure that the header name takes up at least 30 chars, but more if the space is not fully used.

Hello
Wouldn't it be better to store the number of characters in the header length and then assign if they need wrapping or not according to their length?


Feature/codegen geoloc defaults

Default Geolocation Configuration: Enhanced Codegen Composer to include a default geolocation configuration to streamline user setup and improve usability.

Error Handling: Added an error message for cases where the URL input is empty

There is one interesting bug in current solution 😉

I can guide You through the reason of such behaviour 😉

Another enhancement:
as we see example in docs:
https://playwright.dev/docs/codegen#emulate-geolocation-language-and-timezone
It will be safe to add " before and after value.

Resolve bug and add quotes around values for --timezone, --geolocation and --lang options. 🚀

Looks fine - lets merge!


Added @RadioPortal

Pls add ?voicechat to your url (also u can fix url of PlayAStream

Pls add ?voicechat to your url (also u can fix url of PlayAStream

It's a collection of radio channels,
Just like PlayAStream

Thanks


List view UI

Added styling to the list of fruit that appears in the add items area. Styling is not completely finished and touch up may be required depending on the differences to the already implemented UI. Addresses #81

@ochu761 : Resolving conflicts after #93 merge


DRAMSys Agents

All agents work out of the box except for the following:
-train_brute_force.py
-train_ppo.py
-train_single_agent.py
-train_simpleEnv.py

@TensorTyrion9001 I was testing the DRAM agents again and found that the following were not working out of the box. Can you please resolve these?

Following Issues are resolved after resolving acme installation issue and train_ppo.py had issue regarding logging

Awesome @TensorTyrion9001, thanks!


mkdir = True not working in ProjDirs ?

Looking at:
https://nilomr.github.io/pykanto/_build/html/contents/project-setup.html
DIRS = ProjDirs(project_root, data_dir, dataset_name,  mkdir=True) print(DIRS)
yield error:
FileNotFoundError:  where path is formed like this <project_root / 'data'> /   <dataset_name>
having:
project_root = '/path'/
data_dir = project_root / "data" / dataset_name
I synced data from external folder to: project_root / 'data'
Audio files are in:
/path/data/files102/
I also tried to set:
data_dir = project_root / "data" / "files102" / dataset_name
but no success.

Oh, I noticed error was in forming the  data_dir folder with  dataset_name subfolder.
dataset_name should be parent folder,
dataset_name = 'BIGBIRD_2021'
data_dir = project_root / "data" / "raw" / dataset_name
seems confusing to me because dataset_name is not reflected in the tree 👍
I guess dataset_name == project in the example below?
📁 project
├── 📁 data
│   ├── 📁 datasets
│   │   └── 📁 <DATASET_ID>
│   │       ├── <DATASET_ID>.db
│   │       └── 📁 spectrograms
|   ├── 📁 raw
│   │   └── 📁 <DATASET_ID>
│   └── 📁 segmented
│       └── 📁
├── 📁 resources
├── 📁 reports
│   └── 📁 figures
└──


No SVs in the lower half of the plot.

Taking a look at
 and browsing together with @josiahseaman through yeast data, I realized, that there are no arrivals or departures below the lower half of the visualization.
Possible reasons:

The data really is like this, but this is very very unlikely to impossible.
During the component segmentation, something goes wrong.
The components are drawn 2x the height they actually should be drawn.

@superjox
What do you think?

Turns out the height was being multiplied by 2.


In DX9 mode, mPixelConstants overriding already set constants.

When in the DX9 mode, I was having an issue where shader constants weren't being updated at all.
Tracked it down to this like in Renderer9.cpp on line 1929 in function applyUniforms(:
mDevice->SetPixelShaderConstantF(0, (float*)&mPixelConstants, sizeof(dx_PixelConstants) / sizeof(float[4]));
My uniform is being set in the applyUniformnfv function below at psRegisterIndex number 3, but applyUniforms( gets called afterwards which uses slot 0-3 meaning my information was getting overriden!
I've managed to fix the problem I was having by commenting out the line to update mPixelConstants, not sure what this indented to do though etc but thought I should let you all know what I found either way :)

Hi comeradealexi,
Thanks for the info!  This is very interesting.  You must be writing a classic desktop application as DX9 isn't available for Windows Store applications.  This repository has a focus on Windows Store, so we don't see many DX9 issues coming in.  I want to make sure your issue gets some attention from Google as well as they use the DX9 path.  Please post an issue here: https://code.google.com/p/angleproject/issues/list and the Google folks will be alerted.
I can do a bit of looking myself, in addition to the Google folks.

I suspect this issue is limited to our ANGLE repository on GitHub. In our version of ANGLE, we have some additional features that haven't been submitted to Google's version yet. One of these is called render-to-backbuffer, which is a performance improvement for D3D11 mode. Render-to-backbuffer adds a new (4th) entry to dx_PixelConstants, which is probably causing the issue you see.
Render-to-backbuffer has been heavily tested in D3D11-mode but not D3D9-mode. As Cooper says, this repository has a focus on D3D11 mode for Windows Store.
A (better) temporary fix to this issue for D3D9 mode would probably be to remove 'viewScale' from the dx_PixelConstants and dx_VertexConstants structs in RendererD3D.h. We'll investigate a full solution soon.
Thanks a lot for reporting this!

Hi all! Thanks for the quick replies.
Yep, it is for a classic desktop application and in DirectX11 mode it works as intended. I'll give that a go austinkinross instead of just commenting it out.
Here is a link to the Google Code report for this bug: https://code.google.com/p/angleproject/issues/detail?id=1131&thanks=1131&ts=1440094893

Hi comeradealexi, I expect this to have been fixed in this commit on Sept 4th: https://github.com/MSOpenTech/angle/commit/33769f8f0c195a295a228167147a78773765fe9b. Please let us know if you are still experiencing problems!


⚠ Secret Website 3 has degraded performance

In 1559541, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2261 ms

Resolved: Secret Website 3 performance has improved in 5b44304.


storage phase 1 for inference service reconciler

Motivation
rebase #32 to the new inference service reconciler for model mesh
For Storage Spec details, please refer to the design doc: https://docs.google.com/document/d/1rYNh93XNMRp8YaR56m-_zK3bqpZhhGKgpVbLPPsi-Ow/edit#
Additional storages/parameters support will come in phase 2.
Modifications
Result

@njhill @pvaneck Quick question, is the schemaPath only used in Pytorch framework? Right now I have schemaPath as optional parameter as part of the storage Spec, but let me know if these kinds of parameters are more framework specific so I can also change it.
In Kserve, the pytorch server assume both model and graph .mar files are under the model-store folder instead of pointing to a single file.
https://console.cloud.google.com/storage/browser/kfserving-examples/models/torchserve/image_classifier;tab=objects?prefix=&forceOnObjectsSortingFiltering=false&pageState=("StorageObjectListTable":("f":"%255B%255D"))
In Kserve triton server, it assumes the path is pointing to a folder with structure similar to tensorflow's savedmodel format.
https://console.cloud.google.com/storage/browser/kfserving-examples/models/torchscript?pageState=("StorageObjectListTable":("f":"%255B%255D"))&prefix=&forceOnObjectsSortingFiltering=false
I think the schemaPath is useful for backward capability since pytorch didn't have a model saving standard, but I feel like this might be too much to add it as part of the storage spec.

thanks @njhill for your reviews

@Tomcli are you sure we want to include the new serving.kserve.io_inferenceservices.yaml file at this point (it's huge)?
May be better to omit it until the other kserve changes are ready? The PR could still be merged, I don't think the new logic will break anything when used with the existing CRD... the storage spec will just appear empty.

thanks @njhill for your reviews. I updated based on your comments

Thanks @njhill I addressed the pointer changes.

/lgtm


Please elaborate on how to set up POCO entities

Cross posted from here
Please add more information on how to create parameterless POCO entities when using EF Core. For example:
public class User
{
  public string UserName { get; set; }
}

The UserName property should never be null from the developer's perspective, but will be null from the compiler's perspective.
What's the convention then? public string UserName { get; set; } = default!?
Would be nice if the docs could include this piece of information and have a conventional guideline on this.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 93c3721a-da23-d9ea-a054-9d786d2ff4d2
Version Independent ID: 6d3b0f96-6642-75e5-93c8-02c23f142ac4
Content: Working with nullable reference types - EF Core
Content Source: entity-framework/core/miscellaneous/nullable-reference-types.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @roji
Microsoft Alias: avickers

The issue is addressed in this paragraph.


Failed to connect to QMP

I have such a problem when running the run-local.sh file, is there any solution, thank you very much!

Hi, can you try building the base image to see if that fixes it?
The command is ./build-container-image.sh --build-base-image true
Once that's done you should be able to do ./run-local.sh

Hi, can you try building the base image to see if that fixes it?
The command is ./build-container-image.sh --build-base-image true Once that's done you should be able to do ./run-local.sh

I took care of it. Thank you so much！！


Image upload fails

any image upload fails. Any solution?
error log:
2016/08/24 16:24:45 [error] 1531#1531: *14 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: <IP_ADDRESS>, server: himalikiran.com, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php-fpm/php-fpm.sock:", host: "himalikiran.com"

Might be relevant: http://serverfault.com/questions/517190/nginx-1-fastcgi-sent-in-stderr-primary-script-unknown
Seems like a config issue, not a Postleaf issue.

Thank you @claviska I figured out that the problem is about open_basedir configuration in my php.ini file.
now it is working perfectly.
By the way does postleaf supports Ghost themes?

Glad it's working 👍
While Postleaf does use handlebar templates, it doesn't support Ghost themes without certain modifications.
While Ghost is awesome in its own way, there are fundamental differences in certain aspects of each system and I didn't want to have to keep up with their API while managing our own.
One user wrote up a very through post about converting his Ghost theme to Postleaf:
https://www.0x0049.me/switching-from-ghost-to-postleaf
In fact, this is something I should probably throw up on the site as a tutorial.


Display custom User fields

I followed the instructions and added some custom fields to the User class, like FirstName and LastName. They are saved in the database fine. But how can I display that info in a page, like Hello, <FirstName>!?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 431df4fc-4168-cc8f-d053-9b264d2971c1
Version Independent ID: cd157d04-d596-83fa-6edb-24d52193eb34
Content: Add, download, and delete custom user data to Identity in an ASP.NET Core project
Content Source: aspnetcore/security/authentication/add-user-data.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@hmihail  you'll probably get a quicker response if you ask that question on a forum.


fix: initiator domains

Limit initiator domains that can make authentictaed admin API requests.

hi. we also need to include the custom preview and live hosts.

They are included. But the mountpoint hostname is still missing, therefore the sidekick is getting a 401 in edit mode.

Abandoning this approach since it can never work for all configured and transient sites within an org.


node6 runtime error

Getting the below error at runtime for the below use under node 6. Could not duplicate in an isolated test. Anyone seeing something similar?
Usage:
var SegfaultHandler = require('segfault-handler');
SegfaultHandler.registerHandler();

Runtime error:
"Error: Module did not self-register.
    at Error (native)
    at Object.Module._extensions..node (module.js:568:18)
    at Module.load (module.js:456:32)
    at tryModuleLoad (module.js:415:12)
    at Function.Module._load (module.js:407:3)
    at Module.require (module.js:466:17)
    at require (internal/module.js:20:19)
    at bindings (/Users/lmeyerov/Desktop/work4/viz-server/node_modules/graph-viz/node_modules/common/node_modules/segfault-handler/node_modules/bindings/bindings.js:76:44)
    at Object.<anonymous> (/Users/lmeyerov/Desktop/work4/viz-server/node_modules/graph-viz/node_modules/common/node_modules/segfault-handler/index.js:3:37)

I'm also having this problem. I'm searching for alternatives if this doesn't get solved 😢

For now you could do something like this:
if (process.version.indexOf('v4') === 0 || process.version.indexOf('v5') === 0) {
  var SegfaultHandler = require('segfault-handler');
  SegfaultHandler.registerHandler();
}

Yes, I'm requiring it inside a try block, but I would prefer it to work since I find it quite precious when my app just blows the house 😄

This module works for me on Node 6.9.1 .  Is this still a valid bug for you all?


dart2js: assertion failure on inlining constructor body

I can currently only repro this on a 'modular dart2js' build of an old version of flutter gallery
  _InspectorOverlayLayer({
  ^
The compiler is broken.

When compiling the above element, the compiler crashed. It is not
possible to tell if this is caused by a problem in your program or
not. Regardless, the compiler should not crash.

The Dart team would greatly appreciate if you would take a moment to
report this problem at http://dartbug.com/new.

Please include the following information:

* the name and version of your operating system,

* the Dart SDK build number (build number could not be determined), and

* the entire message you see here (including the full stack trace
  below as well as the source location above).

Unhandled exception:
Assertion failure: Only 3 of 4 arguments have been read from: [HCreate(j:class(_InspectorOverlayLayer), [_InspectorOverlayLayer]), parameter overlayRect, parameter selection, HCreateBox()] passed to j:constructor_body(_InspectorOverlayLayer.).
#0      failedAt (package:compiler/src/diagnostics/invariant.dart:49:3)
#1      KernelSsaGraphBuilder._setupStateForInlining (package:compiler/src/ssa/builder_kernel.dart:6200:9)
#2      KernelSsaGraphBuilder._enterInlinedMethod (package:compiler/src/ssa/builder_kernel.dart:6096:5)
#3      KernelSsaGraphBuilder._tryInlineMethod.doInlining (package:compiler/src/ssa/builder_kernel.dart:5922:7)
#4      KernelSsaGraphBuilder._tryInlineMethod (package:compiler/src/ssa/builder_kernel.dart:5935:17)
#5      KernelSsaGraphBuilder._buildConstructor.<anonymous closure> (package:compiler/src/ssa/builder_kernel.dart:885:13)
#6      KernelSsaGraphBuilder._inlinedFrom.<anonymous closure> (package:compiler/src/ssa/builder_kernel.dart:925:21)
#7      CompilerDiagnosticReporter.withCurrentElement (package:compiler/src/compiler.dart:819:15)
#8      KernelSsaGraphBuilder._inlinedFrom (package:compiler/src/ssa/builder_kernel.dart:923:14)
#9      KernelSsaGraphBuilder._buildConstructor (package:compiler/src/ssa/builder_kernel.dart:842:7)
#10     KernelSsaGraphBuilder.build.<anonymous closure> (package:compiler/src/ssa/builder_kernel.dart:489:11)
#11     CompilerDiagnosticReporter.withCurrentElement (package:compiler/src/compiler.dart:819:15)

Fixed via 90127334ea4aab5267135b959e361229dfac6bc9


Document - how to write a UI plugin (external/internal)

Document similar to old/legacy UI how to write a UI plugin with a CRUD (list/create/update/delete) example.

Basic customisation doc added in repo, will need to update on the docs website on separate repo


Specifying Cassandra hosts on different ports

Sometimes different hosts might have different ports. Right now the port must be the same for each host, while instead it should support the host:port format like:
hosts:
   - "<IP_ADDRESS>:9042"
   - "<IP_ADDRESS>:3451"

That depends on the driver, not me. Please stop assigning.

It is assigned to you because you are the best person to close this issue since you implemented the DAO and you are a main contributor of the Cassandra driver that Kong is using.

Unfortunately the driver only supports an array of hosts coupled with a single port as deducible from the connect method. An update can be considered but we'll have to ask the owner first.

Related to https://github.com/jbochi/lua-resty-cassandra/issues/55

PR opened on the driver jbochi/lua-resty-cassandra#56


Add support for group_clusters

New API: https://docs.gitlab.com/ee/api/group_clusters.html
In support of https://github.com/terraform-providers/terraform-provider-gitlab/issues/138

Fixed by PR #685


2fa - appears to be broken

Just tested app with 2fa enabled via Yubico Authenticator, my credentials work on github.com along with my 2fa codes.  However pockethub complains, "Please enter valid password".
If I disable 2fa on github temporarily then I can login fine and it all works, however I don't wish to disable 2fa just so I can use this mobile app. :(
Also verified that 2fa works with other mobile apps that integrate with github login (gitter) and it worked fine.

What version of the app are you running? Is it built from master or the play store?

I am getting the same issue. My version is from the play store (1.9.0).
Both the password and the 2FA code are correctly verified, because I get different errors with the wrong ones: A wrong password will be rejected without a 2FA prompt; a wrong 2FA code will show the error "Unable to connect to github" instead of "Please enter valid login credentials").
I've been using this app with 2FA successfully as recently as May; I don't know when it stopped working.

Since this is a play store issue it's irrelevant for now. The app has been taken down from the Play Store and is not supported. We will in the near future release a app which will fix these issues.


Get spamd working

get spamd working along with nixspamd lists
https://www.openbsd.org/spamd/

Spamd has been removed in favor of using rspamd greylisting.


Support cross-partition continuation tokens in node.js SDK

Right now, node.js SDK only supports continuation tokens for single partition queries. This is a request for cross-partition continuation token support in the node.js SDK.

is this still not possible? my partition key is the id field and i want to paginate my results using a continuation token.  if i use the following the only headers i get back are 'x-ms-request-charge' and 'x-ms-documentdb-query-metrics'.  no continuation token
    const results = await db
      .database(process.env.DATABASE_ID)
      .container('ratings')
      .items.query(querySpec, {
        maxItemCount: 2,
        enableCrossPartitionQuery: true,
        continuationToken: continuationToken ? continuationToken : null,
      })
      .fetchNext()

@topshot99 can you check?

@exiledwolfking To help us reproduce the issue, could you provide the querySpec, SDK version, and response that you're currently receiving?

Sure.   Obviously it only returns the one item with that id though.
headers = {
'cache-control': 'no-store, no-cache',
pragma: 'no-cache',
'transfer-encoding': 'chunked',
'content-type': 'application/json',
server: 'Microsoft-HTTPAPI/2.0',
'strict-transport-security': 'max-age=31536000',
'x-ms-activity-id': '574862da-14b6-42a6-9eb0-8bd3ba865c14',
'x-ms-last-state-change-utc': 'Fri, 17 Mar 2023 18:31:23.150 GMT',
'x-ms-resource-quota': 'documentSize=51200;documentsSize=52428800;documentsCount=-1;collectionSize=52428800;',
'x-ms-resource-usage': 'documentSize=0;documentsSize=162;documentsCount=39;collectionSize=172;',
'x-ms-schemaversion': '1.15',
lsn: '979',
'x-ms-item-count': '1',
'x-ms-request-charge': '2.93',
'x-ms-alt-content-path': 'dbs/game-rater/colls/ratings',
'x-ms-content-path': 'nuJhAKC+4dE=',
'x-ms-documentdb-partitionkeyrangeid': '0',
'x-ms-xp-role': '1',
'x-ms-cosmos-query-execution-info': '{"reverseRidEnabled":false,"reverseIndexScan":true}',
'x-ms-global-committed-lsn': '978',
'x-ms-number-of-read-regions': '0',
'x-ms-transport-request-id': '7',
'x-ms-cosmos-llsn': '979',
'x-ms-session-token': '0:-1#979',
'x-ms-request-duration-ms': '0.809',
'x-ms-serviceversion': 'version=<IP_ADDRESS>',
'x-ms-cosmos-is-partition-key-delete-pending': 'false',
'x-ms-gatewayversion': 'version=2.14.0',
date: 'Fri, 31 Mar 2023 00:39:02 GMT',
'x-ms-throttle-retry-count': 0,
'x-ms-throttle-retry-wait-time-ms': 0
}

Hey @exiledwolfking,
At the moment, you can use the following approach:
` const container = await db.container(process.env.CONTAINER_NAME);
const queryOptions = {
maxItemCount: 2,
enableCrossPartitionQuery: true,
}
const querIterator = await container.items.query(querySpec, queryOptions);
while (querIterator.hasMoreResults()) {
const { resources: result } = await querIterator.fetchNext();
//Do something with result
}
`
With this method, the query iterator is initialized only once, and all the data is retrieved using the iterator. The SDK handles everything in this case.
We are currently working on a solution to retrieve the continuation token from the headers, which will be available soon.

Okay thanks for the help. Looking forward to to it
On Mon, Apr 3, 2023, 1:29 AM Manik Khandelwal @.***>
wrote:

Hey @exiledwolfking https://github.com/exiledwolfking,
At the moment, you can use the following approach:
` const container = await db.container(process.env.CONTAINER_NAME);
const queryOptions = {
maxItemCount: 2,
enableCrossPartitionQuery: true,
}
const querIterator = await container.items.query(querySpec, queryOptions);
while (querIterator.hasMoreResults()) {
const { resources: result } = await querIterator.fetchNext();
//Do something with result
}
`
With this method, the query iterator is initialized only once, and all the
data is retrieved using the iterator. The SDK handles everything in this
case.
We are currently working on a solution to retrieve the continuation token
from the headers, which will be available soon.
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-sdk-for-js/issues/20140#issuecomment-1493743035,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADFXLYM2QJR7RHK6VTCE6MTW7JU6FANCNFSM5NGXFPTQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@topshot99  thanks to get back to me. In case we don't use aggregation in our query will be possible works with continuation tokens? I mean send back that token to the caller so it can use iteratively in his application to retrieve the next page etc..etc..

@diiiego83 Indeed, it would be effective in that scenario

Hey we just ran into this issue. We'll build a java sidecar for now but do you have any time or roadmap when this will get into the Node SDK? :)

@topshot99 the iteration works fine if no need to pass around the continuation token (for this we still have a sidecar). I have better results using the fetchAll() from the JS SDK. Is this method working fine for aggregation queries on cross partition? Just want to know if internally implement the same While/fetchNext() pattern. Thanks

Absolutely, the fetchAll() method is indeed suitable for performing aggregation queries that span multiple partitions. It's worth noting that there's no need for an internal implementation of the While/fetchNext() pattern, as fetchAll() returns all the available results/items.


Support selecting relative revisions for show

Fixes #1499
RELEASE_NOTES=[ENHANCEMENT] Support relative revisions for show
Signed-off-by: Dominik Schulz<EMAIL_ADDRESS>

Codecov Report

Merging #1508 into master will decrease coverage by 0.06%.
The diff coverage is 27.27%.

@@            Coverage Diff             @@
##           master    #1508      +/-   ##
==========================================
- Coverage   60.96%   60.89%   -0.06%
==========================================
  Files         219      219
  Lines       12199    12220      +21
==========================================
+ Hits         7436     7441       +5
- Misses       3940     3955      +15
- Partials      823      824       +1

Impacted Files
Coverage Δ

internal/action/show.go
42.38% <23.81%> (-3.00%)
:arrow_down:

internal/action/commands.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9726700...337ee3c. Read the comment docs.


refactor the flutter-analyze try bot and downstream failure notifications

This is a meta issue to track work related to 1) adding more repositories to our flutter-analyze try bot, and 2) relax some of the analysis settings on the flutter/tests contributed tests repo. The general goal for these changes are to enable the analyzer team to be aware of breakages that their changes would cause, know which places will need to be forward patched to not impede the sdk -> flutter roll process, and to omit a class of issues from needing to be patched (to not break the roll process for some category of changes).
Currently most (all?) of the flutter/tests user contributed tests fail on any analysis change. However, the intent here is more to make sure that flutter is aware of breaking API changes. Below, I propose to change the tests to only fail on more severe analysis issues (errors or warnings). We may in the future make this more sophisticated - to leverage package:flutter_lints in some capacity to also fail on some set of lint warnings.

[ ] have flutter-analyze analyze flutter/flutter (it's doing this today; the potential improvement to this being to also run analysis for dartdoc sample code - https://github.com/flutter/flutter/blob/master/dev/bots/analyze_sample_code.dart)
[ ] have flutter-analyze analyze flutter/engine; we're doing this now, but might want to do some additional work to make it easier to use the same analysis script as what flutter/engine does
[ ] have flutter-analyze analyze flutter/plugins; see https://github.com/dart-lang/sdk/issues/45873
[ ] have flutter-analyze analyze flutter/packages
[ ] update user contributed scripts in the flutter/tests registry/ dir to only fail on errors (or possibly warnings); see https://github.com/flutter/flutter/pull/82778/checks?check_run_id=2606817706 for a list of failed locations for the recent unused imports change
[ ] update the readme in flutter/tests to indicate that contributed tests should not fail on info level analysis items (or, possibly, warning level items)
[ ] come back and decide whether we want to change the flutter/tests analysis criteria to be more sophisticated than just being based on analysis issue severity (perhaps using something based on package:flutter_lints?)
[ ] decide whether we want to exclude some flutter repos from our try bot (flutter/cocoon ?) and rely on the HHH bot to catch issues post-commit

See https://github.com/dart-lang/sdk/issues/46063 for more context; https://github.com/flutter/tests/tree/master/registry for the flutter customer tests repo.

cc @Hixie @goderbauer - if we can agree on some of the items above (wrt flutter/tests changes), I'll follow up with some PRs to flutter/tests

Is there an overview of what the analyzer considers an error or warning? I am curious to see what issues we would still catch for packages who have contributed tests to the tests repository.

Most actual issues related to an API refactoring would be error level severity issues. Lints and hints (essentially built-in lints) are info level severity. There are actually very few warning level severity items (there were more in the Dart 1 days).
Lints can't emit warning level items, however, an analysis options file can later upgrade them to be warning level items for a project. I'll poke around for a list of the warning level items.

Adding the full set if analysis infos, warnings, and errors.
infos.txt
warnings.txt
errors.txt
And here's the set of warnings inlined:
analysis_option_deprecated
camera_permissions_incompatible
dead_null_aware_expression
include_file_not_found
included_file_warning
invalid_dependency
invalid_null_aware_operator
invalid_null_aware_operator
invalid_option
invalid_override_different_default_values_named
invalid_override_different_default_values_positional
invalid_section_format
missing_enum_constant_in_switch
no_touchscreen_feature
non_resizable_activity
path_does_not_exist
path_pubspec_does_not_exist
permission_implies_unsupported_hardware
setting_orientation_on_activity
spec_mode_removed
unnecessary_non_null_assertion
unrecognized_error_code
unsupported_chrome_os_feature
unsupported_chrome_os_hardware
unsupported_option_with_legal_value
unsupported_option_with_legal_values
unsupported_option_without_values
unsupported_value

I couldn't find any documentation on these warnings. Does the presence of these may mean that your app doesn't compile/run anymore?
In other words, I am fine with this proposal as long as we still get notified if we break packages in the tests repository in the sense that their code doesn't compile or run anymore.

I removed some of the warnings for pubspec files and other non-dart files, and added in the descriptions:
dead_null_aware_expression:
  https://dart.dev/tools/diagnostic-messages#dead_null_aware_expression
  The left operand can't be null, so the right operand is never executed.

invalid_null_aware_operator:
  https://dart.dev/tools/diagnostic-messages#invalid_null_aware_operator
  The receiver can't be null, so the null-aware operator '{0}' is unnecessary.

invalid_null_aware_operator:
  https://dart.dev/tools/diagnostic-messages#invalid_null_aware_operator
  The receiver can't be null because of short-circuiting, so the null-aware operator '{0}' can't be used.

invalid_override_different_default_values_named:
  Parameters can't override default values, this method overrides '{0}.{1}' where '{2}' has a different value.

invalid_override_different_default_values_positional:
  Parameters can't override default values, this method overrides '{0}.{1}' where this positional parameter has a different value.

missing_enum_constant_in_switch:
  https://dart.dev/tools/diagnostic-messages#missing_enum_constant_in_switch
  Missing case clause for '{0}'.

unnecessary_non_null_assertion:
  https://dart.dev/tools/diagnostic-messages#unnecessary_non_null_assertion
  The '!' will have no effect because the receiver can't be null.

In other words, I am fine with this proposal as long as we still get notified if we break packages in the tests repository in the sense that their code doesn't compile or run anymore.

Yes, that'll be the case - for those kinds of breakages, we'll emit error level issues.

Looking at that list, it would make sense to fail on errors and warnings. For example, if we add a new value to an existing enum (which presumably triggers missing_enum_constant_in_switch ) we'd want that to be treated as a breaking change.

If it's just that one code - missing_enum_constant_in_switch - I think I'd like to look to make this more restrictive in the future; to look to how we could switch to just using errors (promoting that warning to an error)?
But I think we can tackle that as part of the 'come back and decide whether we want to change the flutter/tests analysis criteria' checkbox above. For now, just ignoring info level items sgtm.

A PR to flutter/tests to update the static analysis and the test guidance: https://github.com/flutter/tests/pull/105. We may evolve the criteria we check on in the future (ignore warnings? use errors and a sub-set of package:flutter_lints?).


Docs > Components > Button-group > Split button : Add "not in ODS" alert message + explanation

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
These buttons group are not present in the Orange Design System (ODS), otherwise, they exist with a toggle behavior.
So, it could be useful to indicate in Boosted's Docs that these components do not belong to ODS and therefore should behave as the ODS unitary button of ODS.
Motivation and context
The goal is to avoid confusion and using a component in ODS when it shouldn't be.

This "Split button" section doesn't exist anymore in Boosted V5.2.
Split button show in the new section "Nesting" and in the "Vertical variation" section. Design callout message have been added. Therefore, I'm closing this issue.


xSQLServerDatabaseDefaultLocation: Integration Tests

Pull Request (PR) description
Created integration tests for xSQLServerDatabaseDefaultLocation
This Pull Request (PR) fixes the following issues:
n/a
Task list:

[ ] Change details added to Unreleased section of CHANGELOG.md?
[ ] Added/updated documentation, comment-based help and descriptions in .schema.mof files where appropriate?
[ ] Examples appropriately updated?
[x] New/changed code adheres to Style Guidelines?
[X] Unit and (optional) Integration tests created/updated where possible?

Codecov Report

Merging #1 into xSQLServerDatabaseDefaultLocation will not change coverage.
The diff coverage is n/a.

@@                       Coverage Diff                        @@
##           xSQLServerDatabaseDefaultLocation     #1   +/-   ##
================================================================
  Coverage                                 96%    96%
================================================================
  Files                                     32     32
  Lines                                   3453   3453
================================================================
  Hits                                    3336   3336
  Misses                                   117    117


Nuget Package

I suggest that we create a Nuget package for this project.  What do you think?

Certainly. I'm going to do the .net core transition first. I've been lazy but will try to do both this week.

+1

@MarkEwer give the nuget package a try with your project and please open a new issue if there's a problem.

sorry for the delay … yes, this worked perfectly. I had to upgrade our Team City build agents and our web farm from .Net 4.5.2 but now that I have done that all is good.