That is true of a lot of cameras. And what I'm telling you is that there is no native support for any cameras currently. The cameras are wifi, so they would have to be interfaced completely differently than the other Iris devices.
The cameras communicate over WiFi, but they were linked to the Iris Hub somehow. Perhaps when the code is released some information will be in it that would facilitate connecting the camera to the Hubitat hub also, even if it is only to report motion and/or temperature.
Before iris shuts down tonight, go to your cameras in the iris devices page, click on the settings icon and scroll down to "local viewing" and take a screen shot of that info. It could help in connecting to other IP camera services. The password field may be needed!
I haven't tried to port the cameras to any other service, but thought that info would be helpful.
The links I posted will give the default login and passwords for the cameras when they are reset to default.
The login for a camera that has been reset is:
Enter this url in your web browser:
When prompted for username and password, use the information above. The links I gave will help with other commands for setting up the camera. As for linking it to the Hubitat hub, I have no idea how to go about doing that.
Then you would just have to write a driver to interface to the camera using that information. What I'm telling you is that there is no cameras that currently interface to HE with a native driver. So, I wouldn't expect the hubitat team to work on the Iris cams first, since there are so many other cams out there that are a lot more popular. But you can write your own driver to interface to them.
To do that, one would need to understand how to write drivers. That is not part of my current skill set. I am providing the information in case there is someone with the skill and inclination to do so to have some information related to these cameras. I'm not saying they have to be prioritized over any other camera.
Hubitat integrates with IFTTT, but no camera setups "natively" with their own drivers, some people have wrote their own drivers and have them going, but they're not currently "supported by" Hubitat since they aren't natively created by Hubitat.
and follow the instructions to get the camera into a factory reset state. This will allow you to talk to the camera and get and set its configuration.
If you were able to change the settings such as the username/password, and get the camera on wifi, the rest is relatively easy.
Lets move to the Hubitat side. You will need to create a virtual motion detector. So install this Driver Code:
and make a Virtual Device:
Name: Camera Motion Sensor
Label: The-Room-It's-In Camera
Type: Virtual Motion with Switch
Use the Rule Maker to make a trigger such as "Camera Motion Detected" Use a Motion type trigger event for your The-Room-It's-In Camera with the value of active. Set it to turn on a light, or something simple that you can easily test.
Go to the device page for your The-Room-It's-In Camera, and click the "on" panel. This should turn on the light.
Install the MakerAPI App Built-In App. In the MakerAPI, you probably only need Local IP address access if the camera is on the same network as the hub. Scroll down and select your The-Room-It's-In Camera. Click the " Get All Devices with Full Details" link and you should see a page of JSON code with info all about your new device. The important parts are the ID and the Commands.
Back on the MakerAPI page, you can scroll down to the last piece of info on how to Send Device Command:
http://[your-hub-ip-address]/apps/api/[MakerAPI-id]/devices/[Device ID]/[Command]/[Secondary value]?access_token=asdf-...
You will fill in the blanks to look something like this:
Paste this into a browser, and it should turn your light on just like clicking the "on" panel on the device page. In fact, if you watch the camera's device page you can see the motion state change from inactive to active.
Finally back to the camera. We need to tell the camera to make that http GET when it sees motion. So run this:
you should see:
We will turn on the notifications and tell it where:
We need to tell the camera to make the call on motion. So looking at the EVENT info:
We want to change some values to:
event_interval=0 (this sets continuous detection. set to 1 for detections 1 minute apart minimum)
On the MOTION page:
On the SYSTEM page, I have:
but not entirely clear about that.
The camera has a log here:
That you can look at (you need to refresh it yourself). If you put your hand in front of the camera you should see:
Alert: PIR & Motion Detection (bundle) triggered.
Alert: Detected motion.
depending if you have pir_mode=1 or pir_mode=0 under SYSTEM.And if your HTTP_NOTIFY is set correctly you will see:
HTTP-NOTIFY:Send notification successfully.
So with all that, you should be able to turn on the lights by waving your arms! Progress!
See comment 23 from Ryan780 below about changes to the driver you might want to make regarding on and off timing.
Apparently, the camera will make a video and email it to you if you are nice to it, but I'm not there yet. I think I need an SD card, for starters. I'll let you know if I get that working.
If you have an easier way to do this, please do tell.