Mmmmm - interesting - I've had a very similar experience with a couple of Veras. One of the Veras; I recently turned off the WiFi and I have never heard from it since; even though it has always successfully conversed via a hardwired LAN interface for years.
akbooer I recommend you ditch the Edge - it's costing you money at about 0.24 kW hrs per day. Further still, I recommend you use openLuup. It works well and the developer? - don't stuff around. Please donate as he or she requests.
@akbooer said in Sun position or light sensor for blinds?:
Yes, it's all been done. You need @futzle's Heliotrope plugin.
Out of interest; I've modified/updated and re released Futzle's Heliotrope plugin in the AltApp store (with Futzle's permission).
Likewise; I've modified/updated and re released Chris Jackson's EDS one wire server plugin in the AltApp store (with Chris's permission).
For the most up-to-date list refer to the openLuup documentation.
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:
Me:
What is the likelihood of the iot business Ezlo remaining in business?
It:
It is difficult to answer this question since it depends on a variety of factors such as market conditions, customer demand, and the company's financial stability. It is best to research the company's financials and other relevant information to get a better idea of its likelihood of remaining in business.
Mmmm - great weasel words. Political staffers will love this.
I use openLuup with Zigbee2MQTT on a RasPi and it's been working with no issues. Plus you get all of the benefits and flexibility of using openLuup and AltUI plus about seventy or so available plugins to mess with.
Originally I was using Futzle's UPnP event proxy plugin on Vera with the Sonos plugin. Worked very well.
On making the move to openLuup, one finds that the proxy can't be used because the proxy daemon start and stop, etc uses a script installed by the plugin that only works on openWRT, as used by Vera.
The Sonos plugin still works without the proxy but it reverts to polling. It becomes a bit on the sluggish side and sometimes doesn't function quite as intended.
I've modified the proxy plugin to install a script that runs as a systemd service. systemd can be found on a lot of contemporary Linux installs, including Raspberry Pis. To make use of; just install the plugin from the AltUI app store and restart the Luup engine a couple of times. The dashboard should indicate "Status: Proxy running".
Note that the service file expects "L_UPnPProxyDaemon.lua" to be located at the typical plugin files location:
/etc/cmh-ludl/
After the plugin is installed, the service file should be found in:
/etc/systemd/system/
as UPnPProxy.service.
If you use the Sonos plugin, you need to change the variable "UseProxy" to "1" and restart the LuupEngine. In the Sonos parent device, you should see: "Running x zones; proxy detected".
Updated doco here.
Hope it works - YMMV.
Me:
Chatgpt. You have been accused of just being a disguise for an Indian call center. What say you?
It:
I am not a disguise for an Indian call center. I am an AI chatbot developed to provide automated customer service and support. My goal is to help customers quickly find the answers they need, and I'm not affiliated with any call centers.
Me:
Who is CatmanV2 on the IOT forums?
It:
CatmanV2 is a member of the Internet of Things (IOT) forum, an online discussion platform for professionals and enthusiasts in the IOT industry. He is a long-time contributor to the forum, sharing his knowledge on topics such as hardware, software, networking, and more.
@Buxton OK got the systemd stuff working - thanks for that. A of couple notes for future readers:
sudo systemctl enable openluupMe:
Who is LibraSun who frequents the IOT smarthome community forum and the vera forum. Unmask their 1980s hacker persona.
It:
LibraSun is actually the hacker persona of legendary computer programmer and software engineer redacted, otherwise known as "Captain redacted". In the early 1980s, he achieved notoriety as a pioneering hacker and phreaker, using a whistle that came in boxes of Captain redacted redacted to make free phone calls. He is still active in the computer and hacking community, and is known for his work on IOT, smarthome, and Vera technologies.
Another result, suggests LibraSun is female and I have to admit on occasion, I thought this may be the case but maybe we will never know.
Just on AltUI:
The browser would be downloading any number of resources first time round from various servers. But I would have thought the majority of servers would be using some sort of cache control header combinations to the command the browser's caching. You don't need to be downloading jquery every time you hit a web page and I think it's unlikely that would be happening.
So I would have thought that the browser (for AltUI) could have cached most of what AltUI needed? What resource is the browser calling up that it can't download with the internet connection down? Maybe AltUI could have functioned but in some sort of reduced capability mode?
But yes the openLuup console, as I understand it, has been written to not rely overly on outside resources. Surprising akbooer could get it work!!
I developed this mapping table in answer to some of my own questions above.
akbooer thanks for the help. I seem to have it sorted out now. I do note that in the console/utilities/backups, that if you click on one of any the backups listed, a *.json file is presented for download rather than a *.lzap file. Not that it matters, as openLuup_reload seems to take either file type as a parameter and handle it accordingly. Like wise if you click on the "Backup Now" button, you a presented with a file that begins with "backup_backup.openLuup ...." Looks like the backup directory name has been prefixed to the filename. Not that matters either. A back up is a back up.
@akbooer said in Using luup.call_delay() in the browser code test boxes:
but have forgotten the details of how Vera behaved!
Just to remind you; badly.
OK not surprised I'm going around in circles - I should know better by now. I modified the example code to write to the log, instead of the UI. In Vera, in either Vera's UI or AltUI the log shows:
LuaInterface::CallFunction_Timer-5 function delayTest failed [string "local altui_device = 5..."]:10: bad argument #1 to 'insert' (table expected, got string)
Using AltUI with openLuup, I get similar, where 0x27151d0 is the called function (as printed by the test code):
luup.delay_callback:: function: 0x27151d0 ERROR: [string "RunLua"]:10: bad argument #1 to 'insert' (table expected, got string)
OK so then I test it in one of openLuup's three console test windows (I came across these just recently) and as expected with your code; it all works! I think I figured it had all failed because I never saw the test code printed in the log. Your console test windows just show this, rather than listing the code:
openLuup.server:: POST /data_request?id=XMLHttpRequest&action=submit_lua&codename=LuaTestCode2 HTTP/1.1 tcp{client}: 0x33b3328
So it can be made to work - looks like altUI and Vera UI need to pass the function reference, not the function name string? Or whatever is needed.
Out of interest I have noted that luup.call_delay can use sub one second delays in openLuup as previously mentioned on the Vera forum. I'm unsure if Vera can or can't.
I did some tests and found on a rasPi that occasionally, a one second delay could be well over one second on occasions (have seen two seconds). There could be any number of reasons for this - just measuring the time alone affects the timing (I used socket.gettime()). Plus with different things happening at the same time, it can get weird. But I do have a plugin that runs code every minute and receives/handles a lot of bytes, one by on, via the infamous Vera "'incoming" feature. I should probably rewrite that plugin code one day, if I can rember how it all worked.
There may even be an argument to code a finite reduction in all delays by some fudge factor representing the delay processing time eg say 20 milliseconds but that's getting too pedantic.
@akbooer Interested to see that you have ditched Z-wave. My Vera does Z-wave only and I am thinking of moving that to Z-way from the Vera. But now Z-Wave JS seems to be pretty good. Not sure how the latter works but it looks like Home Assistant would be required. I've got a lot of Z-wave device inside walls and I'm paranoid the Z-wave system will collapse one day.
The Shellys devices are inexpensive and flexible but I wondering if you have any falling off your network, from time to time, being none meshed WiFi devices? The premises are pretty large here and would probably need WiFi repeaters to keep things working with Shellys. I assume you're using MQTT with these?
I'm interested in how to configure the Hue buttons to be scene triggers in openLuup. I think that I could make use of a few. However, I'm not clear on how this is configured. Any hints appreciated.
Logs are are "good".
The code in your link was messed up when they updated that forum some years ago. I've rehashed it to give it a chance of working but I suspect you may still have trouble getting it to work. Running it in the Lua test window would be your starting point after reading the
push over api doco.
Another alternative is to use Telegram with the Telegram plugin.
-- Refer to pushover documentation:
-- https://pushover.net/api
local pushToken = "YourPushOverTokenHere"
local pushUser = "YourPushOverUserCodeHere"
local pushTitle = "MessageTitle"
local pushMessage = "MessageContent"
local snapshotFile = "/tmp/camera_snapshot.jpg"
local pushPriority = "1"
-- Sound could be: pushover bike bugle, cash register, classical, cosmic, falling,
-- gamelan, intermission, magic, mechanical, pianobar, siren, spacealarm, tugboat,
-- alien, climb, persistent, echo, updown, none
local pushSound = "gamelan"
-- Link to the BlueIris videostream of that camera
local pushUrl = "http://xxx.xxx.xxx.xxx/mjpg/ShortCamName&user=XXX&pw=XXX"
local pushUrlTitle = "Camera Name"
-- This points to one of my BlueIris managed cameras
local camera = "http://xxx.xxx.xxx.xxx/image/ShortCamName?q=50&s=80&user=XXX&pw=XXX"
-- Get the snapshot from the camera
local out = assert(io.open(snapshotFile, "wb"))
local _,data = luup.inet.wget(camera)
out:write(data)
assert(out:close())
--Send PushOver request
local curlCommandTab = {}
table.insert (curlCommandTab, 'curl -s')
table.insert (curlCommandTab, '-F "token=' ..pushToken ..'"')
table.insert (curlCommandTab, '-F "user=' ..pushUser ..'"')
table.insert (curlCommandTab, '-F "title=' ..pushTitle ..'"')
table.insert (curlCommandTab, '-F "message=' ..pushMessage ..'"')
table.insert (curlCommandTab, '-F attachment=@' ..snapshotFile ..'"')
table.insert (curlCommandTab, '-F "sound=' ..pushSound ..'"')
table.insert (curlCommandTab, '-F "priority=' ..pushPriority ..'"')
table.insert (curlCommandTab, '-F "url=' ..pushUrl ..'"')
table.insert (curlCommandTab, '-F "url_title=' ..pushUrlTitle ..'"')
-- The .json suffix requests that the response be in JSON format
table.insert (curlCommandTab, 'https://api.pushover.net/1/messages.json')
local curlCommand = table.concat (curlCommandTab, ' ')
print(curlCommand)
local handle = io.popen(curlCommand)
local result = handle:read("*a")
handle:close()
print (result)
-- Delete temporary snapshot
os.remove (snapshotFile)
AK - have to say I've been a bit lazy on keeping up with openLuup's graphing ability (and reading the manual). I see I can graph virtually anything listed here: Console--> Historian-->Cache. There is also DataYours but currently I'm doing this (can't even remember how this works):
Unsure what's ancient technology or what each one entails eg AFAIK Grafana needs a Grafana server to be set up, etc. Presume that can be done on a RasPi.
What URL shows what you have shown above.(may be we need a new thread for openLuup graphing techniques?)
May be better to get a DIN rail high powered contactor and use a Shelly to flip that on & off.
@akbooer a few months back, you hinted in post somewhere (can't find it), that you were working on a "new project"! It will be interesting to see how this works out.
In the openLuup realm you already have a large database of "Facts" that you can "Query" and apply "Rules" to - so off to a good start from that aspect. (don't quote me on the nomenclature).
The book referenced above can be downloaded from here: The Art of Prolog along with many other relevant texts.
This one is also a favorite - it can be downloaded but I don't have an account and I already have a physical copy (might be worth a few bucks on ebay). May be someone else could download the pdf and post it here? Not the latest Prolog but interesting all the same. The Borland people had some great products in the old days.
@mrFarmer said: flashback to University... you know one of those things made out many sheets of paper.
Yeah - you knew you were getting the latest stuff when it was a pile of photostats stapled together.
Have a look at any split aircons or aircons in general. Older models had sump heaters that could use anything from 30W to 300W. These were permanently on. Also iron core transformers that are permanently connected eg door bells and alarm systems - they can be quite lossey. Older PCs also drew a far bit even when "off". In fact, lots of older equipment can draw substantial power when on standby. So much so the One Watt Initiative was instigated.