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

xAPPO

@xAPPO
Home Assistant Connect ZWA-2 & ZBT-2
therealdbT
Topic thumbnail image
Hardware
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Is there a way to turn this section (image in post) off?
toggledbitsT
Topic thumbnail image
Comments & Feedback
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
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
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
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
About
Posts
21
Topics
3
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Wanting to install in Proxmox.. what’s the best way?
    X xAPPO

    Actually that’s just what I’ve done.

    I did try the Portainer route as there are Proxmox scripts to rapidly create a Docker/Portainer LXC but the Portainer version / UI was very different to the write up here so I installed Reactor & MQTT direct to Docker with Docker Container and it seems to all be working fine 🤞 Portainer I have later installed too and it sees the Reactor container obviously. I’ve had a slight problem with root vs normal user but I think I’ve managed to get everything installed away out of root.

    I like the up to date nature of Docker Compose and I believe MQTT is preserved. So I avoided a direct install to a Linux distribution as I think that would be more work to keep current going forward.

    One more part of my HA setup off of a Pi as I move to have a predominantly MQTT centric system.

    How-To

  • Wanting to install in Proxmox.. what’s the best way?
    X xAPPO

    I’m moving a lot of my home automation Raspberry Pi’s to Proxmox virtualisation and really enjoying it.

    I would like to install Reactor that way too. Having researched this forum I’m surprised more people haven’t ventured into this. Although I use HomeAssistant in Proxmox I don’t want to use the HAOS path addin one user has tried as it seems to be unsupported now.

    What would be the best way to install Reactor under Proxmox? As a Linux VM (flavour?) with manual install or as a Docker install or even following the Portainer write up with Docker install underneath? Proxmox tend to recommend you away from Docker where possible.

    Keeping Reactor upto date easily would be a big consideration too.

    Thanks for any recommendations and anyone running Reactor within Proxmox already ?

    There’s a growing number of helper scripts for Proxmox that one click install home automation favourites as a prebuilt Linux container (LXC) . It would be nice to get Reactor listed and installed this way too…under the automation category

    Proxmox VE Helper-Scripts
    How-To

  • MQTT - add rules support ?
    X xAPPO

    I'm thinking that a useful feature in MQTT would be a topic entry for each rule within Reactor and their current state set or reset updating in real time.

    reactor/rules/myRule1  = reset
    reactor/rules/myRule2  = set
    

    Additionally a topic available that could trigger the rule from MQTT.

    reactor/rules/myRule1/trigger  = set
    

    I would have to think about whether this would trigger the rule always or only if other triggers are also satisfied or an option for either. I would like to avoid manually adding the MQTT payload value as a trigger into each and every rule to achieve this. Maybe I should look at this from Reactions perspective.

    What do you think ?

    New to Reactor but Im assuming an event is available to MQTT code that would advise when rules set and reset and a call available to trigger them manually, perhaps bypassing triggers ?

    Multi-System Reactor

  • [SOLVED]. Build 22021-f83a39c Status page is blank
    X xAPPO

    @toggledbits Sorry - your support is too on the ball 👍 - I had deleted the post as I realized it was non sensical and created a new post

    Multi-System Reactor

  • Recently Changed Entities doesn't update on 22021
    X xAPPO

    The recently changed entities no longer updates when added to the status page. It does display some initial entries. Other widgets do update as do Entities. (Docker)

    Multi-System Reactor

  • MSR support for openHAB?
    X xAPPO

    I read that both OpenHAB and Homey were being worked on although the expected date has slipped a little. I’m interested in both. It’s part of the reason I’m evaluating Reactor MH at the moment.

    You can interact with both of those currently via MQTT but having a tighter integration with entity discovery would be really nice.

    Multi-System Reactor

  • MQTT interface... time for some testing. Where are my experts?
    X xAPPO

    @toggledbits said in MQTT interface... time for some testing. Where are my experts?:

    Did you find the probably dated but maybe marginally helpful docs here?

    Yes I did .. a quick Q - how do I delete an entity ?

    The bit I'm adding currently is

    If the process may be protracted and lengthy, the Promise should resolve earlier and the entities by published as discovered.

    and trying to avoid having to loop through them all on restarts to see if they already exist. This is an aspect that you must have encountered with Hubitat and Hass.

    Making good progress and enjoying it .. great application.

    Multi-System Reactor

  • MQTT interface... time for some testing. Where are my experts?
    X xAPPO

    I notice in the MQTT code you subscribe to the root level with a wildcard which means you receive every payload update. On my (untypical) broker this will produce 10’s of message per second. The good thing is Reactor seems to handle it but obviously it’s resource wasteful. Did you do this with a view to implementing discovery across the broker perhaps?

    Currently it might seem better to just pull the necessary topics from the MQTTController section of reactor.yaml even though this may result in lots of individual subscribes?

    Also just to mention I’ve got my first CBusController half written. It discovers and creates entities for all the 100+ lights I have on my Schneider C-Bus lighting but needs some refining. Learning as I go. Having the MQTT code as an example has been invaluable to me.

    Would you be up to releasing the Hubitat and HomeAssistant controller code as examples? I think that would help people in authoring new controllers, as might a minimal code template that does nothing really.

    Multi-System Reactor

  • MQTT interface... time for some testing. Where are my experts?
    X xAPPO

    It's like having my own on site developer team 🙂 Many thanks for that

    Multi-System Reactor

  • MQTT interface... time for some testing. Where are my experts?
    X xAPPO

    This is working well - thank you for the prompt update.

    For me having the <entity-name> before <entity-id> in the topic hierarchy would have been more informative as you can then see a list of names rather than numbers in expanded topics with say MQTT explorer rather than having to drill down in each one, but I totally understand why it is so much easier in terms of your existing implementation to position it afterwards and this is very workable too.

    70bebe6f-d981-4b60-93da-dade10eed90c-image.png

    Thank you again.
    Kevin

    Multi-System Reactor

  • MQTT interface... time for some testing. Where are my experts?
    X xAPPO

    The incoming action request message to a topic must be complete with all segments as you can't wildcard a publish command. So the <entity-id> will always be unique and present there. You could should you wish subscribe to the topic from your code ignoring any <entity-name> segment with a + wildcard as you don't process it. So that should work fine.

    Human readability.. I agree it's a bit of a reach but my whole system is MQTT based with over 10K topics and 1K+ devices - remembering what they all are and linking to or from those topics from other controllers requires some hints as to what those devices are. Later examination of logic requires understanding what devices are related. Having to refer back to Reactor config each time to identify a device isn't practical (or user friendly).

    Multi-System Reactor

  • MQTT interface... time for some testing. Where are my experts?
    X xAPPO

    Topic hierarchy segments don't have to be unique - in fact I would say most aren't. Keeping the <entity-id> then within the hierarchy would ensure the topic remains unique. Having no easily human identifiable topic is not helpful to other integrations.

    Multi-System Reactor

  • MQTT interface... time for some testing. Where are my experts?
    X xAPPO

    All working well. However in the topic structure for echoed devices (from Hubitat anyway) the <entity-id> is used. Is it possible to instead or even better as well as, include the entity-name ?

    reactor/<mqtt-id>/<ctrl-id>/<entity-id>/state/<capability-name>
    

    perhaps

    reactor/<mqtt-id>/<ctrl-id>/<entity-name>/<entity-id>/state/<capability-name>
    
    Multi-System Reactor

  • MQTT interface... time for some testing. Where are my experts?
    X xAPPO

    Thankyou - that's worked. I had assumed the appropriate version of node was part of the Docker container.

    So pleased to have found this as I use HA, MQTT, Hubitat extensively plus OpenHAB and Homey to a lesser extent so glad you are intending to support those two eventually.

    Multi-System Reactor

  • MQTT interface... time for some testing. Where are my experts?
    X xAPPO

    Its a docker install so I thought that was part of the container .. on the host OS my version is v12.20.0 - should I update that ?

    Multi-System Reactor

  • MQTT interface... time for some testing. Where are my experts?
    X xAPPO

    IN two posts because was too long - sorry

    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8-intern                                                                                                                                          al.h:14:0,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:27,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:6                                                                                                                                           ,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3553:51: note: declared he                                                                                                                                          re
       V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                                       ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    ../src/bindings.cc:182:62: warning: ‘bool v8::Object::Set(v8::Local<v8::Value>,                                                                                                                                           v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declaratio                                                                                                                                          ns]
       inotify->handle()->Set(descriptor, args_->Get(callback_sym));
                                                                  ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8-intern                                                                                                                                          al.h:14:0,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:27,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:6                                                                                                                                           ,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3499:22: note: declared he                                                                                                                                          re
                     bool Set(Local<Value> key, Local<Value> value));
                          ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    ../src/bindings.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYP                                                                                                                                          E NodeInotify::Inotify::RemoveWatch(Nan::NAN_METHOD_ARGS_TYPE)’:
    ../src/bindings.cc:195:31: error: no matching function for call to ‘v8::Value::I                                                                                                                                          nt32Value()’
       watch = info[0]->Int32Value();
                                   ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:67                                                                                                                                          :0,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:2709:40: note: candidate:                                                                                                                                           v8::Maybe<int> v8::Value::Int32Value(v8::Local<v8::Context>) const
       V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const                                                                                                                                          ;
                                            ^~~~~~~~~~
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:2709:40: note:   candidate                                                                                                                                           expects 1 argument, 0 provided
    ../src/bindings.cc: In static member function ‘static void NodeInotify::Inotify:                                                                                                                                          :Callback(uv_poll_t*, int, int)’:
    ../src/bindings.cc:262:86: warning: ‘bool v8::Object::Set(v8::Local<v8::Value>,                                                                                                                                           v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declaratio                                                                                                                                          ns]
     >Set(Nan::New<String>("watch").ToLocalChecked(), Nan::New<Integer>(event->wd));
                                                                                  ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8-intern                                                                                                                                          al.h:14:0,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:27,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:6                                                                                                                                           ,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3499:22: note: declared he                                                                                                                                          re
                     bool Set(Local<Value> key, Local<Value> value));
                          ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    ../src/bindings.cc:263:87: warning: ‘bool v8::Object::Set(v8::Local<v8::Value>,                                                                                                                                           v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declaratio                                                                                                                                          ns]
     Set(Nan::New<String>("mask").ToLocalChecked(), Nan::New<Integer>(event->mask));
                                                                                  ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8-intern                                                                                                                                          al.h:14:0,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:27,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:6                                                                                                                                           ,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3499:22: note: declared he                                                                                                                                          re
                     bool Set(Local<Value> key, Local<Value> value));
                          ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    ../src/bindings.cc:264:91: warning: ‘bool v8::Object::Set(v8::Local<v8::Value>,                                                                                                                                           v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declaratio                                                                                                                                          ns]
     Nan::New<String>("cookie").ToLocalChecked(), Nan::New<Integer>(event->cookie));
                                                                                  ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8-intern                                                                                                                                          al.h:14:0,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:27,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:6                                                                                                                                           ,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3499:22: note: declared he                                                                                                                                          re
                     bool Set(Local<Value> key, Local<Value> value));
                          ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    ../src/bindings.cc:267:104: warning: ‘bool v8::Object::Set(v8::Local<v8::Value>,                                                                                                                                           v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarati                                                                                                                                          ons]
     ing>("name").ToLocalChecked(), Nan::New<String>(event->name).ToLocalChecked());
                                                                                  ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8-intern                                                                                                                                          al.h:14:0,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:27,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:6                                                                                                                                           ,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3499:22: note: declared he                                                                                                                                          re
                     bool Set(Local<Value> key, Local<Value> value));
                          ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    ../src/bindings.cc:275:66: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Lo                                                                                                                                          cal<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
         Local<Value> value = handle->Get(Nan::New<Integer>(event->wd));
                                                                      ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8-intern                                                                                                                                          al.h:14:0,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:27,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:6                                                                                                                                           ,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3553:51: note: declared he                                                                                                                                          re
       V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                                       ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    ../src/bindings.cc:279:34: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(v8                                                                                                                                          ::Local<v8::Object>, int, v8::Local<v8::Value>*) const’ is deprecated [-Wdepreca                                                                                                                                          ted-declarations]
         callback.Call(handle, 1, argv);
                                      ^
    In file included from ../src/node_inotify.h:14:0,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    ../../nan/nan.h:1722:3: note: declared here
       Call(v8::Local<v8::Object> target
       ^~~~
    ../src/bindings.cc:285:34: error: no matching function for call to ‘v8::Value::T                                                                                                                                          oString()’
          handle->Delete(wd->ToString());
                                      ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:67                                                                                                                                          :0,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:2668:44: note: candidate:                                                                                                                                           v8::MaybeLocal<v8::String> v8::Value::ToString(v8::Local<v8::Context>) const
       V8_WARN_UNUSED_RESULT MaybeLocal<String> ToString(
                                                ^~~~~~~~
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:2668:44: note:   candidate                                                                                                                                           expects 1 argument, 0 provided
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8-intern                                                                                                                                          al.h:14:0,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:27,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:6                                                                                                                                           ,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:2684:31: note: candidate:                                                                                                                                           v8::Local<v8::String> v8::Value::ToString(v8::Isolate*) const
                     Local<String> ToString(Isolate* isolate) const);
                                   ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:2684:31: note:   candidate                                                                                                                                           expects 1 argument, 0 provided
                     Local<String> ToString(Isolate* isolate) const);
                                   ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    inotify.target.mk:112: recipe for target 'Release/obj.target/inotify/src/binding                                                                                                                                          s.o' failed
    make: *** [Release/obj.target/inotify/src/bindings.o] Error 1
    make: Leaving directory '/home/kevin/reactor/ext/MQTTController/node_modules/ino                                                                                                                                          tify/build'
    kevin@NUC50:~/reactor/ext/MQTTController$
    
    Multi-System Reactor

  • MQTT interface... time for some testing. Where are my experts?
    X xAPPO

    This is what I see when running step5 ./install.sh

    Installing dependencies...
    make: Entering directory '/home/kevin/reactor/ext/MQTTController/node_modules/in                                                                                                                                          otify/build'
      CXX(target) Release/obj.target/inotify/src/bindings.o
    In file included from ../src/bindings.cc:2:0:
    ../src/bindings.h:10:27: error: ‘Handle’ has not been declared
        static void Initialize(Handle<Object> target);
                               ^~~~~~
    ../src/bindings.h:10:33: error: expected ‘,’ or ‘...’ before ‘<’ token
        static void Initialize(Handle<Object> target);
                                     ^
    ../src/bindings.cc:11:27: error: variable or field ‘Initialize’ declared void
      void Inotify::Initialize(Handle<Object> exports) {
                               ^~~~~~
    ../src/bindings.cc:11:27: error: ‘Handle’ was not declared in this scope
    ../src/bindings.cc:11:27: note: suggested alternative: ‘rand_r’
      void Inotify::Initialize(Handle<Object> exports) {
                               ^~~~~~
                               rand_r
    ../src/bindings.cc:11:40: error: expected primary-expression before ‘>’ token
      void Inotify::Initialize(Handle<Object> exports) {
                                            ^
    ../src/bindings.cc:11:42: error: ‘exports’ was not declared in this scope
      void Inotify::Initialize(Handle<Object> exports) {
                                              ^~~~~~~
    ../src/bindings.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYP                                                                                                                                          E NodeInotify::Inotify::AddWatch(Nan::NAN_METHOD_ARGS_TYPE)’:
    ../src/bindings.cc:146:43: error: no matching function for call to ‘v8::Value::T                                                                                                                                          oObject()’
       Local<Object> args_ = info[0]->ToObject();
                                               ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:67                                                                                                                                          :0,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:2672:44: note: candidate:                                                                                                                                           v8::MaybeLocal<v8::Object> v8::Value::ToObject(v8::Local<v8::Context>) const
       V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
                                                ^~~~~~~~
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:2672:44: note:   candidate                                                                                                                                           expects 1 argument, 0 provided
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8-intern                                                                                                                                          al.h:14:0,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:27,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:6                                                                                                                                           ,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:2686:31: note: candidate:                                                                                                                                           v8::Local<v8::Object> v8::Value::ToObject(v8::Isolate*) const
                     Local<Object> ToObject(Isolate* isolate) const);
                                   ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:2686:31: note:   candidate                                                                                                                                           expects 1 argument, 0 provided
                     Local<Object> ToObject(Isolate* isolate) const);
                                   ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    ../src/bindings.cc:149:27: error: no matching function for call to ‘v8::Object::                                                                                                                                          Has(v8::Local<v8::String>&)’
       if (!args_->Has(path_sym)) {
                               ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:67                                                                                                                                          :0,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3590:37: note: candidate:                                                                                                                                           v8::Maybe<bool> v8::Object::Has(v8::Local<v8::Context>, v8::Local<v8::Value>)
       V8_WARN_UNUSED_RESULT Maybe<bool> Has(Local<Context> context,
                                         ^~~
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3590:37: note:   candidate                                                                                                                                           expects 2 arguments, 1 provided
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3596:37: note: candidate:                                                                                                                                           v8::Maybe<bool> v8::Object::Has(v8::Local<v8::Context>, uint32_t)
       V8_WARN_UNUSED_RESULT Maybe<bool> Has(Local<Context> context, uint32_t index)                                                                                                                                          ;
                                         ^~~
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3596:37: note:   candidate                                                                                                                                           expects 2 arguments, 1 provided
    ../src/bindings.cc:154:31: error: no matching function for call to ‘v8::Object::                                                                                                                                          Has(v8::Local<v8::String>&)’
       if (!args_->Has(callback_sym) ||
                                   ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:67                                                                                                                                          :0,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3590:37: note: candidate:                                                                                                                                           v8::Maybe<bool> v8::Object::Has(v8::Local<v8::Context>, v8::Local<v8::Value>)
       V8_WARN_UNUSED_RESULT Maybe<bool> Has(Local<Context> context,
                                         ^~~
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3590:37: note:   candidate                                                                                                                                           expects 2 arguments, 1 provided
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3596:37: note: candidate:                                                                                                                                           v8::Maybe<bool> v8::Object::Has(v8::Local<v8::Context>, uint32_t)
       V8_WARN_UNUSED_RESULT Maybe<bool> Has(Local<Context> context, uint32_t index)                                                                                                                                          ;
                                         ^~~
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3596:37: note:   candidate                                                                                                                                           expects 2 arguments, 1 provided
    ../src/bindings.cc:155:28: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Lo                                                                                                                                          cal<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
        !args_->Get(callback_sym)->IsFunction()) {
                                ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8-intern                                                                                                                                          al.h:14:0,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:27,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:6                                                                                                                                           ,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3553:51: note: declared he                                                                                                                                          re
       V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                                       ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    ../src/bindings.cc:160:32: error: no matching function for call to ‘v8::Object::                                                                                                                                          Has(v8::Local<v8::String>&)’
       if (!args_->Has(watch_for_sym)) {
                                    ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:67                                                                                                                                          :0,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3590:37: note: candidate:                                                                                                                                           v8::Maybe<bool> v8::Object::Has(v8::Local<v8::Context>, v8::Local<v8::Value>)
       V8_WARN_UNUSED_RESULT Maybe<bool> Has(Local<Context> context,
                                         ^~~
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3590:37: note:   candidate                                                                                                                                           expects 2 arguments, 1 provided
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3596:37: note: candidate:                                                                                                                                           v8::Maybe<bool> v8::Object::Has(v8::Local<v8::Context>, uint32_t)
       V8_WARN_UNUSED_RESULT Maybe<bool> Has(Local<Context> context, uint32_t index)                                                                                                                                          ;
                                         ^~~
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3596:37: note:   candidate                                                                                                                                           expects 2 arguments, 1 provided
    ../src/bindings.cc:163:33: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Lo                                                                                                                                          cal<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
        if (!args_->Get(watch_for_sym)->IsInt32()) {
                                     ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8-intern                                                                                                                                          al.h:14:0,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:27,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:6                                                                                                                                           ,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3553:51: note: declared he                                                                                                                                          re
       V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                                       ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    ../src/bindings.cc:166:36: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Lo                                                                                                                                          cal<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
        mask |= args_->Get(watch_for_sym)->Int32Value();
                                        ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8-intern                                                                                                                                          al.h:14:0,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:27,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:6                                                                                                                                           ,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3553:51: note: declared he                                                                                                                                          re
       V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                                       ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    ../src/bindings.cc:166:50: error: no matching function for call to ‘v8::Value::I                                                                                                                                          nt32Value()’
        mask |= args_->Get(watch_for_sym)->Int32Value();
                                                      ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:67                                                                                                                                          :0,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:2709:40: note: candidate:                                                                                                                                           v8::Maybe<int> v8::Value::Int32Value(v8::Local<v8::Context>) const
       V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const                                                                                                                                          ;
                                            ^~~~~~~~~~
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:2709:40: note:   candidate                                                                                                                                           expects 1 argument, 0 provided
    ../src/bindings.cc:172:45: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Lo                                                                                                                                          cal<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
       String::Utf8Value path(args_->Get(path_sym));
                                                 ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8-intern                                                                                                                                          al.h:14:0,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:27,
                     from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:6                                                                                                                                           ,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3553:51: note: declared he                                                                                                                                          re
       V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                                       ^
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8config.h:328:3: note: in defi                                                                                                                                          nition of macro ‘V8_DEPRECATED’
       declarator __attribute__((deprecated(message)))
       ^~~~~~~~~~
    ../src/bindings.cc:172:46: error: no matching function for call to ‘v8::String::                                                                                                                                          Utf8Value::Utf8Value(v8::Local<v8::Value>)’
       String::Utf8Value path(args_->Get(path_sym));
                                                  ^
    In file included from /home/kevin/.cache/node-gyp/12.20.0/include/node/node.h:67                                                                                                                                          :0,
                     from ../src/node_inotify.h:5,
                     from ../src/bindings.h:4,
                     from ../src/bindings.cc:2:
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3135:5: note: candidate: v                                                                                                                                          8::String::Utf8Value::Utf8Value(v8::Isolate*, v8::Local<v8::Value>)
         Utf8Value(Isolate* isolate, Local<v8::Value> obj);
         ^~~~~~~~~
    /home/kevin/.cache/node-gyp/12.20.0/include/node/v8.h:3135:5: note:   candidate                                                                                                                                           expects 2 arguments, 1 provided
    ../src/bindings.cc:182:61: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Lo                                                                                                                                          cal<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
       inotify->handle()->Set(descriptor, args_->Get(callback_sym));
                                                                 ^
    
    Multi-System Reactor

  • MQTT interface... time for some testing. Where are my experts?
    X xAPPO

    I followed the instructions. Including step 5. I have a feeling I saw an error at some stage in that install so I will revisit that step and report back.

    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