-
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.
Controller shift - How do you do it ?
-
A while back the z-wave module on my veraplus stopped working and as it couldnt be fixed, I bought an external usb z-wave dongle UZB1 (which I plugged in and setup on ‘port’ /dev/ttyACM0 ) which made it operational again, and I’ve been using it again since.
Recently I picked up a new (well 2nd hand) VeraPlus unit and tried to do a full system/zwave network restore from the original one, but it didn’t work.
The restore looked like it worked fine, as it brought everything over, but when nothing worked, I checked the z-wave ‘port’ settings on the new unit, and it too had been set to use an external usb (/dev/ttyACM0) which it obviously doesn’t have , but when I changed it back to the onboard zwave module (/dev/ttyS0) all the z-wave devices disappeared.
To fix this, it sounds like I need to do a controller shift to get the details off the UZB1 key and onto the zwave chip on the veraplus board ?
However not having done one before I’m not sure if the process is - any ideas ?
-
I am afraid a controller shift will not help in this case. The problem stems from rigidity of the restore tool of the vera. What you are observing is completely expected.
The vera controller backup contains two things:- The user-data file along with all your plugin data.
- The zwave dongle network backup.
When you did the restore from backup step on your new vera, your user-data had your port as /dev/ttyACM0 so during the restoration the vera attempted to restore the zwave network to that port which obviously did not exist. What you need to do now that you changed the zwave serial port back to the vera onboard chip, is to manually grab the latest dongle backup file from the old vera (it's in /etc/cmh-ludl) and move it to the new vera in the same location. Use SFTP to do this.
Then SSH into the new vera and runtouch /etc/cmh-ludl/dongle.restorethen reload luup. It should normally restore your previous zwave network configuration into the new vera zwave chip.
Another alternative is of course to just plug your uzb zwave dongle into the new vera.... I actually prefer using USB these days for exactly this kind of moves.To be clear on what a controller shift does:
It is a combination of inclusion of a new controller and moving the zwave master flag from the master controller to the new controller. The problem with this is the node numbering and will leave you with the vera not being node 1 on your zwave network. It could be ok but some devices may not like it. Sensors for example may have issues with their lifeline associations. The lifeline association is essentially a direct relation to the target controller a device reports its data to. The controller shift was very relevant for the time when zwave was just controlling lights from a controller which was a remote control. After that it has become less and less useful. -
Thanks @rafale77
Coincidentally Vera support got back to me with the following instructions. (FYI)
To do the Z-Wave network shift on the controller, you need to follow these steps:
- Make sure both controllers are connected to the same LAN.
- Go to "User & Account info" -> "Security" -> make sure the option "Enable UPnP" is checked.
- Go to "Settings" -> "Net & Wi-Fi" -> make sure the option "Auto-detect devices in my home network" is checked.
- On the controller that will send the network, go to "Settings" -> "Z-Wave Settings" -> "Advanced" -> click "Go" on "Controller shift."
- On the controller that will receive the network, go to "Settings" -> "Z-Wave Settings" -> "Advanced" -> click "Go" on "Copy Z-Wave network from a primary controller."
- The process should take place in the next few minutes.
-
Nope, not the best answer. That will get you a new controller with a new zwave node ID. It will work for switches and lightbulbs but anything which needs instant status or sensor reporting will fail.
You will have to do a lot of reconfiguration of devices and some devices may not work. When I migrated my vera zwave network to z-way, I ended doing a lot of cleanup because of the number of times I had migrated from vera to vera. The screenshot below is one of the reason why I favor z-way. I have full visibility of what the associations are, what they are and I can update them. They are configuration parameters inside the devices. Not in the controller just like the neighbor node information.
In your case "cloning" the zwave dongle is the best answer but it is not documented or supported officially by vera.
-
How is the controller shift instructions provided by Vera above , differ from your suggestion to manually grab the latest dongle backup file from the old vera (in /etc/cmh-ludl) and move it to the new vera, into the same location and then run ‘touch /etc/cmh-ludl/dongle.restore’
The both seem to be copying the Z-Wave network from a original (primary) controller to the new one ?
-
No it is actually very different.
The controller shift is an actual zwave protocol function, not a vera function. What it does is:
- include new controller (meaning add new controller to network and give it a new node ID, send network data to new controller over zwave (RF))
- assign new controller as master, unassigned current controller master flag.
The old controller will remain node 1 until you use the new controller to exclude it. Actually I can't remember with if it actually excludes itself. I don't believe it does. You end up with 2 controllers on your network. One master, one slave and you have shifted the master from one to the other.
The process I gave you clones all the data from one controller chip to the other using the backup file over the serial API of the zwave dongle. It means that they will both have the same node ID "1" and you don't need to do anything to your devices. You however have to take down the old controller or your network will be confused with 2 controllers with the same ID. Or if you tinker like me, keep the old USB dongle as a backup in case the internal one fails so you can stick it in just in case but in any case, you should unplug it and not use both at the same time.
The whole upnp think they ask you to do is to make sure the two vera see one another so they can transfer your user-data... including your security key but you can do that using backup/restore.
-
Does the version of z-wave firmware play any part in this ?
My UZB1 usb stick is on 4.05 L:1 - Role: Suc SIS: YES PRI: YES
The new Vera is on 6.01 L:1 - Role: Master SIS: NO PRI: YES -
The vera upgrades from SDK to SDK very well(unless the new chip has an even newer firmware which the vera did not know of). It is part of their firmware update process. It is downgrading which is more of a challenge. I don't think you'll have any problems.
Fun fact, I had even upgraded my vera's zwave chip firmware far beyond what vera officially supported and had no problems.
-
Hi @rafale77
With your help, could we make this ‘shift’ run almost like a batch like process on the same device, by that I mean.
After doing a backup of the old Vera and a restore onto the new one.
Could I move the UZB1 USB dongle onto the new VeraPlus, ensuring it’s operational and working first under /dev/ttyACM0
Then is there a set of commands I could run that does the cloning straight off from /dev/ttyACM0 (UZB1) onto to /dev/ttyS0 (onboard) ?
And then ideally at the end of that, could it update the new Vera z-wave config to now look at /dev/ttyS0 (onboard) allowing me to move the UZB1 dongle (and store it away) ? -
It's not a very hard thing to do but I unfortunately gave away most of my veras and only have a couple of bricked ones left so I can't test this.
There was another way which was to manipulate the zwave serial port inside your backup user-data.json which is what I had to do but it takes decompressing your backup and the user-data.json.lzo and the compress it back and then restore that backup.
The silliness of the backup restore process is that it is very rigid and doesn't allow you to restore to a different serial port than what your original backup file. What I gave you should work though... manually grab the last dongle file from one unit, move it to the other one and with your UI already showing the new target serial port, start a dongle restore.As I previously said, I also highly recommend you stay with the usb stick. It likely has greater range and upgradeability.
-
@rafale77 said in Controller shift - How do you do it ?:
I also highly recommend you stay with the usb stick. It likely has greater range and upgradeability.
I’d actually seriously consider that, but the upgrading route for the z-way UZB1 dongle, seems so unnecessarily complicated .
One of the reasons for getting the new Vera was because a Fibaro RGBW Module was appearing as many multiple nodes, and Vera support had a look and seemed to suggest it was due to the z-wave version I was running.
parkerc said in Controller shift - How do you do it ?:
My UZB1 usb stick is on 4.05 L:1 - Role: Suc SIS: YES PRI: YES
The new Vera is on 6.01 L:1 - Role: Master SIS: NO PRI: YES -
upgrading firmware on a UZB is actually quite easy...
what is the brand of your stick?
Updating firmware on Silicon Labs Z-wave UZB USB sticks
There may be occasions when it becomes necessary to update the firmware of Silicon Labs Z-wave UZB controller USB sticks. Firmware updates may be needed when new SDKs are released or a change in UZB functionality is required. UZB firmware can be updated using Silicon Labs Windows based Z-Wave...
-
@rafale77 said in Controller shift - How do you do it ?:
what is the brand of your stick?
Z-wave.me - ZMEEUZB
-
Ahhhhh then this is what you need:
and it is indeed a little more complicated due to the need of following this crazy map:
-
Yep, that’s it
and I think you even helped me a while back, as that ‘crazy map’ was doing me head in.Trying to follow it drove me crazy !
-
I can help you read through it and break down the commands to upgrade if you want me to. What is your current firmware version?
-
@rafale77 said in Controller shift - How do you do it ?:
What you need to do now that you changed the zwave serial port back to the vera onboard chip, is to manually grab the latest dongle backup file from the old vera (it's in /etc/cmh-ludl) and move it to the new vera in the same location. Use SFTP to do this.
Then SSH into the new vera and run
touch /etc/cmh-ludl/dongle.restorethen reload luup. It should normally restore your previous zwave network configuration into the new vera zwave chip
Hi @rafale77
Picking this up again as i have managed to find a bit of time - and looking on my Vera I can’t see that a
dongle.restore.shfile, plus the dongle files seem to be in/etc/cmhrather than/etc/cmh-ludlsee below..root@MiOS_55100454:/# find -name dongle*.* ./etc/cmh/dongle.4.5.dump.0 ./etc/cmh/dongle.4.5.dump.1 ./etc/cmh/dongle.4.5.dump.2 ./etc/cmh/dongle.4.5.dump.3 ./etc/cmh/dongle.4.5.dump.4 ./etc/cmh/dongle.4.5.dump.5 ./ezmi/cmh/dongle.4.5.dump.0 ./ezmi/cmh/dongle.4.5.dump.1 ./ezmi/cmh/dongle.4.5.dump.2 ./ezmi/cmh/dongle.4.5.dump.3 ./ezmi/cmh/dongle.4.5.dump.4 ./ezmi/cmh/dongle.4.5.dump.5 root@MiOS_55100454:/#Any ideas where the dongle.restore file might be or if it’s called something different ?
-
Have looked here too, which has helped a bit.. https://smarthome.community/topic/199/problem-migration-z-wave-nw-from-vera-to-uzb1-dongle?_=1632067117298
The issue seems to be the
dongle.restorefile requirementsIf it helps, i found this within the ./mios/www/cgi-bin/cmh/restore.sh file
if [ "$FORM_dongle" == "1" ]; then # LuaUPnP will restore the Z-Wave backup file if it finds the 'dongle.restore.go' file. # To prevent LuaUPnP from restoring a dongle backup until the next boot, # we'll save the file as 'dongle.restore', and the 'Start_cmh.sh' script will rename it to 'dongle.restore.go'. log "Create $MIOS_CONF_PATH/dongle.restore" touch "$MIOS_CONF_PATH/dongle.restore" 2>>$log_file fiAnd then looking in
./usr/bin/Start_cmh.shthe reference there is..# to prevent LuaUPnP from restoring a dongle backup until the next boot, # the web ui saves .restore and LU looks for .go mv /etc/cmh/dongle.restore /etc/cmh/dongle.restore.go || /bin/trueSadly not much further forward…
-
I don't want to be stupid, but have you actually made a backup? Unless it's automatic and storing locally.....
C
-
Yep, I have made a local back up. (Inc z-wave network) and have it stored locally
Both Veras are on the network, I first went into the veraplus with the usb zwave dongle and did the full backup, saved it locally and then logged into the VeraSecure and did the restore.
Everything but the zwave devices was restored and based on what @rafale77 had said before my issue is that it’s trying to restore back to an /dev/ttyACM0 dongle, rather than the onboard one /dev/ttyS0
I somehow need to get the zwave records onto the right tty..
