Hi

I just enabled the Telegram profile in my notification.yaml file. I added my bot ID and Chat ID.

I then added a notify action in a rules Reaction, but no notification is received to my phone.

I can run the raw HTTPS request URL in a browser and that works OK and my notification is received OK.

Also I wasn't sure what this means and I tried it commented out and not.

default_disable_notification: "false"

Likewise with this one:

default_parse_mode: ""

Also I see there is a bug listed here already, maybe related?

Thanks

Please ignore the entire "Tip" below, it ended up hosing my Reactor interface and I had to re-install the Reactor "stable" version to get back up and running. I'll leave it posted for a bit in case someone knows WHY it got hosed.
Sorry,
Chris

Guessing this is the most appropriate area in which to post this . . .

In case nobody has written this yet, I've been using Pushover for a while. First with VeraAlerts on Vera3/UI5, now with Reactor on openLuup/RPi3.

Until recently, Pushover has constrained us by only allowing select notification sounds. Now pushover.net will allow you to upload custom sounds to their internal library.

PushOver.PNG

You may then add these sounds to Patrick's J_ReactorSensor_UI7.js file

values: [ "=(device default)", "none=(none/silent)", "vibrate=(vibrate only)", "pushover=Pushover", "bike=Bike", "Bubbles=Bubbles (VA)", "bugle=Bugle", "cashregister=Cash Register", "classical=Classical", "Cloud=Cloud (VA)", "cosmic=Cosmic", "falling=Falling", "gamelan=Gamelan", "incoming=Incoming", "intermission=Intermission", "iPhone_Ding=iPhone Ding (VA)", "magic=Magic", "mechanical=Mechanical", "pianobar=Piano Bar", "siren=Siren", "spacealarm=Space Alarm", "tugboat=Tug Boat", "alien=Alien Alarm (long)", "climb=Climb (long)", "persistent=Persistent (long)", "echo=Pushover Echo (long)", "updown=Up Down (long)"

Not sure how the above code will format here, but I searched for "Pushover" in the .js file, found the section above, and sprinkled my 3 custom sounds alphabetically into the existing group (following existing formatting)

After that, a browser refresh was all that was needed.

That's All Folks,
Don't Call Me Chrissy

Hi all

I’ve been on a mission for a while now to try and track down where all the energy we use is going (so I can explain the exorbitantly high electricity bill !) .

I’ve done a few posts on this subject already, see below..

https://smarthome.community/topic/534/unifi-energy-report-how-can-i-retrieve-the-value-via-http/6 https://smarthome.community/topic/584/luup-hue-energy-watts-calculator/17?_=1623603224863

Plus I’ve got various energy meter plugs around the house to help me too, but when compared to my CurrentCost (whole house) energy meter, I’m still unable to account for 200+ watts when i believe everything of note are switch off (so no dishwasher, no washing machine running etc.)

Tracked items so far include.. Media Centre (TV/NAS etc.), Office Desk (Laptop/PC/Monitor etc.), Hue Lights, Fridge…

What items/devices could I be missing ? What else could i create a pseudo energy (watts) calculations for ?

For example (2), I‘ve got a couple of Sonos Music players, which are always on, so I’m thinking as they are a media device that report their status, i can calculate a pause/stop watts rating vs a play rating..

Any thoughts on what the missing power hungry items are in a normal house, and/or any new pseudo watt calculator ideas?

Hi,

I need help to create a search within MSR that shows me the name of all sensors in a certain status.

User case: Based on the information from category_num and subcategory_num, return in a string or array the name of all devices that meet the Tripped = 1 status.

Example: generate a warning message of all the windows that are open before triggering the alarm.

Which function should I use in MSR? What would this search look like?

Thanks.

OK, people, here we go! At long last, Multi-System Reactor developer preview is available!

The package can be downloaded from the Reactor bug tracker, a MantisBT system (at https://reactor.toggledbits.com/mantisbt/). There is a download button in the left margin, as well as links to the documentation, which you will need for installation.

UPDATE 2021-02-24 -- To keep spammers off, I've locked down registration on the Bug Tracker. To get access to the Bug Tracker and preview downloads, please PM me (not reply here) your full name and email address and I will set up an account for you.

This version of MSR will run on Linux systems, including RPi's under Raspios Buster, running node.js version 12.10 or higher (v14.15.1). For RPi users, there is an installation script that will install a local copy of node.js (for the logged-in user).

Bugs reports will be handled through the bug tracker only. Discussion and questions in this forum are fine, though (if that leads to a bug report, we'll transition).

This version supports Vera (and openLuup to the degree it's compatible with Vera Luup), Hubitat, and Home Assistant. Some of the device support on the H platforms is still a bit basic, but it is largely controlled by configuration and progress can be made quickly.

The documentation beyond installation is a mess. Of course, I started with the existing documentation and have been massaging into MSR's particulars, but it still has a long way to go on the detail.

I know I don't have to say this, but I will anyway... let me know how it goes!

Hi!

In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan

Hi,

I do not know the community can help but here is the request 😁.

I have a Dome DMS01 device to have sound alerts. To operate it has an APP installed, Dome Chime that calls one of 10 types of sounds by a panel.

9ae09d5f-f41c-4515-bd2f-81c2cb72b646-image.png

d5dff783-16f1-4ed5-888d-11c0ff5d204d-image.png

To use it with Reactor, I had to create a scene for each sound, which Reactor calls and triggers the sound/chime. I would like to check if there is a way to make this call directly from MSR, without going through this ugly scene path.

I already changed the configuration variable, but it only changes what is stored in the Vera, it doesn't change the data in the device, so it doesn't change the bell.

024a8634-c43f-461e-9a86-d5c1df56c8b2-image.png

When using the reconfiguration instruction (x_vera_svc_micasaverde_com_HaDevice1. Reconfigure), it shows an error message and does not make the change.

d58bb0e3-eaea-4600-86d3-d3a93bbde385-image.png

Manual info: http://manuals-backend.z-wave.info/make.php?lang=en&sku=DMS01&cert=ZC10-17015372

In short, I want to do in the MSR the same thing that this APP does.

If anyone can help, I appreciate.

Hello @therealdb with your OpenSprinkler plugin occasionally when I set a zone for an amount of time lets say 10 minutes, something happens and the counter for 10 minutes counts down 5 seconds to 9:55 then it resets back to 10 minutes. This continues to repeat so the zone will stay on for an infinite amount of time. In my experience this usually happens once the plugin has been running for about a day (ie no recent Luup reloads). I grabbed some logs but it doesn't seem to show anything weird happening. This issue does not happen when I set a zone timer through the OpenSprinkler app. Oddly enough when I stop the zone through the OpenSprinkler app when the timer keeps resetting, the same zone gets queued right away. It seems that the plugin is sending the start zone command every 5 ish seconds.

50 06/07/21 19:19:00.469 luup_log:1304: VeraOpenSprinkler[1.50](setVar@135): setVar("urn:upnp-org:serviceId:Dimming1","LoadLevelTarget","9",1310) old value "11" <0x6b8fe520> 06 06/07/21 19:19:00.469 Device_Variable::m_szValue_set device: 1310 service: urn:upnp-org:serviceId:Dimming1 variable: LoadLevelTarget was: 11 now: 9 #hooks: 0 upnp: 0 skip: 0 v:0x16fabd8/NONE duplicate:0 <0x6b8fe520> 50 06/07/21 19:19:00.480 luup_log:1304: VeraOpenSprinkler[1.50](setVar@135): setVar("urn:upnp-org:serviceId:Dimming1","LoadLevelLast","9",1310) old value "11" <0x6b8fe520> 06 06/07/21 19:19:00.481 Device_Variable::m_szValue_set device: 1310 service: urn:upnp-org:serviceId:Dimming1 variable: LoadLevelLast was: 11 now: 9 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x6b8fe520> 50 06/07/21 19:19:00.482 luup_log:1304: VeraOpenSprinkler[1.50](setVar@135): setVar("urn:upnp-org:serviceId:Dimming1","LoadLevelStatus","9",1310) old value "11" <0x6b8fe520> 06 06/07/21 19:19:00.482 Device_Variable::m_szValue_set device: 1310 service: urn:upnp-org:serviceId:Dimming1 variable: LoadLevelStatus was: 11 now: 9 #hooks: 0 upnp: 0 skip: 0 v:0x16fac40/NONE duplicate:0 <0x6b8fe520> 50 06/07/21 19:19:00.494 luup_log:1304: VeraOpenSprinkler[1.50](setVar@135): setVar("urn:upnp-org:serviceId:SwitchPower1","Target","1",1310) old value "1" <0x6b8fe520> 50 06/07/21 19:19:00.495 luup_log:1304: VeraOpenSprinkler[1.50](actionPowerInternal@785): [actionPower] #1310 - 5 <0x6b8fe520> 50 06/07/21 19:19:00.495 luup_log:1304: VeraOpenSprinkler[1.50](sendDeviceCommand@254): sendDeviceCommand("cm",{ 1="en=1", 2="t=540", 3="sid=5", 4="pid=-1", 5="uwt=0" },1304) <0x6b8fe520> 50 06/07/21 19:19:00.496 luup_log:1304: VeraOpenSprinkler[1.50](sendDeviceCommand@276): sendDeviceCommand - url: "http://192.168.8.225:80/cm?en=1&t=540&sid=5&pid=-1&uwt=0&pw=a6d82bced638de3def1e9bbb4983225c" <0x6b8fe520> 50 06/07/21 19:19:00.556 luup_log:1304: VeraOpenSprinkler[1.50](nil@214): [HttpGet] "http://192.168.8.225:80/cm?en=1&t=540&sid=5&pid=-1&uwt=0&pw=a6d82bced638de3def1e9bbb4983225c" - "{\"result\":1}" <0x6b8fe520> 50 06/07/21 19:19:00.557 luup_log:1304: VeraOpenSprinkler[1.50](setVar@135): setVar("urn:upnp-org:serviceId:SwitchPower1","Status","1",1310) old value "1" <0x6b8fe520> 50 06/07/21 19:19:00.557 luup_log:1304: VeraOpenSprinkler[1.50](deviceMessage@244): deviceMessage(1310,"Turning on for 540 seconds",false,15) <0x6b8fe520>```

About one month ago I got a new electrical meter in the house. The new meter is a "smart" meter equipped with a data port. It is more or less the same type of meter that is used in a number of European countries, e.g. The Netherlands, Belgium, Sweden etc.
Norway has selected a different version with a RJ45 port with another protocol.

The dataport is a serial "P1" port in the form of a RJ12 contact that sends quite a lot of data every 10 seconds:
c716b64e-dcac-4ea4-9b1b-8ee29eb55edc-image.png

The data will show both consumption and production if you e.g. have solar panels at home.

My initial though was to use the Tasmota P1 Smart Meter with Mqtt. I tried this and it works, but unfortunately I got some serial data errors every 5-10th message for some reason so I decided to try another solution.

I found a few other alternatives and tested one of them. The upside with this version is that it is adapted to the Swedish data fomat that differs from the Dutch a bit and that it delivers the data in Mqtt form:
2aab179b-a9ea-4041-8c38-f73570206e11-image.png

The hardware is pretty simple. For the Tasmota variant and most of the other solutions you need a ESP8266, e.g. a Wemos mini and then a transistor and two resistors (image below). The version I use is even simpler since it does not need the transistor.
For a lot of the meters delivered (DSMR 5 versions if I am right) you can power the ESP from the 5V provided in the RJ12 port, very handy.

42092756-f6b3-4375-9000-04bcd1e22240-image.png

It is also possible to buy a readymade P1 meter, this one looks quite nice, although I have not tested it.

In order to get a good overview of the data from the meter I have started creating a dashboard in Grafana that gets data from Historian in OpenLuup. It is quite useful to be able to see the load over time per phase etc.
a8276d7b-6b39-4f3a-a663-353173c1da5b-image.png

I also managed to grab the hourly prices in json format and display that in the dashboard via some lua code in a scene.

At the moment I have built no logic around this, but it opens up posibilities for sure. In Sweden the electrical tarrifs will change from daily rates to being higher when demand is higher, perhaps then this can be used.

All in all a fun DIY project that provides some useful data out of the electrical meter. 🙂

I have been trying to get my windowshadeautomation (outside window)to work for some time in reactor but I cant get it working good..
What I want is that shades should close if above 20000lux if window is closed else if window open only set shade position to 0.7

And if shade is closed and window is opened shade should go to 0.7 and if closed again shade should go back to closed

I have tried so many variants with different results.
I need som help...
/Mattias
I have :

Trigger
light sensor ( above 20000 lux )

Constraint
Rainsensor ( no rain)
Windsensor(no wind)
Window (closed, or open )

Set reaction
Cover close or set 0.7

Reset reaction
Cover open

I have "rainstorm lights", those couple lights in the house that come on during the day when it's gotten so dark due to weather that it's almost like night inside. The trigger for this is mode + solar radiation level.

However, this gets triggered in that last hour before I wake in the morning due to the fact that I switch the house from NIGHT mode to DAY mode at 05:30 so climate control has an hour to warm the house appropriately before I rise at 06:30 weekdays (07:30 weekends.) To circumvent that I've added two "excludes" for hours "not between".

Everything is working great with the exception of blocking the pre-alarm hours. I'm posting what I've created for another set of eyes to review and point out my obvious-to-all-but-me error.

969cb424-f1e6-41da-b785-f0b35e9cc644-image.png 50ee5a24-ac0a-4d2c-9e7b-36923b56c4d9-image.png

I have been playing with TTS through an Ikea/Sonos speaker controlled through Hubitat.
When writing the action using variables and then using the PLAY button for that action I get an error message.
Using the PLAY button for the Set Reaction and the TTS works fine.
I'm not sure what the difference is but it is nice that text with variables works fine with TTS.

Spaeker action.png

Spaeker action error.png

Haven't been keeping track with the releases for a while, still on 096.

Is there any risk in using savedata from this old version on the newest, or can i just go ahead and update to the new docker?

Just thinking if there's any changes in savedata format or handling?

Hi all

I’ve been trying to use the Hue api and some of my Lua knowledge to create an energy calculator based on the brightness and wattage of specific models of hue bulb registered on the hub

I’ve pretty much got there, the only stumbling block I have is how I total up all the individual bulb wattages. Can anyone help ?

It’s likely an easy thing for someone more experienced to see, but as I only dip in and dip out now and then, the correct code/syntax does not always come to mind.

Note : as I’ve tried various routes, I’ve commented some things out, but you should be able to get the idea of what I’m trying to do..

Create device json from Hue Hub Decode JSON and extract key values to a table Calculate approx watts based on bulb model and/or watts function Total up watts of all bulbs that are switch on.

Code below...

local hueBridgeIP = '192.168.1.29' local hueBridgeAPI = "80uCoXjnn2LNLhxEJ9PW6nmt-G5KWQ2uP3oONAvcm0j" function getHueLight() local http = require('socket.http') local ltn12 = require('ltn12') local json = require('dkjson') t = {} local url = string.format("http://%s/api/%s/lights", hueBridgeIP, hueBridgeAPI) b, c, h = http.request{url=url, sink = ltn12.sink.table(t), method='GET'} huestring = tostring(table.concat(t)) local hue, pos, err = json.decode(huestring, 1, nil) huelights = {} for k, v in pairs(hue) do local modelno = string.gsub(hue[k]['modelid'], "%s+", "") table.insert(huelights, {k, hue[k]['state']['on'], hue[k]['name'], hue[k]['state']['bri'], modelno, hue[k]['state']['reachable']}) print(k, hue[k]['state']['on'], hue[k]['name'], hue[k]['state']['bri'], modelno, hue[k]['state']['reachable']) end end local fourpointeightwattTable = { [ 1 ] = 0.6 , [ 2 ] = 0.7 , [ 3 ] = 0.8 , [ 4 ] = 0.9 , [ 5 ] = 1.2 , [ 6 ] = 1.4 , [ 7 ] = 1.7 , [ 8 ] = 2.0 , [ 9 ] = 2.3 , [ 10 ] = 2.6 , [ 11 ] = 2.9 , [ 12 ] = 3.1 , [ 13 ] = 3.5 , [ 14 ] = 4.0 , } local sevenwattTable = { [ 1 ] = 1.6 , [ 2 ] = 1.7 , [ 3 ] = 1.8 , [ 4 ] = 1.9 , [ 5 ] = 2.2 , [ 6 ] = 2.4 , [ 7 ] = 2.7 , [ 8 ] = 3.0 , [ 9 ] = 3.5 , [ 10 ] = 3.9 , [ 11 ] = 4.5 , [ 12 ] = 5.1 , [ 13 ] = 5.5 , [ 14 ] = 6.4 , } local ninewattTable = { [ 1 ] = 1.6 , [ 2 ] = 1.7 , [ 3 ] = 1.8 , [ 4 ] = 1.9 , [ 5 ] = 2.2 , [ 6 ] = 2.5 , [ 7 ] = 2.9 , [ 8 ] = 3.5 , [ 9 ] = 3.8 , [ 10 ] = 4.6 , [ 11 ] = 5.5 , [ 12 ] = 6.5 , [ 13 ] = 7.7 , [ 14 ] = 8.5 , } function fourpointeightgetWattage(hue) local index = math.floor(hue / 16.5) if index <= 0 then return 0.2 elseif index >= 15 then return 4.8 else return fourpointeightwattTable[index] end end function sevengetWattage(hue) local index = math.floor(hue / 16.5) if index <= 0 then return 0.4 elseif index >= 15 then return 7.0 else return sevenwattTable[index] end end function ninegetWattage(hue) local index = math.floor(hue / 16.5) if index <= 0 then return 0.4 elseif index >= 15 then return 9.0 else return ninewattTable[index] end end local total = 0 local Value = 0 local huewatts = {} for k,v in pairs(huelights) do if v[2] == true and v[5] == "RS125" and v[6] == true then local watts = fourpointeightgetWattage(v[4]) local Value = tonumber(watts) local total = total + Value print("four point eight watts") print(v[5], v[4], v[2], v[3], watts) table.insert(huewatts, {v[5], v[4], v[2], v[3], watts}) --print(watts) --print(total) elseif v[2] == true and v[5] == "LWA004" and v[6] == true then local watts = sevengetWattage(v[4]) local Value = tonumber(watts) local total = total + watts print("seven watts") print(v[5], v[4], v[2], v[3], watts) table.insert(huewatts, {v[5], v[4], v[2], v[3], watts}) --print(watts) --print(total) elseif v[2] == true and v[6] == true then local watts = ninegetWattage(v[4]) local Value = tonumber(watts) local total = total + Value print("nine watts") print(v[5], v[4], v[2], v[3], watts) table.insert(huewatts, {v[5], v[4], v[2], v[3], watts}) --print(watts) --print(total) end end print(total) print(huewatts) -- confirm if table it there (TBC)

I have MSR installed on two separate TS-251+ devices with the shared MSR_Data folders kept in sync using Hybrid Backup Sync.
The container on the standby or secondary server is stoped so both versions are not operating at once.
I've tried disabling one and switching to the other and that works well. It is nice to have the data backed up and another system ready to go if the first one fails.
It would be nice to have a way for the backup MSR container to be running and watching the primary MSR and take over automatically.

We're 60 days out from the 1.0 release date I gave earlier in this category. For about the next 30 days, I'll entertain new feature requests for anything you all feel is absolutely needed and not yet present for a 1.0 release, and you're going to have to make a strong case. Short of that, it will have to live on the wish list for a possible future release.

Identify and discuss in this topic, please... go!

Feedback / solutions for openLuup's built-in Tasmota MQTT bridge.

Feedback / issues with openLuup's built-in MQTT server

@akbooer, I just woke up to a z-way bridge token expiration again forcing me to login again and reload openluup. It appears to happen once a week. It doesn't appear that the auto renewal of the token is working?

I'm working on a very slow migration from DataYours to Historian and am wondering if there is a list of cache devices that can be modified to include some that are missing, specifically several voltage variable monitors in service EnergyMetering1.

Just checked again and a couple showed up. It could be that these populate slowly after a Vera reboot?

I would also like to modify the storage-aggergation, it is possible to edit that .conf file directly and reboot openLuup?