![]() ![]() Here you can change the logo, colors, text, etc. We do not recommend doing follow-up customization improvement on top of a previous attempt.Ĥ) Go to custom folder and open web.xml file (you can use different programs to open. *Note that you should be using a “clean” version of Xeoma every time you do the customization. *Note that you can run the customization tool on a Windows machine only, but Xeoma for any supported operating system can be rebranded with it.ģ) Copy Xeoma’s executable files (xeoma.exe, xeoma.app, xeoma.dmg etc.) to the corresponding subfolder distrib folder. If you need older versions of Xeoma, please check this page Please do not use previously edited customization files.Ģ) Download the Xeoma version that you’d like to customize web interface for. Update python-wink version and multiple wink fixes/updates.Web interface customization – 9 easy steps:ġ) Download the latest version of our free OEM utility from our website. ![]() New venstar climate component ( home-assistant#11639) Improve foscam library exception support ( home-assistant#11701) Multi-Room Support for Greenwave Reality ( home-assistant#11364)Īdded Xeoma camera platform ( home-assistant#11619) Minor fix to configuration validation and related log line. Report scripts and groups as scenes to Alexa ( home-assistant#11900) Implement Alexa temperature sensors ( home-assistant#11930)įixed rfxtrx binary_sensor KeyError on missing optional device_class ( home-assistant#11925)Īllow setting climate devices to AUTO mode via Google Assistant ( home-assistant#11923)įixes home-assistant#11848 ( home-assistant#11915)Īdd "write" service to system_log ( home-assistant#11901)Īllow separate command and state OIDs and payloads in SNMP switch ( home-assistant#11075)Īdd ERC20 tokens to etherscan.io sensor ( home-assistant#11916) Update pyhomematic to 0.1.38 ( home-assistant#11936) The error message provided in this scenario simply informs the user that no cameras were discovered. In scenario 2 above, you still get a 200 response which makes it difficult to determine exactly why camera discovery failed since incorrect configuration of the web server module within Xeoma can also create a situation in which no cameras will be discovered (though this should be obvious since the user won't be able to access their cameras in the Xeoma web ui either). The main issue is that the web server that Xeoma provides doesn't handle HTTP status codes correctly. In both cases the platform will catch and log the error and since it will only add entities to home assistant for cameras it is able to discover, no non-working camera entities will be added. No credential are provided, but credentials are required: The library will attempt to discover cameras, but none will be found and it will raise a XeomaError.Incorrect credentials are provided: The library will attempt to obtain a session key, but fail and it will raise a XeomaError.If this fails, the library raises a XeomaError with an appropriate message and the platform logs that.Īs far as authentication, there are 2 possible failure scenarios that I can see: The first function call inside the try block, xeoma.async_test_connection(), will test the connection to the server. All of the calls to the library that can fail are inside the following try block. The constructor for the Xeoma object doesn't make any attempt to connect to the Xeoma web server. Xeoma is an NVR similar to BlueIris or Zoneminder so the connection being made is not to individual cameras, but to a web interface that can be enabled within Xeoma which provides direct access to jpgs from all connected cameras. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |