New test version (0.0.24) that adds the motion alarm to the device tile.
This required changing the class from camera to sensor but I can’t see that it takes anything away but let me know if you see anything that goes missing (or should that be don’t see 
).
(As it was a quick one I managed to slip it in while wait for work code to build so don’t tell my boss 
)
Hi Adrian, I tried your new version but i have the same problem.
Hi Adrian, can you imagine the functionality of casting the homey data, eg temperature to the camera, so you can get some kind of dash information on it? Or is it just nnot possible anyway? Thanks
It looks like the Profile T specification allows setting the On-Screen-Display text so it might be possible. Once the current features are stable I will look into it further to see if I can find any details about it. The main problem is to get official detailed specifications requires being a paid up member. So unless I can find free information on the web it is very difficult to know what the format of the commands are.
I have setup a page on GitHub for translations. If anyone is willing to help out and translate the text then I will add then to future updates. I have include instructions in the document.
Thanks,
Adrian.
Version 0.0.24 is now live and there is a new test version 0.0.25.
The test version adds an option to switch back to Pull Events if both types are reported as supported.
Push events are more efficient for homey as it doesn’t have to keep polling the camera. However Push events may not work on some network setups. The switch is in Advanced Setting and called Prefer Pull Events. The switch will only have an effect if the camera reports support for both types of events.
Version 0.0.26 is now in test. This adds retires to the event image capture. I have found that my HikVision camera can only send the snapshot to one client at a time. Therefore if I have the notifications turned on in the HikVision app it gets first pickings on the image and causes Homey to timeout. So in this version it will try up to 3 times to grab the image. I also found that setting the delay in the Advanced Settings to 2 seconds prevents the race condition and actually means the image is captured quicker as the network timeout is about 10 to 15 seconds.
I presume this will not be specific to the HikVision camera so it is something to consider if you have other things capturing snapshot images.
Version 0.0.27 is now in test. This adds the following:
First of all congratulations on this application. After testing the different versions I had better operation on the different camera brands in version 22. With the following some of them no longer work. And would it be possible to change the CLASS of devices to “CAMERA” type as before and not “SENSOR” as is the case in the latest versions?
If I change the class back to camera then we loose the notification icon on the device tile. Is it something specific that you think the change has caused?
What is not working now that was working?
Have you tried with the latest test version and setting the prefer Pull point event option.
I coded part of the homeydash interface to display the image of the cameras when we click on their icon.
There is a previous version where one of my cameras displayed notifications and the “Camera” Class on homeydash.
I tested the latest version which is indeed more stable on event detection. But some brands do not display the notification on homeydash but on the mobile application.
And another brand detects a bad PORT and therefore the camera is not accessible.
I will look into Homeydash as i do use that but just not thought of putting a camera on it. I tried lots of things but couldn’t find anything that stopped working when set to sensor. Maybe I can make it an option in the advance settings so users that want the notification icon can set it to sensor while others can set camera.
Could you send me a log of the one that has the bad port as I am not sure that is related to the class.
I may have expressed myself badly.
On three different brand cameras:
This is the one that I am a bit confused about.
It could just be that the ONVIF port shown in the Port field is different to the snapshot URL.
The ONVIF port is where ONVIF commands are sent. The snapshot URL is is where the image is fetched from which is not necessarily the ONVIF port as the image can be available to non-ONVIF clients as well. The URL is fetched from the camera using an ONVIF command which returns the full URL including the port.
If you can capture the startup information in the diagnostics log then I can verify if that is the case here.
thank you for the information I just looked at more information on the third camera and indeed it is a brand that makes a “false” onvif protocol I think it comes from the.
So I think you shouldn’t take it into account for your application.
I have pushed a new test version (0.0.28) where the device class can be selected in the advanced options.
I have tried adding a camera in homeydash but it doesn’t show the image so was that a change you made to homeydash?
I will test it thank you, for displaying the camera image on homeydash when we click on it I added a piece of code in the file homeydash.app.js
if(device.class == ‘camera’){
// $deviceElement.style.backgroundImage = ‘url(’+device.settings.url+’)’;
// $deviceElement.style.backgroundSize = ‘cover’;
// $deviceElement.style.backgroundPosition = ‘center’;
////$deviceElement.style.webkitMaskImage = ‘url(’+device.settings.url+’)’;
$deviceElement.addEventListener(‘click’, function() {
if ( nameChange ) { return } // No click when shown capability just changed
if ( longtouch ) {return} // No click when longtouch was performed
$infopanel.innerHTML = ‘’;
var $infopanelCamera = document.createElement(‘div’);
$infopanelCamera.id = “infopanel-camera”;
$infopanelCamera.innerHTML = ‘’;
$infopanel.appendChild($infopanelCamera);
$infopanelCamera.style.backgroundImage = ‘url(’+device.settings.url+’)’;
$infopanel.style.visibility = ‘visible’;
//reload image after 10min
timeout = setTimeout(function() {
$infopanelCamera.style.backgroundImage = ‘url(’+device.settings.url+’)’;
}, 600000)
});
}
by removing the first three commented lines the widget is replaced by the camera image
Hi,
I have Imou bullet lite (IPC g22) cam and
Can not connect with app.
Failed: TypeError: Cannot read property ‘width’ of undefined
following log:
Log ID: 2020-05-16T20:24:11.077Z
App version 0.0.24
+0:0:0: ==== Discovery Starting ====
+0:0:274: Reply from {
“protocol”: “http:”,
“slashes”: true,
“auth”: null,
“host”: “192.168.1.196”,
“port”: null,
“hostname”: “192.168.1.196”,
“hash”: null,
“search”: null,
“query”: null,
“pathname”: “/onvif/device_service”,
“path”: “/onvif/device_service”,
“href”: “http://192.168.1.196/onvif/device_service”
}
+0:0:752: ==== Discovery Finished ====
+0:0:2: Discovered: [
{
“name”: “192.168.1.196”,
“data”: {
“id”: “192.168.1.196”,
“port”: null
},
“settings”: {
“username”: “”,
“password”: “”,
“ip”: “192.168.1.196”,
“port”: “”
}
}
]
+0:0:278: Testing connection credentials
+0:0:1: --------------------------
+0:0:2: Connect to Camera 192.168.1.196: - Admin
+0:0:281: Connection Failed for 192.168.1.196 Port: Username: Admin
+0:0:3: Failed: TypeError: Cannot read property ‘width’ of undefined
at Cam. (/lib/onvif/lib/cam.js:687:74)
at Array.forEach ()
at Cam.getActiveSources (/lib/onvif/lib/cam.js:656:20)
at Cam. (/lib/onvif/lib/cam.js:200:14)
at Cam. (/lib/onvif/lib/media.js:930:14)
at /lib/onvif/lib/utils.js:103:6
at Parser. (/node_modules/xml2js/lib/parser.js:304:18)
at emitOne (events.js:116:13)
at Parser.emit (events.js:211:7)
at SAXParser.onclosetag (/node_modules/xml2js/lib/parser.js:262:26)
Is there a way to fix this?
Could you try the test version as I have made changes to that file. Even if it doesn’t fix the problem it will show me the correct line number where the error occurs.
