I made a better remote-live-view page [OLD]

Yes, I've asked Ken if he can provide that time zone information another way so I don't have to delay loading the clip list until I get the first status update telling me what timestamps to use :)
 
@bp2008...how about an option to display the local ip address of each camera?
 
bp2008 said:
Yes, I've asked Ken if he can provide that time zone information another way so I don't have to delay loading the clip list until I get the first status update telling me what timestamps to use :)
Click to expand...
can't you just request status first thing upon login like the app does?

i also see the usefulness of Q's request. my current workaround is to add the last .xxx of each cam's ip address to the cam's OSD text overlay, right after the name...
 
has there been any updates to this with regards to raspberry pi's? looking to turn a touchscreen rpi3 in to a monitor. everything works on a laptop, but trying on any raspberry devices says either username / password is incorrect and will not login, though it will from a laptop.
 
Q™ said:
@bp2008...how about an option to display the local ip address of each camera?
Click to expand...

If I could do it, it would already be in there :) Blue Iris does not provide this information.

pozzello said:
can't you just request status first thing upon login like the app does?
Click to expand...

Yes, in fact that is basically what happens already. Most of the time the server status arrives before the clip list. But there is no guarantee that things will arrive in that order. In order to keep everything correct and as bug-free as possible I would have to enforce a new rule that says the clip list can't be processed until a server status object is received. That is added complexity and a potential loading delay that could be avoided if Blue Iris provides the time zone offset in, for example, the response from the login command which already has to happen before anything else.
 
mkyb14 said:
has there been any updates to this with regards to raspberry pi's? looking to turn a touchscreen rpi3 in to a monitor. everything works on a laptop, but trying on any raspberry devices says either username / password is incorrect and will not login, though it will from a laptop.
Click to expand...

It worked fine the last time I tried it from a pi ... is it possible that your password isn't being entered correctly due to a wrong keyboard layout or something?

An alternative to that is you could whitelist the pi's IP address within Blue Iris so that the pi automatically gets administrator access without having to log in. See Blue Iris Options > Web server > Advanced > Help for details on the "Limit IP addresses" feature.
 
I'll login and give it a shot! right now all i get is a white page, nothing on it in chromium or ff esr on a fresh rpi3.
 
A white page? I thought you said it reported bad credentials?

I've seen a problem before where Blue Iris doesn't redirect you to a valid page after logging in. Could that be it? Should be solved by typing in the ui2.htm address manually.
 
ok, so not sure what I did, but in this screenshot above the sources tab, I clicked what looked like phone/tablet view and it came up with the login page and credentials accepted... screenshot
 
Sounds like you enabled the touchscreen-device emulator. Funny that would make a difference.

The network tab and/or console tab would have possibly indicated what was wrong with the page load.
 
not a clue, but it's working. pretty sweet, gonna test it out for a few days on this touch screen. only thing now is to figure out how to actually get it to boot in to kiosk mode full screen. found nothing that works so far on the latest update for raspbian.
 
In my experience firefox and midori have the best command line automation. Midori beat firefox in startup commands, but firefox was more stable.
 
bp2008 said:
If I could do it, it would already be in there :) Blue Iris does not provide this information.



Yes, in fact that is basically what happens already. Most of the time the server status arrives before the clip list. But there is no guarantee that things will arrive in that order. In order to keep everything correct and as bug-free as possible I would have to enforce a new rule that says the clip list can't be processed until a server status object is received. That is added complexity and a potential loading delay that could be avoided if Blue Iris provides the time zone offset in, for example, the response from the login command which already has to happen before anything else.
Click to expand...

fwiw, when i load up u2.htm (in FireFox, various OS's) it takes a good 15-20 seconds to load the clip list anyways... (1 TB drive and almost 6 weeks of motion-detected recordings for 12 cams)
 
You must log in or register to reply here.
Top Bottom