So, I think I'm in a bit of an unusual situation. I work at a camp & retreat center that has wifi throughout. I want to put a few switches in the office that can control outdoor lighting throughout the camp. We currently have switches in each of the buildings, but it is a particularly frustrating job to get all the lights on in the evening when it is brutally cold out or we are short staffed.
Most of our staff is not very tech savvy (my boss literally has his wife print out his emails for him each day!!!) so, I'd love to avoid having to set up any sort of raspberry pi or new phone app.
Is there type of 3-way switch that can connect to the wifi, turn on a light in another building AND turn on an indicator light in the office, without having any sort of wire running between the buildings? Hopefully looking for a simple solution without breaking the bank too.
I greatly appreciate any input that you can give. Thank you!
I have a X10 wall switch system and I want to get rid of it. What would be the easiest transition to something more modern and easy to use with either wifi/homekit capabilities? My current X10 controls 3 zones in my bedroom. All zones are dimmable.
Zone 1 is 4 canister ceiling lights. LED bulbs
Zone 2 is 1 canister ceiling lights. Halogen Bulb
Zone 3 is 1 canister ceiling lights. Halogen Bulb
I have an old plug-in remote from Radio Shack and a wall switch with 3 buttons, each controlling one zone. (images attached)
My wall switch has one two wires from the wall. One black, one white.
Is there any solution easy to install without the need of an electrician? Thanks for any feedback.
Good morning all,
I'm working on weaning myself off of being totally Vera dependent. I've installed MSR on my Fedora home server, and I've been migrating luup Reactor rules over little by little. My hope is to use Vera as a bare bones z-wave hub, until I replace it either with Ezlo (not so sure about), or perhaps Hubitat. I'm just tired of zero new development in Vera, empty promises of native device integration, and cloud services that go down and leave my automation hanging.
In any case, I digress. I've attempted to use Gcal3 on Vera to integrate Public calendars, such as Federal Holidays, School Calendars, etc. It use to somewhat work, but more often than not, all I get from Gcal3 is "token error code: HTTP/1.1 400 Bad Request". The developer no longer is active, and it's effectively not working anymore.
I'd like to use these public calendars as Entity Attributes or Constraints in MSR. For instance, if it's a Federal Holiday, I don't have to work, and I may want to sleep in, which means lights may not come on as early, window coverings in the bedrooms may open later in the day, etc. Similar idea with a school calendar. If "closed" is in the event, my daughter may want to sleep in, and not want the window coverings opened as early.
I'm aware that Ezlo has integration through NuCal to all sorts of web based services, including Google Calendar, but as I stated earlier, I'm undecided on going down that path. Is there anyway to do this on MSR through any of it's abilities, such as HTTP calls or MQTT ( not experienced in MQTT, so I don't know now it works really).
Has anybody already done this?
Thanks for any advice in advance.
Hello all, I am finally ditching my Vera and moving to HA using a Zooz ZST10 Z wave stick. I have around 50 Z wave devices with a good mix of battery devices, locks, sensors and switches. The plan is to include all the AC powered devices first, starting from the ones closest to my Z wave stick then moving outwards. Once that is complete I will go back and include all battery powered devices in the same fashion.
My question is there any quick way to exclude all my Z wave devices from Vera, or should I just delete all devices without excluding them and factory reset each device before pairing to HA?
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)?
The Debian Linux machine that MSR is running on, has developed an issue and I can no longer login to it via SSH or directly on its terminal.
It was fine earlier this morning I connected to it via WinSCP to copy all the MSR files down for a backup to my laptop.
Then a bit later I could no longer connect to it. Either in WinSCP or Putty SSH, it now says access denied, even though my password is correct.
I then connected a monitor and keyboard up to the Debian box and I cannot login to it directly either, I put in the username and hit enter and I am not given a password prompt to enter it and something I could not read flashes up on the screen very fast and then disappears. I had to record a video and skip through it to capture what is says, see screen capture below.
I tried logging in as user root and my own username same thing happens, it does not even give me a prompt to enter a password.
If I boot the box in to Debian recovery mode instead I am able to login as the root user OK.
Any ideas how to fix this?
Two stores apparently have inventory of RPI 4Bs with 2GB RAM. Get them while they last!Raspberry Pi 4 model B - 2GB - RaspberryStore interadmin12 / 62.95 EUR Raspberry Pi 4 Model B 2GB RAM Raspberry Pi 4 Model B 2GB RAM
Bestel de nieuwe Raspberry Pi 4 B 2GB nu snel en voordelig bij Elektronicavoorjou.nl! - Raspberry Pi Boards, Behuizingen, Heatsinks, Accessoires & meer!
Status Board - What’s your HA Information Dashboard ?
parkerc last edited by parkerc
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..***
parkerc last edited by
I should add - I’ve personally have been using Node-Red’s Dashboard and found it to be pretty good..
rafale77 last edited by
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..
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.
Black Cat last edited by
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..
therealdb last edited by
@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.
toggledbits last edited by
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
Black Cat last edited by
I've also rolled my own. It will be included for optional use with the new multi-system Reactor.
Missed this.......tell us more.......
toggledbits last edited by
@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.