-
I was just going to add my support for a Update Button for the bare bones version of MSR and find the thread has been removed.
I'm wondering what was so provocative that required it's removal?
Have we become as paranoid as an owner of another forum?Anyway +1 for an Update Button.
-
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?
Thanks
-
Sigma have released a new Z-Wave Product that may be or interest to some here.
ThunderBoard Z-wave development board.More details are here....ThunderBoard
Also Dr Z-Waves blog link text
Makes for interesting reading.
It's attractively priced at $64.95 and might be a Z-UNO alternative? -
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 RAMBestel de nieuwe Raspberry Pi 4 B 2GB nu snel en voordelig bij Elektronicavoorjou.nl! - Raspberry Pi Boards, Behuizingen, Heatsinks, Accessoires & meer!
-
Is the Smarthome company still existent? If so, are SwitchLinc switched still available?
UNSOLVED Help please with Node-Red "Lost connection to server"
-
Node-Red on my Linux Debian box seems to be having issues now. It keeps saying repeatedly "Lost connection to server, reconnecting..." in the web browser.
I recently updated nodejs for MSR, I wonder if that might be related:
"Bump recommended nodejs version to 16.13.0; versions 14 and 15 will continue to be supported through March 31, 2022"
Nodejs version = v16.13.1
I have tried updating Node-Red that is now version v2.1.4
I also updated npm to version v8.2.0
I am not sure how or where to look at the log file for node red?
This is the contents of the nodered.service file in this directory:
/etc/systemd/system/multi-user.target.wants# systemd service file to start Node-RED [Unit] Description=Node-RED graphical event wiring tool Wants=network.target Documentation=http://nodered.org/docs/hardware/raspberrypi.html [Service] Type=simple # Run as normal pi user - change to the user name you wish to run Node-RED as User=stuart Group=stuart WorkingDirectory=/home/stuart Environment="NODE_OPTIONS=--max_old_space_size=1024" # uncomment and edit next line if you need an http proxy #Environment="HTTP_PROXY=my.httpproxy.server.address" # uncomment the next line for a more verbose log output #Environment="NODE_RED_OPTIONS=-v" # uncomment next line if you need to wait for time sync before starting #ExecStartPre=/bin/bash -c '/bin/journalctl -b -u systemd-timesyncd | /bin/grep -q "systemd-timesyncd.* Synchronized to time server"' ExecStart=/usr/bin/env node-red-pi $NODE_OPTIONS $NODE_RED_OPTIONS #ExecStart=/usr/bin/env node $NODE_OPTIONS red.js $NODE_RED_OPTIONS # Use SIGINT to stop KillSignal=SIGINT # Auto restart on crash Restart=on-failure RestartSec=20 # Tag things in the log SyslogIdentifier=Node-RED #StandardOutput=syslog [Install] WantedBy=multi-user.targetThanks
-
sudo journalctl -f -u nodered -o cat
#4 Dec 15:52:58 - [error] [tuya-smart-device:Star Light] Error: Error from socket: connect EHOSTUNREACH 192.168.0.119:6668 4 Dec 15:52:58 - [red] Uncaught Exception: 4 Dec 15:52:58 - [error] Error: connect EHOSTUNREACH 192.168.0.119:6668 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16) nodered.service: Main process exited, code=exited, status=1/FAILURE nodered.service: Failed with result 'exit-code'. nodered.service: Service RestartSec=20s expired, scheduling restart. nodered.service: Scheduled restart job, restart counter is at 37. Stopped Node-RED graphical event wiring tool. Started Node-RED graphical event wiring tool. 4 Dec 15:53:20 - [info] Welcome to Node-RED =================== 4 Dec 15:53:20 - [info] Node-RED version: v2.1.4 4 Dec 15:53:20 - [info] Node.js version: v16.13.1 4 Dec 15:53:20 - [info] Linux 4.19.0-18-amd64 x64 LE 4 Dec 15:53:21 - [info] Loading palette nodes 4 Dec 15:53:28 - [info] Settings file : /home/stuart/.node-red/settings.js 4 Dec 15:53:28 - [info] Context store : 'default' [module=memory] 4 Dec 15:53:28 - [info] User directory : /home/stuart/.node-red 4 Dec 15:53:28 - [warn] Projects disabled : editorTheme.projects.enabled=false 4 Dec 15:53:28 - [warn] Flows file name not set. Generating name using hostname. 4 Dec 15:53:28 - [info] Flows file : /home/stuart/.node-red/flows_HP-Thin01.json 4 Dec 15:53:28 - [info] Server now running at http://127.0.0.1:1880/ 4 Dec 15:53:28 - [warn] --------------------------------------------------------------------- Your flow credentials file is encrypted using a system-generated key. If the system-generated key is lost for any reason, your credentials file will not be recoverable, you will have to delete it and re-enter your credentials. You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change. --------------------------------------------------------------------- 4 Dec 15:53:28 - [info] Starting flows 4 Dec 15:53:29 - [info] [tuya-smart-device:Star Light] Recieved the config {"id":"b2799abf.81c1a8","type":"tuya-smart-device","z":"7bd8e249.bbb27c","deviceName":"Star Light","deviceId":"bf62864a9977909c10zuey","deviceKey":"7904f95d6d266841","deviceIp":"192.168.0.119","retryTimeout":"1000","findTimeout":"1000","tuyaVersion":"3.1","eventMode":"event-both","x":880,"y":180,"wires":[["f6422200.35ec7"]]} 4 Dec 15:53:29 - [info] [tuya-smart-device:Star Light] Event subscription : shouldSubscribeData=>true , shouldSubscribeRefreshData=>true 4 Dec 15:53:29 - [info] [tuya-smart-device:Star Light] Connecting to Tuya with params {"id":"bf62864a9977909c10zuey","key":"7904f95d6d266841","ip":"192.168.0.119","issueGetOnConnect":false,"nullPayloadOnJSONError":false,"version":"3.1"} , findTimeout : 1000 , retryTimeout: 1000 4 Dec 15:53:29 - [info] [tuya-smart-device:Star Light] Recieved the config {"id":"d9079dc4.b93c3","type":"tuya-smart-device","z":"7bd8e249.bbb27c","deviceName":"Star Light","deviceId":"bf62864a9977909c10zuey","deviceKey":"7904f95d6d266841","deviceIp":"192.168.0.119","retryTimeout":"1000","findTimeout":"1000","tuyaVersion":"3.1","eventMode":"event-both","x":320,"y":420,"wires":[["2b35a684.a57a9a","8ed8ece1.387ca"]]} 4 Dec 15:53:29 - [info] [tuya-smart-device:Star Light] Event subscription : shouldSubscribeData=>true , shouldSubscribeRefreshData=>true 4 Dec 15:53:29 - [info] [tuya-smart-device:Star Light] Connecting to Tuya with params {"id":"bf62864a9977909c10zuey","key":"7904f95d6d266841","ip":"192.168.0.119","issueGetOnConnect":false,"nullPayloadOnJSONError":false,"version":"3.1"} , findTimeout : 1000 , retryTimeout: 1000 4 Dec 15:53:29 - [info] Started flows 4 Dec 15:53:30 - [info] [tuya-smart-device:Star Light] initiating the find command 4 Dec 15:53:30 - [info] [tuya-smart-device:Star Light] initiating the find command 4 Dec 15:53:33 - [error] [tuya-smart-device:Star Light] Error: Error from socket: connect EHOSTUNREACH 192.168.0.119:6668 4 Dec 15:53:33 - [red] Uncaught Exception: 4 Dec 15:53:33 - [error] Error: connect EHOSTUNREACH 192.168.0.119:6668 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16) nodered.service: Main process exited, code=exited, status=1/FAILURE nodered.service: Failed with result 'exit-code'.192.168.0.119 is a Tuya WIFI lamp that I had powered off.
I can't seem to update any of these nodes, it doesn't seem to do anything when I try.
-
I've now powered that Tuya light back ON again so it is reachable on the WLAN and now I am able to update the nodes OK and then I rebooted the Linux box. Now the "Lost connection to server, reconnecting..." message has stopped appearing. So seems related to this Tuya node / light.
I then powered OFF the Tuya light again and fingers crossed the "Lost connection to server, reconnecting..." message still hasn't come back, so I think managing to update the Tuya node may have fixed it. I will keep an eye on it.