Help with Z-Way plugin
-
No, the problem is not openLuup, and openLuup is not like Vera. You simply don’t need to tear everything down and start again.
- verify that you have the latest openLuup system from the development branch. The Plugin page should show 20.5.3b, or thereabouts.
- delete any ZWay plugin device
- check there are no devices lurking in room 101 (delete them if they are)
- install ZWay once again from the master branch, from the (Alt) App Store.
- send me a Startup log, so that I have something to go on.
- don’t forget to login to the ZWay plugin using the Login action of the plugin.
-
- I have 19.12.27
- Deleted Razberry device, deleted Z-way device
- Cannot see any "Room 101"
- Installed ZWay
- ???Where is the Startup log???
6.???Where is the "Login action of the plugin"???
Sorry if I am being thick.
-
OK, so first you need the latest openLuup version. Simply go to the Plugins page, type development into the update box and click the update button. Wait for it to restart. You should be on 20.5.3b of openLuup.
Let's do that step first.
-
Done, sucessful
-
Excellent! From the AltUI > More > App Store page, install the master version of the ZWay plugin. It should be
v20.5.4.v20.4.5. -
Done, version was v20.4.5 - did you typo?
-
Yes, I did. So you have the latest openLuup and ZWay plugin now.
You need to login in to your ZWay system through the plugin. If you go to the ZWay device control panel (by clicking on its icon on the Devices page) you will find the Actions menu (in blue) and there, right at the top, should be the login action. You need to enter your ZWay system admin username and password and then press the blue Login button.
Returning to the devices page, you should see that the ZWay device is suggesting an openLuup reload. Do that.
-
It worked...at last.Thanks for your patience.
-
No, this is all my fault. The original ZWay plugin was prototyped four years ago, but in the last six months , with the way Vera was going, we ( @rafale77, @DesT, and some others) had a bit of a push to revive it and make it really functional. In the process, of course, documentation was not done.
My fault, too, that when you said
@JMK said in Help with Z-Way plugin:
On the same Raspberry Pi3 I have installed openLuup on which I have installed the Z-Way plugin.
...I assumed that it had all gone according to plan.
So now you see your Fibaro switch, and it works...?
-
Yes, I can see the Fibaro switch and I am able to toggle it. The reason I am going through all this is I also have just about had enough of Vera. I had small configurations (10-15 devices) at two locations that had worked flawlessly for 6 years on Vera3s when it looked like support for the Vera3 would end because of EOL I decided to migrate to VeraPlus. Big mistake. Devices dropping offline, scenes behaving strangely (triggering when they shouldn't, not triggering when they should). At the remote location I had to spend over $200 dollars to replace devices that had worked perfectly on the Vera3, and so on...
Because I cannot afford to loose the automation here locally I am transferring one device at a time from the VeraPlus to the openLuup system - that's my plan anyway.
-
I updated my Z-way plugin to the latest Maser version (v20.4.5). In order to get the plugin to get updated I had to delete the existing Z-way plugin and start over. I had a really old v18.7.16, however it was working ok. I am on OpenLuup20.5.6, so that should be ok.
I now have the latest version of the Z-way plugin, but I need to change IP from the default 127.0.0.1 to the right one (192.168.1.xx), on which my Z-way is running (not the same as my OpenLuup). However when I try to change IP via the "Variables" tab it does not stick, it reverts back to 127.0.0.1 after Luup reload. I have tried both via AltUI and via the OpenLuup (unsure where I should do this) but get no result either way.
Any ideas?
//ArcherS
-
Yes. You should not be using the variable to set the IP address, but, instead, the device attribute named ip.
(The variable you were, I assume, trying to change is an AltUI Display variable, which reflects the IP actually assigned.)
-
Thank's for a really quick reply! That indeed did the trick, I knew it was something easy I missed.
Now I just need to go through my Reactors and re-map my z-way devices. Not too much work.//ArcherS
-
I had a disaster yesterday - my Raspberry Pi SD died and looking at it i think it may have been a Sandisk fake, the labeling and fonts just do not look right. Anyway, I had to re-install Z-Way, openLuup... and this time I decided to put cmh-ludl in etc rather than in my home directory. I noticed that in the manual it says "be careful with permissions". So what are the 'correct' permissions? As you can see I am not too familiar with Linux
-
Sorry more... I also notice that when I execute openLuup_reload I get these messages...
mkdir: cannot create directory ‘/www’: Permission denied
rm: cannot remove '/www/altui/altui*': No such file or directory -
I don't know what they should be but 755 would be a good place to start.
How good are you with Linux? ls -l will show you the current user / group ownership. No idea what user Z-way will run as but you can
chmod 777 -R /www is pretty much bound to work but has some possibly nasty security impacts. I doubt it's a huge issue here thoughC
-
@JMK said in Help with Z-Way plugin:
I decided to put cmh-ludl in etc rather than in my home directory.
I originally suggest that location, in order to mimic Vera's files structure, but during openLuup's evolution it developed a virtual storage system and file aliases which means that it only needs to access folders within its own home directory tree. Even things like
/www/cgi/and/www/cgi-bin/cmh/are handled that way.So, really, I can't think of a good reason to put it in
/etc/, indeed, I think you've found a good reason not to.I think you'll find those two error messages come from AltUI, certainly the second one which I know to be benign.
-
Settled for 0755, seems to be OK. Thanks everyone.
-
Can't seem to get any devices in openluup!
Everything OK in Z-Way:
4 devices working perfectly:
Openluup versions:
Attributes:
Log:
2020-11-04 13:49:44.303 openLuup.scheduler:: [197] Z-Way device startup 2020-11-04 13:49:44.303 luup_log:197: ZWay: v20.4.5 2020-11-04 13:49:44.336 luup_log:197: ZWay: HomeId: c84d9ef4 2020-11-04 13:49:44.336 luup.variable_set:: 197.urn:upnp-org:serviceId:altui1.DisplayLine1 was: 0 vDevs, 0 zNodes now: #hooks:0 2020-11-04 13:49:44.336 luup.register_handler:: global_function_name=HTTP_Z-Way_197, request=z197 2020-11-04 13:49:44.361 luup.set_failure:: status = 0 2020-11-04 13:49:44.361 luup.variable_set:: 197.urn:micasaverde-com:serviceId:HaDevice1.CommFailure was: 0 now: 0 #hooks:0 2020-11-04 13:49:44.361 luup.variable_set:: 197.urn:micasaverde-com:serviceId:HaDevice1.CommFailureTime was: 0 now: 0 #hooks:0 2020-11-04 13:49:44.394 luup.variable_set:: 197.urn:upnp-org:serviceId:altui1.DisplayLine1 was: now: 0 vDevs, 0 zNodes #hooks:0 2020-11-04 13:49:44.394 luup_log:197: ZWay: Asynchronous polling 2020-11-04 13:49:44.394 luup.set_failure:: status = 0 2020-11-04 13:49:44.394 luup.variable_set:: 197.urn:micasaverde-com:serviceId:HaDevice1.CommFailure was: 0 now: 0 #hooks:0 2020-11-04 13:49:44.394 luup.variable_set:: 197.urn:micasaverde-com:serviceId:HaDevice1.CommFailureTime was: 0 now: 0 #hooks:0 2020-11-04 13:49:44.395 openLuup.scheduler:: [197] Z-Way device startup completed: status=true, msg=OK, name=L_ZWay2result:
Any ideas?
-
zway username and password set in the plugin variables?
