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

CatmanV2

@CatmanV2
[Solved] Local expression in Rule does not evaluate as they used to do
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
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
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
About
Posts
1.1k
Topics
98
Shares
0
Groups
1
Followers
0
Following
0

Posts

Recent Best Controversial

  • New HA instance
    CatmanV2C CatmanV2

    I just wanted to post how impressed I am with both HA and MSR. I really don't see that Ezlo have a chance in hell.

    I noticed that my Virtual HA instance was killing my machine's performance, so decided that my project for the weekend would be a stand alone Raspberry Pi instance. Less than an hour to install, restore and configure both HA and MSR and it all just works. Thanks to everyone that contributes to these fabulous projects. Especially our own @toggledbits for the amazing work that is the new Reactor!

    C

    Home Assistant

  • Arduino to make a weather station
    CatmanV2C CatmanV2

    Sorry, just had to...

    e68fbd78-7e6e-405e-9504-9e01f614dc88-image.png

    C

    General Discussion

  • This is me
    CatmanV2C CatmanV2

    Well, if I see further, it's because I stand of the shoulders of giants. I've got where I got because of the experts here. I started about 15 years ago with some really basic X10 stuff. When we moved in 2011 for some reason it simply would not work in the new house, so z-wave was the thing. Vera lite then Vera Plus.

    I'm a child of the 70s. I want the car on the drive to be KITT and my lounge a cross between the bridge of the enterprise and the Lars farm on Tattoine.

    Not there yet, but with about 250 devices (virtual and real) things are fun (when they work!)

    The absolute killer app for me is Alexa bi directional speech. To the extent that I've walked into hotel rooms and said 'Alexa turn the lights on....'
    I'm within a spit of never buying another control and doing everything via Alexa and Reactor (had to drop that in)

    So that's pretty much me.

    C

    Blogs

  • Smart home with no WIFI
    CatmanV2C CatmanV2

    Perhaps another thing to point out is that WiFi<> Internet and there is absolutely no technical reason you cannot have a WiFi network simply because you have no internet access

    C

    General Discussion

  • My migration from Vera, or what I did on my holidays
    CatmanV2C CatmanV2

    Well here we go. A slow, considered migration from Vera to something (I hope) more reliable.
    Hopefully we'll end up with a decent documented process for people as right now I'm still not quite clear 🙂
    Starting point:
    I have a 'mature' Mios set up running on an extrooted Vera Plus with roughly 100 devices, both physical and virtual
    Integration with Alexa both voice control and TTS
    iPhones for Geolocation
    Volumio devices for music playing around the house.
    I have no user defined scenes, all automation is run from Reactor.

    My impetus is final dissatisfaction with the quality of UI7 software delivery and operational rigour (for full disclosure I am a senior IT Operations leader with circa 20 years experience delivering properly stable systems, so I probably have un-realistic expectations 😄 )

    So initial steps:

    1. Raspberry Pi 3 B+ (I think this is my 5, and 6th Pi in total. I may have a problem)
    2. Raspbian
    3. OpenLuup
    4. Verabridge

    That I think is stage 1

    C

    Blogs

  • OT: Universal Remote
    CatmanV2C CatmanV2

    Just to close this off, I managed to get a Harmony Elite and Hub from ebay. Lightly used at a reasonable price.
    God knows why they are pulling out of the market. First impressions is it's an ace bit of gear. Didn't realise quite what the hub could do and am thinking of getting another to replace my Broadlink in the cinema.

    Thanks, all

    C

    General Discussion

  • My migration from Vera, or what I did on my holidays
    CatmanV2C CatmanV2

    OK so time for an update. This has kind of drifted off the 'Here's how you do it'

    Most of getting Openluup, HA Bridge, AltUI, and getting Z-way up and runningwas pretty trivial (all things considered)

    The migration from Vera to Z-way, was not as simple as I'd have hoped. Pretty much 2 days of fettling.

    Couple of gotchas:

    1. My restore to the UZB dongle took a couple of shots. It took quite a long time as well.
    2. Migration to Z-way per se was pretty simple
    3. However, Z-way requires a totally different way of thinking. Pretty much every service creates an individual device. If you're not ready for this you can get in a hell of a mess trying to name stuff. I still have a few odd devices that I'm not quite sure what they are. I suspect tamper switches!
    4. Some devices are not what you think. Sirens. In fact these are shown as switches. Makes total sense when you think about it, but doesn't look great on the interface.
    5. The rooms were not migrated. So although all my rooms already existed in AltUI / Opeluup (from Vera) new devices all appeared in a ZWay room. In retrospect this could be because I already had rooms named, and they had different UIDs
    6. Reactor is still fantastic
    7. There are a couple of devices that aren't supported in Openluup / AltUI. Meh might be worth checking in advance.

    Finally a huge thankyou to @akbooer @rafale77 @therealdb Partrick (is he here? If not can someone ping him the other place) and the rest of you that have made this work.

    This is so much faster, more sensible, reactive, responsive and everything else. Now I just want to do more

    Respect

    Chris

    Blogs

  • Finally gave up on my Ezlo Plus
    CatmanV2C CatmanV2

    @therealdb well we got this place....

    C

    Blogs

  • Finally gave up on my Ezlo Plus
    CatmanV2C CatmanV2

    @librasun said in Finally gave up on my Ezlo Plus:

    Sound familiar?

    Never heard that! 😉

    C

    Blogs

  • IR to IR transmitter
    CatmanV2C CatmanV2

    https://www.keene.co.uk/keene-ir-anywhere-ir-over-ip-modules-pair.html

    Keene are great for all this kind of stuff.

    C

    Hardware

  • Alexa skill for Open Luup / Zway
    CatmanV2C CatmanV2

    @therealdb I got this running in about 30 minutes tops.....

    C

    General Discussion

  • Light automation thoughts
    CatmanV2C CatmanV2

    Hmmm. Now I have HA......

    C

    Software

  • Not so much a blog
    CatmanV2C CatmanV2

    If it doesn't work, it certainly won't be the software's fault!

    Can I really buy another pi :D. That'll be 5 in the server cupboard and one under the sofa!

    And I still need Alexa, but yes, crawling progress

    C

    Blogs

  • New Ezlo Web GUI now in "beta"
    CatmanV2C CatmanV2

    @librasun said in New Ezlo Web GUI now in "beta":

    I prefer the term "Vaporware" until a pitched product at least becomes accessible to a portion of its target audience. The silence from ezlo's team -- aside from acknowledging customer complaints and new Jira tickets -- is deafening.

    Plus ca change....

    C

    General Discussion

  • VeraBridge not auto connected after reboot Pi4
    CatmanV2C CatmanV2

    Ahh this is the same thread as in the old place?

    If you're using Raspian it should be trivial:

    (RPi) Wait For Network at Boot

    (RPi) Wait For Network at Boot

    Files for QuickPi tutorials. Contribute to legotheboss/YouTube-files development by creating an account on GitHub.

    Use the raspi-config tool

    C

    openLuup

  • Up and running
    CatmanV2C CatmanV2

    After much (un-necessary) faffing on Debian 10 I got MSR up and running in about 10 minutes flat this morning, on the same box as AltUI

    As a warning, expect lots of stupid questions. 😉

    C

    Multi-System Reactor

  • Vera firmware 7.32 beta
    CatmanV2C CatmanV2

    @pabla said in Vera firmware 7.32 beta:

    I have been waiting for 7.32 to try out @therealdb 's alexa plugin to finally use Alexa in multiple rooms for synced TTS. WIll install fingers crossed it goes well!

    Works A1 on Openluup 😉

    C

    Vera

  • Disaster recovery and virtualisation
    CatmanV2C CatmanV2

    Well after much trepidation, and some additional work, I think we are complete.

    After the successful virtualisation of my Home Assistant and Music Server hosts, and a successful POC of the main Vera / MQTT / MSR / everything else box I did some testing with a spare UZB stick to make sure I could connect it to the virtual host.

    With a long weekend ahead to solve any issues, this morning I bit the bullet and shut down the hardware device, moved the production UZB stick over to the NAS and spun up the VM.

    It was not entirely smooth as for some reason Z-way-server was saying it wasn't connected and AltUI claimed an authentication issue, but with some judicious restarts and testing, everything that I can think of to test now works!

    Some of the Z-wave commands from remote controls are a little slow, oddly, but I suspect the network needs to sort itself out as it's nearly two months 'old' Direct control from web interfaces / voice commands seems fine so I'm not overly worried.

    So, barring any unforseen failures, I have a fully virtualised system. Better even, when reading about the Synology range, I decided to source an older unit as a backup cluster device so I have some serious resilience 🙂

    Thanks for all the support an input!

    C

    General Discussion

  • OpenLuup IP Address
    CatmanV2C CatmanV2

    @iRobot said in OpenLuup IP Address:

    That is very strange, but has nothing to do with openLuup as far as I know. I think you must look for what is causing this in your Debian or network.

    Looks like you have something in your network that is redirecting your local network through the internet since 217.3.79.1 is not a private but public ip-address

    This. It's a Deutsche Telecom IP range. @Elcid what are you putting into your browser to access OpenLuup?

    What happens if you try on 192.168.1.xx?

    C

    openLuup

  • Owntracks Entity does not update as expected
    CatmanV2C CatmanV2

    Fabulous! For once I wasn't being a complete idiot, and now the entity is True (which is sort of what I'd expect) Thanks so much!

    C

    Multi-System Reactor
  • Login

  • Don't have an account? Register

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