[APP][Pro] Support for ONVIF compatible cameras (Release 2.0.41)

Apps
931

Hi Adrian

I cant seem to find the Person is detected card for my Trackmix camera, but i did find it for the other 2.

And in advance settings what exactly should i change ?

932

The person detected capability appears when the first event occurs, as there is nothing reported to say that is available. So, if the camera doesn’t have that option then it hasn’t been detected.

In the advanced settings, you could try different options for the ONVIF motion setting.

933

It all worked till 2 days ago when the was someone at the door, the general alarm was triggered. And i created flows from this card.

But the general alarm isn’t working anymore. What is wrong ??

11bfce16-83cf-4e95-bafe-1d9252e26a73

Hw: reolink wifi doorbell

934

Same situation here with my Reolink Doorbell Wifi. Log send!

935

Arrg, my bad. I changed the alarm_generic to alarm_visitor without thinking about the consequences. So sorry for the oversight on my part.
I will add it back in the next update ASAP.

936

It should be back in the new test version.

1 Like
937

Thank you for the fast fix :grin:

2 Likes
938

Ive updated to the new version 29 but its still not working

939

Could you open the Configure App screen and select Basic Information for the diagnostic log. Then ring the doorbell to generate the event. Then send the log from the Configure App screen using the Send log button.

940

Is cleared the log and after I pushed the button an event was created.
I send the log

941

None of my cameras work - again

Screenshot_20230220_234555_Homey
Screenshot_20230220_234555_Homey1080×2340 74.2 KB

942

Have you checked the URL’s are still set to use HTTPS?

1 Like
943

New test version. I hope I have found the problem. It looks like when I added the channel tokens for the NVR it messed with single cameras that don’t use tokens.

1 Like
944

Yes everything is ok right now :raised_hands:
I also see the alarms now in the logs

1 Like
945

Not sure when this started but all my camera’s are not working anymore all i get is ONVIF SOAP FAULT Restarted the cams and app already no luck.

946

Could you set the Diagnostics log in the Configure App screen to Basic Information, wait for the errors and then send the log.

947

Send you the log hope your can see what up with this

948

I can see it is getting part way through connecting.
Has the camera’s firmware updated recently?
Was it working?
Maybe change the log level to Full Information and repeat the report.

949

Hi thanks for looking into this. Yes it’s always been working had 3 cams connected. No firmware update on the cams or other changes. Homey has been updated that’s the only thing.

Sensed the full logs maybe that tells you where to look

Thanks

Regards

Stephan Voskamp

950

The error is:

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<s:Envelope
	xmlns:sc="http://www.w3.org/2003/05/soap-encoding"
	xmlns:s="http://www.w3.org/2003/05/soap-envelope"
	xmlns:ter="http://www.onvif.org/ver10/error"
	xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"
	xmlns:wsrf-bf="http://docs.oasis-open.org/wsrf/bf-2"
	xmlns:d="http://schemas.xmlsoap.org/ws/2005/04/discovery">
	<s:Body>
		<s:Fault>
			<s:Code>
				<s:Value>s:Sender</s:Value>
				<s:Subcode>
					<s:Value>ter:NotAuthorized</s:Value>
				</s:Subcode>
			</s:Code>
			<s:Reason>
				<s:Text xml:lang="en">Wsse authorized time check failed.</s:Text>
			</s:Reason>
		</s:Fault>
	</s:Body>
</s:Envelope>

But I can’t see why as the time looks fine in the request:

<s:Envelope
	xmlns:s="http://www.w3.org/2003/05/soap-envelope"
	xmlns:a="http://www.w3.org/2005/08/addressing">
	<s:Header>
		<a:MessageID> urn:uuid:df911ac7-5e49-9b13-79f0-87ac03f86542</a:MessageID>
		<Security s:mustUnderstand="1"
			xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
			<UsernameToken>
				<Username>xxxxxx</Username>
				<Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">xxxxxxxxx=</Password>
				<Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">DpJdYLc4f15I1cSdWhEzbw==</Nonce>
				<Created
					xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2023-03-04T09:05:28.327Z
				</Created>
			</UsernameToken>
		</Security>
	</s:Header>
	<s:Body
		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
		xmlns:xsd="http://www.w3.org/2001/XMLSchema">
		<GetProfiles
			xmlns="http://www.onvif.org/ver10/media/wsdl"/>
		</s:Body>
	</s:Envelope>

And the response to fetching the time is:

 
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<s:Envelope
	xmlns:sc="http://www.w3.org/2003/05/soap-encoding"
	xmlns:s="http://www.w3.org/2003/05/soap-envelope"
	xmlns:tt="http://www.onvif.org/ver10/schema"
	xmlns:tds="http://www.onvif.org/ver10/device/wsdl">
	<s:Header/>
	<s:Body>
		<tds:GetSystemDateAndTimeResponse>
			<tds:SystemDateAndTime>
				<tt:DateTimeType>NTP</tt:DateTimeType>
				<tt:DaylightSavings>true</tt:DaylightSavings>
				<tt:TimeZone>
					<tt:TZ>GMT+01:00PDT,M3.1.1/00:00:00,M11.1.2/00:00:00</tt:TZ>
				</tt:TimeZone>
				<tt:UTCDateTime>
					<tt:Time>
						<tt:Hour>9</tt:Hour>
						<tt:Minute>5</tt:Minute>
						<tt:Second>28</tt:Second>
					</tt:Time>
					<tt:Date>
						<tt:Year>2023</tt:Year>
						<tt:Month>3</tt:Month>
						<tt:Day>4</tt:Day>
					</tt:Date>
				</tt:UTCDateTime>
				<tt:LocalDateTime>
					<tt:Time>
						<tt:Hour>10</tt:Hour>
						<tt:Minute>5</tt:Minute>
						<tt:Second>28</tt:Second>
					</tt:Time>
					<tt:Date>
						<tt:Year>2023</tt:Year>
						<tt:Month>3</tt:Month>
						<tt:Day>4</tt:Day>
					</tt:Date>
				</tt:LocalDateTime>
			</tds:SystemDateAndTime>
		</tds:GetSystemDateAndTimeResponse>
	</s:Body>
</s:Envelope>

So all the calls look good. One thing to try is re-enter your password in the device advance settings page of Homey.