-
Some of you may know that I took at shot at building an alternate geofencing solution for Vera. The core of it was system agnostic, using the OwnTracks application and AWS lambdas to track devices and keep a central data, then disseminate that to the Vera via a websocket-based plugin. It worked with other apps as well, including Tasker and GPSLogger, but of the dozen people that were testing it, most used OwnTracks.
A lot was learned in the process, not the least of which is that the success of any such solution is highly dependent on the phone and its settings. Phone manufacturers love to set things up for the longest battery life, of course, but that's usually very anti-geofencing behavior. In the case of at least one brand, it was unusable and the settings could not be modified. It was also cost-prohibitive to maintain on Amazon, as AWS grabs a dime here and a dollar there and before you know it, it added $100/month to my AWS bill, which my wife deducted from my Scotch budget. Unacceptable.
But it's quite reasonable to use OwnTracks to a local endpoint, and I could pretty easily replicate the functionality as a local application, or maybe even as an additional endpoint built into MSR's API (still separate port and process, but in the package).
So the question really is... would you do it, or would you be too concerned about the security risks associated (e.g., dynamic DNS and NAT mapping in the firewall necessary for the phone to contact the service when not on LAN)?
-
Installed Sitesensor yesterday. Defined a http request towards yr.no for the weather.
Default it only sends requests when the device is armed. When I armed the sensor both of my sirens started bleeping. Not funny with at night with two kids asleep.Simultaneous with arming the device, the first http request probably is send and my first http request did not have the Useragent http header so the result was a 403; this probably made the sitesensor device being triggered.
I unchecked the box "only send requests when armed" and disarmed the sitesensor. This works ok but only one slight mistake with thick fingers and I have armed it again.
I see the sitesensor device is being configured as a SecuritySensor (as it implements the securitysensor serivce?). This makes that sirens react when the sitesensor trips. I have a leakage sensor as well and I know this one triggers the sirens as well. Do not have any doorsensors right now but hope these will not trigger sirens as well.
Is there a way to tell Sirens to ignore Sitesensor and/or other specific devices. Or should sitesensor not be configured as a security device?
Is there an easy solution?Grtz Swiddy
Some details:
-Vera Secure box with built in siren (siren is a separate device)
-POPP Smokedetector with siren
-Upto-date with Vera firmware and Not on Openluup yet but don't think this would make a difference here -
Yet another attempt to create the one standard to rule them all. "The ring of power".
What Is “Project Connected Home Over IP” for Smart Homes? What Is “Project Connected Home Over IP” for Smart Homes?Project Connected Home over IP is a new industry group announced by Apple, Google, Amazon, and the ZigBee Alliance. The group will create a new unifying standard for smart home devices, and that’s a big deal. Here’s why.
I am very skeptical about this. I don't feel it is needed and I think it will only add to the confusion but I am probably not a typical consumer. Thoughts? It seems to want to do the same thing as what a lot of us have already achieved through open source but commercializing it. It's not so different from Apple's HomeKit.
-
Evening (at least here)
2021-02-12 18:05:02.869 luup_log:0: ALTUI: runLua(local GardenTemp = math.floor(0.5+luup.variable_get("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature", 20415)) luup.call_action("urn:dlna-org:serviceId:DLNAMediaController1", "Say", {Text="The temperature outside is" ..GardenTemp.. "degrees.",Volume=40,GroupZones="Everywhere"}, 22)) 2021-02-12 18:05:02.870 luup.call_action:: 22.urn:dlna-org:serviceId:DLNAMediaController1.Say 2021-02-12 18:05:02.870 luup_log:22: VeraAlexa: addToQueue: added to queue for 22 2021-02-12 18:05:04.035 luup_log:0: ALTUI: Evaluation of lua code returned: nil
Alexa TTS has suddenly stopped here (mid afternoon)
Normally I'd replace the cookie.
When I went to the domain, I was forced to change my password. Did that and exported the cookie. But still no voice.
I can't see anything at all in the logs:But I'm sure I need to look somewhere else and damned if I can recall where. Someone give me a pointer?
TIA
C
-
Hi all. Well winter is coming and temperatures are below freezing. I currently have this snippet of Lua:
local GardenTemp = math.floor(0.5+luup.variable_get("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature", 20415)) luup.call_action("urn:dlna-org:serviceId:DLNAMediaController1", "Say", {Text="The temperature outside is" ..GardenTemp.. "degrees.",Volume=40,GroupZones="Everywhere"}, 22)When we turn the house on. Anyone help me to get it to say 'negative' or 'minus' when the temperature is actually sub-zero?
TIA
C
-
I've only recently read that ZLR is not a mesh network, below is quoted from Dr Zwave, which I found interesting and opens up a range of questions. I had assumed that ZLR was similar to ZWP, but it isn't.
Z-Wave Long Range supports FLiRS types of devices but it doesn't support Associations. Z-Wave Long Range is a star network so all communication has to go thru the hub. Then the hub forwards the message on to the FLiRS device after Beaming to wake it up. There is no way for a Long Range end device to send a frame to another end device, it has to go thru the controller.
I found it interesting that Associations have been given the 'flick'
My question is regarding the compatibility of ZWP & ZLR in the same network.
From my understanding ZLR devices can't communicate directly with ZWP devices, this could get interesting as it seems to indicate that there is no backward compatibility.
Perhaps Z-Wave has abandoned Mesh networks and is working towards simpler systems?
Any thoughts? -
Hi,
I hope this is the correct place to ask. I wanted to start with developing smart home systems where I use a raspberry pie as a server and communicate through a phone or tablet.
But I do not know where to and how to start, I have knowledge in developing Web Application, Java and a bit react native.But which Development Language is good for smart home development? Would it be possible to achieve smart home projects with Webapplication and smarthphone app if they communicate with the same server?
Which additional knowledge do I need except development language? I looked on the internet a bit, but kinda got lost with all the information in it right now about smart home.
-
Hi
Go with me here... I recently pick up a unresponsive Vera Secure from eBay for next to nothing, thinking I’d could have a go at trying to restore it, if only as a play thing..
Situation - The power led comes on, but the internet and service leds just flash - no connection made (and even using a direct cable and Wireshark, I can’t see an arp request being made to see if it has a default in address) - I’ve also tried various reset button combinations - no luck.
Perhaps this post is a long shot, but seeing so many familiar ex Micasaverde/Vera forum names - i thought I’d at least ask - just in case anyone had any guidance/advice etc. I could use ..
-
Hi!
I was tipped off about this forum while bitching about my Vera on the Vera forum, as I had grown accustomed to over the years. I know that's not very nice, but that thing brings out the worst in me (and has even driven me to drink on occasions 😉 )!
Anyway, how about a little intro in case anyone is actually interested? I did odd jobs, saved up for and built my first PC from components by the time I was 15 (back when you had to know how to get around a DOS prompt and a 120Mb hard drive was a big deal). Within 6 months I had my own BBS up and running. The internet wasn't really a thing back then -- did AOL really count? I only really discovered home automation almost a decade later, again before it had really taken off. Back then I was using X10 because it was still one of the only consumer options and I had no electronics background. Over the years I have experimented with several home automation technologies, 90% of them ending up as useless scrap and a waste of money. Today I feel like not much has changed, but things are moving in the right direction (wide scale adoption -> more money invested in improving tech to try to get us to part with our money, am I right?). I've never really had the funds to go all out or to get the more expensive gear, but I've found some products that have been worth sticking with -- namely my Elk-M1G and one or two other obscure devices. I recently was "renovicted" during the pandemic and decided to move from my modest apartment in the city to a house out in the woods in the middle of nowhere.
So here I am, with an almost clean slate, looking to set this place up better than ever. The internet access sucks out here, but the house is mine to do what I will with it. I envision a keyless entry system even better than the last one I devised, walls that literally talk and eventually even roboticized structure & furniture (eg. Aquarium lids that rise for maintenance, hidden doors that slide open, a table that transforms into a bar, etc.).
For the moment, though, I'd like to figure out how to replace this *&$%ing Vera. Funds have been tight lately, but at the moment I have several pieces of hardware I can start with: The Elk (as mentioned), ~20 LIFX bulbs/strips, a handful of Amazon Echos, a few Zwave devices, some IR and audio stuff, the Vera, a few other odds and ends.
Ultimately, I'd like to set up a low-power system like a NUC or something that will always be on, running automation as well as handling audio (most likely multi-zoned). I built my last PC as a gaming PC, but I can use it to experiment until I'm ready to purchase an HA system.
Where do I start if I want to learn about OpenLuup? I skimmed through the forums, but they seem quite advanced and are a little beyond my abilities. I do CAD/CAM, not programming, unfortunately!
Thanks!! -
654a0b44-6cec-4466-8701-3566067abbd0-image.jpeg https://www.google.co.uk/url?sa=i&url=https%3A%2F%2Fpanic.com%2Fblog%2Fpanic-status-board-2013-edition%2F&psig=AOvVaw1ERsyah34ZkmLnpWaYLgu-&ust=1600418906446000&source=images&cd=vfe&ved=0CAIQjRxqFwoTCODol5Xn7-sCFQAAAAAdAAAAABAE
I’ve always liked the idea of having a screen, located somewhere in the house that would allow me to see the status of pretty much everything. (Hardware wise I’m just think of a basic Rasp Pi, fixed to a vesa mount, screwed to the back of an old monitor screen)
I’ve tried a number of tools/apps over the years, one of which was PanicBoard (where the above image comes from) - which seemed to have some potential, but the owners stopped developing/investing in that a while back.
What are people using ?
Is there something, perhaps a single tool/app that this community would collectively support/promote, one that no matter what HA you used, you could submit information to and have it displayed ?
**** Just to be clear, I’m referring to status/information boards, not a touch based, control board where you can turn things on/off etc..***
-
-
Not sure this is in quite the right place (again) but I have a device that exists in z-way that I simply cannot remove. It seems to be a zombie. I have no idea what it was.
It claims to be a routing binary sensor that has not woken up since August
I go through the 'Only do this if your device is broken' and it simply will not go.
Any ideas (apart from ignore it)?Cheers
C
-
Hi all
Possibly a long shot - but does anyone know of a way, (maybe you have some code or know of an app) that can help you discover the IR codes of a device when you’ve lost the remote?
Looking online there seems to be a growing number of IR banks, yet I can’t find anything on the market that could cycle through a huge set of different codes (e.g just the power on/off) to let me know which ones are compatible ?
When you consider so many things these days are made in the same place, and often thing can just be re/badges versions of other items - it’s likely that a sets of codes for one branded product will work in the most part with another ..
-
Since one member asked at one point about the "front end" and "back end", I drew this showing the controller from the base to the tip along with what I have found to be the best options from my testing. Almost every controller will try to integrate all elements, especially commercial ones but... they all have strengths and weaknesses so if one can have a medley of the best ones...
-
Hi all. Looking for some guidance as ever
This
luup.inet.wget('https://api.telegram.org/bot1225075966:AAHS5rwhCpOx0hwq3mOnNjtCSKiDeAS6B4/sendMessage?chat_id=@Coalport58&text=House mode is home')Works fine
This
luup.inet.wget('https://api.telegram.org/bot1225075966:AAHS5rwhCpOx0hwq3mOnNjtCSKiDeAS6B4/sendMessage?chat_id=@Coalport58&text=House mode is Home')Throws a 400 error:
openLuup.client:: WGET error status: 400I have munged the bot key to post here, but just changing the 'h' to 'H' breaks it. Any ideas why?
C
-
We are a smart home startup based in England, we are looking for a co-founder/advisor who is good at iot software development.
Many thanks -
-
Is there one? I know TTS is working but suddenly woke up at 0300....
...or does it just use Vera. That seems unlikely from what I know of the architectureTIA
C
Status Board - What’s your HA Information Dashboard ?
-
https://www.google.co.uk/url?sa=i&url=https%3A%2F%2Fpanic.com%2Fblog%2Fpanic-status-board-2013-edition%2F&psig=AOvVaw1ERsyah34ZkmLnpWaYLgu-&ust=1600418906446000&source=images&cd=vfe&ved=0CAIQjRxqFwoTCODol5Xn7-sCFQAAAAAdAAAAABAE
I’ve always liked the idea of having a screen, located somewhere in the house that would allow me to see the status of pretty much everything. (Hardware wise I’m just think of a basic Rasp Pi, fixed to a vesa mount, screwed to the back of an old monitor screen)
I’ve tried a number of tools/apps over the years, one of which was PanicBoard (where the above image comes from) - which seemed to have some potential, but the owners stopped developing/investing in that a while back.
What are people using ?
Is there something, perhaps a single tool/app that this community would collectively support/promote, one that no matter what HA you used, you could submit information to and have it displayed ?
**** Just to be clear, I’m referring to status/information boards, not a touch based, control board where you can turn things on/off etc..***
-
I should add - I’ve personally have been using Node-Red’s Dashboard and found it to be pretty good..
-
-
I too am using grafana... not as fancy as AK's though.
-
...the nice thing about Grafana, is that it can pull data directly from openLuup's Data Historian, which uses an industry-standard API (Graphite.)
-
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?)
-
I'm planning on using Imperihome as long as i can.. this way i can have some controls as well, in addition to grafana graphs..
-
@a-lurker said in Status Board - What’s your HA Information Dashboard ?:
AFAIK Grafana needs a Grafana server to be set up, etc. Presume that can be done on a RasPi.
-
I run Grafana on a windows machine now. It works, but is a bit fiddly as it is at beta stage..
-
Does anyone here use an alternative to imperihome? the Imperihome bridge doesnt transfer all sensors for some reason.. motion sensors, light sensors, UV doesnt come over..
I want a status panel, but I want to be able to set i.e light schemes, open the garagedoor, etc from these panels.. (Old tab's and phones in 3d printed frames)
-
I've been looking at Home Remote, but it seems to need to connect to the vera servers for credentials, and I can't find another way to connect in openluup..
-
@perh Take a look at Homewave if you are on iOS. It works with Vera, both UI5 and UI7 and it also works for OpenLuup. You can have multiple controllers mapped seamlessly at the same time.
For Veras it works with cellular access, for OpenLuup you need a vpn to access the system when being off-site.//ArcherS
-
There is other visualisation software that will do what you want, but it comes with a high price tag...
Possibly the best professional system, IMHO is Eisbaur Scada (google is your friend), there are other professional systems available, it all comes down to price or user familiarity. -
Only one iOS device in the house, and its not mine!
I want this to go local communication only, I just use altUI (via dataplicity) when i'm not home.. This is mainly for some UI pads i plan to have around the house, all android..
-
@perh I ended with my own solution.
I searched a lot, but I couldn’t really find something ready. It’s obviously not generic, but I have thermostats, a/c, sensors and much more. It’s running on fully kiosk in fire tablets, that I control via mqtt/api, so I can display cams after motion events and much more.
-
I've also rolled my own. It will be included for optional use with the new multi-system Reactor.
-
Today I tried to use Fully Kiosk on an old Samsung tablet but the AltUI wouldn’t fully loaded. But it would load fine in the regular Chrome app
-
@toggledbits said in Status Board - What’s your HA Information Dashboard ?:
I've also rolled my own. It will be included for optional use with the new multi-system Reactor.
Missed this.......tell us more.......
-
@black-cat It's a skinnable tile interface that maps properties/capabilities to display controls (widgets). Each widget supports multiple canned layouts, and you can do custom layouts (either as per-device exceptions or globally-available). Widgets are tiled and moveable/sizeable. They are mapped to device properties and you can use expressions to fetch values, map values, etc. For example, the scene widget can be "active" based on the state of any device state or expression, not just the "active flag" on the scene itself--that is, a widget is not limited to sourcing data from one device/thing. So, for example, the thermostat widget can draw current temperature from an in-room multi-sensor, and on-off heating control by a plug-in switch, etc. Basically, instead of having to make a virtual device to collect data to a single object that is then displayed by a canned-appearance widget following rules particular to that device type, the widget just brings all the data together from whatever sources and displays it; actions work the same. If you want your thermostat in the bedroom to display the outdoor temperature in Moscow, you can do it. Easily. If you want a "binary sensor" widget to show tripped/alarm state when the pool pump is running after sunset, no problem. And you can do fun but sensible/expected things like when you activate a scene via a widget, the widget changes to the counter-scene (e.g. when you tap "Kitchen On" the lights come on and the widget then changes to "Kitchen Off"). Colors, fonts, sizes, etc. are all configurate/replaceable (CSS, HTML).
I've used and evolved this dashboard for years in my own home. It actually came into being first in 2017 when I made my first move away from Vera toward HomeAssistant (didn't happen, but that's another story). It was for family use, so right from the start, my idea was that nobody needs to know or care which controller is managing a device. Its hardware abstraction layer served as the launching point for a multi-system Reactor; I'll call it "MSR" here for brevity's sake. This MSR will work in a similar way: knowing the attributes and capabilities of a device, you can create rules using those, and rules that incorporate this data from multiple sources. That is, if your bedroom temperature is controlled by a space heater on a Tasmota-based relay board using control logic driven by input from a ZWay+openLuup-connected multi-sensor's temperature measurement, no problem. You configure any number of "controllers"; each instance announces what devices it has in inventory, and what attributes and capabilities they have. A controller can be an interface to Vera/openLuup, or Hass, or Hubitat, or just an HTTP-based element that fetches weather from OpenWeatherMap, or an interface to your EVL3/4-connect alarm panel, etc. It is an interface that simply says "these are the objects I have and this is what they know and do". So any device could be supported by a plugin in your Vera/openLuup/Hass/HE/other HA controller, or it could come from a dedicated controller crafted just for that device. For example, it currently supports Sonos through the Vera/openLuup plugin, but I (or someone) could write a dedicated Sonos controller that talks directly to the Sonos zones on the network and bypasses the plugin, maybe even uses their new API rather than UPnP. Controllers have a strictly defined behavior/contract, with the intention that others can develop controllers as well. This aspect is making MSR grow legs, a bit... it's really turning into a home automation controller all on its own. I foresee an ecosystem of available add-on controllers for every manner of device in future. This gives you the flexibility to determine what best supports the products you use; for example, if support for a particular Fibaro or Zooz device in Vera/eZLO is lacking/buggy (no--say it's not so!), you can instead include it on your openLuup+ZWay, Hass, or HE controller where the support is better, and MSR can find it there. But when creating your rules and activities, you don't have to know or care where that device lives. To the maximum extent possible, I am also keeping an architecture and implementation in which system objects (devices, groups, scenes, etc.) are entirely overridable and creatable through configuration. If you have a device type on Vera/openLuup that MSR doesn't natively support, you should be able to just go to configuration and say "this device type, or even this specific device, has these capabilities and these attributes". If a capability doesn't exist, you can create it locally immediately. Up and running in five minutes or less (modulo the first-time learning curve, of course). And for all of this, you should be able to contribute the configuration to the community if you wish (or find configurations/capabilities others have done and apply them). And of course, whatever to create/train is available both in the Reactor part and the Dashboard part.
I've focused mostly on the rules and reactions part of MSR for several weeks, and it lives and breathes now. Although algorithmically it shares ideas with Vera/openLuup Reactor, it is an entirely new code base (and not Lua). Huge strides have been made quickly, but of course, there are a lot of "TBD" comments in the code, and I'm sure no shortage of crashes in boundary conditions from things like unfinished input validation and so on. It needs combing out, some deep code reviews (which I prefer to do on paper), and backporting of some evolution of the evolved hardware abstraction to the Dashboard. There's plenty to do. But, with the freedom of creating the environment rather than working in someone else's, it's much faster and easier, and I'm really pleased with acceleration towards something usable over the last month. I'm about ready to cut over my own home's automations to it. There is nothing like the pressure of pleasing my "driving coach" to make sure I get things working well, and quickly.
-
@toggledbits Wow, sounds really exciting!
Today I use Homewave on my iPhone and on iPad, this sounds like the next step up towards a real dashboard.//ArcherS