add :Status to your mios item
eg - Sala:Candeeiro SalaJantar:Status
That way you are just targeting when the light turn is turned on/off
In the debug mode set it to the whole msg
add :Status to your mios item
eg - Sala:Candeeiro SalaJantar:Status
That way you are just targeting when the light turn is turned on/off
In the debug mode set it to the whole msg
ok here what I got now:
I also changed the switch to is true as you said but still nothing happens on the shelly switch
where is the debug node connected?
if I put the debug after the switch nothing happens
the mios section is working, move the link to the true output.
You should then only get a debug message when you turn light on. when you turn light off it will follow the false path.
I am not using home assistant, but i believe that node needs an addon in hass.
can you post the node help information for that node. as it probably tells you how to configure the hass node.
help info for hass node, not switch.
post how the switch is configured
Help:
Sends a request to home assistant for any domain and service available ( light/turn_on
, input_select/select_option
, etc…)
Domain requiredstring
Service domain to call
Service requiredstring
Service service to call
Entity Idstring
A comma-delimited list of entity ids.
NOTICE
If entity_id
exists in the data property it will have precedence over this value.
DataJSON
JSON object to pass along.
Merge Contextstring
If defined will attempt to merge the global and flow context variable into the config
Alternative Template Tagsboolean
Will change the tags used for mustache template to <%
and %>
Output Locationstring
None
Customizable location for the output of the node.
All properties need to be under msg.payload
.
If the incoming message has a payload
property with domain
, service
set it will override any config values if set.
If the incoming message has a payload.data
that is an object or parsable into an object these properties will be merged with any config values set.
If the node has a property value in its config for Merge Context
then the flow
and global
contexts will be checked for this property which should be an object that will also be merged into the data payload.
As seen above the data
property has a lot going on in the way of data merging, in the end, all of these are optional and the rightmost will win if a property exists in multiple objects
Config Data, Global Data, Flow Data, Payload Data ( payload data property always wins if provided
domainstring
Service domain to call
servicestring
Service service to call
dataObject
Service data to send with API call
All properties will be under what is defined in Output Location
in the config.
domainstring
Service domain
service was called with
servicestring
Service service
was called with
dataObject
Service data
used in a call, if one was used
{
"domain": "light",
"service": "turn_on",
"data": {
"entity_id": "light.kitchen"
}
}
you need to select is true next to == up and down arrows
WAO! thank you so much!
Sorry to be so ignorant, but I just started using node red…
Thanks again for your patience!
Would there be any chance an update could happen with the MIOS Node Red to allow the device nodes to have an “input” as well as “output”? In this screenshot the following devices are on Hubitat (Except Master Bath Motion) connected to Node Red.
“Master Bath Motion” is a Vera/Mios Node Red node device, as you can see I’m unable to include the device into the sequence like I can with the Hubitat Nodes.
Hi
Is it possible to have node red monitor for when a Vera scene is run ?
Thanks
I use the http in node, just send a http request using Lua in scene trigger.
Indeed that was my plan B.
You should make it plan A, as it offers a response if needed .
Edit- Also i dont think the mios node listens for scenes.
Great example, could your export the flow from your Node Red instance and share it here - to help others ?
56 posts were merged into an existing topic: Using Node-Red for Google Home TTS announcements and other stuff eWeLink
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules