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

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

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.

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

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.

A so it’s time i see now on the camera’s that they are one hour ahead. I will look into that to fix that and see if that helps.

Thanks for looking into this will let you know if it’s fixed can try tonight.

Regards

Stephan Voskamp

Hi Adrian,

It was the DST option that was enabled on the cams. I disabled them and synced with ntp and al is working again.

Sorry for taking your time on this much appriciate your help in pointing where the problem was with me.

Keep up the great work

1 Like

On the Homey Pro 2023 the app (2.0.30) installs and I can add my Reolink doorbell but when I click it in Devices, the Homey app crashes. Is that a known issue or am I doing something wrong?

Hello !

I have a problem with when I install the app, it appears among the installed apps for a few seconds and then disappears. have the new homey pro 2023

Markus

Can you try the test version. I have submitted for it to be released but I’m not sure when Athom will have time for the review.

The test version works just fine with HP23.

1 Like

Regular version did not install in new Homey Pro 23, but new test version did. Thanks for fixing that. Hopefully this new version will be approved soon by Athom.
Really happy with your app on my old Homey early 2016.

1 Like

I am currently unable to integrate the Imou Ranger Pro camera. The camera is found by itself via the IP. I keep getting a SOAP error message (Error: ONVIF SOAP Fault). Since it does not change no matter if I enter the data correctly or not admin + device password, I suspect another error than wrong credentials.

Do I need to enter a specific port like 554? Then I get the error message: Error: read ECONNRESET

Anyone have any ideas what could help? Thanks a lot!

Could you go to the Configure App page, select the Diagnostics tab and set the Level to Full Information. Then try to add your camera. Once it has shown the error, go back to the Log and tap on Send Log.

I reset the camera once and set a new device password. Apparently it was no longer what I had stored. I also disabled the video encryption. Then it went :).

2 Likes

I’m not sure how many are aware, but I only recently discovered, if you right click on the image in the web app and select view in a new tab, you see the full resolution image instead of the small thumbnail that is shown in the device page.

Thanks to your app i could install my reolink doorbell wifi. But it doesn’t get a trigger like motion of doobell button pressed. It only says: “Last valua unknown”
The logging is saying: "App.unscribe: no push entry for host: 192.168.1.24
Server closed. I get a thumbnail on the device.
onvif are both on 8000
and HTTP on 80.
Could you help me? Thanks

Could you send me the log.
Also, just to be sure can you verify if the motion button is on?

Thanks Adrian. I didn’t switch on motion detection. I thought it was just a indication.
Now when i press the button i see visitor detected.
But this won’t trigger a flowcard to announce it over my google speakers.

I sent you a large log. I hope this helps?

I have a Reolink door bell connected to Homey via the ONVIF App. This is (part of) my flow:

Thank you for thinking with me. I see a vistor detected light up when pushing the button. But no general alarm.
Strange thing it is a reolink doorbell wifi and i read in the forum that when the button is pushed it would present itself (general alarm.)

Must i set it as sensor instead of camera?