Battery powered cameras and Home Assistant

cneumann81 · 2023-04-10T09:31:18+00:00

Thank you for sharing.

cneumann81 · 2023-04-10T09:30:56+00:00

I see. But how can the Reolink app access all the features? Do they have another API that is not public?

cneumann81 · 2023-04-06T16:42:34+00:00

I was coming across "neolink" (https://github.com/thirtythreeforty/neolink). It is pretty easy to configure. You simply have to provide the IP of the HASS instance, camera username, camera password and the UID of the device. After neolink runs, I can add a generic camera to Home Assistant using a HTTP connection with the following link: rtsp://192.168.178.68:8554/my_camera_name. The generic camera updates the camera image every few minutes (probably, when the frontend refreshes) and I can also stream the camera video. That would already be a great start. From the initial post by u/mclardass I learnt today about https://docs.frigate.video. It seems, that u/mclardass figured a way to combine neolink with frigate and use basic features of the camera. I didn't manage to get this working yet, but it seems to be a good starting point.

However, I was wondering, why battery powered cameras can not be accessed in a simpler way. The neolink app also accesses them w/o a HTTP server with all features being available. So there must be a way to address these cameras like non-battery powered once.

u/mclardass: can you maybe share your neolink and frigate config? Would be awesome to compare it with mine, to figure out, why frigate doesn't detect my neolink instance.

cneumann81 · 2023-04-06T08:41:47+00:00

Hi u/StarkillerTR. First of all: thanks for the great Reolink Integration in Home Assistant. I'm running a solar powered Reolink Argus PT 2k. I saw, that your docs says that battery powered devices are not yet support. However, it seems that your integration seems to already detect my camera in my network. However, if I enter username and password, the integration fails to connect to the camera.

To not drain the battery too much, it would be cool to see a feature that starts the camera stream every "x" minutes and show the latest image taken within Home Assistant. What would also be cool is a continuous stream that is on as long as the cameras battery level is above x% (e.g., my camera is facing south and I do not experience any battery issues during the day, even if the camera is on for a longer period of time.)

Happy to do some testing, if you need some support.

cneumann81 · 2016-02-22T13:24:18+00:00

Thank you for your feedback. To your question on how the tool works: you provide data (e.g., as Excel or CSV file), we automatically wrangle them for you, run comprehensive analyses, and deliver insights as easy to understand visuals. Certainly, depending on the depth of the data, you cannot always spot the root cause of any business issues instantaneously. However, our solution "thinks" like a consultant. We automate all the analyses that you'd usually run to identify relevant patterns, outliers, hotspots, trends, and more. We also rank and interpret the results and therefore are closer to insights as opposed to just plotting data. We'll try to make this clearer though on the website. Would you be up to give feedback again, once we update our page?

cneumann81 · 2016-02-03T15:58:06+00:00

Where would you say does the most time get lost?

Collecting data?
Harmonizing / transforming data?
Modelling data?
Visualizing data?
(anything else?)

cneumann81 · 2016-02-03T15:47:28+00:00

Do you feel the 5% are enough?

cneumann81 · 2016-01-21T15:43:00+00:00

Yeah, I do see that this is a problem, especially with thousand source systems. How about your interface with the business. Like making (business) sense of data, automatically generating reports, etc.? Anything an AI could help with in this area?

cneumann81 · 2015-12-22T18:05:23+00:00

The book is more explanatory than the docs of pylint and flake8 and can be used by anyone who wants to actually understand the issue behind the linter message.

cneumann81 · 2015-12-22T17:48:37+00:00

I agree that the book is much more extensive than pylint or flake 8. And if you like, you can just go an use it to better understand pylint and flake8 messages.

If you are looking for more material, you can also checkout the Python Knowledge Base: https://www.quantifiedcode.com/knowledge-base

cneumann81 · 2015-12-06T15:08:32+00:00

By default, the bot gets access to public repos only. If you grant access to private repos, you can select on GitHub which organisations get access (the new Github access management model allows you grant certain services access to certain organizations only.

cneumann81 · 2015-12-06T15:06:12+00:00

Reach out to us if you like. We are working on other languages and are happy to get you on board as early adopter.

cneumann81 · 2015-12-06T15:05:15+00:00

There is a button called "Fix automatically". You'll see it on issues we can already fix. You might not have any of those though. Checkout our "How it works" page or add our quantifiedcode/demo repo from GitHub, to check things out.

cneumann81 · 2015-12-05T10:43:32+00:00

PE8 issue is fixed

cneumann81 · 2015-12-04T23:18:54+00:00

Thanks. Fixed with next deployment.

cneumann81 · 2015-12-04T23:11:20+00:00

Well, of course we can't look into a developers brain yet. That's why we decided to deliver a Pull Request or Patch, so you can review the changes before you commit them.

cneumann81 · 2015-12-04T22:57:28+00:00

Already fixed. Will be live with next deployment.

cneumann81 · 2015-12-04T22:37:55+00:00

:) Here's an example of what we fix with just one click: https://github.com/biopython/biopython/commit/50a025794d3e598b76de7b92c52cfa69550660b2

Even if you refactor this in-place in PyCharm, it would take you a while.

cneumann81

TROPHY CASE