iHost (4Gb)
Firmware 2.4.0
Philips Ceiling Light
There is no option to create a scene like:
If
Is 22:30 AND Philips Ceiling Light is ON
Then
Change the color temperature to warm
When I set like this:
The device disappear from the device list on the “Then” option:
If I start creating the scene by the “Then”, I can see the device listed correctly, but it’s NOT listed on the “If” condition.
Hey
Using the same device both as triggers and actions is not supported yet.
If you need this feature, I will help to turn this into a feature request for votes.
Thx for your feedback.
I guess it’s not a feature, but a bug.
The temperature of the light should change only if the light is already ON, so I need to check if it’s ON using the “if”.
Not in your case but if they were to allow the same device to be both it’d be very easy to create a circle or devices that don’t appear to work. For example IF Device X ON turn then turn on Device X for a circle or appearing not to work: If Device X on turn off Device X. Your particular wanted scene would only be evaluated repeatedly for 60 seconds a day locally. Not ideal but also not a huge problem. If you replaced the scene with a flow in Node Red on the iHost then it would (by default) only be triggered once (at the second the time became true) and not repeatedly whilst the time is true. You could replicate the multiple loops if you wanted but you’d need to actively try to do it. To create this scene in Node Red you need to add an AND gate to your Palette, my favourite is Boolean Logic Ultimate, but there are loads and you could code it yourself using a Function node, but then why bother when you can download a palette.
Really? 
If a time is specified, iHost should trigger it only when the time becomes true.
Different programming. It is while the time is true not the first occasion only. It would reassess the Boolean every time it is asked while the time is true.
Yes obviously. If you tried to turn on the device it would turn off after a fraction of a second and the user might think their device was broken. What else do you think could happen?
My answer was a sarcasm.
That your example was quite ridiculous, sorry.
Is the same as saying “is better to not produce a hairdryer, because the user can use it in the bathtube”
Some users do that. Some do it only once in their lives, therefore they don’t learn.
It’s a IF function and not a WHILE funcion.
If…
Then…
End…
We should never see a loop as in your example.
If it’s different of this, we have a bug on how iHost is doing the actions.
This is not a bug but a design feature, although like you I don’t consider it the best one. True that there are platforms that work in the same way but for example Smartthings that I use allows this. It’s a case of as @ward said
I have decided not to ever read anyone who used the childish emoticon so you are now being ignored and nothing you ever post will be read. I did not read your post and never will read anything you ever say again. Goodbye and good luck.
Holy shit! It’s a mind blowing decision. I’m impressed.
You can build the scene you want. You need to use a manual scene in an automatic scene.
IHOST has limitations in creating scenes and you need to create a workaround.
e.g. In smartthing you can do everything in one scene.
Hey guys
As the discussion expands, I’m splitting it from the main thread of eWeLink CUBE.
The limitation was designed to avoid unexpected loops. Some users may not be aware of what they configure and such loops would cause trouble, especially when mixed with more scenes in the THEN sections.
To bypass this, you can use manual scenes as @ociepa.ekotox mentioned.
I gave up on creating scenes in ihost. I transferred all the scenes and automations to home assistant. Ihost is a waste of money for me. I currently only use it for TRVZB because of updates. Unfortunately, that doesn’t work properly either 
This can be easily fixed in your code.
For example: if the device have more than one feature (like brightness, colour), then it can be allowed to be in both trigger and action.
If the device have only one feature (like a light switch: ON/OFF), than it must be allowed just in the trigger or just in the action (not on both).
colleague @renatoyamane says well. I think so too.
