Logic Programming

[RHCPNG]

Ok, we are a step further. All variables are there now. Firstly, there is a small error in the DirectStreamingURL though. The brackets should not be there.

I have removed them, but still no image.

This is the only thing I get in the log:

2020-11-22 09:56:05.011   luup.variable_set:: 93.urn:micasaverde-com:serviceId:HaDevice1.CommFailureTime was: 0 now: 0 #hooks:0
2020-11-22 09:56:05.011   openLuup.scheduler:: [93] Lobo device startup completed: status=true, msg=Ready, name=Lobo
2020-11-22 09:56:05.011   openLuup.scheduler:: [297] Amcrest Dahua device startup
2020-11-22 09:56:05.011   luup.set_failure:: status = false
2020-11-22 09:56:05.011   luup.variable_set:: 297.urn:micasaverde-com:serviceId:HaDevice1.CommFailure was: false now: false #hooks:0
2020-11-22 09:56:05.011   luup.variable_set:: 297.urn:micasaverde-com:serviceId:HaDevice1.CommFailureTime was: 1606035145 now: 1606035365 #hooks:0
2020-11-22 09:56:05.011   luup.variable_set:: 297.urn:micasaverde-com:serviceId:HaDevice1.Commands was: camera_full_screen,camera_left,camera_right,camera_up,camera_down,camera_preset,camera_zoom_in,camera_zoom_out now: camera_full_screen,camera_left,camera_right,camera_up,camera_down,camera_preset,camera_zoom_in,camera_zoom_out #hooks:0
2020-11-22 09:56:05.011   openLuup.scheduler:: [297] Amcrest Dahua device startup completed: status=, msg=, name=
2020-11-22 09:56:05.012   luup_log:3: ALTUI: UPNPregisterDataProvider(3,Vera@192.168.1.14,http://127.0.0.1:3480/data_request?id=lr_HTTP_VeraBridgeMirror_192.168.1.14,[{
  "default":"device.serviceId.name",
  "key":"mirror",
  "label":"Mirror",
  "type":"text"
}])
2020-11-22 09:56:05.012   luup.variable_set:: 3.urn:upnp-org:serviceId:altui1.DataStorageProviders was: {"emoncms":{"url":"","callback":"sendValueToStorage_emoncms","parameters":[{"default":1,"type":"number","key":"node... now: {"Vera@192.168.1.14":{"url":"http://127.0.0.1:3480/data_request?id=lr_HTTP_VeraBridgeMirror_192.168.1.14","callback... #hooks:0
2020-11-22 09:56:05.012   luup_log:3: ALTUI: UPNPregisterPlugin(3,urn:schemas-toggledbits-com:device:SiteSensor:1,J_SiteSensor1_ALTUI.js,SiteSensor_ALTUI.DeviceDraw,,,,SiteSensor_ALTUI.Favorite)
2020-11-22 09:56:05.016   luup.variable_set:: 3.urn:upnp-org:serviceId:altui1.PluginConfig was: {"urn:schemas-micasaverde-com:device:PowerMeter:1":{"DeviceDrawFunc":"ALTUI_PluginDisplays.drawPowerMeter","ScriptF... now: {"urn:schemas-micasaverde-com:device:PowerMeter:1":{"ScriptFile":"J_ALTUI_plugins.js","DeviceDrawFunc":"ALTUI_Plugi... #hooks:0
2020-11-22 09:56:05.017   luup_log:3: ALTUI: UPNPregisterPlugin(3,u

BTW I have tried the complete URL in the browser and that works.

[rafale77]

Good news is that the plugin code is executing.
Stating the obvious but, did you check that the ip address and the credentials are setup?
It is working fine here (with the brackets). The display of the stream/snapshot is actually done by ALTUI. depending on the browser you use, it may buffer a bit strangely.

[RHCPNG]

I've put the ip-address in the attributes and the username and password in the variables yes. Maybe add the port? It doesn't need it when I put the URL directly in the browser, so probably not.

[rafale77]

Nope port should not be needed. What version of ALTUI and openLuup are you running?
I am fairly certain now that the plugin I published works since it is working for me. Have to look at other things...

[RHCPNG]

AltUI v2.50.2549. Openluup v20.5.22. It's annoying that the logging does not give anything useful.

[rafale77]

Could you provide a screenshot of your attribute screen as well as a list of all your variables? I really have no idea why it isn't working for you. I even just added a camera to my openLuup setup and had no problem so something else is different. Are you seeing the camera control screen? Can you send commands to the camera like pan and tilt? What browser are you using? Can you try a different browser?

[RHCPNG]

Ok, youre right, the plugin seems to work. I have tested with an other Amcrest model and that one does work. So the problem lies in the older models I have, that's a pity. I will have to do it through zoneminder then.

The PTZ does not seem to work however for my model.

I'm getting this error:

Unknown control type:js_button. See Debug

[rafale77]

I'd be happy to improve the plugin to support more cameras if I can.
If the url is correct and the video is not working it is likely because the codec is not supported by the browser. If you tell me what camera it is, I will take a look.

The error you are seeing about the button is not normal. I will take a look as well. This command is in javascript and is done by ALTUI. I don't believe it is in the plugin code but will check.

[RHCPNG]

I don't get it. When I put the full URL directly in the browser window, like this, I get a stream (outside AltUI).

http://admin:<password>@192.168.1.17/cgi-bin/mjpg/video.cgi?channel=1&subtype=1

So that would mean it isn't the codec, right?

The model is: Amcrest IP3M-943B

[rafale77]

Not sure why they would not work. It uses the same H264 and mjpg codec but your url uses mjpg. I have a bunch of IP3M-956/954 and they all work fine too.
Good catch on the js_button. I never noticed it but it seems to be inherited from deprecated code. I will fix that. Only some buttons were affected.

I took advantage to fix a few thing around pan tilt/scanning. Released version 0.4.
This plugin was very raw when I took it over... I am finding so many things which were not quite right.

[RHCPNG]

There are some annoying issues with my model. I can't even manage my camera's through Chrome or Firefox, only through IE.

Will try your new version soon.

[RHCPNG]

I have tested the new version with my working model, but the buttons still do nothing. The error is gone and I don't see anything strange in the log.

2020-11-26 08:56:33.263   openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=377375215&Timeout=60&MinimumDelay=1500&_=1606377363201 HTTP/1.1 tcp{client}: 0x55f5f5b61a78
2020-11-26 08:56:33.642   luup.variable_set:: 10665.urn:upnp-org:serviceId:TemperatureSensor1.CurrentTemperature was: 19.60 now: 19.50 #hooks:0
2020-11-26 08:56:33.946   openLuup.server:: request completed (20648 bytes, 2 chunks, 682 ms) tcp{client}: 0x55f5f5b61a78
2020-11-26 08:56:34.059   openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=377375217&Timeout=60&MinimumDelay=1500&_=1606377363202 HTTP/1.1 tcp{client}: 0x55f5f5b61a78
2020-11-26 08:56:34.991   luup.variable_set:: 10664.urn:micasaverde-com:serviceId:HaDevice1.BatteryDate was: 1606377364 now: 1606377394 #hooks:0
2020-11-26 08:56:35.195   openLuup.server:: request completed (28287 bytes, 2 chunks, 1135 ms) tcp{client}: 0x55f5f5b61a78
2020-11-26 08:56:35.307   openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=377375219&Timeout=60&MinimumDelay=1500&_=1606377363203 HTTP/1.1 tcp{client}: 0x55f5f5b61a78
2020-11-26 08:56:37.593   openLuup.server:: GET /data_request?id=action&output_format=json&DeviceNum=297&serviceId=urn:micasaverde-com:serviceId:PanTiltZoom1&action=MoveLeft HTTP/1.1 tcp{client}: 0x55f5f5fd7d88
2020-11-26 08:56:37.593   luup.call_action:: 297.urn:micasaverde-com:serviceId:PanTiltZoom1.MoveLeft 
2020-11-26 08:56:37.593   openLuup.server:: request completed (60 bytes, 1 chunks, 0 ms) tcp{client}: 0x55f5f5fd7d88
2020-11-26 08:56:37.630   openLuup.client:: WGET error status: -1, request: http://admin:DWvBqx6yT7SkMogw@192.168.1.18/cgi-bin/ptz.cgi?action=start&channel=0&code=Left&arg1=0&arg2=1&arg3=0
2020-11-26 08:56:37.934   openLuup.server:: request completed (19020 bytes, 2 chunks, 2626 ms) tcp{client}: 0x55f5f5b61a78
2020-11-26 08:56:38.091   openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=377375220&Timeout=60&MinimumDelay=1500&_=1606377363204 HTTP/1.1 tcp{client}: 0x55f5f5b61a78
2020-11-26 08:56:38.733   openLuup.client:: WGET error status: -1, request: http://admin:DWvBqx6yT7SkMogw@192.168.1.18/cgi-bin/ptz.cgi?action=stop&channel=0&code=Up&arg1=0&arg2=0&arg3=0
2020-11-26 08:56:39.741   openLuup.server:: GET /data_request?id=action&output_format=json&DeviceNum=297&serviceId=urn:micasaverde-com:serviceId:PanTiltZoom1&action=MoveRight HTTP/1.1 tcp{client}: 0x55f5f5fd7d88
2020-11-26 08:56:39.741   luup.call_action:: 297.urn:micasaverde-com:serviceId:PanTiltZoom1.MoveRight 
2020-11-26 08:56:39.742   openLuup.server:: request completed (61 bytes, 1 chunks, 1 ms) tcp{client}: 0x55f5f5fd7d88
2020-11-26 08:56:39.775   openLuup.client:: WGET error status: -1, request: http://admin:DWvBqx6yT7SkMogw@192.168.1.18/cgi-bin/ptz.cgi?action=start&channel=0&code=Right&arg1=0&arg2=1&arg3=0
2020-11-26 08:56:40.280   openLuup.server:: request completed (19020 bytes, 2 chunks, 2188 ms) tcp{client}: 0x55f5f5b61a78
2020-11-26 08:56:40.424   openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=377375221&Timeout=60&MinimumDelay=1500&_=1606377363205 HTTP/1.1 tcp{client}: 0x55f5f5b61a78
2020-11-26 08:56:40.857   openLuup.client:: WGET error status: -1, request: http://admin:DWvBqx6yT7SkMogw@192.168.1.18/cgi-bin/ptz.cgi?action=stop&channel=0&code=Up&arg1=0&arg2=0&arg3=0
2020-11-26 08:56:41.476   openLuup.server:: GET /data_request?id=action&output_format=json&DeviceNum=297&serviceId=urn:micasaverde-com:serviceId:PanTiltZoom1&action=MoveUp HTTP/1.1 tcp{client}: 0x55f5f5fd7d88
2020-11-26 08:56:41.476   luup.call_action:: 297.urn:micasaverde-com:serviceId:PanTiltZoom1.MoveUp 
2020-11-26 08:56:41.477   openLuup.server:: request completed (58 bytes, 1 chunks, 0 ms) tcp{client}: 0x55f5f5fd7d88
2020-11-26 08:56:41.497   openLuup.client:: WGET error status: -1, request: http://admin:DWvBqx6yT7SkMogw@192.168.1.18/cgi-bin/ptz.cgi?action=start&channel=0&code=Up&arg1=0&arg2=1&arg3=0
2020-11-26 08:56:41.600   openLuup.server:: request completed (19020 bytes, 2 chunks, 1176 ms) tcp{client}: 0x55f5f5b61a78

The working model is the Amcrest IP4M-1051

[rafale77]

I am not getting any of the WGET errors in my logs. I am not sure what this status -1 means besides the fact that the camera is rejecting the call. I am also a bit surprised that your credentials in the url are only partially encoded. (the username is doesn't appear to be). Something doesn't seem right.

Honestly I have not gotten to the bottom of the stream. One of my cameras which I just added has all the pan and tilt buttons work so it is communicated properly but the video does not show. I tested on firefox and none of the cameras show any images.
Will try to dig deeper into this as I think it is more java code from ALTUI than it is a plugin/openLuup problem.

[rafale77]

Alright so I made some progress with this. Sorry I am not very good in JS so it took me a while to understand how ALTUI handles this.

I have updated the plugin which should enable getting images from the camera if your browser has the ability to disable cross origin restrictions (i.e Safari "develop" menu). I have tested this on firefox as well but unlike safari, firefox somehow sends an URL without the credentials... which means that you won't be able to see your camera feed. I submitted a pull request to @amg0 to implement credentials in ALTUI.

[RHCPNG]

Nice job figuring this out. Would this mean the feed of my older models would possibly work too? I'm getting a login screen sometimes when using the complete URL (with username and password) directly in my browser. That shouldn't happen, I would think.

[rafale77]

Yes the older models would work too and yes you do need to get you browser to log in.
The reason is this:
All the plugin commands go from openLuup to the cameras. This should work without any problems.
The video stream however is a call from your client web-browser to the camera. This requires a separate login on top of the credentials which have already been established between openLuup and the cameras. The behavior obviously then varies a lot from browser to browser. For example Safari remembers the credentials so you only need to log in once and the call from ALTUI done by safari automatically adds the credentials. I discovered that firefox doesn't do that and requires the credentials to be added back in the url.

[RHCPNG]

O ok, thanks for the explanation. That's nasty. I use Chrome and that works similar as Firefox then. But what is the difference with the newer models then?

[rafale77]

This was the very core of the design of ALTUI. The vera was very underpowered already so ALTUI moved the UI processing to the client browser using javascript instead of relying on the webserver on the vera (lightttpd). As the vera is properly incapable of processing high resolution camera streams, ALTUI moved that processing to the browser (and rightfully so) and therefore all the authentication must be done by the client browser.
By the way @amg0 has taken in my pull request so you can expect the next version of ALTUI to support this. I personally didn't notice any problem because I was using Safari.

[RHCPNG]

Hi @rafale77 ,

Am I correct that in the latest release of AltUI your addition was rolled out? Should it be working now?

[rafale77]

Yes, they should all work. It has for me. Check it out and see if you need any more help.