-
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?
-
Hi! I want to install a smart lock on my front door, but I don't know which one to choose. There are many different models available on the market. Do you have a reliable model to recommend?
-
Hi
I’m looking to rework some code I found online so I can use it on Vera, and while I’ve managed to translate / convert a number of things, I’ve got stuck on a few things it does, around encryption/decryption etc.
All the original Lua code is here - > (https://forum.logicmachine.net/showthread.php?tid=232&pid=16580#pid16580 )
Plus there looks to be a python version too here - > (https://github.com/florianholzapfel/panasonic-viera/issues/9#issuecomment-476919658)
Here’s an extract of the code where AES 128 CBC is required?
function encrypt_soap_payload(data, key, hmac_key, iv) payload = '000000000000' n = #data payload = payload .. string.char(bit.band(bit.rshift(n, 24), 0xFF)) payload = payload .. string.char(bit.band(bit.rshift(n, 16), 0xFF)) payload = payload .. string.char(bit.band(bit.rshift(n, 8), 0xFF)) payload = payload .. string.char(bit.band(n, 0xFF)) payload = payload .. data aes_cbc, err = aes:new(key, nil, aes.cipher(128, 'cbc'), { iv = iv }, nil, 1) ciphertext = aes_cbc:encrypt(payload) sig = encdec.hmacsha256(ciphertext, hmac_key, true) encrypted_payload = encdec.base64enc(ciphertext .. sig) return encrypted_payload end function decrypt_soap_payload(data, key, hmac_key, iv) aes_cbc, err = aes:new(key, nil, aes.cipher(128, 'cbc'), { iv = iv }, nil, 0) decrypted = aes_cbc:decrypt(encdec.base64dec(data)) decrypted = string.gsub(string.sub(lmcore.strtohex(decrypted), 33), '%x%x', function(value) return string.char(tonumber(value, 16)) end) return decrypted endI can get to the point where I can create the parameters for the payload encrypt request (example below), it’s just the encryption/decryption I cant do..
data="1234" key="\\S„ßÍ}/Ìa5!" hmac_key="¹jz¹2¸F\r}òcžÎ„ 臧.ª˜¹=¤µæŸ" iv=" {¬£áæ‚2žâ3ÐÞË€ú "I’ve found this aes.lua (https://github.com/openresty/lua-resty-string/blob/master/lib/resty/aes.lua ) module online, but that requires loads of others modules too, most notably ffi.lua. Which I’d ideally like to avoid.
I also came across this aes128.lua (https://github.com/somesocks/lua-lockbox/blob/master/lockbox/cipher/aes128.lua ) but i’m not sure how that handles all the other parameters e.g specify the cbc aspect etc.
Finally there’s this aes256ecb.lua script (https://github.com/idiomic/Lua_AES/blob/master/AES.lua) , could that be converted to aes 128 cbc and then used in the above?
Any help/advice on this would be appreciated..
-
I just upgraded the firmware for the inverter for my solar panels and that made it possible to enable Modbus TCP.
At a glance that would be perfect for live production data fed into my home automation environment but my lack of knowledge about the protocol and how to put the data where I want it failed me.What I have:
MSR
openLuup
Vera Secure
Ezlo Plus
Mosquitto
Homebridge
Windows Server
Ubuntu Server
Quite decent PowerShell skills
Enough Lua knowledge to write my own functions and handlers
The inverters Modbus interface definitionsWhat I want to achive:
Something that can be run by systemd och anything else monitoring the status and keeping the Modbus connection alive.
Publish readings over MQTT or whatever fits my setup, the goal is to feed the data into openLuup in someway so Historian can log the data for Grafana and display current production to HomeKit (as a mqttthing light sensor, since there is no other accessory suitable at the moment).Anyone implemented Modbus TCP in similar projects or have any guidance on how to reach my goal?
Open for alternative solutions as well, all suggestions are appreciated!
-
Hi to all,
I am user of vera controller. I have a dahua door intercom with relay. Relay activates with username and password authentication. I can activate the relay http://admin:a1234567@192.168.1.111/cgi-bin/accessControl.cgi?action=openDoor&channel=1&UserID=101&Type=RemoteAs you can see intercom username admin and password is a1234567 I build a scene with luup code luup.inet.wget( "http://admin:a1234567@192.168.1.111/cgi-bin/accessControl.cgi?action=openDoor&channel=1&UserID=101&Type=Remote" ) But can not activate relay. Is there any idea?
-
Hi to all, I have a bricked vera secure that is replaced with new one. Old vera secure serial numbers are deleted from vera servers so I cannot use it. Vera secure's are orginally Sercomm's NA502 model devices. Recently I install openwrt to the old vera secure unit without problem. Is there any way to use it any automation system with internal z-wave. I install domoticz but I cannot setup internal z-wave unit, it only accept usb zwave radios. Is there any ideas?
-
I ordered a Fibaro Dimmer 2 and Bypass device for my upstairs landing / hallway lights.
I have 2 light switches one at the bottom of the stairs and another one upstairs on the landing.
But I am struggling to make sense of my current wiring, more details / photos on the Vera forum.
Jan 27 Anyone good at electrical wiring for light switches? Anyone good at electrical wiring for light switches?Hi I ordered a Fibaro Dimmer 2 and Bypass device for my upstairs landing / hallway lights. I have 2 light switches one at the bottom of the stairs and another one upstairs on the landing. I have no neutral wires in the house behind the light switches. These are photos of the light switch...
Thanks
-
Hello,
Looking to all the dev's and tinkerers on this community for ideas on how to implement a solution to my problem. Kind of a long intro, sorry.Problem statement:
I have a geothermal heat pump that has a loop that is slightly undersized. During the cold weather months in the Pacific Northwest (one or two months of the year), the loop can get below 32 degrees. If it goes on for a few days, it can generate significant frost heaving in my yard and under the flagstone deck, Actually fixing the issue is cost prohibitive.Current mitigation:
I have DS18B20 tied into Home Assistant and monitoring the temp of the fluid coming out of the loop and if it drops below 35 degrees, MSR triggers a Fibaro Implant to add a resister into the external temp circuit and fool the Venstar to think the outside temp is below 32 degrees and issue a Heat Pump lockout and switch to AUX heat. While this is working fine and the AUX heat is only coming on once or twice a day, I would like to simplify the setup so it runs on something other than HA and MSR. I think they are overkill for my issue. Also want this to be independent of anything else in the house so it can stay behind if I am not around to maintain.I only have two inputs and one output:
Inputs: Loop temp, Furnace running
Outputs: Switch relay to drop resistance to external thermostat connection on thermostat.
Logic is super simple:
If temp is below 36 degrees and furnace is running, turn on relay
If furnace stops, turn off relay.
I am sure even I can figure that out on Python.Trying to determine the best platform for a set it and forget it black box that works with as close to zero maintenance as possible.
Options I have thought of are:
Pi zero with a GPIO controlled relay ESPHome (Not very knowledgeable about that platform, but willing to explore) Arduino Anything anyone else suggestsAny ideas are appreciated.
-
Greetings,
I’m researching a migration from Vera+ to Hubitat C7 and want to know if anyone has successfully connected the Hubitat to the “HA Bridge” for local Alexia calls.
The HA Bridge does not callout Hubitat natively from what I see.Thanks for your assistance.
Z-Wave Plus (ZWP) & Z-Wave Long Range (ZLR)
-
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?aka Zedrally
-
This is quite confusing.... From this announcement, it is supposed to be backward compatible.
I note the Beaverton, OR location which is beyond local to me... it is a stone throw away from where I am.But then this article clearly states exactly what you spoke about.
Then the engineer in me starts frowning. The way I read this new spec is: range is increased by the RF TX power of the device. A major no-no. why? Because it means much more cross network interference, device detectability (security anyone) and less efficient air-time. It does have a dynamic PHY power to make up for this but I would still be very uncomfortable with it and the use cases for which this would be beneficial would be very limited (to be nice... most likely none). I can imagine an edge device from my neighbor having to beam at full power, overshadowing all my devices causing all kinds of disruptions. One main benefit of the mesh concept is that each device range is very limited and therefore will not interfere with others. Certainly extending the RF range of my devices by jacking up the PHY output power is not a anything I am looking for. If it was improving the RX sensitivity I would be all in.
On the other hand the star network simplifies the routing of course and reduces the need for repeating signals and potentially free up air time but it breaks route redundancy and as I said, the power will increase interference within the network and cross networks. Not a fan... -
Associations are not possible with ZLR, it all makes sense to me now.
I was recently contacted by a manufacturer who supplies us with Z-wave Plus Dimmers, the GEN 5 has Associations, which is useful in grouping dimmers and works extremely well.
After reading the product spec's I couldn't find any information on Association Groups in the G7 and voiced my concerns to the manufacturer.
Now I know why, GEN 7 doesn't support mesh, so much for backward capabilities, EZLO's new hub is useless unless you role out a new and different Z-wave system.
I'm now wondering why I'm even bothering with Z-wave and why not just go for Zigbee and WiFi.......aka Zedrally
-
@black-cat said in Z-Wave Plus (ZWP) & Z-Wave Long Range (ZLR):
Now I know why, GEN 7 doesn't support mesh, so much for backward capabilities, EZLO's new hub is useless unless you role out a new and different Z-wave system
If that’s true I know understand why they want to use multiple controllers together. No mesh means that large properties will not be easily supported. I’ve placed my unit centrally, but some nodes are not directly reachable and the mesh is doing its job.
-
The more I think about it and the more horrified I am by this "long range" approach. I see the benefit of eliminating the whole routing and topology management but this is coming at the cost of humongous increase in noise and likely degradation in reliability due to lack of redundancy of edge device signals and difficult management of packet collisions. As I said in my previous post, it makes also the devices more detectable from longer range which makes your network easier to hack. I will write a note to the alliance... One of the key benefits of z-wave for me was its low range. Jacking up the TX power from -1dB to up to +30dB is not a feature I want to see. For those who play with their wifi network, they should also know that optimizing one's wifi is to try to lower the TX power as much as possible in order to increase bandwidth. It is to avoid the cacophony of multiple devices screaming at the controller with megaphones at the same time.
-
More on this from the hubitat forum:
Hubitat and Z-Wave Long Range
We were going to save this for a surprise but our community sleuths have put 2+2 together. As many of you may know, Z-Wave Alliance recently announced the release of Z-Wave Long Range, which will open new opportunities for the Z-Wave protocol. I am happy to announce that we designed Hubitat...
Apparently it occupies a different channel so that's how the compatibility is retained. There are some marginal cases with devices being out of range where this could be helpful but all in all, I still think it is a horrible idea for most installations. Granted it simplifies some setup from not having to keep track of mesh routing or for example being able to include from a different location than the final location where the device will be but, at least from my observations, interferences and air time are the top source of reliability and latency, especially on a large network and freeing up the controller's air time is key to improving reliability. Long range would do the opposite. It is however for now not meant to convert the entire network but only an additional option.
-
Thanks for the link, it makes interesting reading.
I'm hoping that the best option is that we can choose to use either ZLR or ZWP rather than being forced into a upgrade.
