I think you can do everything you ask today. It would be easier if there was a harmony plug in but this new environment permits HTML calls so you could find the Harmony HTML command structure and embed the various ir command strings into your scenes. Further if some of your devices are on the same LAN they may have HTML commands to control them without ir.
Thanks! The advantage of the Harmony is that it allows both IR and html.
For example, Our media room is upstairs and I want to get the room set up before we get there.
So fire up the projector so it warms up; IR command through Harmony; No HTML available; Turn on Yamaha amplifier, switch to proper input IR command through Harmony;; Close curtains; Harmony triggers IR command; :Lower AC temperature using Vera commands, Turn on lighting using Vera. Lock doors using Vera. So the key missing ingredient is Harmony, or a solution to trigger IR commands through EzLo. Does this help with the requirement?
Ezlo Hubs only support Broadlink RM Pro hubs currently for IR stuff.
There was talk of them doing a Harmony plugin but as yet no news.
The original Harmony plugin for the Vera hub does have a HTTP API, so you could use an Ezlo hub and the new Meshbot automation rules, to send http requests out to the Vera hub / Harmony plugin.
But is there much point doing that? As youād still need the Vera hub.
Iām still using my Vera Plus as my main hub.
No Harmony plugin on the Ezlo hub is also a bit of a show stopper for me also. Although Harmony remotes are now EOL, so who knows if Ezlo will actually spend time and money doing a new plugin?
OK just an update:
My earlier problem with requiring an extra , nil to fix the command below is no longer needed. I was migrated to newer firmware 2.0.29.2027.3 and just for fun I took the , nil out and the LUA script works. So a bit of a fire drill for nothing. It must have been a bug they fixed in the current release.
core.set_item_value( item.id, not( item.value), nil ) -- toggles state from prior
Hi @curiousB ,
Indeed, the latest firmware includes some fixes and improvements related to Lua and expressions.
Thank you for the constant feedback, this really helps us to improve the platform.
Find more:
@curiousb is correct ā Generic IP cameras do not work with the Ezlo. The app wonāt install them (throws an error about the URL being incorrect, even though its the same URL that worked with a Vera), and the new web interface wonāt install devices of any kind.
Iāve installed some generic IP cameras (all Foscam) with the Vera App on an Ezlo Plus. With the web interface this seem to be not possible at the moment.
1 Like
trcollins, Actually I did get my FOSCAM PTZ camera to work with Ezlo Plus using the generic IP Camera selection. Now when I say āworkingā I mean it renders video. None of the PTZ functions are operational.
That said I was able to test PTZ movements using an HTTP Request GET as the action in a Scene. I just pasted in the HTTP CGI command line and the camera did what is was supposed to. pan, tilt, zoom, jump to preset, ā¦ Its a bit awkward creating a bunch of scenes to replicate all the pan and zoom functions but you can do it today. Of course you need a way to trigger the scenes while in the video viewing window so I assigned them to a mini-mote handheld buttons. This all works fine but not exactly a clean interface. I would think the Plug in for this would be easy for a software developer but I only dabble in scripts so its probably beyond my talents.
For PTZ commands you have to have two HTTP GETs. One to start the movement, then approx 750msec later issue a PT or Zoom stop command or else the PTZ movement continues to the outer limits of travel.
I made an excel spreadsheet to generate all the PTZ and preset command strings based on a specific camera ip address, userid, and password but I canāt seem to upload it here. Iāll paste the body of the spreadsheet below for any one interested. All FOSCAM cameras use the same CGI command string format.
p.s. all of the scenes were created from the ezlogic.mios.com web interface which is very nice for editing these kinds of scenes. I donāt know how you would do it from your iPhone/Android. Adding the IP Camera was done from the IPhone client.
|ptzMoveUp|http://192.168.2.12:80/cgi-bin/CGIProxy.fcgi?cmd=ptzMoveUp&usr=admin&pwd=passwerdy|
|ptzMoveRight|http://192.168.2.12:80/cgi-bin/CGIProxy.fcgi?cmd=ptzMoveRight&usr=admin&pwd=passwerdy|
|ptzMoveLeft|http://192.168.2.12:80/cgi-bin/CGIProxy.fcgi?cmd=ptzMoveLeft&usr=admin&pwd=passwerdy|
|ptzStopRun|http://192.168.2.12:80/cgi-bin/CGIProxy.fcgi?cmd=ptzStopRun&usr=admin&pwd=passwerdy|
|ptzGotoPresetPoint|http://192.168.2.12:80/cgi-bin/CGIProxy.fcgi?cmd=ptzGotoPresetPoint&name=pointName&usr=admin&pwd=passwerdy|
|zoomIn|http://192.168.2.12:80/cgi-bin/CGIProxy.fcgi?cmd=zoomIn&usr=admin&pwd=passwerdy|
|zoomOut|http://192.168.2.12:80/cgi-bin/CGIProxy.fcgi?cmd=zoomOut&usr=admin&pwd=passwerdy|
|zoomStop|http://192.168.2.12:80/cgi-bin/CGIProxy.fcgi?cmd=zoomStop&usr=admin&pwd=passwerdy|
|ptzAddPresetPoint|http://192.168.2.12:80/cgi-bin/CGIProxy.fcgi?cmd=ptzAddPresetPoint&name=pointName&usr=admin&pwd=passwerdy|
|ptzDeletePresetPoint|http://192.168.2.12:80/cgi-bin/CGIProxy.fcgi?cmd=ptzDeletePresetPoint&name=pointName&usr=admin&pwd=passwerdy|
|getPTZPresetPointList|http://192.168.2.12:80/cgi-bin/CGIProxy.fcgi?cmd=getPTZPresetPointList&usr=admin&pwd=passwerdy|
Mine (not a Foscam) doesnāt use a cgi-based script like yours and the Vera app device installer refuses to accept the URL. Again, this is the same URL that works with the old Vera web interface, so thereās an issue to address here.