@toggledbits yes that was the problem, thanks on the fix.

Best regards

@toggledbits here is the log

[latest-22328]2022-11-30T19:58:30.832Z httpapi:ERR httpapi: perform hvac_heating_unit.set_setpoint on Thermostat#hass>climate_vivax failed: [TypeError]Typ>
[latest-22328]2022-11-30T19:58:30.834Z httpapi:CRIT TypeError: Type mismatch on config reactor.engine.monitored_entities, expecting array, got object
TypeError: Type mismatch on config reactor.engine.monitored_entities, expecting array, got object
at Configuration.getConfig (/opt/reactor/server/lib/Configuration.js:163:23)
at Function.getConfig (/opt/reactor/server/lib/Configuration.js:151:82)
at HTTPAPI._handlePerformRequest (/opt/reactor/server/lib/httpapi.js:834:56)
at /opt/reactor/server/lib/httpapi.js:396:61
at Layer.handle [as handle_request] (/opt/reactor/node_modules/express/lib/router/layer.js:95:5)
at next (/opt/reactor/node_modules/express/lib/router/route.js:144:13)
at Route.dispatch (/opt/reactor/node_modules/express/lib/router/route.js:114:3)
at Layer.handle [as handle_request] (/opt/reactor/node_modules/express/lib/router/layer.js:95:5)
at /opt/reactor/node_modules/express/lib/router/index.js:284:15
at param (/opt/reactor/node_modules/express/lib/router/index.js:365:14)

and another on with different request

[latest-22328]2022-11-30T20:02:22.335Z httpapi:ERR httpapi: perform hvac_control.set_mode on Thermostat#hass>climate_vivax failed: [TypeError]TypeError: T>
[latest-22328]2022-11-30T20:02:22.336Z httpapi:CRIT TypeError: Type mismatch on config reactor.engine.monitored_entities, expecting array, got object
TypeError: Type mismatch on config reactor.engine.monitored_entities, expecting array, got object
at Configuration.getConfig (/opt/reactor/server/lib/Configuration.js:163:23)
at Function.getConfig (/opt/reactor/server/lib/Configuration.js:151:82)
at HTTPAPI._handlePerformRequest (/opt/reactor/server/lib/httpapi.js:834:56)
at /opt/reactor/server/lib/httpapi.js:396:61
at Layer.handle [as handle_request] (/opt/reactor/node_modules/express/lib/router/layer.js:95:5)
at next (/opt/reactor/node_modules/express/lib/router/route.js:144:13)
at Route.dispatch (/opt/reactor/node_modules/express/lib/router/route.js:114:3)
at Layer.handle [as handle_request] (/opt/reactor/node_modules/express/lib/router/layer.js:95:5)
at /opt/reactor/node_modules/express/lib/router/index.js:284:15
at param (/opt/reactor/node_modules/express/lib/router/index.js:365:14)

I tried tonight with curl and postman i get the same response
request failed
no further info.... this is only happening when i try to make a request to entity.

I also tried to make a reaction with the http request to reactor and the response is:
Reaction "re-lb2sork5" (re-lb2sork5) step 1 http request failed
Error: HTTP request failed: 400 Bad Request

I hope this gives you more info

Hello @toggledbits im trying to control reactor from external source, for this example i'm using web browser.

(this is example for the docker installation on ubuntu server)
When i hit a web page http://192.168.0.39:8111/api/v1/entity/hass_container>climate_vivax/perform/hvac_heating_unit.set_setpoint?setpoint=26
i get a response
'Request failed'
and the action is not executed

When i hit a web page http://192.168.0.39:8111/api/v1/reaction/re-lb1bejbo/run
i get response
{"status":true,"message":"Vivax Off started"}
and the action is executed

On the unraid server docker installation when i hit http://192.168.0.81:8111/api/v1/entity/hass>climate_vivax/perform/hvac_heating_unit.set_setpoint?setpoint=26
i recieve a response
{"status":true,"message":"Performed hvac_heating_unit.set_setpoint on Thermostat#hass>climate_vivax"}
and the action is executed

when i hit http://eonnet.duckdns.org:8112/api/v1/entity/hass>climate_vivax/perform/hvac_control.set_mode?mode=off
i recieve a response
{"status":true,"message":"Performed hvac_control.set_mode on Thermostat#hass>climate_vivax"}
and the action is executed.

Best regards

Hello @toggledbits I have a strange issue with the HTTP request that i send to Reactor.
I have two reactors one on a Unraid server and one on Ubuntu server installed as a docker, when i send http get request to the Unraid server to control home assistant entity everything is going ok, but when i send the same request to the ubuntu modified accordingly it says "Request failed" but when i try to run reaction via http request it works.

When i go to entities and try to control the entity manually its working.

Any idea's?

Best regards

@vezinpi yes hassos

@vezinpi in addon settings add 3000 port to the host.
And than you can access the zwavejs2mqtt addon via ws://ip:3000

Hello, i managed to connect the HA add on to reactor. The first thing i noticed is that mappings for fan on ZXT-600 and ZXT-120 IR extender for AC are incorrect, on reactor are as follows: 0-off, 1 - auto, 2 - continuous, 3 - periodic, 4 - low, 5 - medium, 6 - high, in zwavejs web console are 0 - Auto low, 1- Low, 3 - High, 5 - Medium

Hello, i'm running zwavejs2mqtt addon on Home Assistant and the addon don't allow to connect to the addon via IP address. Is there a solution for this or i'm out of luck?

I'm running my Reactor on a docker on Unraid, and home assistant os as a VM on the unraid, i can't install docker zwavejs2mqtt because for some unknown reason my zwave stick loses a connection with the docker after couple of days and cant find the solution for that.

cheers

I’m using HA with zwavejs2mqtt addon

@perh The addon menu is just a docker containers, you have all of them as a separate docker which you can install.

Thanks, found the problem updated and its working, in your instruction for installation the container is named toggledbits/ezmqtt:latest-generic-amd64 and in the docker hub latest version is toggledbits/ezmqtt:latest-amd64, that is why it didnt update.

cheers

Hello @toggledbits i run ezmqtt in a docker, updated to the latest version and still have the same issue:
here is the error in the log that i recieve

at EzloClient.handle_message (/opt/ezmqtt/lib/ezlo.js:664:25)
at /opt/ezmqtt/lib/wsclient.js:233:29
at new Promise (<anonymous>)
at WSClient.trigger (/opt/ezmqtt/lib/wsclient.js:229:16)
at WebSocket.<anonymous> (/opt/ezmqtt/lib/wsclient.js:76:30)
at WebSocket.emit (node:events:390:28)
at Receiver.receiverOnMessage (/opt/ezmqtt/node_modules/ws/lib/websocket.js:1008:20)
at Receiver.emit (node:events:390:28)
at Receiver.dataMessage (/opt/ezmqtt/node_modules/ws/lib/receiver.js:517:14)
at Receiver.getData (/opt/ezmqtt/node_modules/ws/lib/receiver.js:435:17) {
code: -32602,
reason: Unexpected Json format for value type 'bool': ["true","true"]
}
mqtt: <ezmqtt/set/device/61e8937e124c35129921171d/item/switch true> failed; Wrong field of object (-32602): Unexpected Json format for value type 'bool': ["true","true"]

I send plain payload true on topic ezmqtt/set/device/61e8937e124c35129921171d/item/switch.

version that is shown in the log file is Version 21357

cheers

Hi @toggledbits,

i tried the ezmqtt today, i have some issues most likely that i'm doing something wrong.

i have on my ezlo hub 3 switches, 1 dimmer and 1 motion sensor

i can control the dimmer via ezmqtt/set/device/<device-id>/item/<item-name>
but i can't control the switches.

i receive on ezmqtt/tele/device/61e8937e124c35129921171d/item/switch payload true or false depending on the state of the switch, but when i send on ezmqtt/set/device/61e8937e124c35129921171d/item/switch payload true or false nothing happens, its the same for all switches.

what i'm doing wrong?

Cheers

@crille i haven’t tried it wit ezmqtt i intend to try it today, but have tried it with zwavejs2mqtt and its pretty smooth.

@crille you can use the mqttthing plugin on homebridge

Thanks both @toggledbits and @Elcid. I will use the @toggledbits idea because i dont need instantaneous feedback from ezlo.

Did anybody tested ezlo with higher number of devices how it compares with Vera? i have around 50 zwave devices and when i turn on scene with multiple devices sometimes it takes 1 minute scene to complete, i get a lot of retries especially with the dimmers, the zwave network is good because the 50 devices are in 60 sqm apartment on 2 floors so 50 devices make excellent mesh 90% of the devices are mains powered.

My idea is to use Ezlo hub for zwave devices and transfer them to Control4 via HTTP calls. that is why i will use @toggledbits solution because ezlo -> Control4 is just for feedback i dont need instantaneous response, from C4 -> Ezlo i will use direct http call so that will be instant

@toggledbits said in Sustained condition is missing from MSR:

So, you want to do something when it has not changed for 3 seconds... think about how to structure that.

What i'm trying to do is to import ezlo dimmer in vera and have 2 way communication. If i do action on change without sustain sometimes it goes in a loop, so i want to make sure that dimmer has reached the level and stayed on that level for couple of seconds before i send the information back to vera. In vera i'm using your virtual dimmer. But for some reason when you turn on ezlo the dimmers make a short stop for couple of hundred milliseconds somewhere in between causes a race between the two dimmers.

What should i choose, what i'm trying to achieve is that when dimmer level changes and stays for example 35% for 3 seconds pass the dimmer level to a http call