-
Hi all
I’ve been trying to use the Hue api and some of my Lua knowledge to create an energy calculator based on the brightness and wattage of specific models of hue bulb registered on the hub
I’ve pretty much got there, the only stumbling block I have is how I total up all the individual bulb wattages. Can anyone help ?
It’s likely an easy thing for someone more experienced to see, but as I only dip in and dip out now and then, the correct code/syntax does not always come to mind.
Note : as I’ve tried various routes, I’ve commented some things out, but you should be able to get the idea of what I’m trying to do..
Create device json from Hue Hub Decode JSON and extract key values to a table Calculate approx watts based on bulb model and/or watts function Total up watts of all bulbs that are switch on.Code below...
local hueBridgeIP = '192.168.1.29' local hueBridgeAPI = "80uCoXjnn2LNLhxEJ9PW6nmt-G5KWQ2uP3oONAvcm0j" function getHueLight() local http = require('socket.http') local ltn12 = require('ltn12') local json = require('dkjson') t = {} local url = string.format("http://%s/api/%s/lights", hueBridgeIP, hueBridgeAPI) b, c, h = http.request{url=url, sink = ltn12.sink.table(t), method='GET'} huestring = tostring(table.concat(t)) local hue, pos, err = json.decode(huestring, 1, nil) huelights = {} for k, v in pairs(hue) do local modelno = string.gsub(hue[k]['modelid'], "%s+", "") table.insert(huelights, {k, hue[k]['state']['on'], hue[k]['name'], hue[k]['state']['bri'], modelno, hue[k]['state']['reachable']}) print(k, hue[k]['state']['on'], hue[k]['name'], hue[k]['state']['bri'], modelno, hue[k]['state']['reachable']) end end local fourpointeightwattTable = { [ 1 ] = 0.6 , [ 2 ] = 0.7 , [ 3 ] = 0.8 , [ 4 ] = 0.9 , [ 5 ] = 1.2 , [ 6 ] = 1.4 , [ 7 ] = 1.7 , [ 8 ] = 2.0 , [ 9 ] = 2.3 , [ 10 ] = 2.6 , [ 11 ] = 2.9 , [ 12 ] = 3.1 , [ 13 ] = 3.5 , [ 14 ] = 4.0 , } local sevenwattTable = { [ 1 ] = 1.6 , [ 2 ] = 1.7 , [ 3 ] = 1.8 , [ 4 ] = 1.9 , [ 5 ] = 2.2 , [ 6 ] = 2.4 , [ 7 ] = 2.7 , [ 8 ] = 3.0 , [ 9 ] = 3.5 , [ 10 ] = 3.9 , [ 11 ] = 4.5 , [ 12 ] = 5.1 , [ 13 ] = 5.5 , [ 14 ] = 6.4 , } local ninewattTable = { [ 1 ] = 1.6 , [ 2 ] = 1.7 , [ 3 ] = 1.8 , [ 4 ] = 1.9 , [ 5 ] = 2.2 , [ 6 ] = 2.5 , [ 7 ] = 2.9 , [ 8 ] = 3.5 , [ 9 ] = 3.8 , [ 10 ] = 4.6 , [ 11 ] = 5.5 , [ 12 ] = 6.5 , [ 13 ] = 7.7 , [ 14 ] = 8.5 , } function fourpointeightgetWattage(hue) local index = math.floor(hue / 16.5) if index <= 0 then return 0.2 elseif index >= 15 then return 4.8 else return fourpointeightwattTable[index] end end function sevengetWattage(hue) local index = math.floor(hue / 16.5) if index <= 0 then return 0.4 elseif index >= 15 then return 7.0 else return sevenwattTable[index] end end function ninegetWattage(hue) local index = math.floor(hue / 16.5) if index <= 0 then return 0.4 elseif index >= 15 then return 9.0 else return ninewattTable[index] end end local total = 0 local Value = 0 local huewatts = {} for k,v in pairs(huelights) do if v[2] == true and v[5] == "RS125" and v[6] == true then local watts = fourpointeightgetWattage(v[4]) local Value = tonumber(watts) local total = total + Value print("four point eight watts") print(v[5], v[4], v[2], v[3], watts) table.insert(huewatts, {v[5], v[4], v[2], v[3], watts}) --print(watts) --print(total) elseif v[2] == true and v[5] == "LWA004" and v[6] == true then local watts = sevengetWattage(v[4]) local Value = tonumber(watts) local total = total + watts print("seven watts") print(v[5], v[4], v[2], v[3], watts) table.insert(huewatts, {v[5], v[4], v[2], v[3], watts}) --print(watts) --print(total) elseif v[2] == true and v[6] == true then local watts = ninegetWattage(v[4]) local Value = tonumber(watts) local total = total + Value print("nine watts") print(v[5], v[4], v[2], v[3], watts) table.insert(huewatts, {v[5], v[4], v[2], v[3], watts}) --print(watts) --print(total) end end print(total) print(huewatts) -- confirm if table it there (TBC) -
I've implemented this:
https://smarthome.community/topic/20/openluup-version-log/18
into my own MQTT Server and that's cool, since I'm now pushing every variable via MQTT, originating from the Vera.
Just a couple of questions for @akbooer
do I need to check that sock is connected, from time to time? is there anything specifically to retry the command?I'm running it in the latest hour, and everything seems OK, but I want to code it for the worst situations. Thanks, always inspiring!
-
Hi all
Here’s another snippet of code I like to use, to see what’s going on.
local variables = {"Watts"} local NRG_SER = "urn:micasaverde-com:serviceId:EnergyMetering1" local total = 0 for lul_device in pairs(luup.devices) do local readings = {} -- create empty array called readings for _, variable in ipairs(variables) do -- using the id and value in variables table above local value = luup.variable_get(NRG_SER, variable, lul_device) local name = luup.attr_get ('name', lul_device) table.insert( readings, { variable, tonumber(value), name}) -- populate readings table end for _, reading in ipairs(readings) do local Variable = reading[1] local Value = reading[2] or 0 local Name = reading[3] or "Unknown" total = total + Value if Value ~= 0 then print(Name, Variable.. " - ".. Value) end end end print("Total watts = " ..total)
If anyone has any variations on this, I’d love to see it. -
Sharing the love...
As I have a number of foscam cameras around the house, using their API I created the following bit of code to set to retrieve any settings across all of them, to keep them in sync.
This one gets the device name from each of them. If anyone has any variations or ways to improve the bit of code please let me know..
local url = require("socket.url") local URL = "http://" local username = "admin" local password = "password" local cmd = "getDevName" -- /cgi-bin/CGIProxy.fcgi?cmd=getDevName&usr=admin&pwd= local foscamsIPs = { { NO=1, IP="192.168.102.165:88", LOCATION="conservatory"}, { NO=2, IP="192.168.102.38:80", LOCATION="boiler room"}, { NO=3, IP="192.168.102.223:88", LOCATION="Living room"}, { NO=4, IP="192.168.102.245:88", LOCATION="front room"}, { NO=5, IP="192.168.102.104:88", LOCATION="kitchen"}, } for k,v in pairs(foscamsIPs) do -- Read each value. local update = URL .. v["IP"] .. "/cgi-bin/CGIProxy.fcgi?cmd="..cmd.."&usr="..username.."&pwd="..password -- do this for each reading. local status, result = luup.inet.wget(update) print(v["LOCATION"].. " status is " ..status.. " : result is " ..result) end```` -
I have this block of lua and I am using luup.call_delay to delay the sending of IR codes. it works as intended but I am trying to eliminate the use of luup.sleep for the delay before the tcp:close() as well. i cant figure out how to implement luup.call_delay() for the tcp:close() and keep the luup.call_delay intact for the delay between the IR codes.
Thanks in advance.
function Delay1() --[[HDMI Matrix B1--]] local socket = require("socket") tcp = assert(socket.connect("192.168.255.204", 4998)) tcp:send("sendir,1:3,1,38000,1,69,341,171,22,21,22,21,22,21,22,21,22,21,22,21,22,21,22,21,22,64,22,64,22,64,22,64,22,64,22,64,22,64,22,64,22,21,22,21,22,64,22,21,22,64,22,21,22,21,22,21,22,64,22,64,22,21,22,64,22,21,22,64,22,64,22,64,22,1493,341,85,22,3669" .. "\r\n") luup.sleep(1050) tcp:close() end luup.call_delay("Delay1", 1) function Delay2() --[[HDMI Matrix B2--]] local socket = require("socket") tcp = assert(socket.connect("192.168.255.204", 4998)) tcp:send("sendir,1:3,1,38000,1,69,343,171,21,21,22,21,22,21,22,21,21,21,22,21,22,21,21,21,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,63,22,21,22,63,22,21,21,21,22,21,22,21,21,22,21,21,22,63,22,21,22,63,22,63,22,63,22,1528,342,85,22,1528" .. "\r\n") luup.sleep(1050) tcp:close() end luup.call_delay("Delay2", 5) -
I have a script calling io.popen to get the file system partition info, running on the Vera to check for space, and it's getting "cannot allocate memory error".
Any suggestions, beside doing a luup.reload?
-
In my Virtual HTTP plugin I have patterns that could be specified to dynamically compose HTTP URLs based on current values. So, if you enter
http://myip/color?v=%sit gets replaced with the current color. It's very handy when having more parameters, or if your parameter is in a different position.
The problem is that from time to time, there are users with legitimate % in their URLs (since it's the escape char in URLs, after all) and this is causing weird behavior or crash.
So, I want to find something smarter to support both.
Any hints here is appreciated. -
The plugins listed here are available via the Alternative App Store. The app store becomes accessible via a new menu item in the Alternative User Interface once configured.
Both the Alternative User Interface (AltUI) and AltAppStore (AltAppStore) plugins need to be installed on Vera to access the store. With openLuup; this is all "automatically" set up and ready to go as part of the openLuup suite.
The Alternative App Store can be found here.
Publishing a plugin in the store is pretty easy. First your plugin code must be available in GitHub. Publish it, using the Publish command in the AltAppStore web page. You need to enter the salient information and it's ready to go.
Plugin icons can be stored on GitHub eg like so. After a "few days" the raw json describing the plugin appears here.
Vera 3 users should note the store will not work, as Vera 3 doesn't have the https capability required to access GitHub. However, the apps can always be downloaded from GitHub and manually installed.
For those just interested in what the store contains; refer to the list below - as of 2021 July 27 there were about 75 plugins available:
Plugin Comments ABC: Aeratron fans Alternative App Store Built into openLuup ALTHue ALTUI Amcrest Dahua AutoVirtualThermostat BroadLink-Mk2 Canal Plus Not in GitHub Countdown Timer Originated by Futzle DEF: DALI Planet DarkSky Weather Service is rumoured to be closing in late 2021. The "Multi Provider Weather Station" plugin can potentially be used as a replacement. DataYours DelayLight DeusExMachinaII Domoticz Bridge Non functional: needs work check here Domoticz Bridge 2 Originated by 999LV and updated by perhusaas DreamColorESP8266 DreamColorLedRGB Ecobee Edisio Gateway EDS One Wire Server Originated by Chris Jackson EKM metering Emby Interface Enphase Envoy Solar Monitor EventWatcher Ezlo Bridge FritzBox Sensor GHI: Google Calendar 3 Harmony Hub Control Heliotrope Originated by Futzle. openLuup incorporates the same functionality, so this plugin is not required in that casse. Homebridge 2 openLuup HomeWave Push HundredGraphs Logger IKEA Tradfri Image Map Remote Info Viewer For Vera only IPhone Locator IPX800 Irrigation Caddy JKL: KSenia Lares 16 Bridge LuaView MNO: Multi Provider Weather Station Netatmo Network Monitor OpenSprinkler OpenTherm Gateway openWeather PQRS: Paradox EVO IP150 web page scrapper Pioneer Receiver Rachio Rainforest Eagle Based on robertmm's work RaZberry (ALPHA) Reactor RGB Controller Rules Engine SiteSensor SMA inverter Smartmeter Reader Solar Meter Sonos Originated by lolomodo and updated by toggledbits. Sony Bravia IP Surveillance Station Remote (BETA) Switchboard TUV: Telegram Tesla Car UPS Sensor UPnP Event Proxy OpenWRT only - originated by Futzle VeraAlexa Virtual HTTP Devices MQTT commands & status are only available with openLuup. http & Lua can be used by Vera and openLuup. Virtual Pronto Remote Virtual Sensor VW CarNet WXYZ: WES Xee Yamaha RX HTTP Z-Way ZiBlue Gateway ZiGate Gateway -
Here is a simple integration of OpenLuup/vera device to Alexa via Node-red.
E1cid/Node-red-Vera E1cid/Node-red-VeraNode-red flows for Vera. Contribute to E1cid/Node-red-Vera development by creating an account on GitHub.
The speed is fast sub 1 second responses.
Requirements -
node-red.
alexa.
node-red-contrib-amazon-echo(local Hue devices).
openluup or Vera (or any controller via http requests).Capabilities-
Binary switch.
dimming switch.
rgb switch.
Run scenes.Each alexa device node is configured in the topic of the amazon-echo device node -
(device number#type of switch)
bnary - 123#binary.
dimming - 123#dimming.
rgb - 123#colour (W/D is default 310 to adjust colour temp add value to end e.g. 123#colour#300
scene - 123#scene#124 (123 on 124 off. 124 can be omitted).Enter the ip of your controller in the http request block.
[ { "id": "de7838ac.ebead", "type": "amazon-echo-hub", "z": "8659fc6b.981b4", "port": "8980", "processinput": "0", "discovery": true, "x": 150, "y": 840, "wires": [ [ "cd0ae070.e98378", "a605448.899d8b8", "21ca89ff.b0f6ce" ] ] }, { "id": "a605448.899d8b8", "type": "amazon-echo-device", "z": "8659fc6b.981b4", "name": "bedroom four", "topic": "199#colour", "x": 410, "y": 860, "wires": [ [ "688830f.c57775" ] ] }, { "id": "21ca89ff.b0f6ce", "type": "amazon-echo-device", "z": "8659fc6b.981b4", "name": "app safe", "topic": "164#binary", "x": 390, "y": 900, "wires": [ [ "688830f.c57775" ] ] }, { "id": "cd0ae070.e98378", "type": "amazon-echo-device", "z": "8659fc6b.981b4", "name": "lounge 1", "topic": "8#dimming", "x": 390, "y": 940, "wires": [ [ "688830f.c57775" ] ] }, { "id": "688830f.c57775", "type": "function", "z": "8659fc6b.981b4", "name": "", "func": "let types = {\n \"dimming\":[\"urn:upnp-org:serviceId:Dimming1\",\"SetLoadLevelTarget\",\"newLoadlevelTarget\"],\n \"binary\":[\"urn:upnp-org:serviceId:SwitchPower1\",\"SetTarget\",\"newTargetValue\"],\n \"scene\":[\"urn:micasaverde-com:serviceId:HomeAutomationGateway1\",\"RunScene\",\"SceneNum\"],\n \"colour\":[\"urn:micasaverde-com:serviceId:Color1\",{\"tt\":\"SetColor\",\"hs\":\"SetColorRGB\",\"ct\":\"SetColorTemp\"},{\"tt\":\"newColorTarget\",\"hs\":\"newColorRGBTarget\",\"ct\":\"newColorTempTarget\"}] \t\n}\nfunction binaryPayload(device, type, turnOn, payload) {\n payload.id = \"action\";\n payload.serviceId = type[0];\n payload.DeviceNum = device;\n payload.action = type[1];\n payload[type[2]] = (turnOn === true ? 1 : 0);\n payload.message = payload[type[2]];\nreturn payload;\n}\n\nfunction dimmingPayload(device, type, level, payload) {\n payload.id = \"action\";\n payload.serviceId = type[0];\n payload.DeviceNum = device;\n payload.action = type[1];\n payload[type[2]] = level;\n payload.message = level;\nreturn payload;\n}\nfunction scenePayload(device, type, turnOn, payload) {\n payload.id = \"action\";\n payload.serviceId = type[0];\n payload.action = type[1];\n payload[type[2]] = (turnOn === true ? device[0] : (device[2] || device[0]));\n payload.message =\"Run Scene \" + payload[type[2]];\nreturn payload;\n}\n\nfunction rgbPayload(device, types, msg, payload) { \n if(msg.on === true && msg.meta.changes.on === false && msg.meta[\"input\"].on === true){\n payload = binaryPayload(device[0], types[\"binary\"], msg.on, {});\n }else if (msg.meta.changes.percentage && msg.on === true){\n payload = dimmingPayload(device[0], types[\"dimming\"], msg.percentage, {});\n }else if (msg.on === true && msg.colormode === \"hs\"){\n payload.id = \"action\";\n payload.serviceId = types[\"colour\"][0];\n payload.DeviceNum = device[0];\n payload.action = types[\"colour\"][1][\"hs\"];\n payload[types[\"colour\"][2][\"hs\"]] = msg.rgb.join(\",\");\n payload.message = msg.rgb.join(\",\");\n }else if (msg.on === true && msg.colormode === \"ct\"){\n let diff = msg.ct - (Number(device[2]) || 310);\n msg.ct = (diff < 0) ? \"D\" + Math.min(Math.abs(diff * 1.7),255).toFixed() : \"W\" + Math.abs(Math.min((diff * 1.7),255) - 255).toFixed();\n payload.id = \"action\";\n payload.serviceId = types[\"colour\"][0];\n payload.DeviceNum = device[0];\n payload.action = types[\"colour\"][1][\"ct\"];\n payload[types[\"colour\"][2][\"ct\"]] = msg.ct;\n payload.message = msg.ct;\n }\nreturn payload;\n}\n\nmsg.topic = msg.topic.split(\"#\").map(Function.prototype.call, String.prototype.trim);\nmsg.hold = msg.payload;\nmsg.payload = {};\nlet type = msg.topic[1] || \"binary\";\nif(msg.topic[1] === \"scene\"){\n msg.payload = scenePayload(msg.topic, types[\"scene\"], msg.on, {});\n}else if (msg.topic[1] === \"binary\" || msg.percentage === 0 || msg.on === false){\n msg.payload = binaryPayload(msg.topic[0], types[\"binary\"], msg.on, {});\n}else if(msg.topic[1] ===\"dimming\"){\n msg.payload = dimmingPayload(msg.topic[0], types[\"dimming\"], msg.percentage, {});\n}else if (msg.topic[1] === \"colour\"){\n msg.payload = rgbPayload(msg.topic, types, msg, {});\n}\nlet error = [\"green\", msg.topic[1] + \" | \" + msg.topic[0], msg.payload.message];\ndelete msg.payload.message;\nif (Object.keys(msg.payload).length < 1){\n error[0] =\"red\";\n error[2] =\"failed to create payload\";\n}\nnode.status({\"fill\": error[0],\"shape\":\"ring\",\"text\": error[1] + \" | \" + error[2]});\n\nreturn msg;\n", "outputs": 1, "noerr": 0, "initialize": "", "finalize": "", "x": 590, "y": 940, "wires": [ [ "680d28ae.8a163" ] ] }, { "id": "680d28ae.8a163", "type": "http request", "z": "8659fc6b.981b4", "name": "Get request", "method": "GET", "ret": "txt", "paytoqs": "query", "url": "http://192.168.1.11:3480/data_request", "tls": "", "persist": false, "proxy": "", "authType": "", "x": 760, "y": 1000, "wires": [ [ "cb471442.5d60c8" ] ] } ]
Just copy code and import into Node-red -
Moved from https://smarthome.community/topic/56/disable-vera-zwave-device-polling-at-the-device-level where you'll find the referenced code.
-
So, I was messing with my Alexa routines and ha bridge, and I want to share something very cool you could do with the ability to get the last Alexa that heard your command. I mentioned it a couple of times on the old place, but Vera's OS is missing the jq package, but openLuup could have it installed.
Basically, just execute -lastalexa with my VeraAlexa plug-in:
local lastAlexa = luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1", "RunCommand", {Command="-lastalexa"}, 666)Then use it in your scene, to dynamically generate your TTS response with the device you've asked your question seconds before!
local temperature = 25 -- get it from your sensor luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1", "Say", {Text="Ok, outise temperature is " .. temperature .. " degree", Volume=50, GroupZones= lastAlexa, Repeat = 2}, 666Very cool indeed 🙂
-
Hi,
I'm working on new features for my Virtual Devices Plug-in. One of the things I want to add is the ability to poll an endpoint to get power consumption.
So, I want to store the URL and the JSON path in a variable, but I'm confused on how to dynamically parse JSON paths in LUA.
I have something like this in a string variable
data.meters[1].powerand I have to extract the corresponding value from the JSON I got over HTTP.
Any suggestion is very appreciated. Thanks.
-
I'm trying to write a sensor similar to this:
home-assistant/core home-assistant/core
:house_with_garden: Open source home automation that puts local control and privacy first - home-assistant/core
I've already translated it to LUA, but I'm getting strange values. Maybe it's because it's not that cool yet.
Anyone has already done something similar? I have outside and inside sensors and I want to run my de-humidifier based on certain conditions. I want to avoid condensation on the large windows. Last year I ran it based on a fixed threshold, but I want to optimize this if possible.
-
I'm trying to implement the support for http_async in my Virtual Devices plugins. From my tests, Vera's UI seems less busy, but I want to automatically detect if it's installed. Right now I'm using a code like this one:
if pcall(require, "http_async") then else ... endbut I'm not sure it's the best way to do it. Any one? @akbooer? Thanks!
-
I have finally integrated my new motorized (blackout) blinds in the home office, since I'm planning to mainly work from home at least since the end of the year.
I'm quite satisfied, since I made them completely automatic, but I noticed that I have two problems:
rainy days: I have a rain sensor for the exterior sunscreens, so I can think about moving the interior ones as well moving season: while moving them to a middle position for the night is good now at 30 minutes before sunset, I'm not sure it will be OK in autumn or winter.So, I was thinking about adding some logic linked to sun position, or a light sensor device.
Any hints, before re-inventing the wheel? Thanks. -
I’m sure there is a better/more polished way to do this, but this remains one of my go to report urls on Vera.
-- http://forum.micasaverde.com/index.php?topic=52025.msg334246#msg334246 local d, n local file = io.open("/www/sb.html", "w") file:write("<head> <meta http-equiv='refresh' content='30' /> </head>\n") file:write("<style>.custom { font-size: 1em; font-family: Gill Sans Extrabold, sans-serif; padding:5px; border-collapse: collapse; border: 1px solid black; }</style><table class=custom><tr class=custom><th class=custom>Security Sensor</th><th class=custom>Last Tripped</th></tr>\n") local tt = {} for n,d in pairs(luup.devices) do if d.category_num == 4 then -- local lasttrip = tonumber(luup.variable_get("urn:micasaverde-com:serviceId:SecuritySensor1", "LastTrip", n) or 0,10) local lasttrip = tonumber(luup.variable_get ("urn:micasaverde-com:serviceId:SecuritySensor1", "LastTrip", n) or os.time()) local timeString = os.date(" %Y/%m/%d - %X", lasttrip) if lasttrip > 0 then table.insert(tt, { devnum=n, last=lasttrip, ltime=timeString }) end end end table.sort(tt, function(a,b) return a.last > b.last end) -- sort highest to lowest for n,d in ipairs(tt) do file:write("<tr class=custom><td class=custom>" .. luup.devices[d.devnum].description .. "</td><td class=custom>".. d.ltime .. "</td></tr>\n") print ( d.ltime .. ' : ' .. luup.devices[d.devnum].description .. " Sensor was last tripped") end file:write("</table>\n") file:close() -
Responding to @PrincessClevage's request through a PM,
I am posting my Roomba integration:
First of course you will have to have Home Assistant installed and running. I will not be covering that.
Home Assistant iRobot Roomba iRobot Roomba
Then you will need to add and configure the roomba component which can now be done through the UI
Instructions on how to integrate your Wi-Fi enabled Roomba and Braava within Home Assistant.
I won't cover this either.
Next, on Vera or openLuup, I used a sitesensor with the following configuration:
Screen Shot 2020-07-10 at 10.15.55.png
I also have a preset function loaded in my startup lua to directly send post commands to my home assistant instance which I posted here:
https://smarthome.community/topic/39/lua-function-in-openluup-startup-lua-to-send-async-command-to-home-assistant-apiwhich then enables me to create a variety of scenes triggered by the site sensor: For example disarming the site sensor docks the roomba by creating a variable watch on the arm status of the site sensor and then run this code:
Screen Shot 2020-07-10 at 10.22.19.png
Likewise I can get it to start cleaning from openLuup through a similar scene
Screen Shot 2020-07-10 at 10.23.02.png
And you can let wild of your creativity from there... I have an identical integration for the xiaomi robot and am tuning the vacuum noise according to whether I am on the same floor while the robot is cleaning...
-
I'm struggling to fix the code attached here
dbochicchio/vera dbochicchio/vera
LUA Scripts for the eZlo Vera Platform (UI7). Contribute to dbochicchio/vera development by creating an account on GitHub.
Under certain circumstances (thanks @DesT!) I see that it's causing a luup reload infinite cycle, because child devices are being created, then deleted. Specifically, I see this in the logs:
2020-06-01 19:35:30.482 luup.chdev.sync:: [102] Open Sprinkler Test, syncing children 2020-06-01 19:35:30.482 openLuup.chdev:: deleting [413] Daily Garden 2020-06-01 19:35:30.482 openLuup.chdev:: deleting [414] Water Level 2020-06-01 19:35:30.482 openLuup.chdev:: deleting [411] Daily Cedars 2020-06-01 19:35:30.482 openLuup.chdev:: deleting [412] St-Eustache Rules AM 2020-06-01 19:35:30.482 openLuup.luup:: device 102 'Open Sprinkler Test' requesting reloadThe devices are created (look at line 357/410), but when I call luup.chdev.sync, they got deleted. Any hints? Thanks
-
With all the acquisition of Dark Sky by Apple in the plans, I thought I would share my rain sensor setting which is used as input for my irrigation system:
Install @toggledbits site sensor Register for a free tier account from http://weatherbit.io an pick up the API key the url I use is using forecast over 2 days (replace with your coordinates and key): https://api.weatherbit.io/v2.0/forecast/daily?lat=**yourlat**&lon=**yourlong**&key=**yourkey**&days=2 The trip expression is as follows as I also pull a variable from within the sensor variable for the calculation: tonumber(response.data[1].precip)+ tonumber(response. data[2].precip) + tonumber(getstate( 67, "urn:toggledbits-com:serviceId:SiteSensor1", "PastRain"))> 5 For display I also pull these value expressions: "Total Rain "+(tonumber(response.data[1].precip)+ tonumber(response.data[2].precip) + tonumber(getstate( 67, "urn:toggledbits-com:serviceId:SiteSensor1", "PastRain")))+" mm" "Tomorrow "+response.data[2].precip+" mm" "Today Probability "+response.data[1].pop+"%" "Tomorrow Probability "+response.data[2].pop+"%" response.data[1].precip "Today "+response.data[1].precip+" mm" "Accumulated "+getstate( 67, "urn:toggledbits-com:serviceId:SiteSensor1", "PastRain") Add a time based scene with the following lua code to record the past day rain accumulation every night at the time of your choosing (I use 23:00). Replace the sensorid variable with your sensor id) local sensorid=**yoursitesensorid** local siteid= "urn:toggledbits-com:serviceId:SiteSensor1" local current =luup.variable_get(siteid,"Value5", sensorid) luup.variable_set(siteid,"PastRain", current, sensorid)With this, my yard irrigation only turns on when the sensor is not tripped... meaning less than 5mm of water is accumulating across 3 days (yesterday, today and tomorrow). Adjustments in value can easily be made.
-
function POSTHA(path, payload, token) local async = require "http_async" local ltn12 = require("ltn12") local resp = {} async.request( { url = path, method = "POST", headers = {["Content-Type"] = "application/json", ["Content-Length"] = payload:len(), ["Authorization"] = token, }, source = ltn12.source.string(payload), sink = ltn12.sink.table(resp) }, function() end) end
example of usage:
local hass_token = "*********" local path = "http://hass_ip:8123/api/services/vacuum/turn_off" local payload = [[{"entity_id": "vacuum.upstairs_roomba"}]] POSTHA(path, payload, hass_token)
define the token obtained from home assistant in the scene lua or startup lua:
Roomba integration through Hass
-
Responding to @PrincessClevage's request through a PM,
I am posting my Roomba integration:
First of course you will have to have Home Assistant installed and running. I will not be covering that.
Then you will need to add and configure the roomba component which can now be done through the UI
iRobot Roomba
Instructions on how to integrate your Wi-Fi enabled Roomba and Braava within Home Assistant.
I won't cover this either.
Next, on Vera or openLuup, I used a sitesensor with the following configuration:
I also have a preset function loaded in my startup lua to directly send post commands to my home assistant instance which I posted here:
https://smarthome.community/topic/39/lua-function-in-openluup-startup-lua-to-send-async-command-to-home-assistant-apiwhich then enables me to create a variety of scenes triggered by the site sensor: For example disarming the site sensor docks the roomba by creating a variable watch on the arm status of the site sensor and then run this code:
Likewise I can get it to start cleaning from openLuup through a similar scene
And you can let wild of your creativity from there... I have an identical integration for the xiaomi robot and am tuning the vacuum noise according to whether I am on the same floor while the robot is cleaning...
-
Oh dear. This may break me. I need a Roomba.....
C
-
@rafale77
Is it possible that site sensor can also send the command to Roomba without home assistant? -
It probably is possible but I never looked at the API itself. Home Assistant is too convenient as a bridge to many other APIs piping through its own API into openLuup... Actually I have not even found the documentation for it.
Edit: It isn't an open API so it is not documented...
-
@rafale77
I am really trying to avoid having multiple units to manage home automation e.g this hub bridges to that device which then executed on another and I really only have time to put effort into one device. I have read this forum but what is presented here would be way past the average joe (not that it is aimed at the average joe). So far I have been able to contain all my automation in Vera and Alexa/google home and use firewalla/pihole for security / privacy which is working well but I can see the lack of the current Vera evolving a problem for the future and curious what options are out there, that also help keep as many much as possible local -
Unfortunately at this point there is no commercial offering which can cover absolutely everything.
The closest platform to doing this that I know of is actually home assistant which is open source and as I explained here:https://smarthome.community/topic/123/the-home-automation-controller-pyramid
Even IT often needs to be paired with something else to be fully complete. Some people are content with some compromises they have to make with the platform they have chosen: For home assistant, it is currently a slightly lacking zwave support and a not so easy and complete automation builder which is why people are running it either with node-red or like most of us here, with openLuup and are living with their zwave support or bridging it to hubitat, homeseer or for some, with vera. It is however the fastest and most complete local API integration hub...
All others are good at one thing and not at others. Vera was very innovative with their lua logic and plugin layer but were catastrophic at RF network management. Homeseer are very good at network management but lack zigbee and are expensive. Hubitat is very good overall for device management but lacks some cross platform and API integration...
OpenLuup offers the advantage of being very transparent to vera. It runs all the same plugins, scenes and has the same API/logic architecture. It only lacks radio management which is brought it through bridge pluging like zway bridge or vera bridge.
The work required to reverse engineer the home assistant plugin to roomba and make an equivalent for openLuup is possible but to me, it is a lot more work than to install home-assistant and bridge the device through it. It is a lot more efficient also because it opens the door to doing the same thing with all the home-assistant integrations which, let's be honest, we (with openLuup) won't be able to compete with given the relative size of that community and the speed at which they are going. OpenLuup+HomeAssitant+Z-way is the best approach for someone coming from Vera. That's just my opinion...
Besides all three together are a lot less work and a lot less maintenance than vera alone... Infinitely less. That's my experience. Staying with one platform may not be the simplest way to go...
Open API availability for a Wi-Fi connected Roomba. | iRobot Customer Care