Author
Topic: Y-Cam Camera (Read 5683 times)

Right, I have learnt that the proper procedure (after following the instructions posted by possy) is to create a trac ticket with the sqlCVS Batch IDs. Find out what these are by going to http://schema.linuxmce.org/sqlCVS/?site=batch/view and looking in dce and ir.

Matt, I have now added a trac ticket or twelve (my apologies again chaps!) for this template, so let's see what happens.

Cool, I'll wait until I can get template 2163. There's no mega rush at the moment, as I'm moving house this weekend and it'll take a few days to get everything connected back together and running. I have a whole load of Z-wave devices that will probably keep me busy for the next week or so too....lol. Might need to find a bigger server to host this forum.

After my success with the webcam I tried adding the Y-CAM IP camera as a child device of 'Motion' too (using the generic IP camera template), and after setting the path in the template as suggested by cht_winston it started working. Now I'm not sure what has changed, as I tried this last week and never got a picture, but as of last night it was working a treat. It needed a core restart to get it to work properly, perhaps thats what was missing last time I tried it, but I'm happy to say that its functional. I also tried to add it as a child of the core without motion, but this still didn't work. Don't know why.

Glad it's working for you. Obviously the template that I did wasn't designed to add the camera as a motion device, only as a standalone viewer. Which is your preference in this case, motion or viewer?

When you say you tried to add it as a child of the core, which template were you using for that?

You'll often find that sometimes things need a reset or two, doesn't hurt to reset the cameras themselves also.

I would be interested to know what the camera is like to live with and how reliable it is, whether it's worth the money, etc - I am currently in the market for an outdoor IP camera and saw a Y-Cam somewhere.

When I tried to add the camera as a direct child of the core I had to choose the generic IP camera template, as there still isn't one for the Y-CAM in the list. I'm not sure whatever happened to the template you created, but its not on my list. I'd have preferred to just use the camera without motion, as it already has motion detection software built in, but I was just glad to get it working so its staying as it is for now. I am going to have to adjust the refresh rate I think, as I am used to viewing it as a camera, not as a series of stills(I know its the same thing, but when you view it from a browser it refreshes itself seemlessly)

I've had mine for 18 months now, and its been faultless. The only slight gripe is that it uses an activeX script to refresh with a browser, and my old mobile phone couldn't function with this so I couldn't view it on my phone over the home wifi. Still it works great on the IPad, and now with MCE too. I like the fact that you can log into it too, mine's always been in the boy's bedroom, so I could see him when I'm working overseas. This should still work unless the router on the core fails.

For a standalone viewer I would try using the Panasonic one (that's what I used for the template), add it manually and change the path, password etc to match your Y-Cam settings. Once you get that working we can make a template in confidence.

You know that motion in LMCE not only records motion, but also detects motion, essentially turning the camera into a motion sensor for the alarm system right? Or it can switch on lights, whatever you want!

I assume you entered trac ticket 1064. Is your email address really abc@gmail.com? We use the email address to contact people sometimes, to verify trac tickets. It would help if the correct email address is used.

Yes, that is the trac ticket, and no, that is not the correct email address. I used that email address as an experiment as I can never submit tickets without getting the spam thing, and it worked first time. I swear that in the past I have used my genuine email address and it's not worked.

Sorry, should have mentioned, yes it was based on the Panasonic template.

I also should have mentioned that initially I tried the username and password in the AuthUser and AuthPassword fields respectively, but it did not work (hence frigging about with the username/password in the path/IP, just to see what's going on).