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
Disaster recovery and virtualisation
CatmanV2C

Following on from my last thread, some progress has been made over the weekend.

With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system.

Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic.

Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work.

Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic.

Once that hurdle is sorted I'm torn between:

Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.)

Decisions, decisions.

C

General Discussion
Remote access of Zwave stick from Z-wave server
CatmanV2C

Afternoon, all.

In my continued attempts to virtualise my system, I'm in the last (I hope throes)

I don't fancy relying on Synology not to break more USB activities, so decided to set up ser2net on a Raspberry pi and plug in a spare Z-wave.me stick

So on the Raspberry pi: ser2net. yaml

catman@Zwave:/etc $ cat ser2net.yaml %YAML 1.1 --- # This is a ser2net configuration file, tailored to be rather # simple. # # Find detailed documentation in ser2net.yaml(5) # A fully featured configuration file is in # /usr/share/doc/ser2net/examples/ser2net.yaml.gz # # If you find your configuration more useful than this very simple # one, please submit it as a bugreport define: &banner \r\nser2net port \p device \d [\B] (Debian GNU/Linux)\r\n\r\n connection: &zwave0 # Bind to TCP port accepter: tcp,4000 enable: on options: kickolduser: true # Ensure mDNS is disabled mdns: false connector: serialdev, /dev/ttyACM0,115200N81,nobreak,local

And if I telnet to it from anywhere:

catman@ChrisMBP15-2018 ~ % telnet 192.168.70.128 4000 Trying 192.168.70.128... Connected to 192.168.70.128. Escape character is '^]'.

Which makes me think that ser2net is doing its thing.

Now in my virtualised Z-wave server I have this:

Screenshot 2025-04-10 at 17.36.52.png

(I've tried with a colon and a space between the ip and the port)

The result:

An unexpected error occurred during loading data. Try to reload the page. Please check 1.) if the controller is plugged in correctly, 2.) that in the app 'Z-Wave Network Access' the right port is entered (UZB: '/dev/ttyACM0', RaZberry shield: '/dev/ttyAMA0', UZB-Windows: '\\.\COM3', Z-Stick: '/dev/ttyUSB0', embedded boxes: '/dev/ttyS0' or '/dev/ttyS1') 3.) the app is aktiv. If not you could activate it under Menu > Apps > Active or add a new one under Menu > Apps > Local. The Setting 'Expert View' needs to be active under Menu > My Settings.

Any pointers as to what I'm doing wrong?

TIA!

C

Software
Organizing/ structuring rule sets and rules
R

Hi guys,

Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.

Maybe there are better ways to organize my rule sets.

I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.

Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT

I have installed MSR on a RP5 bare metal and then copied the config and store files. Everything seems to be on the RP5 but I am missing all global expression and I don't see the controller time.

Screenshot 2025-04-06 201446.png

My browser is Microsoft Edge Version 135.0.3179.54 (Official build) (64-bit)

I have probably done something stupid or missed a step but I am stuck.

Thanks for any help.

Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M

Hi,
It seems that the widget deletion does not work. I tried to drag the widget to the left (as explained in here https://smarthome.community/topic/1071/deleting-widgets?_=1744037333660)
but it does not delete it. Anyone else experiencing the same problem?

Also the landing page after login is empty and seems be have some JS issues on the dev console:

Screenshot from 2025-04-07 18-06-19.png

fd7f0424-debb-49d3-86d8-9a3b09ad3868-image.png

Using dockerized version of Reactor (Multi-hub) latest-25082-3c348de6 on Chromium 135.0.7049.52 (Official Build) snap (64-bit)

br,
mgvra

Multi-System Reactor
Need help reducing false positive notifications
T

Good day all,
I have an notification set up for my washing machine to let me know when it's complete. I have a templete sensor set up in HAAS to let me know if it's Washing, in Standby, or off, based upon the power consumption (Shelly 1PM on outlets)

- name: "Washing Machine" state: > {% if states("sensor.washer_switch_0_power")|float == 0 %} Off {% elif states("sensor.washer_switch_0_power")|float <= 2.9 %} Standby {% else %} Washing {% endif %} icon: > {% if states("sensor.washer_switch_0_power") == "off" %} mdi:washing-machine-alert {% elif states("sensor.washer_switch_0_power")|float <= 2.9 %} mdi:washing-machine-off {% else %} mdi:washing-machine {% endif %} minutes: 2

The MSR code is relatively simple. I have a built in false positive attribute for if MSR gets rebooted, because I would suddenly get tons of notifications when I upgraded MSR.

6774565a-06cc-443f-99c1-e71301b33d83-image.png

What I'm trying to introduce, is a way to verify that I just didn't bump the knob on the washing machine when transferring loads from the washer to the dryer, which turns on the display and brings the power above the Standby threshold.

The power goes up to 3.7W for about 4 minutes if the selector knob is bumped/turned.

What would the best way to do this be? I have most of my MSR code set up for a couple of years now, and my coding logic is struggling a bit.

I think I need a power threshold to be substained for a minimum time period (say 2 or 3 minutes, above 10W), before the other triggers can act. What would the best way to do that be?

Running: latest-25082-3c348de6
Fedora 41 Server
HAAS:
Core
2025.3.4
Supervisor
2025.03.4
Operating System
15.1
Frontend
20250306.0

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
Deleting widgets
tunnusT

Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266

Multi-System Reactor
MQTT configuration question
tunnusT

I have the following yaml configuration in local_mqtt_devices file

x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }'

While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?

Multi-System Reactor
System Configuration Check - time is offset
F

Hi!

I get this message when I'm on the status tab:

System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.

I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1

I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...) 🙂
/Fanan

Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT

I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB.

While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed.

So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response.

While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits

Thanks!

Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N

Hi ,
I'm on
-Reactor (Multi-hub) latest-25067-62e21a2d
-Docker on Synology NAS
-ZWaveJSUI 9.31.0.6c80945

Problem with ZwaveJSUI:
When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white.
I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui.

I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb".
After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color.

This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite.

x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33}

The "cold white" and "warm white" settings interfer with the rgb color settings.

Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white
are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white.

So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have

x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor

In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set.

x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33

Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this?

x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33}

Thanks in advance.

Multi-System Reactor
Problem with simultaneous notifications.
T

Good day all,
I have a reaction set up, that I use for both troubleshooting and changing home modes when one of my family members either arrive or are leaving. I use the companion app for HAAS on our iPhones, and HAAS reports if the person associated with the iPhone enters or leaves the geofenced area around my home. I'm sure most MSR and HAAS users are familiar with this.

I use this rule set mainly as a condition for other rules, however, as part of troubleshooting, a notification is sent through HAAS to the companion app when the rule becomes true. The problem is that I'm getting notifications now for both arriving and departing simultaneously.

96b3f7db-ba09-499e-a78c-86903b603857-image.png

36903cdd-a87f-473b-82ef-af9ef96d3c44-image.png It used to work fine as intended. I'm not sure exactly when it changed, but now I'm getting two notifications when either of these conditions change.

Any idea what could be happening?

Edit:
Running: latest-25082-3c348de6, bare-metal Linux
ZWaveJSControllerr [0.1.25082]

Multi-System Reactor
Problem after upgrading to 25067
R

MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem?
I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.

Multi-System Reactor
Global expressions not always evaluated
tunnusT

Similarly as for local expressions, global expressions evaluate and update fine when getEntity(...) structure is used. However, at least when certain functions are in use, expressions do not update.

Consider the following test case:

Screenshot 2025-03-13 at 16.29.42.png

Even though auto-evaluation is active, value does not change (it changes only if that expression is manually run). MSR restarts do not help.

Screenshot 2025-03-13 at 16.31.43.png

Note: Tested using build 25067 on Docker. I have also a PR open (but couldn't now get details or PR number as my Mantis account was somehow expired?).

Multi-System Reactor
[Solved] Local expression evaluation
V

Trying to understand what cause a local expresssion to be evaluated. I have read the manual but I am still not clear about it. Using the test rule below, I can see in the log that the rule is being automatically evaluated every time the temperature entity is changing. That is great...

What I am trying to understand is why the expression is not evaluated based on time as well since the "case" statement has time dependencies.

Any help would be appreciated

I have the following test rule:

eba6a3ea-ff61-4610-88c9-9b9864f11ff8-Screenshot 2025-01-21 095244.png

2d9c1ff5-7b73-4005-b324-9029c2709db9-Screenshot 2025-01-21 095302.png

Here is the expressioncode:

vFrom1 = "09:25:00", vFrom2 = "09:30:00", vFrom3 = "09:41:00", vTo = "10:55:00", # Get current time (format HH:MM:SS) vToDay = strftime("%H:%M:%S"), #Get current house temperature CurrentHouseTemp = getEntity( "hass>Thermostat2 " ).attributes.temperature_sensor.value, case when CurrentHouseTemp <= 19 and vToDay >= vFrom1 && vToDay <= vTo: "true1" # From1 when CurrentHouseTemp <= 20 and vToDay >= vFrom2 && vToDay <= vTo: "true2" # From2 when CurrentHouseTemp < 26  and vToDay >= vFrom3 && vToDay <= vTo: "true3" # From3 else "false" end
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S

I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved.

The Runtime Error is different in the two browsers
Safari v18.3

@http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.

Google Chrome 133.0.6943.142

TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.

Steps to reproduce:
Click the pencil to edit a global reaction with a group.
Click the Exit button.
Runtime error appears.
or
Click Create Reaction
Click Add Action
Select Group
Add Condition such as Entity Attribute.
Add an Action.
Click Save
Click Exit
Runtime error appears.

I don’t know how long the error has been there as I haven’t edited the global reaction in a long time.

Reactor (Multi-hub) latest-25060-f32eaa46
Docker
Mac OS: 15.3.1
Thanks

Multi-System Reactor
Cannot delete Global Expressions
SnowmanS

I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons.

I have not created a global expression for some times and just noticed this while doing some clean-up.

I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success.

Here's what the log shows.

[latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }

Reactor latest-25067-62e21a2d
Docker on Synology NAS

Multi-System Reactor
Advice on Storing and Backing Up Bind Mounts - Docker
PablaP

Hello all, after seeing Catman's posts about their disaster recovery and move to Docker I took that as a sign to migrate everything (aside from HA) to Docker. After a small learning curve I had Docker+Portainer up and running in a few days.

Instead of using named Volumes I opted to use Bind Mounts so I can easily edit conf files and any other file needed. I do understand the nuances that come with bind mounts, such as migration to a different host may require changing file structures, the possibility of someone editing the bind mount files and permissions but to me those aren't too big of a deal.

My question is what is the best way to keep a back up of these bind mounts? I currently have them stored in the /etc directory in another directory named on a per container basis. I was thinking to move it all to a /home/user/docker/ directory so that I can use a simple cp command to my mounted SMB share to backup all the container data files. Anyone else do it differently?

Side note: I finally got to flex the benefits of Docker with updating Reactor.. it was dead simple. I had no idea what I was missing out on lol!

Software
Local notification methods?
CatmanV2C

Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method.

This was prompted by yesterday's fun and games with my ISP.

I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone)

I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions?

TIA

C

Multi-System Reactor
About
Posts
21
Topics
3
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.

  • 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
  • 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 ?

  • [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

  • 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)

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

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

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

  • 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

  • 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

  • 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).

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

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

  • 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 ?

  • 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$
  • 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));
                                                             ^
  • 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.

  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved