Could the temperature values be pulled into MSR from one of these devices: OW-SERVER: 1-Wire to Ethernet Server

71.57 GBP OW server (Ethernet) OW server (Ethernet)

Description The OW-SERVER is an inexpensive Ethernet to 1-Wire interface that is designed to efficiently monitor and control 1-Wire devices. The OW-SERVER will allow you to use industry standard Ethernet products (switches, hubs, etc.) to build the backbone of your 1-Wire based sensor / control...

Thanks.

I know I have mentioned this before somewhere, but i simply can't find the thread..

Plugins like Auto Virtual Thermostat and Delaylight from Vera/openLuup are functions that whould be lovely to have in MSR - is there any possibility to implement these in some way?

I could offcourse program them myself and copy them to where i want to use them, but if i'm not wrong that would be a fairly advanced ruleset that in any case would be beneficial to share with the community in some way when they are made and done.

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?

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 end

I 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..

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.

Hi Patrick/AK Booer

I am able to see Reactor expressions in the AltUI UI per the below and the expressions work as they should in my reactor sensors. When an expression changes, the reactor sensor responds accordingly.

javascript.png

However, I cannot see the expressions in luup state variables or the luup logs:

Luup.png

Log.png

I tried reinstalling openLuup (latest development) and when that failed to change the noted behavior, I reinstalled lua5.1. There was also no change. Rebooting the machine also produced no change.
I suspect this is an openLuup issue as I also see nil values for some plugins:

plugin.png

And other plugins are fine:

2022-01-12 20:47:12.027 luup.variable_set:: 63.urn:upnp-micasaverde-com:serviceId:Weather1.CurrentDewPoint was: 32 now: 29.7 #hooks:0 2022-01-12 20:47:12.028 luup.variable_set:: 63.urn:upnp-micasaverde-com:serviceId:Weather1.WindSpeed was: 1.76 now: 2.8 #hooks:0 2022-01-12 20:47:12.028 luup.variable_set:: 63.urn:micasaverde-com:serviceId:HumiditySensor1.CurrentLevel was: 30 now: 27 #hooks:0 2022-01-12 20:47:12.028 luup.variable_set:: 65.urn:micasaverde-com:serviceId:HumiditySensor1.CurrentLevel was: 30 now: 27 #hooks:0 2022-01-12 20:47:12.028 luup.variable_set:: 63.urn:upnp-micasaverde-com:serviceId:Weather1.LastUpdate was: 1642047430 now: 1642049231 #hooks:0

Any ideas on how to troubleshoot this.....

Could MSR at some point support openHAB as a controller?

I'm probably going to release my first pass at the MQTTController for Reactor (aka MSR) this week. It doesn't yet intrinsically know about a lot of devices, but you can train it for pretty much anything, I think, and it would be great if a couple of our heavy MQTT users could help check it out and maybe help contribute some device templates.

I'm hoping to package it up for mid-week, assuming the rest of life stays on track.

Success factors for the test: solid familiarity with MQTT, a big mix of devices, and comfortable editing YAML (for creating the templates/mappings).

I've recently moved my Nest Thermostats from Vera to Home Assistant, using the official integration. This is a how-to migrate it completely on Home Assistant, thus retaining control and status in your Vera (i.e.: because you have code/scenes/Reactor rules/whatever to maintain - in my case it was all the above and more).

Prerequisite: goto https://github.com/dbochicchio/vera-VirtualDevices and install the virtual heater/thermostats files. Follow instructions, if in doubt.

First, go to your Vera, enter your thermostat Advanced Settings, under Params be sure to remove the plugin, by setting its value to 0. Then

change device_file to D_VirtualThermostat1.xml change impl_file to I_VirtualHeater1.xml change device_json to D_VirtualThermostat1.json change subcategory_num to 1 (if necessary)

Repeat for other thermostats - you could use the first as master, so look for the doc for more info on this point. Be sure to remove the plugin from humidity sensors as well.

After the luup reload, hard refresh (CTRL+F5) your browser and then set all these variables to skip (we will not execute actions on setpoint/mode changes, we'll just save variables).

SetPowerURL SetPowerOffURL SetSetpointURL

At this point, the actions to change mode/setpoint will write your desired value to SetpointTarget and ModeTarget variables. We will use them in MSR to get the actions and execute them in Home Assistant.

Under MSR, be sure to write two rules.
One rule is watching for SetpointTarget and ModeTarget variables under the Vera Virtual Thermostat, to execute the actions on your thermostat.

f70a6c94-df72-4b89-8d69-0edced1c5440-image.png

You'll need to translate the values from Vera's mode (Off, HeatOn, CoolOn) to HASS one (off, heat, cool). Since this thermostat is heating only, I'm just translating the ones I have. Repeat these steps for every device you have.

Then, you'll need to write a rule looking for temperature, setpoints, mode and so on. I have a unique rule to synchronize all of them, so I'm looking for humidity entity, temperature entity, and thermostat to update the Vera's variable. I have a set of expressions to translate to Vera's friendly variables:

730b32f0-d232-4bc4-9981-26dfaa00d56c-image.png

You'll need to just set the variables like this:
890083b3-ccd6-4039-99cb-1c90d64f00d5-image.png

Variables involved:

Service Variables Value urn:upnp-org:serviceId:TemperatureSensor1 CurrentTemperature ${{temperature}} urn:micasaverde-com:serviceId:HumiditySensor1 CurrentLevel ${{humidity}} urn:upnp-org:serviceId:TemperatureSetpoint1 CurrentSetpoint ${{setpoint}} urn:upnp-org:serviceId:TemperatureSetpoint1_Heat CurrentSetpoint ${{setpoint}} urn:upnp-org:serviceId:TemperatureSetpoint1 SetpointAchieved ${{setpointachieved}} urn:upnp-org:serviceId:TemperatureSetpoint1_Heat SetpointAchieved ${{setpointachieved}} urn:upnp-org:serviceId:HVAC_UserOperatingMode1 ModeStatus ${{modestatus}} urn:micasaverde-com:serviceId:HVAC_OperatingState1 ModeState ${{modestate}} urn:upnp-org:serviceId:HVAC_UserOperatingMode1 EnergyModeStatus ${{energymodestatus}}

Just repeat these steps for every thermostat and you should be good to go. It could be adapted for a different mix of devices/systems, of course. I hope this will help someone else achieving the same results! Now we can control the thermostat from both point and everything is in sync!

I could not find a post or PR for this so apologies if it has been answered.
There seems to be a fixed width for the columns in the Entities page making it impossible to see the full Canonical ID of long ID's and a lot of white space in the Entity Name column.
I tried to adjust the width in Chrome and Edge without success, is it a feature or or am I doing it wrong?

columns.PNG

latest-22004-6d6c6b7 bare metal.

Well with all that has been going on with Vera/eZlo, many people are abandoning the Vera hubs and moving on to other solutions, such as Hubitat (my case), HASS, HA, and many other controllers.

In the past, I had already been informed that when the migration was over, my Vera would go to the incinerator, or under the wheel of my car, and of course, I did not comply.

So I wanted to open a debate, for those who have not yet sold their Vera on eBay, are with the equipment idle, what destination could be given?

I see many saying that it has become a laboratory, I don't see much sense, since it is becoming obsolete and without a drive. But it can be a destiny. Has anyone thought about whether it is feasible to change the hub's SO so that it becomes a host for MSR, for example? Or even Home Assistance? I have no knowledge, but it seems to me that processor and memory have to do something like that, already has embedded wifi and network.

Does anyone have any idea if it is possible to give this equipment a destination other than a box?

I just published an update to my Virtual Devices Plug-in.

What's new in version 1.5:

support for async HTTP (out of the box on openluup, just download https://github.com/akbooer/openLuup/blob/master/openLuup/http_async.lua and copy with the plug-in files on Vera) experimental support for setpoints management in Virtual Heaters (you know, the device will turn itself off if temperature is reached, and automatically on when temperature is not beyond the setpoint) external device for temperature in Virtual Heaters (just set urn:bochicchio-com:serviceId:VirtualHeater1/TemperatureDevice variable) small fixes, stabilization

Grab your copy from https://github.com/dbochicchio/vera/tree/master/VirtualDevices

As always, 100% local, 100% apps friendly, 100% supported by Alexa (and Google Home, I guess).

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 suggests

Any ideas are appreciated.

Following the docs:
In expressions; dynamic groups can be referred to in the groups key of the matchEntities() function, or by passing the group's canonical ID to getEntity(). The former is probably preferable, as it's much easier to read and understand what is going on.
Example in docs:

each e in matchEntities({group:'groups>low_battery_entities'}): e.name each id in getEntity('groups>low_battery_entities').attributes.sys_group.members: getEntity( id ).name

I set up a Dynamic group:

- id: groups name: Dynamic Group Controller enable: true implementation: DynamicGroupController config: groups: "EzloDevicesNotResponding2": name: Ezlo Devices Not Responding select: - include_controller: ezlo - include_capability: x_ezlo_device filter_expression: entity.attributes.x_ezlo_device.reachable != true

group_entity.PNG

But when I try the Expression I get a compilation error

e_name.PNG

Log:

[latest-22004]2022-01-09T12:24:35.420Z <Engine:NOTICE> [Engine]Engine#1 expression testing has changed; recomputing dependencies [latest-22004]2022-01-09T12:24:35.421Z <Engine:ERR> [Engine]Engine#1: error evaluating expression testing: [ReferenceError]ReferenceError: Invalid reference to member name of ezlo>device_61baf610129e0725bd9f80f3 [latest-22004]2022-01-09T12:24:35.422Z <Engine:ERR> [Engine]Engine#1: expression: each e in matchEntities({group:'groups>EzloDevicesNotResponding2'}): e.name [latest-22004]2022-01-09T12:24:35.422Z <Engine:5:Engine.js:960> [Engine]Engine#1: path testing->testing [latest-22004]2022-01-09T12:24:35.422Z <Engine:CRIT> ReferenceError: Invalid reference to member name of ezlo>device_61baf610129e0725bd9f80f3 ReferenceError: Invalid reference to member name of ezlo>device_61baf610129e0725bd9f80f3 at _run (/home/homebridge/reactor/common/lexp.js:1411:31) at _run (/home/homebridge/reactor/common/lexp.js:1514:41) at /home/homebridge/reactor/common/lexp.js:1246:29 at Array.forEach (<anonymous>) at _run (/home/homebridge/reactor/common/lexp.js:1245:28) at run (/home/homebridge/reactor/common/lexp.js:1609:22) at Object.evaluate (/home/homebridge/reactor/common/lexp.js:1645:20) at Engine._eval_expr (/home/homebridge/reactor/server/lib/Engine.js:958:280) at Engine.notify (/home/homebridge/reactor/server/lib/Engine.js:644:142) at /home/homebridge/reactor/server/lib/MessageBus.js:106:223 [latest-22004]2022-01-09T12:24:35.424Z <Engine:5:Engine.js:1000> [Engine]Engine#1 set global testing; value=(object)(null)

When not referring to e.name It's an array with three members

e.PNG

latest-22004-6d6c6b7 bare metal installation.

What I'm I doing wrong?

I can't post on the original thread its been locked for some reason

https://smarthome.community/topic/743/how-to-rule-for-vera-can-t-detect-device-errors-and-reset?_=1641661663657

I am sometimes seeing this alert to do with this:

de844f5c-53db-4fc9-abac-a85606ea5e66-image.png

How do you fix it?

Thank you

@toggledbits Is there a way to get Current Alerts as an entity so I could monitor those and send notifications if needed.
My usecase is sometimes openLuup crashes and MSR picks that up pretty quick, sending a pushover notification to me would get my attention to restart it.
Of course there are many ways to monitor connectivity but since MSR already is doing that it would be neat to take advantage of it.

Hi

We have a newish dev on the Vera forum making a few new plugins, which is good to see as we have hardly any 3rd party devs left any more.

He's created a nice little plugin here, that pulls down your current WAN IP in to a plugin device in the Vera UI7 gui.

I was under the impression that Vera plugin device support had to be explicitly added by the MSR dev ?

However it seems that this particular plugin has just bounced in to my Vera Edge Entities list after a Reboot of MSR and is showing this output, so appears to be just working.

x_vera_device.configured=false x_vera_device.device_number=162 x_vera_device.device_type="urn:nodecentral-net:device:ExternalIP:1" x_vera_device.failed=null x_vera_device.mapped_by="*" x_vera_device.mapped_class="generic_device" x_vera_device.parent_device=0 x_vera_device.room_id="0" x_vera_svc_micasaverde_com_HaDevice1.Configured="0" x_vera_svc_nodecentral_net_ExternalIP1.Current External IP="xx.xx.xx.xx" x_vera_svc_nodecentral_net_ExternalIP1.Icon="0" x_vera_svc_nodecentral_net_ExternalIP1.Last Changed="1641612887" x_vera_svc_nodecentral_net_ExternalIP1.Last Changed HR="1641612887" x_vera_svc_nodecentral_net_ExternalIP1.Last Checked="1641612887" x_vera_svc_nodecentral_net_ExternalIP1.Last Checked HR="1641612887" x_vera_svc_nodecentral_net_ExternalIP1.PluginStatus="Plugin variables being set up 2/2" x_vera_svc_nodecentral_net_ExternalIP1.PluginVersion="0.2" x_vera_svc_nodecentral_net_ExternalIP1.Previous External IP="0.0.0.0" Capabilities: x_vera_device, x_vera_svc_micasaverde_com_HaDevice1, x_vera_svc_nodecentral_net_ExternalIP1 Actions: x_vera_device.set_variable, x_vera_svc_micasaverde_com_HaDevice1.AllowPairing, x_vera_svc_micasaverde_com_HaDevice1.Poll, x_vera_svc_micasaverde_com_HaDevice1.Reconfigure, x_vera_svc_micasaverde_com_HaDevice1.Remove, x_vera_svc_micasaverde_com_HaDevice1.SetPollFrequency, x_vera_svc_micasaverde_com_HaDevice1.StressTest, x_vera_svc_micasaverde_com_HaDevice1.ToggleState, x_vera_svc_nodecentral_net_ExternalIP1.refreshExternalIP

Thanks

Hi

Is it possible to access the information that the MSR has about the last date and time that a device suffered a change? The information that appears in the Entities area?

dfd353df-15f9-44ef-bda3-8351363ea486-image.png

Use Case: I want to monitor all devices, and those that are not communicating/acting for more than 48 hours, take notice and action

Of course there are some that will not communicate by their nature, such as a water valve, so a list of exceptions would be created.

The principle is almost the same as Hubitat's WatchDog APP, but I want to have my own, and not be dependent on Hubitat's communication or action.

Thanks.

Good afternoon. Due to the new ezlo not being available in europe yet, I wanted to change the z-wave getway that works with the reactor to add to the home assistant. What advises?
Thanks

Everyone,

As a side project, building on some deep innards borrowed from Reactor, I have released two new projects (unrelated to Reactor). Both are published on npmjs (for installation via npm), and on GitHub.

ezmqtt — a standalone app that acts as a conduit between Ezlo hubs and MQTT. It's published on npmjs.com and on Github. node-red-contrib-ezlo — Node-RED nodes (installable package) for Ezlo hubs. It's published in the Node-RED Nodes Library, at npmjs.com, and on Github

Why? Because choices are a good thing.

There are docker containers available for ezmqtt, but I haven't finished the work there, so they may not be quite ready for prime time; but feel free to test/play if you want.