SmartHome Community

@akbooer not sure if it's related to openLuup or ALTUI...

But since a couple of update (both openLuup and ALTUI), some basic function in RulesEngine are not working, like "saving" a rule after an edit and also "deleting" a rule...

It's probably "javascript" related

Hi @toggledbits

I'm trying to use OWM, apparently, I receive the correct information, but after a while, the MSR disconnects.

My configuration is as follows.

- id: weather enabled: true implementation: OWMWeatherController name: OWM Weather config: # Place your OWM API key here (remember to enable the controller after adding your appid) appid: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" # How often weather is allowed to be refreshed. This helps limit OWN API use, # to keep you in their good graces (and on their free tier). This value is # in minutes. interval: 30 locations: - id: home name: Home Weather # Set the location by specifying ONE OF: latitude+longitude, OWN city # ID, or location (as postal,country). If none is set, the system # location will be used. latitude: 8.9936 longitude: -79.5197 city_id: 3703443 #location: "30269,us" # Enable "save_full_response" to save the full response (you may have # need to use parts of the response that are not part of the wx # capability in your dashboard widgets). #save_full_response: false

When I request a systemctl status reactor I get this message:

root@main:/home/wilson/reactor/logs# systemctl status reactor ● reactor.service - Multi System Reactor Loaded: loaded (/etc/systemd/system/reactor.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2023-09-08 21:03:13 EST; 5s ago Main PID: 194711 (node) Tasks: 11 (limit: 9390) Memory: 82.5M CPU: 2.508s CGroup: /system.slice/reactor.service └─194711 /usr/bin/node app -p Sep 08 21:03:13 main node[194711]: Error: Incompatible serialization data; can't unserialize Sep 08 21:03:13 main node[194711]: at System.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) Sep 08 21:03:13 main node[194711]: at /home/wilson/reactor/server/lib/Controller.js:458:70 Sep 08 21:03:13 main node[194711]: at Array.forEach (<anonymous>) Sep 08 21:03:13 main node[194711]: at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) Sep 08 21:03:13 main node[194711]: at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) Sep 08 21:03:13 main node[194711]: at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) Sep 08 21:03:13 main node[194711]: at /home/wilson/reactor/server/lib/Controller.js:93:37 Sep 08 21:03:13 main node[194711]: [latest-23242]2023-09-09T02:03:13.855Z <NUTController:null> Module NUTController v22305 Sep 08 21:03:13 main node[194711]: [latest-23242]2023-09-09T02:03:13.859Z <SystemController:null> Module SystemController v23214 root@main:/home/wilson/reactor/logs# root@main:/home/wilson/reactor# systemctl status reactor ● reactor.service - Multi System Reactor Loaded: loaded (/etc/systemd/system/reactor.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2023-09-08 20:48:36 EST; 2min 58s ago Main PID: 194353 (node) Tasks: 11 (limit: 9390) Memory: 66.0M CPU: 9.493s CGroup: /system.slice/reactor.service └─194353 /usr/bin/node app -p Sep 08 20:48:37 main node[194353]: at System.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) Sep 08 20:48:37 main node[194353]: at /home/wilson/reactor/server/lib/Controller.js:458:70 Sep 08 20:48:37 main node[194353]: at Array.forEach (<anonymous>) Sep 08 20:48:37 main node[194353]: at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) Sep 08 20:48:37 main node[194353]: at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) Sep 08 20:48:37 main node[194353]: at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) Sep 08 20:48:37 main node[194353]: at /home/wilson/reactor/server/lib/Controller.js:93:37 Sep 08 20:48:37 main node[194353]: [latest-23242]2023-09-09T01:48:37.017Z <NUTController:null> Module NUTController v22305 Sep 08 20:48:37 main node[194353]: [latest-23242]2023-09-09T01:48:37.024Z <SystemController:null> Module SystemController v23214 Sep 08 20:48:37 main node[194353]: [latest-23242]2023-09-09T01:48:37.475Z <Timer:null> Timer#rule-l7ujwva5 just a note: I'm setting a delay of > lines 1-20/20 (END)

I can see this information in the log, but I don't understand what I should do to fix it.

[latest-23242]2023-09-09T02:03:13.838Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-23242]2023-09-09T02:03:13.845Z <Structure:INFO> Structure#1 loading controller interface weather (OWMWeatherController) [latest-23242]2023-09-09T02:03:13.847Z <OWMWeatherController:null> Module OWMWeatherController v22294 [latest-23242]2023-09-09T02:03:13.850Z <Controller:WARN> OWMWeatherController#weather failed (1) to restore entity controller_all: [Error] Inco> [latest-23242]2023-09-09T02:03:13.850Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Group.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) at /home/wilson/reactor/server/lib/Controller.js:458:70 at Array.forEach (<anonymous>) at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) at /home/wilson/reactor/server/lib/Controller.js:93:37 [latest-23242]2023-09-09T02:03:13.851Z <Controller:WARN> OWMWeatherController#weather failed (1) to restore entity default: [Error] Incompatibl> [latest-23242]2023-09-09T02:03:13.851Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) at /home/wilson/reactor/server/lib/Controller.js:458:70 at Array.forEach (<anonymous>) at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) at /home/wilson/reactor/server/lib/Controller.js:93:37 [latest-23242]2023-09-09T02:03:13.852Z <Controller:WARN> OWMWeatherController#weather failed (1) to restore entity system: [Error] Incompatible> [latest-23242]2023-09-09T02:03:13.852Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at System.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) at /home/wilson/reactor/server/lib/Controller.js:458:70 at Array.forEach (<anonymous>) at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) at /home/wilson/reactor/server/lib/Controller.js:93:37 [latest-23242]2023-09-09T02:03:13.853Z <Structure:INFO> Structure#1 loading controller interface nut (NUTController) [latest-23242]2023-09-09T02:03:13.855Z <NUTController:null> Module NUTController v22305 [latest-23242]2023-09-09T02:03:13.855Z <Controller:INFO> Loaded NUTController version "0.1.22305"; Patrick Rigney/Kedron Holdings LLC <patrick@> [latest-23242]2023-09-09T02:03:13.857Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [

And finally, I have a second house, with the same OWM configuration I made today, and it doesn't show any errors.

Please, your traditional help.

Thanks.

@toggledbits

After a prolonged power cut, the UPS was unable to cope with the weather and shut down the entire system.

When I returned, I had the problem that the host time displayed in the browser and automatically used in the rules was not correct.

I searched for a topic here on this forum that talked about it, but it referred to a container installation. There was a recommendation to go into the storage/states directory and delete the files and restart MSR, I did it and it didn't solve the problem.

There was also a recommendation to go directly to the browser to check the time, and I did so and I see that the time is correct.

8ad429c8-ea5f-45b4-8670-7d0353a50a0e-image.png

As you can see on the screen above:

MSR browser shows the correct browser time 21:23, but host time 13:02; In the browser below the direct query and the host time is correct 9:22:54 PM; Setting the VM date command on the third screen, the time is 9:23:00 PM.

I've opened the entire reactor.log file and searched for any errors, and there aren't any.

^L [latest-23242]2023-09-15T02:11:12.928Z <app:null> Reactor build latest-23242-5ee8e1d4 starting on v18.12.0 [latest-23242]2023-09-15T02:11:12.929Z <app:null> Process ID 1807 user/group 1000/1000; bare-metal; platform linux/x64 #179-Ubuntu SMP Mo> [latest-23242]2023-09-15T02:11:12.929Z <app:null> Basedir /home/leonardo/reactor; data in /home/leonardo/reactor/storage [latest-23242]2023-09-15T02:11:12.929Z <app:null> NODE_PATH=/home/leonardo/reactor [latest-23242]2023-09-15T02:11:12.933Z <app:INFO> Configured locale (undefined); selected locale(s) en_US.UTF-8 [latest-23242]2023-09-15T02:11:12.955Z <app:INFO> Loaded locale en-US for en-US [latest-23242]2023-09-15T02:11:12.958Z <Structure:null> Module Structure v23172 [latest-23242]2023-09-15T02:11:12.959Z <Capabilities:null> Module Capabilities v22356 [latest-23242]2023-09-15T02:11:12.969Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 23914 revisi> [latest-23242]2023-09-15T02:11:12.978Z <Plugin:null> Module Plugin v22300 [latest-23242]2023-09-15T02:11:12.981Z <TimerBroker:null> Module TimerBroker v22283 [latest-23242]2023-09-15T02:11:12.983Z <Entity:null> Module Entity v22353 [latest-23242]2023-09-15T02:11:12.986Z <Controller:null> Module Controller v23069 [latest-23242]2023-09-15T02:11:12.992Z <default:null> Module Ruleset v22293 [latest-23242]2023-09-15T02:11:12.992Z <default:null> Module Rulesets v22146 [latest-23242]2023-09-15T02:11:12.996Z <GlobalExpression:null> Module GlobalExpression v23211 [latest-23242]2023-09-15T02:11:13.003Z <Predicate:null> Module Predicate v23093 [latest-23242]2023-09-15T02:11:13.005Z <AlertManager:null> Module AlertManager v22283 [latest-23242]2023-09-15T02:11:13.007Z <Rule:null> Module Rule v23107 [latest-23242]2023-09-15T02:11:13.009Z <GlobalReaction:null> Module GlobalReaction v22324 [latest-23242]2023-09-15T02:11:13.010Z <Engine:null> Module Engine v23231 [latest-23242]2023-09-15T02:11:13.012Z <httpapi:null> Module httpapi v23058 [latest-23242]2023-09-15T02:11:13.019Z <wsapi:null> Module wsapi v23172 [latest-23242]2023-09-15T02:11:13.019Z <app:NOTICE> Starting Structure...

As you can see, the time in the log is 02:11, which is correct, because I'm in time zone -5, which means it's 09:11PM for me.

I've restarted the VM, the computer hosting the VM, and the MSR a few times and the same difference remains. What do you recommend for the next step in understanding and solving the problem?

Thanks.

I installed a new iblind this evening and it is appearing in ZWaveJS. It is operational thru Home Assistant just fine. It is operational thru the HA ZwaveJS plugin just fine.

Where it is non-responsive is in MSR for some reason. The entities are there. Adding the node to a Reaction and then attempting to run said Reaction nets me this:

[latest-23242]2023-09-08T05:33:08.454Z <ZWaveJSController:5:ZWaveJSController.js:655> ZWaveJSController#zwavejs _apply_value motion_sensor.state=false [latest-23242]2023-09-08T05:33:08.455Z <ZWaveJSController:5:ZWaveJSController.js:722> ZWaveJSController#zwavejs setting Binary Sensor#zwavejs>11-0.x_zwave_values.Binary_Sensor_Motion to false [latest-23242]2023-09-08T05:33:08.692Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event statistics updated entity Binary Sensor#zwavejs>11-0 [latest-23242]2023-09-08T05:40:23.960Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.open on Cover#zwavejs>20-0 with [Object]{ } [latest-23242]2023-09-08T05:40:23.962Z <ZWaveJSController:5:ZWaveJSController.js:1843> ZWaveJSController#zwavejs no implementation mapped; attempting default [latest-23242]2023-09-08T05:40:25.062Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.refresh on Cover#zwavejs>20-0 with [Object]{ } **[latest-23242]2023-09-08T05:40:25.063Z <ZWaveJSController:5:ZWaveJSController.js:1843> ZWaveJSController#zwavejs no implementation mapped; attempting default** [latest-23242]2023-09-08T05:40:25.065Z <ZWaveJSController:5:ZWaveJSController.js:294> ZWaveJSController#zwavejs sending #1694151625064<9/8/2023, 1:40:25 AM>: [Object]{ "command": "node.refresh_values", "nodeId": 20, "messageId": 1694151625064 } [latest-23242]2023-09-08T05:40:26.307Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event statistics updated entity Cover#zwavejs>20-0 [latest-23242]2023-09-08T05:40:26.317Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event value updated entity Cover#zwavejs>20-0 [latest-23242]2023-09-08T05:40:26.318Z <ZWaveJSController:5:ZWaveJSController.js:667> ZWaveJSController#zwavejs update node 20 value "0:128:level:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 20, "args": { "commandClassName": "Battery", "commandClass": 128, "property": "level", "endpoint": 0, "newValue": 100, "prevValue": 100, "propertyName": "level" } } [latest-23242]2023-09-08T05:40:26.319Z <ZWaveJSController:5:ZWaveJSController.js:684> ZWaveJSController#zwavejs updating attributes for node 20 value "0:128:level:"=100: [Array][ "battery_power.level", "battery_power.since" ] [latest-23242]2023-09-08T05:40:26.320Z <ZWaveJSController:5:ZWaveJSController.js:698> ZWaveJSController#zwavejs updating attribute battery_power.level with [Object]{ "entity": "20-0", "impl": { "expr": "float( value ) / 100", "valueId": "128:level:" } } [latest-23242]2023-09-08T05:40:26.321Z <ZWaveJSController:5:ZWaveJSController.js:591> ZWaveJSController#zwavejs _apply_value entity Cover#zwavejs>20-0 battery_power.level [latest-23242]2023-09-08T05:40:26.322Z <ZWaveJSController:5:ZWaveJSController.js:655> ZWaveJSController#zwavejs _apply_value battery_power.level=1 [latest-23242]2023-09-08T05:40:26.323Z <ZWaveJSController:5:ZWaveJSController.js:698> ZWaveJSController#zwavejs updating attribute battery_power.since with [Object]{ "entity": "20-0", "impl": { "expr": "time()", "valueId": "128:level:" } } [latest-23242]2023-09-08T05:40:26.323Z <ZWaveJSController:5:ZWaveJSController.js:591> ZWaveJSController#zwavejs _apply_value entity Cover#zwavejs>20-0 battery_power.since [latest-23242]2023-09-08T05:40:26.324Z <ZWaveJSController:5:ZWaveJSController.js:655> ZWaveJSController#zwavejs _apply_value battery_power.since=1694151626324<9/8/2023, 1:40:26 AM> [latest-23242]2023-09-08T05:40:26.325Z <ZWaveJSController:5:ZWaveJSController.js:722> ZWaveJSController#zwavejs setting Cover#zwavejs>20-0.x_zwave_values.Battery_level to 100 [latest-23242]2023-09-08T05:40:26.333Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event value updated entity Cover#zwavejs>20-0 [latest-23242]2023-09-08T05:40:26.334Z <ZWaveJSController:5:ZWaveJSController.js:667> ZWaveJSController#zwavejs update node 20 value "0:128:isLow:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 20, "args": { "commandClassName": "Battery", "commandClass": 128, "property": "isLow", "endpoint": 0, "newValue": false, "prevValue": false, "propertyName": "isLow" } } [latest-23242]2023-09-08T05:40:26.336Z <ZWaveJSController:5:ZWaveJSController.js:324> ZWaveJSController#zwavejs request 1694151625064<9/8/2023, 1:40:25 AM> (node.refresh_values) success notification [latest-23242]2023-09-08T05:40:26.337Z <ZWaveJSController:5:ZWaveJSController.js:684> ZWaveJSController#zwavejs updating attributes for node 20 value "0:128:isLow:"=false: [Array][ ] [latest-23242]2023-09-08T05:40:26.338Z <ZWaveJSController:5:ZWaveJSController.js:722> ZWaveJSController#zwavejs setting Cover#zwavejs>20-0.x_zwave_values.Battery_isLow to false [latest-23242]2023-09-08T05:40:26.558Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event statistics updated entity Cover#zwavejs>20-0

Please note the highlighted logpart - no other iblind has this. In addition, in MSR>Entities several show as null rather than having a value as the others do.

69631fbc-db4e-4e8d-aa98-10565811cd93-image.png

I tried deleting all Entities associated with this device from MSR and then refreshing ZWaveJS in Home Assistant and restarting MSR - the Entities return but in the same state/s.

Admittedly, it's been a very long three weeks at work - I could have missed something obvious during setup but I sure can't figure what it is.

Hey guys...

We are replacing the heat pump and furnace this week and I will also need to replace my nest thermostat at the same time 'cause Nest is ending the cloud thing end of the month.

Anyway, I'm looking to use the

T6 Pro Z-Wave Programmable Thermostat | Smart Home | Honeywell Home

That's what the heat pump installer recommend BUT, using Nest I was also using it to control the home humidifier using a single wire connected to nest... but no low voltage thermostat is able to do that, I checked all of them...

So I need some help on how I can do that, to connect the home humidifier using zwave also....

Hi
I am trying to connect a vintage radio to my home smart network, replacing the old parts with a smart speaker. I have a small light bulb inside the radio hooked up to a 6v battery that I also want to connect to the home network. Is it possible to get a smart device that I can use as a switch for this light bulb circuit? if not, I would be grateful for any ideas on how to connect a small (torch-sized - it needs to slot into a 10mm hole) light bulb to the home network.
many thanks

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.

Hi

We are looking for a solution where we can detect presence of a «thing» (people , car , dog, cat, and more..

We need:

fast detections, 1-3 seconds in range from 0 to 20 m from «base» fysical «client» , chip , transmitter , unit. base , receiver placed at a door, gate, house, etc uniq Identifying wireless

The client:

no need for pressing any thing (no buttons) battery , hoply 2-5 years battery time.

Have someone done anything like this?
What technologi will be best?

Set up:

a) Many many many many kms from home: laptop connected to modem router. Router running wireguard client to create a virtual network.

b) Home: modem router running wireguard server. openLuup pi4 connect to router and also a PC and other stuff, etc.

The problem: When accessing charts, AltUI or the openLupp console the web pages are returned OK up to the point where they are truncated and therefore fail to display anything useful.

Note this all works fine over short distances eg around a major city (I tested it) but not seemingly at world wide distances. ie network delays seem to be the issue here? Windows TeamViewer works fine overy the exact same network/wireguard set up. That's how I was able to get the openLuup logs shown below.

Here is any example of openLuup trying to return a chart:

2023-09-04 21:31:20.463 openLuup.io.server:: HTTP:3480 connection from 10.0.0.2 tcp{client}: 0x55aed35038 2023-09-04 21:31:20.464 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=316885191&Timeout=60&MinimumDelay=1500&_=1692128389970 HTTP/1.1 tcp{client}: 0x55ae538348 2023-09-04 21:31:20.465 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=316885191&Timeout=60&MinimumDelay=1500&_=1692129024374 HTTP/1.1 tcp{client}: 0x55addbe1e8 2023-09-04 21:31:20.477 openLuup.server:: GET /data_request?id=lr_render&target={temp_first_floor.w,temp_ground_floor.w,temp_back_wall_of_office.w,temp_inside_roof.w,temp_jps_bedrm_north.w,temp_outside.w}&title=Temperatures&height=750&from=-y&yMin=0&yMax=40 HTTP/1.1 tcp{client}: 0x55aed35038 2023-09-04 21:31:20.478 luup_log:6: DataGraph: drawing mode: connected, draw nulls as: null 2023-09-04 21:31:20.502 luup_log:6: DataGraph: Whisper query: CPU = 23.122 mS for 2016 points 2023-09-04 21:31:20.532 luup_log:6: DataGraph: Whisper query: CPU = 22.952 mS for 2016 points 2023-09-04 21:31:20.561 luup_log:6: DataGraph: Whisper query: CPU = 22.738 mS for 2016 points 2023-09-04 21:31:20.575 luup_log:6: DataGraph: Whisper query: CPU = 9.547 mS for 2016 points 2023-09-04 21:31:20.587 luup_log:6: DataGraph: Whisper query: CPU = 9.569 mS for 2016 points 2023-09-04 21:31:20.598 luup_log:6: DataGraph: Whisper query: CPU = 9.299 mS for 2016 points 2023-09-04 21:31:20.654 luup_log:6: visualization: LineChart(2016x7) 196kB in 51mS 2023-09-04 21:31:20.655 luup_log:6: DataGraph: render: CPU = 51.219 mS for 6x2016=12096 points 2023-09-04 21:31:20.755 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x55aed35038' sending 2 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:20.855 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x55aed35038' sending 6 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.037 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x55aed35038' sending 2 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.138 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x55aed35038' sending 6 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.332 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x55aed35038' sending 2 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.432 openLuup.server:: error 'socket.select() not ready to send tcp{client}: 0x55aed35038' sending 6 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.507 openLuup.server:: error 'closed' sending 196367 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.507 openLuup.server:: ...only 144000 bytes sent 2023-09-04 21:31:21.507 openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.507 openLuup.server:: ...only 0 bytes sent 2023-09-04 21:31:21.507 openLuup.server:: error 'closed' sending 5 bytes to tcp{client}: 0x55aed35038 2023-09-04 21:31:21.507 openLuup.server:: ...only 0 bytes sent 2023-09-04 21:31:21.507 openLuup.server:: request completed (196367 bytes, 10 chunks, 1030 ms) tcp{client}: 0x55aed35038 2023-09-04 21:31:21.517 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x55aed35038 2023-09-04 21:31:22.824 openLuup.io.server:: HTTP:3480 connection from 10.0.0.2 tcp{client}: 0x55aea22c88

Re: socket.select() not ready to send

Is there some sort of timeout I change; to see if this can make this work?

Note that openLuup is still running everything flawlessly for ages now, including the more recent addtions of ZigBee stuff. Much appreciated.

Good afternoon,
I'm running my MSR instance on an old NAS server running Fedora 37 Server. This is an older Core i5-4690K server that has served me well overall, but it's showing it's age, and will often reboot into maint mode if it applies updates overnight. I've been trying to troubleshoot, but it's also in my office (makes my office hot), and I'm looking at getting either a QNAP or Syslogy rack mount NAS to replace it.

What I'm wondering is what the process would be to migrate my current MSR config and move it to a different platform. I have quite a large ruleset that I don't want to have to recreate. I know I can run it in a container on either platform, but I'm not sure how I would migrate all my rules over. Is there one config file that has all of the rules, or could I simply copy my /reactor directory over to a enw platform?

I am also considering moving the MSR instance to a stand alone RPI 4 with a SSD. This way, while I'm migrating all of my files off of my NAS, I'm not loosing Reactor's functionality until I have whichever rack mount NAS I go with up and running, with all of the data migrated.

Thoughts?

Hello,

I've installed MSR in a Docker container on my Synology NAS. I'm able to access my Vera, but I'm having trouble using the Reactor import within the Docker environment. I'm using the Docker terminal, and I've navigated to "/opt/reactor". However, when I try to run the command, it's telling me I'm not in the installation directory, even though I can see the "tools" directory and the "apps.js" file there. I've also tried changing the file permissions, but nothing seems to work. How do you manage this in a Synology Docker container? Do you use the terminal inside Docker, or SSH into the Synology itself? I'm not finding the "/opt/reactor" path, but I see a "/var/reactor" directory, which I placed in my storage folder.

ERROR: This script must only be run from the Reactor app directory.

Hey everyone, I'm currently working on developing a bed sensor that can detect when you're out of bed. It could be used to trigger other smart home gadgets, like lights or blinds, temperature etc.
The sensors are placed under the legs of your bed post. Should look and feel like "smart furniture pads" with size 2 inches in diameter and 1/4 inch thick.
Before we go any further, I'd love to get your thoughts on this - would a bed sensor like this be something you'd find useful? We're still in the early stages of development, so any feedback you have would be greatly appreciated. Thanks in advance!

smart möbeltass.JPG

@toggledbits

Maybe I'm missing something, but this appears to be a bug.

I'm troubleshooting a rule to see if one of the system participants is arriving (presence changes from not home to home). I want this arriving state to be less than 5 minutes (300 seconds), to differentiate between being home for a longer period of time, and just getting home.

In the restrictions sections of the Trigger, I set "Condition must be sustained for less than 300 seconds", and I save the trigger.

After I save and exit, I'm looking at the rule, and it's changed itself to x_hass.state == home; for at least 300 secs. I go back into edit the rule, and it in fact shows "at least" from the drop down.

This logic is of course failing and I can't seem to get it to work.

Changed to less than, and saved:

10a57ff9-4d8c-46b3-b594-399ef2a6d320-image.png

Exited:

a81587d6-f0fa-4518-ad00-a9f601f14509-image.png

Back in rule:

b8e27dd2-e6e7-4f93-844e-83e2b11e976d-image.png

I'm running latest-23218-ebab7a1b.

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

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

C

I added the Proximity integration to HA to create automations based on if a person is on vacation or not. The integration creates an entity and its x_hass.state is the distance to the zone you have setup in HA. For some reason MSR sees that value as a string so I am not able to use the<, >, etc operators as a trigger. Is there anyway this could be fixed without needing to convert the string in a local expression?

MSR 23218
HA 2023.8.3

Entity Attributes if needed

x_hass.domain="proximity" x_hass.entity_id="proximity.arman_proximity" x_hass.services=["proximity"] x_hass.state="0" x_hass_attr.dir_of_travel="unknown" x_hass_attr.friendly_name="arman_proximity" x_hass_attr.nearest="Arman’s iPhone" x_hass_attr.unit_of_measurement="km"

MSR Version: latest-23218
Running as Docker Container : Docker version 24.0.5, build ced0996
OS: Linux 15BPMSR1 6.1.26-05272-g26c406245a2c #1 SMP PREEMPT_DYNAMIC Thu Apr 27 10:15:40 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

SMTP notifications had been working fine and I am unsure exactly what action(s) stopped it from working.

I have verified that the SMTP server configured in notifications.yml is working properly.

To duplicate the problem I am forcing an SMTP email notification using the set reaction play button, the reactor.log shows the following errors:

[latest-23218]2023-08-21T14:23:22.462Z <wsapi:ERR> [WSAPI]wsapi#1 can't queue reaction rule-lgxmrba4:S: [Error] Engine has not been started [-] [latest-23218]2023-08-21T14:23:22.463Z <wsapi:CRIT> Error: Engine has not been started [-] Error: Engine has not been started at Engine.queueReaction (/opt/reactor/server/lib/Engine.js:1494:46) at WSAPI.clientMessage (/opt/reactor/server/wsapi/wsapi.js:782:64) at WebSocket.<anonymous> (/opt/reactor/server/wsapi/wsapi.js:301:157) at WebSocket.emit (node:events:527:28) at WebSocket.emit (node:domain:475:12) at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1068:20) at Receiver.emit (node:events:527:28) at Receiver.emit (node:domain:475:12) at Receiver.dataMessage (/opt/reactor/node_modules/ws/lib/receiver.js:517:14) at Receiver.getData (/opt/reactor/node_modules/ws/lib/receiver.js:435:17)

I have tried:

OS level: apt udate and apt upgrade and reboot

docker pull toggledbits/reactor:latest-aarch64 latest-aarch64: Pulling from toggledbits/reactor Digest: sha256:d8a019d457c9fef61f7c3e6908db1f1d0a2d14b6f7c5e9d4fc536c791503d152 Status: Image is up to date for toggledbits/reactor:latest-aarch64 docker.io/toggledbits/reactor:latest-aarch64

docker stop reactor
docker start reactor

docker compose down
docker compose up -d

To no avail.

I feel like I'm missing something obvious but can't put my finger on it.

Thank you in advance for any guidance.
-bh

I have a rule that's driving my pool heater to match the solar excess. In the previous iteration, I checked for the status every minute, but I wanted something different and smarter. The logic is basically:

run continuously from 9:15 to 18:15 check for conditions, and if there's solar excess, use the power to turn on the heater, then wait 1 minute to check again turn off the heater, then wait 5 minutes to prevent frequent on/off cycles

I thought that this could be very similar to Reactor-Ex machina's logic, so I crafted a rule that's basically doing the same: an infinite loop from 9:15 to 18:15 that's checking for status and has a delay based on the heater's condition.

All went well, but after a couple of hours, I got this:

Reaction task "49683" failed due to an exception. Please see the log. rule-liy7z3gf:S (Pool-Heater-Solar) step 0: Error: Task has run too much! Runaway?

and the rule was reset (and the heater was left on). Is that by design and I should adopt another strategy? What are others doing when they have a state machine?

With the EV charger I did two groups of condition, each triggering every x minutes based on the charger status, but this seems less smarter and very rudimental. Any suggestion is appreciated. Thanks.

I have a Tripp-Lite UPS (https://www.tripplite.com/smartpro-lcd-120v-1500va-900w-line-interactive-ups-avr-tower-lcd-usb-10-outlets~smart1500lcdt) that connected by a USB cable to my computer, reports various power supply and failure information, as shown in the panel below.

b9f0ea34-d654-4b26-b968-4f8cf0a4e0c1-image.png

afa73913-5318-42c6-af9a-02d36e2e6ea1-image.png

The application I installed runs Java and opens the console to send the information.

Has anyone tried to bring the information into the MSR? Or even a VeraPlus?

Thanks.

Hi

I am stuck trying to extract the "SignalLevel" value which is the WIFI Signal Strength off my Foscam via a http request. The request returns this, which isn't Json formatted data I don't think.

<CGI_Result> <result>0</result> <SignalLevel>52</SignalLevel> </CGI_Result>

I created a rule that saves the http response into a Global Expression

872f534e-5899-43e4-ade5-f2b8ab54a412-image.png

But I am struggling to work out what is the correct expression code to extract the value?

Can anyone more knowledgeable please help?

Thank you.

Hi

Today in MSR alerts I see 100 alerts saying that the devices on my Ezlo controllers no longer exist.

They do still exist. I checked some of these devices in the Ezlo Online API Tool doing a hub.devices.list query.

I then checked that the ID numbers were the same for the devices and they are the same device ID's still.

So my devices do still exist with the same device ID's it seems.

So not sure why MSR has over 100 alerts saying otherwise.

9d7c4732-40f3-4551-b8d4-e24e0e8dda10-image.png

I then looked in Entities selected my Ezlo Plus controller and it listed all my devices OK I think and nothing looked out of place.

Thanks