Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
D

dcmChrissy

@dcmChrissy
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
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.
Multi-System Reactor
Notice to Docker + ARM Users (RPi 3/4/5 and others)
toggledbitsT
This post does not apply to users of Intel/AMD-based systems. If you are using a Reactor image tagged latest-amd64 or stable-amd64, then this post does not apply to you. It also does not apply to bare-metal installs; it's for users of docker images on ARM-based systems only (principally Raspberry Pi hosts, but could be others). After January 15, 2026, I will no longer produce the aarch64-tagged docker image for Reactor. The ARM images will be arm64 for 64-bit operating systems, and armv7l for 32-bit operating systems. For those of you running a container from the aarch64 image today, this will be a relatively simple change: you just need to switch the image used for your docker container to a differently-tagged image. If you are using docker-compose, then this is a relatively simple matter of changing the image line in your docker-compose.yaml file and then stopping (docker-compose down) and restarting (docker-compose up -d) your Reactor daemon. But there's a catch... not all of you can safely just switch from the aarch64 image to the arm64 image. And, you can't just trust the output of uname -m, for example, because this exposes the CPU architecture, but not the word size of the OS running on that CPU. For Raspberry Pi systems, the transition to 64-bit operating systems was long (starting in 2016) and not always obvious — although there was a first "official" 64-bit OS for RPis in 2020, it did not become a default recommendation in the Raspberry Pi Imager until 2021, and then that was only the default for Pi 3/4 systems with >4GB RAM; it was 2022 before it was universally recommended for all 64-bit CPUs regardless of RAM size. Depending on when you first imaged your RPi system and what default you may have been offered/chosen, you could today easily have a 64-bit CPU Raspberry Pi running a 32-bit version of the operating system. Upgrades along the way would not change this; changing it to fully 64-bit requires a full reimage of the system. To establish if your OS is 64- or 32-bit, log in to your Pi and run: sudo dpkg-architecture -q DEB_HOST_ARCH. If the response is arm64 or aarch64, then you are running a 64-bit OS and you should use the arm64-tagged image. If it's anything else, you are running a 32-bit OS, and you should use the armv7l-tagged image. pi@rpi4-1:~ $ sudo dpkg-architecture -q DEB_HOST_ARCH armhf pi@rpi4-1:~ $ uname -m aarch64 pi@rpi4-1:~ $ In the example above, the uname command reports that the CPU is 64-bit architecture (aarch64), which is true for the host on which I ran these commands, but the DEB_HOST_ARCH value is armhf, indicating a 32-bit operating system. This system has to use the armv7l-tagged image. Other systems will have their own ways of determining the word size of the running OS. Since the majority of Reactor users running ARM systems are on Raspberry Pis, I am able to supply the above instructions, but if you happen to have a different ARM system, you'll need to do some web searching to figure out how to expose that information. Or, you can just try the arm64 image, and if it doesn't start up, try the armv7l image. Remember to always back up your system before making any changes. For everyone, please make this change as soon as possible, and if you have any trouble finding a working image, please (1) go back to the current aarch64 image; and (2) let me know in this thread along with as much detail about your host system as you can offer (including the output of the dpkg-architecture command mentioned above).
Multi-System Reactor
Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
M
Hi, I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available. None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5. Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image? Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way: docker buildx build --push \ -t <localrepo>/<project>:<tag> \ --platform=linux/arm64,linux/amd64 \ --file ./apps/<project>/Dockerfile . This produces both the AMD64 and ARM64/v8 variants automatically. Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications. @toggledbits - tagging you in case you missed this. Thanks, mgvra
Multi-System Reactor
Script action and custom timers
therealdbT
Sorry to write here without trying, but I’m flying today. Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes? That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Multi-System Reactor
Help resolve change in behaviour post update
CatmanV2C
Topic thumbnail image
Multi-System Reactor
There is an alternative to homebridge-mqttthing
CrilleC
Just throwing out a general hint to the people running Homebridge and MQTT. Homebridge MQTT-Thing hasn't been updated in almost 2 years and it falls behind on compatibility with the development of Homebridge. I was looking for a replacement and found Homebridge Easy MQTT and I think it's a good replacement for MQTT-Thing. I particularly find Easy MQTT Value tranformers easier to to understand and use compared to MQTT-Thing Apply function. It took a while to migrate everything but I'm pleased and can recommend.
Software
Reactor w/HA 2025.11 error on set_datetime service call setting only time
CrilleC
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1? [latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } } [latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed! [latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320} [latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1 [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } } [latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed! [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323} [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2 [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Multi-System Reactor
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
Shelly Wall Display XL
therealdbT
I don't know if you guys are into dashboards, but I am. For a second home I tried the Shelly Wall Display 2, and while not so big, it worked well over the summer. Since we're remodeling our house, I just swapped my old Fire Tablet (with its own problems) with two new Shelly Wall Display XL. I just removed the standard firmware, and I added mine (https://github.com/dbochicchio/ShellyElevate), forked from https://github.com/RapierXbox/ShellyElevate I just managed to support buttons (this thing has 4 of them) and it's all auto-discovered by Home Assistant and accessible via Reactor. I also have a new build in the works with support for buttons inside HA. I added a bonus Javascript interface sending events (screen/screensaver status, buttons, motion) to automatically drive the dashboard (all doing in HTML+Javascript and monitoring Reactor's variable). This specifical thing excluded, go get one of them, the device has a decent CPU for HA dashboards and blends wonderfully in the decor.
Hardware
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
Topic thumbnail image
Multi-System Reactor
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor
Strange behavior in MSR latest-25304 with disabled groups in Reaction
therealdbT
Topic thumbnail image
Multi-System Reactor
Do you Matter?
akbooerA
Is anyone using the Matter protocol to connect devices?
General Discussion
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Caution: zwave-js-ui docker 11.4.0 is broken
toggledbitsT
About 20 hours ago, the author of zwave-js-ui posted build 11.4.0 of that product, and it contains an error and won't start (at all) under docker. The author is aware and working on a fix. In the meanwhile, stick with 11.3.1 or earlier. Ref: Issue 4401
Software
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
About
Posts
15
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • MIOS - UI5 web login
    D dcmChrissy

    After a long (8+ months) period of non-access, I am again able to login remotely through mios. Believed (unconfirmed) the issue was a redirection to fwd4 vs. fwd3 which was my previous default. I can currently successfully test by:

    1. Browsing to https://status.getvera.com/
    2. Under Portal (Legacy - UI5) clicking the "Login & User Accounts" link redirects to my Vera 3 (UI5)
    Keep in mind that this did NOT work for the longest time. I tried a few Tech Support tickets via the Vera and also a plea on their forum. For the heck of it, I tried to access via status.getvera.com and one day I was surprised that it works again (but now using fwd4)

    Also, the less secure link via ALTUI of:
    https://fwd4.mios.com/USER/PASSWORD/ACCESSPOINT/data_request?id=lr_ALTUI_Handler&command=home#

    . . . works again.

    ![UI5-RemoteLogin.PNG](Something went wrong while parsing server response)

    (Unable to upload screenshot .png at this time)
    EDIT: perhaps not enough posts to allow me to "Upload Image"

    General Discussion

  • (Tip) Pushover and Original Reactor using openLuup / ALTUI
    D dcmChrissy

    @toggledbits
    Thanks!
    Testing and manual typing of the custom sound names works great!
    Chris

    Vera/openLuup plugins

  • (Tip) Pushover and Original Reactor using openLuup / ALTUI
    D dcmChrissy

    UPDATE: With @toggledbits update for "R4V" below, your new notification sounds will work just by typing your custom soundfile name into the Sound: field of the Notify Action. Editing the J_ReactorSensor_UI7.js is not an undertaking for the simple user 😲

    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

    Vera/openLuup plugins

  • AltUI/Reactor issue?
    D dcmChrissy

    @perh
    No, I did not notice. I guess I would have realized it the next time I wanted to look at a logic summary!

    Crap

    Guess I should figure a way to roll back . . .

    On Chrome by the way.

    openLuup

  • AltUI/Reactor issue?
    D dcmChrissy

    @mrfarmer
    May be related.
    Occasionally, (indeed happened on the latest ALTUI update), after updating ALTUI, a Reactor will lose the buttons at the bottom. The picture below attempts to illustrate.
    Reactor Devices.PNG

    At this point, I do not dig into the reactor UI to see any other oddness like (maybe) the screenshots posted above. Instead, when I see this, I'll reset ALTUI by . . .
    Reset ALTUI.PNG

    Reload & refresh the luup engine / browser, and Reactor is back to normal.

    . . . Just a guess
    DCMChrissy

    openLuup

  • openLuup: Windows Subsystem for Linux (WSL)
    D dcmChrissy

    @akbooer
    Great! Pretty simple, thank you for the instructions!

    Already had WSL enabled, although an older version.

    I downloaded & installed the Alpine WSL from the windows store.

    Starting the app presented the terminal window.

    Trying to install the packages . . .
    $ apk add [package name] gives a permission denied error

    error.PNG

    If I su and then install the packages from the # prompt, they install.

    Following the rest of the steps from a $ prompt work as you instructed, including manually adding the vera bridge and updating openLuup to your development branch.

    openLuup runs great, but GetVeraFiles always download zero byte png files in the /icons folder (ongoing problem for me on all of my recent openLuup installs) A "permissions" problem? Even though I never change any permissions unless instructed in your install instructions.

    Love the local access to the cmh-ludl tree!

    Again, thanks
    DCMChrissy

    openLuup

  • Massive discounts on Shelly for black friday
    D dcmChrissy

    Thanks,
    Took advantage of the discounts at the Shelly USA store. (i3 dual pack)
    Chris

    Hardware

  • Move UZB from Windows 10 to RPi 3 (Buster)
    D dcmChrissy

    Just a follow-update . . .
    Installed the razberry package with no issues.
    API key carried over without having to re-enter.
    Did have to force interview which worked for 2 powered devices, but failed with a battery PIR (Monoprice)
    Excluded then Included the PIR & the interview process completed.

    Installed the openLuup Z-Way plugin (master), followed instructions.
    Bingo!
    Neat.

    A good practice exercise for me, but turns out to be possibly temporary.
    The mentioned mini-PC options in this thread are drawing me to a more reliable solution.
    @mrFarmer, thanks for the tip, if I stay on the Pi3, I'll definitely add the SSD drive.

    Best,
    DCMChrissy

    Z-Wave.me

  • Telegram Plug-in to send text, images and video notifications
    D dcmChrissy

    @therealdb
    Sorry db, thanks PerH - 'nuff said, properly chastened
    😬

    Plugins

  • Telegram Plug-in to send text, images and video notifications
    D dcmChrissy

    @toggledbits
    I've got something similar. Running ALTUI 2.50.2549 (from the bottom banner)
    Installed the Reactor.stable branch for the Pushover enhancements.
    Oddly, although my Plugins tab for Reactor reads GitHub.stable, my Reactor Logic Summary page notes:

    Version: 3.9develop-20318.1220 config 20263 cdata 20045 ui 20190 pluginDevice 98 LuaXP 1.0.2enh

    Reactor_Display.PNG

    Plugins

  • Move UZB from Windows 10 to RPi 3 (Buster)
    D dcmChrissy

    Amazing and almost endless choices / configurations are available.

    Z-Wave.me

  • Move UZB from Windows 10 to RPi 3 (Buster)
    D dcmChrissy

    @perh
    Thanks for the tip!

    O.T. those Gemini Lake boxes look way cool

    C

    Z-Wave.me

  • Move UZB from Windows 10 to RPi 3 (Buster)
    D dcmChrissy

    @rafale77
    Thanks for the pointers!

    The RPi system running on a Micro SD is certainly NOT optimal as the card is bound to fail eventually.

    I've been practicing with various Debian builds (including a Raspbian image) running on several VirtualBox VMs to help me get more comfortable with Linux.

    Although I'm getting familiar with the Linux os CLI (and there's always google), I'm still too inexperienced with the networking part of it and need a LOT more learning / practice.

    My end goal is to have a 24/7 mini PC with Linux.

    Again, Thanks

    DCMChrissy

    Z-Wave.me

  • Move UZB from Windows 10 to RPi 3 (Buster)
    D dcmChrissy

    First Post . . .

    Good to "see" y'all here!

    Last week, I purchased the Z-Wave.me UZB1 dongle and also purchased the Z-Way license.

    Knowing in advance that the combination (Windows 10 and the Z-Way server) was lacking, I wanted to install anyway on a Windows 10 machine, and include a few spare z-wave devices to see how things worked. Pretty well, for the most part.

    @rafale77 had written that the UZB stick works well in the RPi compared to the RaZberry card (which I also purchased but is still in it's packaging), I would like to plug this UZB1 into my Pi running openLuup/ALTUI (then hopefully installing the Z-Way plugin)

    I'm not confident enough yet to plug the UZB into my Vera3 (UI5) and transfer my existing z-wave devices to the stick.

    Without creating a new Buster image downloaded from Z-Way, could I possibly . . .

    1. Plug the UZB1 into the Buster Pi3
    2. From the terminal, run,
    wget -q -O - razberry.z-wave.me/install | sudo bash
    

    then, if I can reach the :8083 port (as quoted by PoltoS) "go to Settings -> Apps -> Active -> ZWave and change /dev/ttyAMA0 to /dev/ttyACM0"

    and expect that my UZB1 will now run on the Pi ?

    If it is mostly that simple, would my license transfer?

    Should I exclude the (3) z-wave devices I had running on the Windows 10 Z-Way server first?

    If I'm oversimplifying, tell me to "shut up" and read some more! 😕

    Thanks again,

    DCMChrissy

    Z-Wave.me
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved