SmartHome Community

kfxo

Night and day difference for me. I think I was getting a lot of interference in my media closet. Devices were very slow to respond and sometimes not at all. Switched to UZB and used a USB extender to place it a good 5 ft from the location of my pi. Now things are fast and reliable.

kfxo

@akbooer
I have been messing with this today. I do not currently run openluup through docker so this may not even be the best way to do this but it is what I did to get it up and running and with the ability to easily see and manipulate all openluup files within "File Station" on the synology.

I created three folders on my synology:
/docker/openLuup/cmh-ludl
/docker/openLuup/logs
/docker/openLuup/backups

Then I created three volumes with a bind to the created folders
'openluup-env' bound to '/volume1/docker/openLuup/cmh-ludl'
'openluup-logs' bound to '/volume1/docker/openLuup/logs'
'openluup-backups' bound to '/volume1/docker/openLuup/backup'

I used portianer but you can ssh into your synology and use the command line to create these volumes with the binds, see this

Then I created the container using portainer making sure to set the correct ports and volume mappings, which can also be done in the command line with

docker run -d \
       -v openluup-env:/etc/cmh-ludl/ \
       -v openluup-logs:/etc/cmh-ludl/logs/ \
       -v openluup-backups:/etc/cmh-ludl/backup/ \
       -p 3480:3480
       vwout/openluup:alpine

Hope this helps.

Edit: The binds are not necessary, I only did it to make it easy to access the files. Without the bindings, the volumes are somewhat hidden on synology that is not easily accessible for example at '/volume1/@docker/volumes/openluup-env/_data'

kfxo

@akbooer said in Delete all device in Room 101:

Yes, absolutely (although I kind of wonder how you reached that figure...!)

The openLuup plugin has an action EmptyRoom101 with the parameter named AreYouSure which requires the value yes (to save nasty accidents.)

Thanks. I see it. They are all old verabridge devices ( and some z-way devices that I had to repair) that are no longer needed as I am fully cloned to z-way and mostly vera free (still have two zigbee door sensors on vera).

kfxo

Parameters of devices can be set through the api using this URL

YOURIP:8083/ZWaveAPI/Run/devices[DEVICE#].instances[0].Configuration.Set(PARAMETER,PARAMETER_VALUE,size=PARAMETER_SIZE)

Replace:
YOURIP with the IP of Z-way for example 192.168.1.2.
DEVICE# with the Z-way device # of the devices parameter you want to change
Parameter with the parameter # you want to change
VALUE with the Parameter value
PARAMETER_SIZE with the size of the parameter (should be 1, 2, or 4)

An example to change device 51's parameter 3 to a value of 1 with a size of 1:

192.168.1.2:8083/ZWaveAPI/Run/devices[51].instances[0].Configuration.Set(3,1,size=1)

To run it in Luup code

local status, result = luup.inet.wget("192.168.1.2:8083/ZWaveAPI/Run/devices[51].instances[0].Configuration.Set(3,1,size=1)", 5)

kfxo

@toggledbits said in MSR in Alpine Docker:

OK. Let's see how this does in your hands. I've installed and uninstalled 3-4 times and it seems OK. In the bug tracker, go to #58, in the notes you'll find a download link and draft installation instructions. You can use the "monitor" function to follow that PR (emails you when things are posted--might get chatty with a lot of people in there, though). Please use that PR for reporting install-related issues.

This loads up nicely. Running unconfigured right now. I will transfer over my configs later and test it out.

kfxo

Another good release. Confirming that 0000078 and 0000077 are tested and working on my system.

kfxo

@rafale77 said in Delete all device in Room 101:

Congrats on the move! Please report back on positive or negative effects.

Will do. Still working through things and figuring stuff out. So far, the experience has been mostly positive with a few minor hiccups. I also have some scripts I wrote that I plan to share that helped ease my transition.

kfxo

Which synology NAS are you looking at? I have a DS920+ and run MQTT in a docker container. Works great and easy to set up. Some of the lower end ones may not support docker.

kfxo

Spinning up a dedicated VM on my synology right now in anticipation of the first preview. Can't wait!

kfxo

@perh said in Imperihome - missing devices:

While i wait for a replacement app for my local UI devices, i want to use imperihome as long as I can.. But i'm missing a lot of devices!

All Z-Way bridge devices, all security/smoke and motion sensors (local RFXtrx child devices)..

Found the "include vera bridge" in imperihome.lua, what else could cause this?

I had the same issue. Check that the attribute "disabled" is not set to '1' for the missing devices. See this thread

kfxo

@toggledbits said in Integrate UPS with MSR:

Fixed now, 22152 build of NUTController available for download.

Confirmed fixed. Thanks.

kfxo

@toggledbits

Getting this error in the log when restarting Reactor after performing the installation steps for NUT controller. I am on Reactor 22149 installed on Ubuntu in Docker.

[latest-22149]2022-06-01T16:54:36.344Z <Structure:INFO> Structure#1 loading controller interface nut (NUTController)
[latest-22149]2022-06-01T16:54:36.345Z <Controller:CRIT> Controller: failed to load nut implementation /var/reactor/ext/NUTController/NUTController.js: [TypeError]TypeError: Incompatible base version; is 22125, requires at least 22145
[latest-22149]2022-06-01T16:54:36.346Z <Controller:CRIT> TypeError: Incompatible base version; is 22125, requires at least 22145
TypeError: Incompatible base version; is 22125, requires at least 22145
    at Function.requires (/opt/reactor/server/lib/Controller.js:327:19)
    at Object.<anonymous> (/var/reactor/ext/NUTController/NUTController.js:9:53)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:168:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:197:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:337:24)
[latest-22149]2022-06-01T16:54:36.346Z <Structure:ERR> Structure#1 controller nut (NUT) skipped, implementation could not be loaded.

edit: Fixed in build 22152. See below.

kfxo

@toggledbits said in Integrate UPS with MSR:

I use NUT on Linux (and I have a Reactor controller for it that I can publish). I know nothing about it on Windows.

I would be interested in trying out the NUT controller if you publish.

kfxo

@snowman said in Strange MSR behaviours after NAS reboots:

Interestingly, everything seems to be working like it should even if I don't do anything. Which is weird.

So everything ends up working but the visual errors persist? It would be unsettling seeing all those errors even though it works fine.

kfxo

My guess would be that home assistant is still loading when MSR starts and MSR is not seeing all the entities initially.

kfxo

Not sure what else to try as you already commented out the Influx. Maybe back up your MSR files and try a fresh install.

kfxo

The logs dont say anything else? If not I dont know and you might have to wait for @toggledbits

kfxo

Maybe the logs will have a clue? The other day I moved HA to a new computer and MSR was trying to connect to the old machine and MSR would not load. Sure enough the logs indicated that MSR could not connect to HA. Fixed that and all was well.

kfxo

Is it marked as failed in z-wave (z-way?) server? If you can reset the device without excluding it, I think you can use the replace failed node operation on the z-way server control section.

kfxo

This is off topic to the original post so maybe it should be moved but it is directed towards the Home Assistant event_targets discussed above.

I defined an event_target in my system for emulated roku that looks like this:

    event_targets:
      "LR_Emulated_Roku_Home_Keypress":
        name: "LR Emulated Roku Home Keypress"
        capabilities:
          - button
        events:
          - event:
              event_type: "roku_command"
              data:
                source_name: "LR_Roku"
                type: "keypress"
                key: "Home"
            response:
              "button.since":
                expr: "time()"
              "button.state": true

This works great, detects the event and stores the time and True in the respective button entity attributes. However upon restarting MSR the values of the button entity attributes clear to null (e.g. button.since=null).

Is this expected behavior or should these values be maintained on restart?

Constraints under triggers or under constraints, what is the difference?

Adding remotes, scene controllers as entities to MSR

The Home Remote with MSR

Condition must occur after -restriction not working

Reactor (Multi-System/Multi-Hub) Announcements

[Solved] Changes in 22178 for HASS sensor no longer provide a value in topic "value", MQTTController echo capability

Status of SMARTHOME and SwitchLinc products

Using InfluxDB with MSR

git hub docker container not available?

Synology NAS docker image replacement

Cheapest platform on which to run MSR

Copying configuraiton and rules from QNAP install to Raspberry PI 4 install

OpenLuup - problem with solar AZ and ALT variables?

Alexa TTS via Home Assistant?

Integrate UPS with MSR

Reactor as tab in Hass sidebar

Documentation>Network Status

MSR Upgrade from 22119 to 22136 fails, service wont start

[Solved] suninfo.period "night" and rule trigger for sunset are at different times

Status page rule history length.

kfxo

@kfxo

Best posts made by kfxo

Latest posts made by kfxo