*** /etc/my_init.d/40_install_xeoma.sh failed with status 1 etc/my_init.d/40_install_xeoma.sh: line 131: /config/nf: No such file or directory Grep: /config/nf: No such file or directory *** Running /etc/my_init.d/40_install_xeoma.sh. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh.

Contact us xeoma software#

This actually means you can go periods of time without having to renew your license so it actually saves you money while still having the latest version (and also gives the company incentive to keep updating their software since you only pay for upgrades outside of your license). I prefer this release cycle because if they don't release updates when my license expires I just keep using the same version (latest) and not paying until they actually release a new version. Here is the Xeoma change history page they always update: I have all my keys and their purchase date in Lastpass to keep it easy (as well as their expiration date) and just compare the release page to what dates I have for my licenses. All you do is go to Xeoma's change list and see what versions were released while your license was active. Lots of software uses a release cycle like this and it is nothing new or complicated. This makes it a bit tougher to 'predict' what version you can use (though, of course, sticking to the version that is current when you got your license will work, but you MAY be entitled to a later version). Any versions that are released after your license expiration will not work. You do not get a license for a specific version, you get a license for a specific date. I think it may even be a bit stranger than that. Since i changed this, this docker works think you should add that to the first page (the version should be the highest you payd for)

Contact us xeoma update#

So, be sure to dont use auto update on this container, or this command in 'extra parameters' (without quotes ofc)

So lets say u buy version 1.0 then you get till version 1.1 free, when the container updates to 1.2, your setup stops working. Your licence is only up to a special version. I found out why this program 'sometimes' from one day to other day stopped working. I tried using this docker awhile ago, but just ended up using a vm for it and it's been rock solid. I've tried most of them and settled on Xeoma. Of course that is just my opinion, but I hope this helps others who are trying to determine which surveillance software to use. Xeoma is a great choice for many people to balance resource utilization, licensing cost, features, and UX (user experience). I opt not to buffer the stream so I get near real-time data and decode it on the computer I'm watching the stream from and use the GPU to handle the decoding so I don't get any connection issues.

Contact us xeoma archive#

For example, if you choose to buffer and transcode the archive on your server rather than the client your server hardware needs to be powerful enough to handle that. As for why PTZ isn't working in your case you should contact the developer and explain your issue with your specific camera model.Īs for your connection issue, it might be your camera configuration module or client settings. Once I set those settings I rarely change them. Nearly all of my camera configurations like zoom, rotation, text overlay, network settings, picture quality settings, I set using my camera's UI as well. I don't have PTZ cameras, but do have a couple varifocal and zooming does work through Xeoma (just tested). I couldn't even get a decent camera connection going.I admit my IP camera is a Foscam on the older side, but it wouldn't give me much control over it, like tilt and pan, etc.I had to keep dropping back to the camera UI to make adjustments. (when I have time to include presence detection this workflow will be updated to query HA for presence prior to uploading to Slack)

Xeoma: Send an http request to node-red Xeoma: Create an archive (only way to get an mp4) Xeoma: When a motion event is triggered Combining node-red with Xeoma has given me even more flexibility to set up complex workflows that can't be done using Xeoma only.įor instance one of the workflows I have is integrating Xeoma with Slack: I've used Xeoma for years and continue to do so because the developer is responsive to emails, bugs I've brought up get patched usually in the next version, chaining modules gives you a lot of control over specific workflows, and Xeoma is relatively light on hardware resources compared to others. What are you trying to do in Xeoma that has led you to think it's terrible? Unfortunately tho, Xeoma is a terrible product and you get much, much more functionality with Zoneminder, its looks dated.