This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Official
Comments
Another alternative is perhaps to use the sunset or sun-up as trigger and check the away-state.
https://github.com/ArjanKranenburg/virtual-devices/issues/57
Then I'll investigate when time and priority are right.
cheers all!
I'm trying to have Alexa properly turning on my Hi-fi.
Simple virtual device (switch) since Buttons are not supported by Alexa.
If switch is turned on - sent command to receiver to be switched on
If switch is turned off - sent command to receiver to be switched off
easy.
Now, the Hifi can be turned on/off manually. Which results in the switch being switched off manually and if set to off by Alexa, it doesn't trigger. It was already turned off and visa versa. The virtual switch and the state of the device are no longer in sync.
I thought, lets use my power meter to detect whether the device is actually on. But then I get into loops and all kind of issues.
How did you guys do it?
Flow 1:
IF HiFi is turned on - THEN turn VD on
Flow 2:
IF VD is turned on - THEN turn HIFI on
Flow 3& 4: similar with the "off status"
The loop is not forever, because it only react to status changes of your devices (thus "is turned on/off"). E.g. it cannot be turned on twice..
https://forum.athom.com/discussion/5315/stateless-virtual-device#latest
When creating a virtual device Thermostat with cool / heat/off/auto selection I would like to trigger a flow depending on the value so that I can send that to my heatingpump API. Is that possible or am I missing something.
Thanks!
Current state Hifi is Off.
The Hifi is turned on.
This triggers flow 1
This triggers flow 2
but it doesn't trigger flow 1 since its not 'turned' on. It was already on.
hMM. Sounds logical. I'll need to play. The fact that the trigger is 'turned' on. Its a little if statement in the trigger itself. Because it implies that the device is Off.
1 Add the card entitled 'Set a virtual sensor value' in the Then-column of a flow.
2 Set the technical name (see below) of the sensor-capability in the first field.
3 Set the value in the second field. This can also be a tag from another device or card.
The technical name card shows alarm_motion but this does not work.
Unless its an alarm sensor from alarms and not sensors and is a different one.
But I could be wrong.
But how can I pick this previous value up in a flow? Can you explain that? There's a few tags on the virtual device. But I can't figure out which one contains the previous value.
there are 4 tags and 1 generic tag on my multi-mode device. A tag for each mode (home,away,sleep,vacation) but they are named all the same. I need to assume that the order of the tags is equal to the statuses.
But still, you implemented my awesome suggestion. I'm going on holiday so i was about to do some nice flow-building but couldn't figure how out how you implemented it. Please help.
The previous state is only added for new Virtual Multi-mode devices. Did you create a new Multi-mode device?
Then the previous value is stored in a tag called:
"en": "Previous Multi-mode state",
That's a huge operation. Its used in 50+ flows and the Search is not always giving all the results.
But thanks! I will definitely do it. Because I want to be able to trigger things when i'm back from vacation or go on holiday etc.
https://forum.athom.com/discussion/comment/75265/#Comment_75265
- temperature
- luminance
- battery
What would be the easiest way to accomplish this? The data is coming from a MQTT device subscription. So I need to parse it in some form.
The Virtual Selector could be implemented with an enum, but then I would need the enums from all users up front.
The only way to implement this was with a multi-mode. Would that be suitable for you?
I do forward the data from my domoticz install to homey and that works
I only do not have a nice device in Homey to show the current power consumption and the total power of the meter.
I can see the in better logic
I have tried this weekend to further test a Virtual PIR, but I can get it working, not with alarm_motion and not with one of the existing values like measure_temperature.
Further the Virtual on/off type or Virtual switch is not recognised by Heimdall at all
Made a flow with a trigger to set the Virtual PIR and switch, but Heimdall does not show anything in the log about these devices.
The Virtual PIRr is recognised by Heimdall as a valid device, but not possible to trigger the Virtual switch is not recognised at all.
I suspect that this needs changes in Virtual Device?