Xeoma - Surveillance Software


Recommended Posts

On 10/29/2020 at 2:33 AM, vakilando said:

My xeoma docker (I'm using https://hub.docker.com/r/coppit/xeoma/from coppit) only sends telegram messages to me when motion is detected.

As @CraziFuzzy said xeomas HTTP Request sender can also send requests to HA's http sensor.

The other way around my home assistant starts and stops the the surveillancy with a http switch that breaks the xeoma curcuit. This is done manually by a switch in HA and automatically at night and when I'm away (a curl command). When I'm away and a door is opened the recording starts also.

Thanks guys. Yes I use HA to turn on and off the recording as well. I use node-red for all my automations and used to use a http in node to etc stuff from xeoma for a long time until it broke and http stuff had hiccups. I then install mqtt and went from there. I havent tried http directly into HA but will investigate.....

Link to comment
On 10/29/2020 at 2:33 AM, vakilando said:

My xeoma docker (I'm using https://hub.docker.com/r/coppit/xeoma/from coppit) only sends telegram messages to me when motion is detected.

As @CraziFuzzy said xeomas HTTP Request sender can also send requests to HA's http sensor.

The other way around my home assistant starts and stops the the surveillancy with a http switch that breaks the xeoma curcuit. This is done manually by a switch in HA and automatically at night and when I'm away (a curl command). When I'm away and a door is opened the recording starts also.

I was trying to get the http request sender to work but when I hit the test button it says its succesful but at the http server end I dont see it....... 

Link to comment
  • 1 month later...

Anyone else having issues starting this docker?

 

*** Running /etc/my_init.d/40_install_xeoma.py...
2020-12-15 20:56:48 Determining version of Xeoma to use
2020-12-15 20:56:48 Config version is "latest"
2020-12-15 20:56:48 Fetching version information from Felenasoft at http://felenasoft.com/xeoma/downloads/version3.xml
Traceback (most recent call last):
File "/etc/my_init.d/40_install_xeoma.py", line 182, in <module>
version_number, download_url, alternate_download_url = resolve_download_info()
File "/etc/my_init.d/40_install_xeoma.py", line 70, in resolve_download_info
version_number, download_url, alternate_download_url = latest_version()
File "/etc/my_init.d/40_install_xeoma.py", line 38, in latest_version
e = xml.etree.ElementTree.ElementTree(file=urllib.request.urlopen(VERSION_URL)).getroot()
File "/usr/lib/python3.6/urllib/request.py", line 223, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib/python3.6/urllib/request.py", line 532, in open
response = meth(req, response)
File "/usr/lib/python3.6/urllib/request.py", line 642, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python3.6/urllib/request.py", line 570, in error
return self._call_chain(*args)
File "/usr/lib/python3.6/urllib/request.py", line 504, in _call_chain
result = func(*args)
File "/usr/lib/python3.6/urllib/request.py", line 650, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 404: Not Found
*** /etc/my_init.d/40_install_xeoma.py failed with status 1

*** Killing all processes...
Dec 15 20:56:49 5f32b2e3a36b syslog-ng[13]: syslog-ng shutting down; version='3.13.2'

 

Link to comment

Same error here.

 

http://felenasoft.com/xeoma/downloads/version3.xml

 

It's a 404 now...

 

The correct url location now looks like:

http://felenasoft.com/xeoma/downloads/version.xml

 

On 12/16/2020 at 4:53 AM, mi5key said:

Anyone else having issues starting this docker?

 


*** Running /etc/my_init.d/40_install_xeoma.py...
2020-12-15 20:56:48 Determining version of Xeoma to use
2020-12-15 20:56:48 Config version is "latest"
2020-12-15 20:56:48 Fetching version information from Felenasoft at http://felenasoft.com/xeoma/downloads/version3.xml
Traceback (most recent call last):
File "/etc/my_init.d/40_install_xeoma.py", line 182, in <module>
version_number, download_url, alternate_download_url = resolve_download_info()
File "/etc/my_init.d/40_install_xeoma.py", line 70, in resolve_download_info
version_number, download_url, alternate_download_url = latest_version()
File "/etc/my_init.d/40_install_xeoma.py", line 38, in latest_version
e = xml.etree.ElementTree.ElementTree(file=urllib.request.urlopen(VERSION_URL)).getroot()
File "/usr/lib/python3.6/urllib/request.py", line 223, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib/python3.6/urllib/request.py", line 532, in open
response = meth(req, response)
File "/usr/lib/python3.6/urllib/request.py", line 642, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python3.6/urllib/request.py", line 570, in error
return self._call_chain(*args)
File "/usr/lib/python3.6/urllib/request.py", line 504, in _call_chain
result = func(*args)
File "/usr/lib/python3.6/urllib/request.py", line 650, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 404: Not Found
*** /etc/my_init.d/40_install_xeoma.py failed with status 1

*** Killing all processes...
Dec 15 20:56:49 5f32b2e3a36b syslog-ng[13]: syslog-ng shutting down; version='3.13.2'

 

 

Edited by pcaro
Link to comment
11 hours ago, tsakodim said:

So is it official? Xeoma app dead?

No, I just put the VERSION in the /mnt/user/appdata/Xeoma/xeoma.config and it works just fine.  But coppit will have to update the image with the correct URL for the automatic updates to come in.

 

# The version to use. Valid values are a string like '17.5.5', 'latest', 'latest_beta', or a URL.
#VERSION='latest'
VERSION='20.11.30'

 

Edited by mi5key
Link to comment
7 hours ago, mi5key said:

No, I just put the VERSION in the /mnt/user/appdata/Xeoma/xeoma.config and it works just fine.  But coppit will have to update the image with the correct URL for the automatic updates to come in.

 


# The version to use. Valid values are a string like '17.5.5', 'latest', 'latest_beta', or a URL.
#VERSION='latest'
VERSION='20.11.30'

 

Thanks mi5key i did it and now its running but.... can't connect to it. This is what docker logs xeoma returns:

 

*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/10_syslog-ng.init...
Dec 19 11:27:06 d0de56771b3d syslog-ng[13]: syslog-ng starting up; version='3.13.2'
*** Running /etc/my_init.d/30_parse_config_file.sh...
Configuration:
  PASSWORD=<hidden>
  VERSION=20.11.30
*** Running /etc/my_init.d/40_install_xeoma.py...
2020-12-19 11:27:07 Determining version of Xeoma to use
2020-12-19 11:27:07 Config version is "20.11.30"
2020-12-19 11:27:07 Using Xeoma version 20.11.30 (a user-specified version)
2020-12-19 11:27:07 Downloaded file /config/downloads/xeoma_20.11.30.tgz already exists. Skipping download
2020-12-19 11:27:07 Installing Xeoma from /config/downloads/xeoma_20.11.30.tgz
2020-12-19 11:27:08 Installation complete
*** Running /etc/my_init.d/50_configure_xeoma.sh...
[Dec 19 11:27:08 AM] Setting the password


Password set successfull
*** Booting runit daemon...
*** Runit started as PID 70
[Dec 19 11:27:08 AM] Starting the server in 5 seconds. See the log directory in your config directory for server logs.
Dec 19 11:27:08 d0de56771b3d cron[75]: (CRON) INFO (pidfile fd = 3)
Dec 19 11:27:08 d0de56771b3d cron[75]: (CRON) INFO (Running @reboot jobs)
[Dec 19 11:27:08 AM] Not using archive cache
/bin/sh: 1: ip: not found
/bin/sh: 1: ip: not found
/bin/sh: 1: ip: not found
/bin/sh: 1: ip: not found

 

I run it in bridge mode but I have tried also host mode and still the same. I ping the address from a windows pc and nothing there too.

 

I must have missed an important step I guess

 

 

Screenshot 2020-12-19 133203.jpg

Link to comment
7 hours ago, tsakodim said:

Thanks mi5key i did it and now its running but.... can't connect to it. This is what docker logs xeoma returns:

 

...

 

I run it in bridge mode but I have tried also host mode and still the same. I ping the address from a windows pc and nothing there too.

 

I must have missed an important step I guess

 

 

Screenshot 2020-12-19 133203.jpg

That all looks normal, same as mine.  Is this a first time setup?

Link to comment
  • 2 weeks later...
  • 1 month later...
  • 2 weeks later...

Welp... I just went ahead and tried to install this docker since no one is responding on this thread any longer and realized that the docker just doesn't work. I've tried removing and re-installing, and it just doesn't seem to work. 

current errors:

Feb 21 14:53:55 Tower nginx: 2021/02/21 14:53:55 [error] 5517#5517: *2598679 connect() to unix:/var/tmp/Xeoma.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.174, server: , request: "GET /dockerterminal/Xeoma/token HTTP/1.1", upstream: "http://unix:/var/tmp/Xeoma.sock:/token", host: "tower", referrer: "http://tower/dockerterminal/Xeoma/"
Feb 21 14:53:55 Tower nginx: 2021/02/21 14:53:55 [error] 5517#5517: *2598911 connect() to unix:/var/tmp/Xeoma.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.174, server: , request: "GET /dockerterminal/Xeoma/ws HTTP/1.1", upstream: "http://unix:/var/tmp/Xeoma.sock:/ws", host: "tower"

Link to comment
  • 1 month later...

Just updated to version 21.3.4 (image from coppit).

Xeoma still works as expected (webUI, Client on Linux/Android).

Waiting some time to see if all the schemes/chains (with http-switches, automations in home assistant) still work as expected...

my xeoma.conf looks like this now:

# The password for clients to use to connect. Avoid backslashes and apostrophes.
PASSWORD='nonononotshownhere'

# The version to use. Valid values are a string like '17.5.5', 'latest', 'latest_beta', or a URL.
#VERSION='latest'
#VERSION='19.4.22'
#VERSION='19.11.26'
#VERSION='20.4.28'
#VERSION='20.11.30'
VERSION='21.3.4'

 

Link to comment
  • 2 months later...
  • 5 months later...
Password set successfull
*** Booting runit daemon...
*** Runit started as PID 67
[Nov 27 10:51:51 PM] Starting the server in 5 seconds. See the log directory in your config directory for server logs.
[Nov 27 10:51:51 PM] Not using archive cache
Nov 27 22:51:51 20f92adf2710 cron[71]: (CRON) INFO (pidfile fd = 3)
Nov 27 22:51:51 20f92adf2710 cron[71]: (CRON) INFO (Running @reboot jobs)
/bin/sh: 1: ip: not found
/bin/sh: 1: ip: not found
/bin/sh: 1: ip: not found
/bin/sh: 1: ip: not found
/bin/sh: 1: ip: not found
/bin/sh: 1: ip: not found

What to do? Anyone got any advice?

Link to comment
  • 8 months later...

The container stopped running after the latest release. I got the following error in the config:
Aug 19 13:18:04 53bcf951e6c9 syslog-ng[13]: syslog-ng starting up; version='3.13.2'
*** Running /etc/my_init.d/30_parse_config_file.sh...
Configuration:
PASSWORD=<hidden>
VERSION=latest
*** Running /etc/my_init.d/40_install_xeoma.py...
2022-08-19 13:18:04 Determining version of Xeoma to use
2022-08-19 13:18:04 Config version is "latest"
2022-08-19 13:18:04 Fetching version information from Felenasoft at http://felenasoft.com/xeoma/downloads/version3.xml
2022-08-19 13:18:04 Using Xeoma version 22.8.16 (the latest stable version)
2022-08-19 13:18:04 Deleting files in /config/downloads to reclaim space...
2022-08-19 13:18:04 Downloading from http://felenasoft.com/xeoma/downloads/latest/linux/xeoma_linux64.tgz into /config/downloads
2022-08-19 13:18:04 Downloading from http://felenasoft.com/xeoma/downloads/latest/linux/xeoma_linux64.tgz
2022-08-19 13:18:09 Downloaded to /config/downloads/xeoma_22.8.16.tgz
2022-08-19 13:18:09 Skipping installation because the currently installed version is the correct one
*** Running /etc/my_init.d/50_configure_xeoma.sh...
[Aug 19 01:18:10 PM] Setting the password
/etc/my_init.d/50_configure_xeoma.sh: line 58: 61 Segmentation fault /usr/bin/xeoma -setpassword "$PASSWORD"
*** /etc/my_init.d/50_configure_xeoma.sh failed with status 139
*** Killing all processes...
Aug 19 13:18:10 53bcf951e6c9 syslog-ng[13]: syslog-ng shutting down; version='3.13.2'
I tried deleting the config and setting a new password, but the issue continues.
Any ideas?

Link to comment
  • 2 weeks later...
On 8/19/2022 at 4:31 PM, chris1 said:

The container stopped running after the latest release. I got the following error in the config:
Aug 19 13:18:04 53bcf951e6c9 syslog-ng[13]: syslog-ng starting up; version='3.13.2'
*** Running /etc/my_init.d/30_parse_config_file.sh...
Configuration:
PASSWORD=<hidden>
VERSION=latest
*** Running /etc/my_init.d/40_install_xeoma.py...
2022-08-19 13:18:04 Determining version of Xeoma to use
2022-08-19 13:18:04 Config version is "latest"
2022-08-19 13:18:04 Fetching version information from Felenasoft at http://felenasoft.com/xeoma/downloads/version3.xml
2022-08-19 13:18:04 Using Xeoma version 22.8.16 (the latest stable version)
2022-08-19 13:18:04 Deleting files in /config/downloads to reclaim space...
2022-08-19 13:18:04 Downloading from http://felenasoft.com/xeoma/downloads/latest/linux/xeoma_linux64.tgz into /config/downloads
2022-08-19 13:18:04 Downloading from http://felenasoft.com/xeoma/downloads/latest/linux/xeoma_linux64.tgz
2022-08-19 13:18:09 Downloaded to /config/downloads/xeoma_22.8.16.tgz
2022-08-19 13:18:09 Skipping installation because the currently installed version is the correct one
*** Running /etc/my_init.d/50_configure_xeoma.sh...
[Aug 19 01:18:10 PM] Setting the password
/etc/my_init.d/50_configure_xeoma.sh: line 58: 61 Segmentation fault /usr/bin/xeoma -setpassword "$PASSWORD"
*** /etc/my_init.d/50_configure_xeoma.sh failed with status 139
*** Killing all processes...
Aug 19 13:18:10 53bcf951e6c9 syslog-ng[13]: syslog-ng shutting down; version='3.13.2'
I tried deleting the config and setting a new password, but the issue continues.
Any ideas?

I Had a similar issue with the latest (22.8.16) version.

only option for me was to download a previous version, for me only 22.3.16 was available, and putt it in the appdata-download folder of Xeoma.

editing the config file to mentioned the version 22.3.16, and now its working again.

not sure what the problem with the 22.8.16 is.

Edited by Matt77
Link to comment
  • 2 weeks later...
On 8/27/2022 at 6:40 PM, Matt77 said:

I Had a similar issue with the latest (22.8.16) version.

only option for me was to download a previous version, for me only 22.3.16 was available, and putt it in the appdata-download folder of Xeoma.

editing the config file to mentioned the version 22.3.16, and now its working again.

not sure what the problem with the 22.8.16 is.

 

I tried doing this initially and it didn't work - the problem was I had to use the Linux 64 version and also rename the file in the download folder to xeoma_22.3.16.tgz for the docker init scripts to pick it up.

 

For convienience you can download older Xeoma versions here: https://felenasoft.com/xeoma/en/changes/

Edited by joshkrz
Added Xeoma old version links
Link to comment
  • 4 weeks later...

Same here...

I tried updating to the latest version 22.8.16:

  1. manually downloaded the latest version 22.8.16 (xeoma_linux64.tgz) from felenasoft
  2. renamed xeoma_linux64.tgz to xeoma_22.8.16.tgz
  3. put it in the xeoma download directory (/mnt/cache/appdata/Xeoma/downloads)
  4. changed the config file xeoma.conf by adding: VERSION='22.8.16'

When starting the container it stucks at:

Sep 29 20:09:44 5b7e2d0c1c9d syslog-ng[13]: syslog-ng starting up; version='3.13.2'
Configuration:
  PASSWORD=<hidden>
  VERSION=22.8.16
[Sep 29 08:09:47 PM] Setting the password

 

Reverting to version 22.3.16 and everything is fine....

 

Did somebody find a way to get it up and running, perhaps by manually setting the password?

Link to comment
  • 2 weeks later...

Finally got it working. Going back to 22.3.16

To sum it up.

 

Install the missing ip command we see in the log.

start Xeoma and "quickly" click the icon and select $_ console

run the commands

apt update

apt install iproute2

stop the Xeoma docker container

 

Download Linux 64bit version from https://felenasoft.com/xeoma/en/changes/ (scroll down a bit)

Put it in your config folder, for me it is /mnt/user/appdata/Xeoma

Rename the file to xeoma_22.3.16.tgz

Put it in /mnt/user/appdata/Xeoma/downloads/

I also unpacked it via a shell by going to the downloads folder and running the command 

tar zxvf xeoma_22.3.16.tgz

then I went back to /mnt/user/appdata/Xeoma

changed the config file as below

# The password for clients to use to connect. Avoid backslashes and apostrophes.
PASSWORD='xxxxxxxxx'

# The version to use. Valid values are a string like '17.5.5', 'latest', 'latest_beta', or a URL.
VERSION='22.3.16'

 

Started Xeoma in the Unraid docker tab.

I'm back up and running.

 

With the missing ip command, it may work with the latest but right now, I just want to be up and running again.

 

 

Link to comment
  • 4 weeks later...

Performance Downgrade with docker | What could it be?.

 

Before i was running a LXC Container in Proxmox (Ubuntu 20.04), with 2 Cores available:

 

Screenshot_20221031_110239.png.7e0d441fb007facd37251648d585b1ce.png

Average around 40 - 50%

 

And this is the CPU load with docker, in the same 2 cores:

(Not running other Docker / VM's at the moment)

 

image.png.e6d43f9b1ea263450f731d6a59ee73fd.png

Average 70 - 98%

image.png.61de466c6900789b48cb2c3d0f6fd7e6.png

 

 

 

The setup of Xeoma and load its exactly the same, as the number of cameras and  configurations didnt change (Using the export setup method).

 

So.... i find it estrange, i was expecting some changes, but considering that both are running the same APP, in a simillar linux kernel, so having double the load can be right... right?

 

 

  • This seems normal?, where should i start to look?
  • Docker has higher overhead than a lxc container?, if so, this much?
  • Can i do something other than upgrading my CPU?

Greetings!

Edited by mrdavvv
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.