Best posts made by kfxo | Smart Home

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

@akbooer said in Moving to Docker:

but I can't access it at all or work out where the openLuup files go.

You are using the synology docker package to create and deploy your container, correct? At minimum, to get the container accessible, change the port settings to 3480(local):3480(container). Then you should be able access it at http://YourSynologyIP:3480/

kfxo

@rafale77 It does allow you to subscribe.

You can subscribe to a topic by creating a child device :

Add a new device and choose a type (e.g. "D_BinaryLight1.xml" or "D_TemperatureSensor1.xml").
Reload LUUP engine.
Change the attribut "id_parent" with the id of the MQTT plugin device.
Reload LUUP engine and refresh your browser.
You should see variables "mqttTarget" and "mqttTopic" in your newly created device.
Set the topic you want to subcribe to and the target (format: service,variable=(formula in LUA)).
Reload LUUP engine.
If the payload of the received message is in JSON, the plugin will try to decode it and put it in the variable "payload" in the context of the LUA formula.

kfxo

@therealdb said in Multi-System Reactor Developer Preview AVAILABLE:

Can't wait for guidance on apdaters/plugins to contribute with Shelly and MQTT

MQTT will be huge.

kfxo

@akbooer said in Moving to Docker:

I understand that to make any changes last across container/NAS restarts, I need to make the volumes external to the container, as per the above yaml. So this is my next step.

Any further insights welcomed. Perhaps Portainer is that next step?

You cannot create named volumes through the synology GUI. You will need to use portainer or you can ssh into your synology and run the manual commands as outlined by vwout/openluup

You can also do this manually. Start by creating docker volumes:

docker volume create openluup-env
docker volume create openluup-logs
docker volume create openluup-backups

Create an openLuup container, e.g. based on Alpine linux and mount the created (still empty) volumes:

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

kfxo

@rafale77 Have you seen this mqtt plugin? i have been using it to subscribe to topics for some time. Maybe it has some hints as to your issue.

kfxo

@cw-kid said in Sunset with offset didn't run:

Also I have seen this saving problem on more than just one rule.

I've seen in on a few rules when either adding items like additional triggers or removing items.

Then you cannot click either of the two save buttons.

Only the red exit w/o saving button works.

I have been able to possibly reproduce your saving issue. I have noticed with rules that have a Date/Time After Trigger cannot be modified and saved.

kfxo

I think I had this same issue. If you copy the files in cmh-ludl from an existing openluup install into ' /OpenLuup/openluup-env' it should start right up.

kfxo

@kfxo said in MSR in Alpine Docker:

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

Just an update, I copied over config and storage directories to the mounted docker volume and Reactor would not start until I also created a 'logs' directory in the mounted docker volume. All looked well after that but going to continue to run it on my Debian VM for now.

kfxo

There is a post from me above in this thread (sorry don't know how to link specific post) that explains how I got it to work. Have you tried that? I think the issue is synology gui does not support the correct type of volumes and you have to ssh into synology and run the correct docker command to set it up.

kfxo

That actually makes perfect sense and upon further inspection I see that the timers I was noticing in the logs are with respect to one rule that I had recently turned on that resets often.

kfxo

Reactor-Editor / Reactor-ui-Status Errors

every X days field uneditable

[Reactor] Use VirtualEntityController actions to drive a Reolink spotlight

Darker Reactor style

Which user to install nodejs as ? Debian Linux

Reactor (Multi-System/Multi-Hub) Announcements

OpenAI Controller for Reactor

Thanksgiving lighting took a holiday

[How-to] Managing holidays in Reactor

Reference error - null object

Trouble Configuring Multi-System Reactor Logic Across Devices

openLuup email server

MSR UI on a mobile browser

ZWaveJSController - Warning/Error Traceback - Registering action set volume for Aeotec Siren 6 (ZW164)

High temperature sensor for Zigbee

New to Home Automation Looking for a Single app?

UZB/RaZberry Firmwares - Update

Sending data to a USB port to interface with a wireless switch

Seeking Advice:

[Reactor] Assignment to alarm ignored -- expression-driven global cannot be set by assignment

Posts