+1 for geofencing via OwnTracks
@lmilcent for your bug, I tried to reproduce it, but without success.
Could you be more specific about:
- what you expect to happen
- what actually happens
Because I couldnât even understand your bug in the end ![]()
I have a scene that works like this:
- Retrieve the humidity sensor value from my room
- Check if > 65%
- If yes, send me a message
There is no trigger for this scene. I start it manually or via another scene.
Manually, I do receive a message when the value is exceeded, but via the main scene that calls it, I receive no message.
@lmilcent Ok, I just re-tested, this time with several scenes to reproduce your behavior as closely as possible, and itâs impossible to reproduce: it still works for me ![]()
If you want, I can suggest we call today to look at this together live?
Iâll let you know when Iâm available this week, I admit Iâm a bit busy today.
What time zone are you in, so we can find a time that works for both of us?
I am in Central Indonesia Time (GMT+8), which is 6 hours ahead of France.
This week, in French time, I am available on Thursday before 12 PM and Friday before 11 AM ![]()
Is it still possible on Friday, given that the live event is scheduled?
It depends on the time, with the live stream Iâll be busy from 9:00 a.m. to 11:00 a.m. I think (preparation before + 1h30-2h of broadcasting depending on the questions), if you want before 9:00 a.m. we can call? (8:30 a.m.?) Or depending on when it ends, after the live stream, but I canât guarantee it ^^
Otherwise, next week ![]()
Weâll postpone to next week then to make it simpler ![]()
Every day before 11 a.m. then?
Nope!
Next week:
- Monday before 12 p.m.
- Thursday before 12 p.m.
![]()
Weâll see this on Monday then ![]()
Perfect! What time? At 10 a.m.?
Perfect, itâs booked in my calendar, 10 a.m. Paris time. ![]()
edit: Are there any prerequisites for the investigation?
@lmilcent See you later
No special prerequisites, weâll look at it together! Iâll send you a Google Meet link later.
@lmilcent Super call, thanks for your feedback!
Iâve updated the title of your issue: Bug: When calling a scene from a scene, the scope is passed as reference and other scenes are read/writing the same object · Issue #1200 · GladysAssistant/Gladys · GitHub
Iâll keep you posted ![]()
The other two issues mentioned have been opened:
https://github.com/GladysAssistant/Gladys/issues/1206
Thank you for your availability this morning ![]()
@lmilcent Itâs good, your bug is normally fixed in the latest dev build! ![]()
I was going to test and validate, but still no zigbee2mqtt.
If it takes too long, Iâll try to recreate it with the last working version.
Now that the Zigbee bug is fixed, I can confirm that your patch solved the problem!