Maybe I can help a bit. I use the same cameras and went on this mission to find answers after the Iris generation 2 hub made my cameras unusable with my iSpy server.
Once I used Lowes' "migration utility" to move my cameras from the Generation 1 hub to the Generation 2 hub, my iSpy server could not connect to the cameras at all. Any connection attempt using RTSP or HTTP (using VLC Media player, which works great for testing video streams) resulted in a username and password prompt.
Long before I stumbled across this forum, and eventually got credentials from Danin Fuchs, I tried hard resetting the camera in an attempt to make it work the way it used to. I was eventually able to get the cameras to where I could connect to the RTSP and HTTP feeds using VLC and iSpy, but the rest of the cameras configuration was gone. The Iris hub would no longer pair the cameras and because of this, I was no longer able to configure the wireless. The cameras did however work fine as long as they are hard wired.
To reset the camera's (I did this on both the indoor and the outdoor cameras), first, for safety purposes, unplug the Iris hub from your network (assuming that it's still plugged in), make sure there is a wired network cable plugged in to the camera and use a pin or paperclip to push the reset button on the back of the camera and hold it for 30 seconds. Once you let go, the camera will reset, wait about 1 minute for it to finish its startup cycle (you should be able to the hear the IR cut filter click and see the IR lights come on if you are in a dim-ish room). After it's done starting up, pull the power cord and wait for a few seconds then plug it back in. Wait for the startup cycle to finish again. By default, the camera should get an IP address via DHCP handed out by your router or whatever is handing out IPs on your network. Now the video streams should be accessible using VLC or iSpy without asking for the username and password and the credentials supplied by Danin Fuchs should work for sending API calls to the camera's. NOTE: I did have to go through the reset process a couple of times on one of the cameras before I got it to work.
I even called Iris support a couple of times to see if I could get anything useful out of them. Of course, they were next to useless. The only thing I was able to get out to of them is that since the cameras were not able to pair to the generation 2 hub (which seems to be a common problem, "once they are paired with a Gen 2 hub and you remove the pairing, they will not re-pair with the hub"), Iris support emailed me a letter to take to a Lowes store where they would replace my Iris cameras with new ones (great idea since my cameras are over two years old).
After I got that information I got the credentials that Danin Fuchs supplied above and figured out that after a few hard resets of the cameras, as long as the Gen 2 Iris hub has not tried to pair to the cameras, then the cameras firmware is in a state where the above credentials will work allowing you to adjust the camera's configuration using the API commands listed here: https://github.com/edent/Sercomm-API
But, as most people messing with this have realized, these cameras have been crippled quite a bit, and without going through the process that Danin Fuchs used, it's going to be a little hard to do much of anything aside from just basic "turning settings on and off".
I haven't had a lot of time to test, but I am working on setting up the wireless using the API commands, I can't seem to pass the commands to the camera in a way that they will accept the input to connect them to my wireless, I assume that all of the commands need to be sent in a string of some sort for it to accept them but without the web interface on the camera, or a working web interface to play with, I'm not sure I will be able to figure it out any time soon. But I'm going to keep trying.
Hopefully this information will be useful to someone else.