We have moved at community.getvera.com

Author Topic: Plugin: Razberry support for openLuup/ALTUI  (Read 27496 times)

Offline CudaNet

  • Beta Testers
  • Hero Member
  • *****
  • Posts: 1401
  • Karma: +42/-11
  • Chimichanga !
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #15 on: July 09, 2016, 06:14:15 pm »
And Z.Wave logs...
openLuup, AltUI, Zway and HomeWave, enough said...

Offline amg0

  • Beta Testers
  • Master Member
  • *****
  • Posts: 3174
  • Karma: +210/-8
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #16 on: July 09, 2016, 06:41:35 pm »
great. this 6 in 1 is not the easiest device to start with but let's try
thanks for the screens and json data, it is quite useful
do you know how does it look like on a real vera ? (how many devices and of which type )


also : try to install latest version from Github ( master branch ) as AK and I are making quite a number of changes in the device detection & creation. would be curious that you a) update ALTUI and RAZB code to the latest from Github and b) delete the 6in1 device and let luup reload. it should recreate several devices

thx
« Last Edit: July 09, 2016, 06:44:03 pm by amg0 »

Offline CudaNet

  • Beta Testers
  • Hero Member
  • *****
  • Posts: 1401
  • Karma: +42/-11
  • Chimichanga !
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #17 on: July 09, 2016, 07:46:01 pm »
A screen cap of Vera and JSON extract of the nodes in question. Let me check AK's branch and see what I'm running. I'll post back versions...
Edit: I grabbed the latest AltUI from the AppStore, and I think the latest of Raz.. Hard to tell which is latest, 0.4 or 0.latest.  Rolling the dice I opted for 0.latest. I'm running AK's dev branch which looks to have the latest files. Just in case, I posted the startup...

Code: [Select]
2016-07-09 19:31:51.364   :: openLuup STARTUP ::
2016-07-09 19:31:51.364   openLuup.init::        version 2016.06.30  @akbooer
2016-07-09 19:31:51.433   openLuup.scheduler::   version 2016.04.30  @akbooer
2016-07-09 19:31:51.436   openLuup.wsapi::       version 2016.07.05  @akbooer
2016-07-09 19:31:51.438   openLuup.server::      version 2016.06.09  @akbooer
2016-07-09 19:31:51.451   openLuup.rooms::       version 2016.06.23  @akbooer
2016-07-09 19:31:51.460   openLuup.scenes::      version 2016.05.19  @akbooer
2016-07-09 19:31:51.469   openLuup.chdev::       version 2016.06.02  @akbooer
2016-07-09 19:31:51.471   openLuup.userdata::    version 2016.06.30  @akbooer
2016-07-09 19:31:51.472   openLuup.requests::    version 2016.06.22  @akbooer
2016-07-09 19:31:51.475   openLuup.io::          version 2016.04.30  @akbooer
2016-07-09 19:31:51.476   openLuup.luup::        version 2016.06.06  @akbooer
2016-07-09 19:31:51.479   luup.create_device:: [1] D_ZWaveNetwork.xml /  /
2016-07-09 19:31:51.500   luup.create_device:: [2] D_openLuup.xml / I_openLuup.xml / D_openLuup.json
2016-07-09 19:31:51.502   openLuup.init:: loading configuration user_data.json
2016-07-09 19:31:51.503   openLuup.userdata:: loading user_data json...
2016-07-09 19:31:51.548   openLuup.userdata:: loading rooms...
2016-07-09 19:31:51.548   openLuup.userdata:: ...room loading completed
2016-07-09 19:31:51.548   openLuup.userdata:: loading devices...
2016-07-09 19:31:51.549   luup.create_device:: [1] D_ZWaveNetwork.xml /  /
2016-07-09 19:31:51.659   luup.create_device:: [3] D_ALTUI.xml / I_ALTUI.xml / D_ALTUI_UI7.json
2016-07-09 19:31:51.675   luup.create_device:: [4] D_AltAppStore.xml / I_AltAppStore.xml / D_AltAppStore.json
2016-07-09 19:31:51.706   luup.create_device:: [5] D_RAZB.xml / I_RAZB.xml / D_RAZB.json
2016-07-09 19:31:51.707   openLuup.userdata:: loading scenes...
2016-07-09 19:31:51.707   openLuup.userdata:: number of scenes = 0
2016-07-09 19:31:51.707   openLuup.userdata:: ...scene loading completed
2016-07-09 19:31:51.707   openLuup.userdata:: loading installed plugin info...
2016-07-09 19:31:51.708   openLuup.userdata:: [openLuup] openLuup (.baseline.)
2016-07-09 19:31:51.708   openLuup.userdata:: [8246] Alternate UI (not.installed)
2016-07-09 19:31:51.708   openLuup.userdata:: [AltAppStore] Alternate App Store (.baseline.)
2016-07-09 19:31:51.708   openLuup.userdata:: [VeraBridge] VeraBridge (not.installed)
2016-07-09 19:31:51.708   openLuup.userdata:: [8211] DataYours (not.installed)
2016-07-09 19:31:51.708   openLuup.userdata:: [razberry-altui] RaZberry (ALPHA) (0.latest)
2016-07-09 19:31:51.708   openLuup.userdata:: ...user_data loading completed
2016-07-09 19:31:51.708   openLuup.init:: running _openLuup_STARTUP_
2016-07-09 19:31:51.710   luup_log:0: startup code completed
2016-07-09 19:31:51.710   openLuup.init:: init phase completed
2016-07-09 19:31:51.711   openLuup.server:: starting HTTP server on 10.0.4.122:3480 tcp{server}: 0x573c68
2016-07-09 19:31:51.711   openLuup.scheduler:: starting
2016-07-09 19:31:51.711   openLuup.scheduler:: [2] device startup
2016-07-09 19:31:51.711   luup_log:2: synch in 8.3 s
2016-07-09 19:31:51.712   luup.variable_set:2: 2.urn:upnp-org:serviceId:altui1.DisplayLine2 was: EMPTY now:  #hooks:0
2016-07-09 19:31:51.712   luup.variable_set:2: 2.openLuup.Version was: EMPTY now: 16.7.5 #hooks:0
2016-07-09 19:31:51.713   luup.register_handler:2: global_function_name=HTTP_openLuup, request=openLuup
2016-07-09 19:31:51.713   luup.register_handler:2: global_function_name=HTTP_openLuup, request=openluup
2016-07-09 19:31:51.713   luup.chdev.append:: [AltAppStore] Alternate App Store
2016-07-09 19:31:51.713   luup.chdev.sync:: syncing children
2016-07-09 19:31:51.713   luup.variable_set:2: 2.openLuup.Memory_Mb was: EMPTY now: 2.2 #hooks:0
2016-07-09 19:31:51.714   luup.variable_set:2: 2.openLuup.CpuLoad was: EMPTY now: 0.3 #hooks:0
2016-07-09 19:31:51.714   luup.variable_set:2: 2.openLuup.Uptime_Days was: EMPTY now: 0 #hooks:0
2016-07-09 19:31:51.715   luup.variable_set:2: 2.urn:upnp-org:serviceId:altui1.DisplayLine1 was: EMPTY now: 2 Mb, cpu 0.3%, 0 days #hooks:0
2016-07-09 19:31:51.715   luup_log:2: 2 Mb, cpu 0.3%, 0 days
2016-07-09 19:31:51.715   openLuup.scheduler:: [2] device startup completed: status=true, msg=synch in 8.3 s, name=L_openLuup
2016-07-09 19:31:51.715   openLuup.scheduler:: [3] device startup
2016-07-09 19:31:51.715   luup_log:3: ALTUI: initstatus(3) starting version: v1.60
2016-07-09 19:31:51.716   openLuup.scheduler:: [3] device startup completed: status=nil, msg=nil, name=nil
2016-07-09 19:31:51.716   openLuup.scheduler:: [4] device startup
2016-07-09 19:31:51.716   luup_log:4: AltAppStore : starting...
2016-07-09 19:31:51.717   luup.variable_set:4: 4.urn:upnp-org:serviceId:altui1.DisplayLine1 was: AltAppStore now: AltAppStore #hooks:0
2016-07-09 19:31:51.717   luup.variable_set:4: 4.urn:upnp-org:serviceId:altui1.DisplayLine2 was:  now:  #hooks:0
2016-07-09 19:31:51.717   luup.set_failure:4: status = 0
2016-07-09 19:31:51.718   luup.variable_set:4: 4.urn:micasaverde-com:serviceId:HaDevice1.CommFailure was: 0 now: 0 #hooks:0
2016-07-09 19:31:51.718   luup.variable_set:4: 4.urn:micasaverde-com:serviceId:HaDevice1.CommFailureTime was: 0 now: 0 #hooks:0
2016-07-09 19:31:51.718   openLuup.scheduler:: [4] device startup completed: status=true, msg=OK, name=AltAppStore
2016-07-09 19:31:51.718   openLuup.scheduler:: [5] device startup
2016-07-09 19:31:51.718   luup_log:5: RAZB: initstatus(5) starting version: v0.03
2016-07-09 19:31:51.719   openLuup.scheduler:: [5] device startup completed: status=nil, msg=nil, name=nil
2016-07-09 19:31:52.333   openLuup.server:: new client connection: tcp{client}: 0x57b9d0
2016-07-09 19:31:52.334   openLuup.server:: /data_request?id=lu_status2&output_format=json&DataVersion=110632409&Timeout=60&MinimumDelay=1500&_=1468110535775 tcp{client}: 0x57b9d0
2016-07-09 19:31:52.835   luup_log:3: ALTUI: startupDeferred, called on behalf of device:3
2016-07-09 19:31:52.836   luup.variable_set:3: 3.urn:upnp-org:serviceId:altui1.LocalHome was:  now:  #hooks:0
2016-07-09 19:31:52.847   luup.variable_set:3: 3.urn:upnp-org:serviceId:altui1.Version was: v1.60 now: v1.60 #hooks:0

great. this 6 in 1 is not the easiest device to start with but let's try
thanks for the screens and json data, it is quite useful
do you know how does it look like on a real vera ? (how many devices and of which type )


also : try to install latest version from Github ( master branch ) as AK and I are making quite a number of changes in the device detection & creation. would be curious that you a) update ALTUI and RAZB code to the latest from Github and b) delete the 6in1 device and let luup reload. it should recreate several devices

thx
« Last Edit: July 09, 2016, 08:34:13 pm by CudaNet »
openLuup, AltUI, Zway and HomeWave, enough said...

Offline zedrally

  • Hero Member
  • *****
  • Posts: 1224
  • Karma: +15/-5
  • Black Cat Control Systems
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #18 on: July 09, 2016, 08:10:06 pm »
Use the documentation on GitHub to do a baseline install of openLuup.  It's nowadays very easy:

Fateful last words, I had so many problems trying to get openLuup up and going when it was first released that I eventually gave up. I'm sure it's easy when you know how, but I'm lost at the first line.

Loaded my Raspbian turn-key image to my spare Pi2.
I was never able to get past this point and don't remember where I obtained it from in the first place.
I'd love to be part of this, however, I have met my match and can only watch from the stands and cheer for you guy's breaking new ground.
Perhaps, one day there will be a one click install.
Living in the Land of Oz, give me a vegemite sandwich. Home Seer, Vera Lite & Edge, Popp, Black Cat Smart Hub & Vera G, Black Cat Lite 1 & 2's a Black Cat Dimmer or 2, Fantem Tec and then some  Black Cat Cat's Eye PIR's & Door-Window Sensors, RFXComm, Broadlink RMPro & Mini plus a Z-UNO or 2.

Offline CudaNet

  • Beta Testers
  • Hero Member
  • *****
  • Posts: 1401
  • Karma: +42/-11
  • Chimichanga !
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #19 on: July 09, 2016, 08:48:50 pm »
Observed an error.. This was using the latest Git for Raz... Same thing for 0.latest from AppStore...

Code: [Select]
2016-07-09 19:47:14.994   luup_log:5: RAZB: debug: resyncZwayDevices(5)
2016-07-09 19:47:14.995   openLuup.context_switch::  ERROR: [string "[5] I_RAZB.xml"]:654: bad argument #1 to 'ipairs' (table expected, got nil)
2016-07-09 19:47:14.995   luup.delay_callback:: function: 0x1e63bf0 ERROR: [string "[5] I_RAZB.xml"]:654: bad argument #1 to 'ipairs' (table expected, got nil)
2016-07-09 19:47:15.502   openLuup.server:: request completed (1743 bytes, 1 chunks, 7708 ms) tcp{client}: 0x1e73868
2016-07-09 19:47:15.605   openLuup.server:: /data_request?id=lu_status2&output_format=json&DataVersion=111623411&Timeout=60&MinimumDelay=1500&_=1468111589955 tcp{client}: 0x1e73868
openLuup, AltUI, Zway and HomeWave, enough said...

Offline akbooer

  • Moderator
  • Master Member
  • *****
  • Posts: 6387
  • Karma: +292/-70
  • "Less is more"
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #20 on: July 10, 2016, 03:17:11 am »
Fateful last words, I had so many problems trying to get openLuup up and going when it was first released that I eventually gave up. I'm sure it's easy when you know how, but I'm lost at the first line.

OK, so ignore the documentation and just do the four commands I listed in that post.  It is not one-click, but typing four lines is not too hard.
3x Vera Lite-UI5/Edge-UI7, 25x Fibaro, 23x TKB, 9x MiniMote, 2x NorthQ Power, 2x Netatmo, 1x Foscam FI9831P, 9x Philips Hue,
Razberry, MySensors Arduino, HomeWave, AltUI, AltHue, DataYours, Grafana, openLuup, ZWay, ZeroBrane Studio.

Offline akbooer

  • Moderator
  • Master Member
  • *****
  • Posts: 6387
  • Karma: +292/-70
  • "Less is more"
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #21 on: July 10, 2016, 03:47:47 am »
I grabbed the latest AltUI from the AppStore, and I think the latest of Raz.. Hard to tell which is latest, 0.4 or 0.latest.

FYI, the easiest way to update either of these to the latest from the master branch is simply to go to the Plugins page and click the update button against the appropriate plugin.
3x Vera Lite-UI5/Edge-UI7, 25x Fibaro, 23x TKB, 9x MiniMote, 2x NorthQ Power, 2x Netatmo, 1x Foscam FI9831P, 9x Philips Hue,
Razberry, MySensors Arduino, HomeWave, AltUI, AltHue, DataYours, Grafana, openLuup, ZWay, ZeroBrane Studio.

Offline amg0

  • Beta Testers
  • Master Member
  • *****
  • Posts: 3174
  • Karma: +210/-8
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #22 on: July 10, 2016, 04:49:52 am »
I grabbed the latest AltUI from the AppStore, and I think the latest of Raz.. Hard to tell which is latest, 0.4 or 0.latest.

FYI, the easiest way to update either of these to the latest from the master branch is simply to go to the Plugins page and click the update button against the appropriate plugin.
0.latest is the latest.  otherwise it is when I formalize a release. I intend to put quick bugfix directly available under 0.latest

Offline amg0

  • Beta Testers
  • Master Member
  • *****
  • Posts: 3174
  • Karma: +210/-8
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #23 on: July 10, 2016, 04:54:03 am »
Observed an error.. This was using the latest Git for Raz... Same thing for 0.latest from AppStore...

Code: [Select]
2016-07-09 19:47:14.994   luup_log:5: RAZB: debug: resyncZwayDevices(5)
2016-07-09 19:47:14.995   openLuup.context_switch::  ERROR: [string "[5] I_RAZB.xml"]:654: bad argument #1 to 'ipairs' (table expected, got nil)
2016-07-09 19:47:14.995   luup.delay_callback:: function: 0x1e63bf0 ERROR: [string "[5] I_RAZB.xml"]:654: bad argument #1 to 'ipairs' (table expected, got nil)
2016-07-09 19:47:15.502   openLuup.server:: request completed (1743 bytes, 1 chunks, 7708 ms) tcp{client}: 0x1e73868
2016-07-09 19:47:15.605   openLuup.server:: /data_request?id=lu_status2&output_format=json&DataVersion=111623411&Timeout=60&MinimumDelay=1500&_=1468111589955 tcp{client}: 0x1e73868

I have tried to check in a quickfix in 0.latest

Offline CudaNet

  • Beta Testers
  • Hero Member
  • *****
  • Posts: 1401
  • Karma: +42/-11
  • Chimichanga !
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #24 on: July 10, 2016, 10:39:56 am »
Thanks AK and Amg0.. I'm now used to the AppStore but I often forget about the plugins...

I grabbed the latest AltUI from the AppStore, and I think the latest of Raz.. Hard to tell which is latest, 0.4 or 0.latest.

FYI, the easiest way to update either of these to the latest from the master branch is simply to go to the Plugins page and click the update button against the appropriate plugin.
openLuup, AltUI, Zway and HomeWave, enough said...

Offline CudaNet

  • Beta Testers
  • Hero Member
  • *****
  • Posts: 1401
  • Karma: +42/-11
  • Chimichanga !
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #25 on: July 10, 2016, 10:47:06 am »
All is well now. 1 device created. Let me know if you need anything (logs etc..).

Observed an error.. This was using the latest Git for Raz... Same thing for 0.latest from AppStore...

Code: [Select]
2016-07-09 19:47:14.994   luup_log:5: RAZB: debug: resyncZwayDevices(5)
2016-07-09 19:47:14.995   openLuup.context_switch::  ERROR: [string "[5] I_RAZB.xml"]:654: bad argument #1 to 'ipairs' (table expected, got nil)
2016-07-09 19:47:14.995   luup.delay_callback:: function: 0x1e63bf0 ERROR: [string "[5] I_RAZB.xml"]:654: bad argument #1 to 'ipairs' (table expected, got nil)
2016-07-09 19:47:15.502   openLuup.server:: request completed (1743 bytes, 1 chunks, 7708 ms) tcp{client}: 0x1e73868
2016-07-09 19:47:15.605   openLuup.server:: /data_request?id=lu_status2&output_format=json&DataVersion=111623411&Timeout=60&MinimumDelay=1500&_=1468111589955 tcp{client}: 0x1e73868

I have tried to check in a quickfix in 0.latest
« Last Edit: July 10, 2016, 11:11:14 am by CudaNet »
openLuup, AltUI, Zway and HomeWave, enough said...

Offline CudaNet

  • Beta Testers
  • Hero Member
  • *****
  • Posts: 1401
  • Karma: +42/-11
  • Chimichanga !
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #26 on: July 10, 2016, 10:56:53 am »
And for those in the U.S. wanting (F) instead of (C).. Here's some quick directions..

(Raspbian Jessie)
[1] Log in via SSH.
[2] root level: cd /
[3] elevate permissions: sudo su
[4] transition to proper directory: cd /opt/z-way-server/config
[5] nano (or other editor): nano Defaults.xml
[6] within the <CommandClass> node, locate the following sub-nodes and modify accordingly:
where 0 = (C) and 1 = (F); 0 = default value.

Code: [Select]
                <SensorMultilevel>
                        <Fahrenheit>1</Fahrenheit><!-- Default scale to use -->
                </SensorMultilevel>
                <ThermostatSetPoint>
                        <Fahrenheit>1</Fahrenheit><!-- Default scale to use -->
                </ThermostatSetPoint>

[7] cntrl-o, press enter and cntrol-x
[8] reboot

Give z.way some time to adjust. At first the z-way consoles (both Expert and SmartHome) displayed a negative int.
Hope this helps...
openLuup, AltUI, Zway and HomeWave, enough said...

Offline akbooer

  • Moderator
  • Master Member
  • *****
  • Posts: 6387
  • Karma: +292/-70
  • "Less is more"
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #27 on: July 10, 2016, 12:31:04 pm »
Just an update on the plugin progress...

Here's a device page snapshot of a system with:
  • Everspring door sensor
  • Everspring dimmer module
  • Fibaro RGBW controller
  • Everspring ST-814 temperature/humidity
  • Aotec MiniMote 4-button controller
  • Aotec Multi-sensor 3

and also a Parent/Child diagram showing the correct tree structure relationship between the plugin and the multi-sensors.

Currently, though, only the two motion detectors actually work (one can be seen activated in the screen shot) ...... there is actually a very, very long way to go to get it all working.



« Last Edit: July 10, 2016, 01:09:53 pm by akbooer »
3x Vera Lite-UI5/Edge-UI7, 25x Fibaro, 23x TKB, 9x MiniMote, 2x NorthQ Power, 2x Netatmo, 1x Foscam FI9831P, 9x Philips Hue,
Razberry, MySensors Arduino, HomeWave, AltUI, AltHue, DataYours, Grafana, openLuup, ZWay, ZeroBrane Studio.

Offline ShawnParr

  • Jr. Member
  • **
  • Posts: 54
  • Karma: +4/-1
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #28 on: July 10, 2016, 04:09:26 pm »
I also have a Aeotec 6 in 1 multi sensor, although mine isn't showing the nice picture in the Z-Way expert interface like CudaNet has. I just paired an Aeotec recessed door sensor. I'm not sure exactly what information would be helpful, but I'll try to include everything CudaNet did for now. If you need something else, just let me know.


Offline ShawnParr

  • Jr. Member
  • **
  • Posts: 54
  • Karma: +4/-1
Re: Plugin: Razberry support for openLuup/ALTUI
« Reply #29 on: July 10, 2016, 04:16:35 pm »
More screenshots in case it is helpful.

And a conceptual question:

In getting the Caseta Plugin working I ultimately had to grab a number of D_ and S_ files from /etc/cmh-lu on the Vera itself. This of course requires using pluto-lzo to decompress them. I assume for the time being more of these files are going to be necessary, but going forward will some of them be re-created and/or specialized for the OpenLuup environment?

Interestingly without them I was able to add the Caseta Bridge, it auto created all the devices as usual, and I could control them via the AltUI devices section. The issue came when trying to do scenes or workflows as they didn't list any available actions. Adding the /etc/cmh-lu files made those actions show up.

Also as a side note to others playing around with this, on my first attempt I had the Caseta plugin working well, but without actions. So I started adding those files. Eventually things got a little weird, so I reinstalled OpenLuup and used my user_data.json file (with only the Caseta bridge added, I let it reconfigure the devices automagically). After doing that I could see the Caseta devices and their actions. However I couldn't control them either with automation, or just in the devices section. I'm not sure what went wrong, but the LuaUPNP.log showed a lot of TCP errors, and either 0 bytes sent or -1 for each command I tried to send. I wiped out all the Caseta and OpenLuup files and reinstalled all again and that fixed it.