Currently I have a Vera and Hue hub all reliably controlled by openLuup with AltUI, plus any number of plugins. Been working really well for a few years now. However would like to head for a more MQTT based set up. Eliminate the Hue hub and hopefully eliminate Vera by using ZWAVE JS UI. Noting that Zwavejs2mqtt has been renamed to Z-Wave JS UI. Probably also run the stuff using Docker. Just because. Everything would end up on the one computer for easier management. Erhhh that's the hope.

Some of the new Zigbee Aqara stuff is very good and inexpensive plus it fits in with HomeKit. Also the Aqara battery powered stuff looks to have a good battery lifetime: ie suggested up to five years. The battery operated Hue buttons I have; have lasted for ages. Would like to use zigbee2mqtt with a SonOff dongle, which would allow access to the over two and half thousand devices zigbee2mqtt now supports:

| Zigbee2MQTT

AK has the MQTT stuff working in openLuup. Have played around with it and it works well, as one would expect. Love the UDP to MQTT code.

Shellys are great and also very inexpensive and they spit out & accept MQTT but I would prefer to stay away from WiFi. Not meshed and higher power consumption. Horses for courses.

Now here's the query:
Got about forty or more ZWave twin light switches, plus a few other ZWave bits & pieces such as blind controllers. Then there are the Hue devices on top of that. That's a lot of virtual devices to set up in openLuup. What's an appropriate way to do this?

It seems there is no "auto magic bridge set up". Do I need to use say @therealdb's Virtual Devices plugin that supports MQTT or is there some other approach?

I have to confess I still don't understand the master child approach in that plugin. Seems one light switch would have all the other light switches hanging off it? Helps Vera but not a problem with openLuup - why is that? Suspect AK's good coding beats Vera's?

dbochicchio/vera-VirtualDevices dbochicchio/vera-VirtualDevices

Virtual HTTP Devices plug-in for Vera and openLuup - dbochicchio/vera-VirtualDevices

Setting up manually say 100 virtual devices is a bit much to ask. I had a look at hacking the user_data.json file. Good approach till you see all the UIDs and the individually numbered ControlURL and EventURLs that need to be set up.

I need some way of say of creating about 80 light switches in "No room" or in say the "ZWave upgrade" room. Or say some sort of code that could go through all my existing bridged ZWAVE devices in openLuup and create virtual devices for each one. I caould then use the openLuup console to name them and place them in their rooms:

openLuup_IP_address:3480/console?page=devices_table

At that point I could hack the user_data.json file to insert the MQTT topics fairly easily for each? Plus any other fine tuning needed.

Then the old ZWave stuff could be swapped over to ZWAVE JS UI and all the virtual MQTT devices would be ready to go or am I dreaming? Then delete all the old Vera bridged stuff. I'm not too fussed about scene code and the like, as a I have all my code in one block, that is set up in the openLuup start up.

It seems that with ZWay you can create all the ZWave device by doing some sort of interrogation of ZWay's API? Seems also to be the case with the Shelleys?

So any ideas, suggestions or code snippets are welcome on how to move towards MQTT and in particular ZWAVE JS UI and zigbee2mqtt.

I'm in no hurry as openLuup is performing nicely, with the old Vera handling all my ZWave devices.

With Raspberry Pi boards continuing to be relatively scarce, I've been trying a few alternatives to see what may be usable and good. I had previously written about the Jetson Nano 2GB, which is great, but a little pricey, so I'm trying to find sub-US$100 boards that will run Reactor.

I've got four that I'm trying now, but one in particular goes right to work in the most predictable way and seems worth a mention immediately: the Libre Computer Board AML-S905X-CC 2GB (known as "Le Potato").

The form factor is very similar to that of the Raspberry Pi 3 B+, and has comparable CPU (ARM Cortex-A53, quad 64-bit cores at 1.5+GHz -- slightly higher clock speed). It's US$35 on Amazon and LoverPi in the (recommended) 2GB configuration, and easy to get.

Startup is like RPi: download one of the available OS images (Ubuntu, Raspbian, Debian, ARMbian, etc.) from their site and write the image to a MicroSD card, insert into slot, power up, and off you go. I tried the Ubuntu 22.04 image first and it comes right up. No problem getting nodejs 18.12.1 installed and running (with Reactor).

No WiFi on board, but I don't see that as a minus for use as a controller/hub (which should be hard-wired, IMO). The 40-pin GPIO connector is compatible with typical RPi HATs (PoE, breakouts, etc.).

There is an available eMMC (solid state storage) module to use instead of MicroSD, which I would recommend for long-term use. It runs US$25 for 32GB (64GB and 128GB available). The module is scarcely larger than the chip it carries, and has the smallest board-to-board connector I've ever seen.

Next up: ESPRESSObin 2GB (spoiler: it's... technical...)

EDIT: Seems related to any restart without any configuration changes. If I revert to 22310 I can restart Reactor from UI and with systemd within seconds, but with 22328 it fails to restart., both from UI and systemd. I have to stop the service and then start again.

I tested to comment out my http (not https) baseurl in the config on my bare metal Ubuntu install latest-22328 and triggered a restart from the UI but Reactor would not start after that.
If I uncomment the key and restart the service, Reactor comes back to life.
Is my setup an exceptional circumstance or is this only applicable on new installs?

Virtual HTTP Devices plug-in:

I wanted to try this out. Installed the plugin and created one device, which came up as a light bulb. So far so good. In AltUI I clicked on the On/Off slider on the page. The log shows that the Target is set to one. Likewise for the Variable list in AltUI. However the Status never gets set to one and the light bulb icon doesn't go yellow.

In some plugins you set the Target and then the plugin checks the physical device actually went on by checking an actual status report from the device, which can be used to set the variable Status.

In other cases a plugin will send a message to the physical device but that device will have no status feedback mechanism available. So the Status variable has to be set locally when the Target is set and everybody hopes the physical device all worked.

Not to sure what Virtual HTTP Devices plug-in does in this regard? Does the above go in anyway to explaining what I'm seeing? Is the plugin looking for status feedback?

Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.

Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.

So it was time to update MSR (and then HA but I got stuck here)
Can't figure out what I have missed.

My installed version of MSR was 22240.
Node.js is version 16.15.1

First I tried to update, following online manual.

Spoiler

Download a Reactor distribution ZIP from https://reactor.toggledbits.com/download/ and place it in the folder above your existing reactor (runtime) directory.
Stop and remove any existing Reactor service:

cd \path\to\reactor
node tools\install_reactor_windows_service.js -u .
Remove any existing package-lock.json file from your Reactor directory.

Unzip the archive file and copy its contents over the contents of your existing Reactor install directory.
From the Reactor install directory, re-install/upgrade all package dependencies:

npm install --no-save --omit dev
If you are running Reactor as a Windows service, repeat those steps above.

Restart Reactor (restart the service).
Hard-refresh all browsers that are displaying Reactor content.

I found several (maybe it was 3) package-lock.json and I deleted all I could search in reactor folder.
Unzip the new version and replaced old existing files.

Install the reactor service again by instructions.

Spoiler

In a command prompt window, running as Administrator, change directory to your Reactor install directory.
Install the node-windows package as a global package (it must be global or the service will not work, and you must install the specific version provided by the command below):

npm uninstall node-windows
npm uninstall -g node-windows
npm install -g node-windows@1.0.0-beta.6
npm link node-windows
Run the script to install:

node tools\install_reactor_windows_service.js -i .

So this failed. Service wont start.

Tried again.

Then deleted everything exept my config folder and did a new install.
Also downloaded 22310 again, but from "latest" build instead of "stable"
When running node app.js in command promt i get some kind of error message:

c:\reactor>node app.js Reactor latest-22310-a6da8097 app 22310 configuration from c:\reactor\config NODE_PATH C:\reactor [latest-22310]2022-11-23T22:18:43.030Z <app:null> Reactor build latest-22310-a6da8097 starting on v16.15.1 c:\reactor\app.js:277 log['always'](a0_0x3d42be(0x26a), BUILD_VERSION, process['version']), log['always']('Process\x20ID\x20%1\x20user/group\x20%2/%3;\x20%4;\x20platform\x20%5/%6\x20%7;\x20locale\x20%8', process['pid'], process[a0_0x3d42be(0x269)](), process[a0_0x3d42be(0x278)](), is_docker ? 'docker' : a0_0x3d42be(0x288), process[a0_0x3d42be(0x287)], process['arch'], os[a0_0x3d42be(0x263)](), sys_locale), log[a0_0x3d42be(0x28c)]('Basedir\x20%1;\x20data\x20in\x20%2', c[a0_0x3d42be(0x1f8)], c[a0_0x3d42be(0x27b)]), log[a0_0x3d42be(0x28c)](a0_0x3d42be(0x21b), process['env'][a0_0x3d42be(0x291)]); ^ TypeError: process[a0_0x3d42be(...)] is not a function at Object.<anonymous> (c:\reactor\app.js:277:226) at Module._compile (node:internal/modules/cjs/loader:1105:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) at node:internal/main/run_main_module:17:47

But I can't figure out what TypeError means?

Also, before I tried a new install, there apperd an warning when installing reactor service.

c:\reactor>npm install -g node-windows@1.0.0-beta.6 npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. added 5 packages, and audited 6 packages in 3s 2 vulnerabilities (1 moderate, 1 critical) To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details.

Running npm audit fix --force seems to broke something, because I could not install service after that.

c:\reactor>npm audit fix --force npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. npm WARN using --force Recommended protections disabled. up to date, audited 89 packages in 826ms 12 packages are looking for funding run `npm fund` for details found 0 vulnerabilities c:\reactor>node tools\install_reactor_windows_service.js -i . node:internal/modules/cjs/loader:936 throw err; ^ Error: Cannot find module 'node-windows' Require stack: - c:\reactor\tools\install_reactor_windows_service.js ←[90m at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m ←[90m at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m ←[90m at Module.require (node:internal/modules/cjs/loader:1005:19)←[39m ←[90m at require (node:internal/modules/cjs/helpers:102:18)←[39m at Object.<anonymous> (c:\reactor\tools\install_reactor_windows_service.js:102:15) ←[90m at Module._compile (node:internal/modules/cjs/loader:1105:14)←[39m ←[90m at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)←[39m ←[90m at Module.load (node:internal/modules/cjs/loader:981:32)←[39m ←[90m at Function.Module._load (node:internal/modules/cjs/loader:822:12)←[39m ←[90m at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)←[39m { code: ←[32m'MODULE_NOT_FOUND'←[39m, requireStack: [ ←[32m'c:\\reactor\\tools\\install_reactor_windows_service.js'←[39m ] }

Is anyone actively developing anything on these IoT chips?
In particular, using NodeMCU for Lua programmability?
Just got a development board to play with myself...

After a fruitless search for WiFI pulse utility meter readers (can't believe I couldn't find anything suitable) and also having resolved a while ago not to include any homebrew hardware in my HA configuration, I've decided in the end to try this out, after all.

Having cut my teeth on Lua, thanks to Vera, it seems promising to use it for development, rather than Arduino programming, and the hardware is SO much cheaper, smaller, and neater than a RPi or the like.

Any experiences welcomed!

AK

A long while ago (May, 2015) I wrote my 2000-th post on another forum: openLuup - running unmodified plugins on any machine. Here’s the gist of it:

...I want to work in a more open and stable [Vera] environment...

...All would be solved if Luup was open source and could be run on the plethora of cheap and reliable hardware available today. But it’s not. But we could get something like that effect if we engineered a sufficient subset of Luup to run on such a platform. Could it be done? What would we need?

1. UI
2. scheduler
3. web server
4. Luup compatible API
5. Device and Implementation xml file reader
6. Zwave bridge to Vera
7. runs most plugins without modification

What we wouldn’t need is UPnP.

What have we (nearly) got already?

We have, courtesy of @amg0, the most excellent AltUI: Alternate UI to UI7, and that, I think, is probably the hardest one to do in the above list. Items 2 - 5, and 7, I’ve prototyped, in pure Lua, and posted elsewhere: DataYours on Raspberry Pi, running selected plugins unmodified, including: DataYours, EventWatcher, Netatmo, RBLuaTest, altUI. See screenshot attached.

Is it worth the effort? Probably not. Will I pursue this quest? Yes.

openLuup was the result.

DE2056BF-E548-4611-972B-40276F00BFEB.jpeg

Hello All -

I'm still working on moving dozens of devices from Vera (internal Reactor) to HASS and (external - bare metal) Reactor.

One thing I've noticed is sometimes I move a few ZWave/Vera devices and find myself digging through rules finding where a device was used. Has anyone found a good way to do this?

I plan on digging in to this thread but thought I'd check to see if there's anything more recent.

https://smarthome.community/topic/483/entities-where-used-and-what-triggered-it?_=1669137134654

Hass: 2022.11.3
Hardware: Pi
MSR: latest-22310-a6da8097

I'm trying to use MSR in automations to change the page displayed on a wall tablet (Windows and Edge in Kiosk mode)
Example use would be motion detected will change to the security dashboard, or heating turns on, shows the heating dashboard.

Screenshot_20221122_193138.png I have Browser Mod installed and working and the entities are present in MSR. My only option for the entity which controls the page/dashboard displayed is "x_hass.call_service"

What I need to change is the state of the entity
state.png state2.png

Is this possible in MSR? Despite much searching i'm unsure what service to call to set the state?

I have tried using service: browser_mod.navigate but get an error
(this service detailed here https://smarthomescene.com/guides/how-to-setup-browser-mod-2-0-in-home-assistant/ )
error1.png

Also trying to lay the data out like this with/out quotes and other variations has not helped

{ "/home-overview/heating" }

Here's my second attempt at a Reactor Controller, this time to integrate LG TVs:

GitHub - dbochicchio/reactor-lgtv: Reactor controller for LG TV (webos) GitHub - dbochicchio/reactor-lgtv: Reactor controller for LG TV (webos)

Reactor controller for LG TV (webos). Contribute to dbochicchio/reactor-lgtv development by creating an account on GitHub.

Standard capabilities are provided and TV volume, mute and switch status are controllable.
There's also an action to send toast notifications on your TV.

webos 5+ is required.

I've moved many of my MQTT devices to Reactor, so I've coded a couple of templates and I'm publishing them for anyone in the same boat:

GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor

Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.

I'll add more in the future, since I still have a couple of things running in my own bridge that I'll eventually move to Reactor with dedicated templates.

Let me know if you need other templates, I'll probably add a couple more for Shellies (button as scene controller and i3/i4 as scene controller).

Hi all

Looking for some ideas about how I might be able to automate my lights.

Currently I have Fibaro FGMS001 (combined lux / motion / temperature sensors)

I can currently get the lights to come on in a room by simply implying that lux <100 and the movement sensor is tripped. That's not so bad, although it's a bit crude.

Struggling more with:
Keeping them on: I've turned the motion sensitivity up quite a lot, but when (fore example) reading in bed, they trip off
Extending a timer (so there's a minimum time of 'on' after trip) needs to get quite high, such that you might be in a room for 10 seconds, and the lights stay on for 20 minutes.

Any bright ideas?

Cheers

C

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!

Before I'll open a feature request, I want a reality check, because this is maybe achievable in other ways.

Long story short: I want to react to a device in quasi-real time, but 15 or 30 secs are enough (and will prevent the rule from throttling). Right now, I've moved to 1 min, but it's obviously too late to catch all the variations. 15 secs or 30 are OK, so my first reaction to circumvent this limitation was to host the timer myself and send it via MQTT, but it's obviously a not welcome complication.

So, @toggledbits, is there any reason the minimum interval is 1 min and/or do you have any suggestion for my use case? Thanks Patrick!

HI
I have a smart plug (one of many) that has the annoying habit that no matter what the condition it is in, if Openluup restarts, the plug turns on.
Any suggestions as to where I can look to correct this (i.e. I'd like it to go into its previous condition like everything else does....

TIA

C

I'm still trying to fully wrap my brain around Pulsing. Let's see if I have it:

2a1da895-5170-499f-a1ff-708d3ded1f5c-image.png

I believe this to indicate that this will wait five minutes, do the thing, wait five seconds and repeat.

Backstory: this is a reset ruleset for my HVAC. Sometimes Honeywell is finicky about taking the original commands so this should follow along and submit a retry after five minutes... continuing until the setting is accepted.

a24c656e-b5d1-4e22-b774-517184e70792-image.png

I have a couple of issue with Openluup ATM. I'm going to work through them in the order that they appeared if that's OK 🙂

OpenLuup on bare metal (Debian Bullseye) running Z-way server and Z-wave.me

Issue:
I deleted a (I think) virtual switch in OpenLuup
Now when I call up all devices I have this in a 'tile'

Error displaying device 0-20510 - urn:schemas-upnp-org:device:BinaryLight:1 nil is not defined

And below (in room 101)

ReferenceError: nil is not defined at eval (eval at evaluateConditions (http://192.168.70.249:3480/J_ALTUI_verabox.js:960:18), :1:1) at Object.evaluateConditions (J_ALTUI_verabox.js:960:18) at Object._evaluateConditions [as evaluateConditions] (J_ALTUI_verabox.js:1642:37) at Object._evaluateConditions [as evaluateConditions] (J_ALTUI_multibox.js:629:89) at Object. (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2572:23) at Function.each (https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js:2:2976) at _getDeviceIconPath (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2569:10) at _deviceIconHtml (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2739:18) at _internalDeviceDraw (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2765:19) at _deviceDraw (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2840:4)

Any ideas from anyone?

Full reboot has been done....

Cheers

C

Hi @toggledbits !!

Would it be possible to improve the error messages, and instead of showing the "technical name", show the name we assigned to the rule?

a8298689-0c7b-43ef-a582-16baece4e4d1-image.png

In the above case, I have no idea what rule is causing the problem.

Thanks.