-
Replacing Google Map with Bing Map rafale77/IPhoneLocator IPhone Locator plugin for Micasaverde VERA and openLuup - rafale77/IPhoneLocator Here Map rafale77/IPhoneLocator IPhone Locator plugin for Micasaverde VERA and openLuup - rafale77/IPhoneLocator Both tested on openLuup
-
I've made some mods to Futzle's upnp event proxy and placed it in the AltApp store (with her permission). ie it's here in GitHub. Now it seems some people say it works with openLuup already. However the version released by Futzle required two things in order to function: the file L_UPnPProxy1.lua was expected to be compressed, as it would be on a Vera eg: L_UPnPProxy1.lua.lzo the hardware needs to be running OpenWrt; ie as per Vera does. I modified the code to fix point 1) (see the script below) but I would like to see point 2) resolved, so a RasPi can be used. That is modify the script to allow a deamon to be run on a RasPi without fiddling around with say "/etc/rc.local". So has any one got the proxy going on any hardware that is NOT using OpenWrt ? I'm unsure how to do it. Basically this script and/or the script it includes needs to be modified or even merged to suit. You'll note that after the shebang, it requires the file "etc/rc.common" (reproduced further below). The latter appears to be some sort of template file that is overriden as required by the first script. It cites "$IPKG_INSTROOT", whatever that is. However it may be possible to make use of it somehow on a RasPi? #!/bin/sh /etc/rc.common # Copyright (C) 2007 OpenWrt.org START=80 PID_FILE=/var/run/upnp-event-proxy.pid PROXY_DAEMON=/tmp/upnp-event-proxy.lua start() { if [ -f "$PID_FILE" ]; then # May already be running. PID=$(cat "$PID_FILE") if [ -d "/proc/$PID" ]; then COMMAND=$(readlink "/proc/$PID/exe") if [ "$COMMAND" = "/usr/bin/lua" ]; then echo "Daemon is already running" return 1 fi fi fi # openLuup: Look for the uncompressed proxy daemon Lua source. if [ -f /etc/cmh-ludl/L_UPnPProxyDaemon.lua ]; then PROXY_DAEMON_UC=/etc/cmh-ludl/L_UPnPProxyDaemon.lua elif [ -f /etc/cmh-ludl/files/L_UPnPProxyDaemon.lua ]; then PROXY_DAEMON_UC=/etc/cmh-ludl/files/L_UPnPProxyDaemon.lua # Vera 3: Else look for the compressed proxy daemon Lua source. elif [ -f /etc/cmh-ludl/L_UPnPProxyDaemon.lua.lzo ]; then PROXY_DAEMON_LZO=/etc/cmh-ludl/L_UPnPProxyDaemon.lua.lzo elif [ -f /etc/cmh-lu/L_UPnPProxyDaemon.lua.lzo ]; then PROXY_DAEMON_LZO=/etc/cmh-lu/L_UPnPProxyDaemon.lua.lzo fi if [ -n "$PROXY_DAEMON_UC" ]; then cp "$PROXY_DAEMON_UC" "$PROXY_DAEMON" elif [ -n "$PROXY_DAEMON_LZO" ]; then /usr/bin/pluto-lzo d "$PROXY_DAEMON_LZO" "$PROXY_DAEMON" fi # Close file descriptors. for fd in /proc/self/fd/*; do fd=${fd##*/} case $fd in 0|1|2) ;; *) eval "exec $fd<&-" esac done # Run daemon. /usr/bin/lua "$PROXY_DAEMON" </dev/null >/dev/null 2>&1 & echo "$!" > "$PID_FILE" } stop() { if [ -f "$PID_FILE" ]; then PID=$(cat "$PID_FILE") if [ -d "/proc/$PID" ]; then COMMAND=$(readlink "/proc/$PID/exe") if [ "$COMMAND" = "/usr/bin/lua" ]; then /bin/kill -KILL "$PID" && /bin/rm "$PID_FILE" return 0 fi fi fi echo "Daemon is not running" return 1 } And here is "etc/rc.common" as found in OpenWrt initscripts. Note the command actions it implements - in particular disable & enable, which set up Sxxy (start) & Kxxy (stop) files in the directory "etc/rc.d", which is not found in the RasPi directory structure: #!/bin/sh # Copyright (C) 2006-2009 OpenWrt.org . $IPKG_INSTROOT/etc/functions.sh initscript=$1 action=${2:-help} shift 2 start() { return 0 } stop() { return 0 } reload() { return 1 } restart() { trap '' TERM stop "$@" start "$@" } boot() { start "$@" } shutdown() { stop } disable() { name="$(basename "${initscript}")" rm -f "$IPKG_INSTROOT"/etc/rc.d/S??$name rm -f "$IPKG_INSTROOT"/etc/rc.d/K??$name } enable() { name="$(basename "${initscript}")" disable [ "$START" ] && ln -s "../init.d/$name" "$IPKG_INSTROOT/etc/rc.d/S${START}${name##S[0-9][0-9]}" [ "$STOP" ] && ln -s "../init.d/$name" "$IPKG_INSTROOT/etc/rc.d/K${STOP}${name##K[0-9][0-9]}" } enabled() { name="$(basename "${initscript}")" [ -x "$IPKG_INSTROOT/etc/rc.d/S${START}${name##S[0-9][0-9]}" ] } depends() { return 0 } help() { cat <<EOF Syntax: $initscript [command] Available commands: start Start the service stop Stop the service restart Restart the service reload Reload configuration files (or restart if that fails) enable Enable service autostart disable Disable service autostart $EXTRA_HELP EOF } . "$initscript" ALL_COMMANDS="start stop reload restart boot shutdown enable disable enabled depends ${EXTRA_COMMANDS}" list_contains ALL_COMMANDS "$action" || action=help [ "$action" = "reload" ] && action='eval reload "$@" || restart "$@" && :' $action "$@"
-
As another one asked for it on the other forum, I finally created a new plug-in for Telegram notifications: https://github.com/dbochicchio/vera-Telegram/ You can: send text messages send (still) images send videos (gif or mp4) send silent notifications I remember @CatmanV2 was searching for something similar (maybe?). I'm using it to send push notifications to me and my wife, using a group. I have my own code streaming my cameras and sending a video as gif based on certain events (ie motion sensors or door/entryways left open). While this part is not included into the plug-in, if you're able to get a video yourself (by pointing to a URL), you'd good to go. Still images from cams (or, let's say, your favorite weather map, or any video/gif/image on the Interner ot local) are supported as well. 100% compatible with bot Vera and openLuup (where it was developed, anyway). Feel free to ask questions or suggest new features.
-
On my VeraPlus I use the Countdown timer plugin. If I click on details via my apps, I can create multiple timers. Now I want to switch to openluup and have installed the Countdown timer plugin via appstore. Only 1 timer is visible. Is it possible to create more timers
-
The plugin has been updated to ver 0.56 which improves the RF learning procedure. It also recognises some of the newer RM4 devices (thanks Bruce Lacey). Existing uses just need to upload the "L_BroadLink_Mk2_1.lua" file. RF learning has been improved but is never particularly reliable. You can invoke testing by executing this code in the Lua Test box: local DeviceID = the_id_of_the_IR_child_device luup.call_action('urn:a-lurker-com:serviceId:IrTransmitter1', 'LearnRFCode', {}, DeviceID) return true Running the code illuminates the LED on the BroadLink device. If you do nothing at this point, the learning times out after about 24 seconds and the result is "No RF code was learnt". While in the learning mode, tap the remote button to be learnt, every 2/3 of a second or so. If the LED goes out (typically after about say 5 seconds) some result was learnt. The result can be found in the parent device by looking at the variable "LearntRFCode". However, it is far easier to look at the log file, which logs the process as it proceeds and also the result. You need to learn a few results to try and determine if the results are at all consistent.
-
I just published an update to my Virtual Devices Plug-in. What's new in version 1.5: support for async HTTP (out of the box on openluup, just download https://github.com/akbooer/openLuup/blob/master/openLuup/http_async.lua and copy with the plug-in files on Vera) experimental support for setpoints management in Virtual Heaters (you know, the device will turn itself off if temperature is reached, and automatically on when temperature is not beyond the setpoint) external device for temperature in Virtual Heaters (just set urn:bochicchio-com:serviceId:VirtualHeater1/TemperatureDevice variable) small fixes, stabilization Grab your copy from https://github.com/dbochicchio/vera/tree/master/VirtualDevices As always, 100% local, 100% apps friendly, 100% supported by Alexa (and Google Home, I guess).
-
I am looking at making openLuup to act as an MQTT client for a variety of applications. I may write a plugin for it myself based on either of these two libraries: xHasKx/luamqtt luamqtt - Pure-lua MQTT v3.1.1 and v5.0 client. Contribute to xHasKx/luamqtt development by creating an account on GitHub. Yongke/luamqttc A lua mqtt client which support MQTT version 3.1.1 - Yongke/luamqttc Still have to learn the details of how it would work. If people have ideas, feel free to post here!
-
Hi I've got a licence for AltUI. On my laptop, it's shown and my configuration of favourites etc is saved. On my desktop, there's a licensing message and none of my favourites are there. Are licences per machine or per instances of AltUI? Cheers C
-
As @mrFarmer aka Reneboer is here.. Are you thinking to remove darksky API and use something else as Apple take over DarkSky
-
Anyone any idea what this might mean? We have two iPhones. Mrs C's and mine. Mine is totally fine. Mrs C's says 'forceRefresh error, check logs / 300 s' and refuses to tell me where she is Same settings in both instances (in fact I have created a second instance for Mrs C and that does the same). I know the username / password are correct, and the iCloud list populates in the right manner. The log has this: 2020-07-05 11:58:55.866 luup_log:25: IPhoneLocator: loop: an error occurred during execution of forceRefresh():[string "L_IPhone.lua"]:639: attempt to index local 'obj' (a nil value) 2020-07-05 11:58:55.866 luup.variable_set:: 25.urn:upnp-org:serviceId:IPhoneLocator1.MsgText was: 2020-07-05 11:58 now: forceRefresh error, check logs / 300 s #hooks:0 Any ideas? Cheers C
-
Morning, all Not sure if there's an alarm clock currently available for Openluup? While not perfect, it wasn't too bad for use. Might it just be a case of extracting the files from Vera and creating a new device? Cheers C
-
I promise I'll stop asking for thing soon Vosmont colour wheel is installed from the Alt store When I go into the Settings tab: an error occurred while displaying the javascript tab. devid: 0-21 err:Cannot read property 'showColorWheel' of undefined stack:TypeError: Cannot read property 'showColorWheel' of undefined at eval (eval at _deviceDrawControlPanelJSTab (http://192.168.70.249:3480/J_ALTUI_uimgr.js:3024:17), :1:15) at _deviceDrawControlPanelJSTab (http://192.168.70.249:3480/J_ALTUI_uimgr.js:3024:17) at _deviceDrawControlPanelOneTabContent (http://192.168.70.249:3480/J_ALTUI_uimgr.js:3719:8) at _displayActiveDeviceTab (http://192.168.70.249:3480/J_ALTUI_uimgr.js:3746:4) at HTMLAnchorElement. (http://192.168.70.249:3480/J_ALTUI_uimgr.js:7038:4) at HTMLDivElement.dispatch (http://ajax.googleapis.com/ajax/libs/jquery/3.4.1/jquery.min.js:2:42571) at HTMLDivElement.v.handle (http://ajax.googleapis.com/ajax/libs/jquery/3.4.1/jquery.min.js:2:40572) at Object.trigger (http://ajax.googleapis.com/ajax/libs/jquery/3.4.1/jquery.min.js:2:70627) at HTMLAnchorElement. (http://ajax.googleapis.com/ajax/libs/jquery/3.4.1/jquery.min.js:2:71222) at Function.each (http://ajax.googleapis.com/ajax/libs/jquery/3.4.1/jquery.min.js:2:2777) I can see the J_ALTUI_uimgr.js file in the root folder and in /files Does it need to be somewhere else? TIA C
-
Latest Vera Ecobee Plugin: rafale77/vera-ecobee Vera Plugin for ecobee Thermostat. Contribute to rafale77/vera-ecobee development by creating an account on GitHub.
-
The latest/working version of OpenSprinkler for openLuup, is it the one from @therealdb ?
-
I just got my ALTUI/openLuup system working but I am again stuck. I want to create a scene that is triggered every hour and turns on a Z-wave switch, delays 1 minute, then turns the switch off again. I cannot seem to get this working and I can find no documentation that helps me. Regards.
-
Reactor: Issue trying to view actions on Vera from Altui. I have a bunch of reactors installed on my VeraPlus. When I am looking at them in ALTUI, and go to the actions page, I get a pop up that says OK Success and Waiting for system ready.... Then the browser slowly fades to black. Is that the expected behavior? Tried it from a PC as well has via localhost on the RPI. Does Reactor need to also be installed on the RPI to make this work? Thanks, Roger
-
rafale77/Amcrest-Dahua-Openluup Plugin for Amcrest/Dahua Cameras on openLuup. Contribute to rafale77/Amcrest-Dahua-Openluup development by creating an account on GitHub.
-
This is a modified version of the countdown timer plugin to make it work on openLuup. The original one would fail because it relied on the vera being slow to catch a variable state change. openLuup tends to be too fast at changing the veriable state on and off which lead to it becoming inconsistent. rafale77/MiOS-CountdownTimer Plugin for MiOS home automation gateways to make countdown timer devices that trigger events on completion - rafale77/MiOS-CountdownTimer
-
rafale77/vera-pioneer Plugin for vera. Contribute to rafale77/vera-pioneer development by creating an account on GitHub.
BroadLink Mark II plugin
-
The plugin has been updated to ver 0.56 which improves the RF learning procedure. It also recognises some of the newer RM4 devices (thanks Bruce Lacey).
Existing uses just need to upload the "L_BroadLink_Mk2_1.lua" file.
RF learning has been improved but is never particularly reliable. You can invoke testing by executing this code in the Lua Test box:
local DeviceID = the_id_of_the_IR_child_device luup.call_action('urn:a-lurker-com:serviceId:IrTransmitter1', 'LearnRFCode', {}, DeviceID) return trueRunning the code illuminates the LED on the BroadLink device. If you do nothing at this point, the learning times out after about 24 seconds and the result is "No RF code was learnt".
While in the learning mode, tap the remote button to be learnt, every 2/3 of a second or so. If the LED goes out (typically after about say 5 seconds) some result was learnt.
The result can be found in the parent device by looking at the variable "LearntRFCode". However, it is far easier to look at the log file, which logs the process as it proceeds and also the result. You need to learn a few results to try and determine if the results are at all consistent.
-
@a-lurker said in BroadLink Mark II plugin:
You can invoke testing by executing this code in the Lua Test box
Presumably, you can also access this from either AltUI or the openLuup console Action page for the device, which would be even easier.
-
Yep - many ways to skin a cat but you might only have a dog to work with.
