Netatmo Security - Hubitat port

I've just added the device driver for the presence camera to github:

I get the following response after saving it:

×unable to resolve class physicalgraph.device.HubAction @ line 271, column 21.

this screen I have, after it shows me the devices:


It doesnt create a device after i click done

Ahh, I haven't ported the Presence driver. Sorry, I don't have a Presence so I realised I hadn't uploaded and put it there for you quickly.

Give me half an hour and I'll sort it.

I'm in the middle of looking at the webhook events. I've worked out why the person seen event is failing from the Welcome camera. The event_type is being sent to the wrong driver.

1 Like

Ok, that driver should save now and then it should create a device once you click done on the page you posted.

ah ok so you put in in the Person folder. Code looks ok, I added it to the drivers.. The device doesnt appear after clicking done unfortunately. I think something is wrong in the app

Can you clear the logs and then post the Netatmo Security log taken while you try to add the device?

I'm getting event status for all my cameras and people. Let's see if we can work out why the presence won't add.

app:3532021-02-01 23:49:28.178 debugapiGet response status 200
app:3532021-02-01 23:49:27.970 debugAPI Get: [uri:https://api.netatmo.com, path:/api/gethomedata, query:[access_token:xx1|xx2]]
app:3532021-02-01 23:49:27.966 debugRefreshing camera and person data
app:3532021-02-01 23:49:27.962 debugPolling
app:3532021-02-01 23:49:27.959 debugDelete: []
app:3532021-02-01 23:49:27.955 errorError creating device: com.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Netatmo Presence' in namespace 'copycat73' not found
app:3532021-02-01 23:49:27.951 debugCreating child
app:3532021-02-01 23:49:27.948 debugIn createChildDevice
app:3532021-02-01 23:49:27.945 debugCreating Presence camera Frontyard (Thuis)
app:3532021-02-01 23:49:27.940 debugapiGet response status 200
app:3532021-02-01 23:49:27.737 debugAPI Get: [uri:https://api.netatmo.com, path:/api/gethomedata, query:[access_token:xx1|xx2]]
app:3532021-02-01 23:49:27.734 debugRefreshing camera and person data
app:3532021-02-01 23:49:27.731 debugInitialized with settings: [clientId:cid1, devices:[MAc address], clientSecret:cid2, installWebhook:true]
app:3532021-02-01 23:49:27.607 debugUpdated with settings: [clientId:cid1, devices:[MAC Address], clientSecret:cid2, installWebhook:true]
app:3532021-02-01 23:49:24.017 debugapiGet response status 200
app:3532021-02-01 23:49:23.774 debugAPI Get: [uri:https://api.netatmo.com, path:/api/gethomedata, query:[access_token:xx1|xx2]]
app:3532021-02-01 23:49:23.676 debugRefreshing camera and person data
app:3532021-02-01 23:49:23.673 debugListing devices
app:3532021-02-01 23:49:22.355 debugShowing the devices page
app:3532021-02-01 23:49:22.256 debugIn authPage

ok, it's having trouble finding the driver. Let me just check there's not a naming issue

yep, can you see the 'namespace copycat73?'

In the Presence device driver on line 17, change the namespace to match the case.

so, namespace: "copyCat73" --> change to: namespace: "copycat73"

Goodness knows how these worked in the past, unless ST didn't care about case.

1 Like

haha yes i found it, it shows up now

Excellent..... I'll change the github file as well.

I've also managed to fix the seen() method for the Welcome camera. I'll post the new versions shortly.

Nice work man!! Now i will see what kinds of mischief i can create for the wife, neighbours and all of their cats :smiley:

1 Like

Ok,

Fixes:

  1. The Presence camera driver is now ported and uploaded
  2. I've adjusted the webhook event, on the main app, so the person event_type is pushed to the person device rather than the camera - new app version uploaded
  3. I double checked the naming of all the files and adjusted accordingly.

I've been running with this one for months with no issues.

Does yours do anything different or better?

I looked for this, more than once, before I put the effort in. Obviously not hard enough, lol. Thanks for bringing it to my attention

I'll take a look.

I'd planned to look at the way people devices were working as I use seen() events to trigger virtual switches for Alexa routines and I wanted to see if I could take the virtual switches out of the equation.

I see the logging levels are configurable which was also on my list to look at.

I'll have a play with this release and see what works for me. :slight_smile:

Im getting "unable to resolve class physicalgraph.device.HubAction @ line 271, column 21." when I try to install Netatmo Presence drivers. What do you think is wrong?

Suggest you use this port

It has all the features that I had planned and I've recently contributed.

2 Likes

Ok, I’ll try that instead. Thanx! :+1:

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.