I’ve initially created a scene on the WebUI with a manual trigger. I then go into the Vera Mobile (iOS) to modify the trigger based on location/geofence that I’ve created. At the very end when I click “Finish” in Vera Mobile, the scene disappears from the WebUI dashboard. If I were then to change the trigger to say “Schedule”, the scene reappears.
Has anyone else seen this? I would think that this is a bug? If not, does anyone have any ideas why it is designed this way?
I am running 1.7.513 on the WebUI and 1.3 for Vera Mobile. I am also using the “House Modes Plugin” (to change house modes when I enter/exist the geofence)
I’ve seen exactly the same thing. In addition to disappearing, the room tag for that scene is removed, as in Imperihome I still see the scene in the ‘no room’ group.
Clearly a bug from a user point of view (perhaps due to the interplay of two new features: room attribution not yet supported on mobile and geolocation triggers not yet supported on the web app), though I wonder if it is semi deliberate while they add support for such scenes to the web app? My guess is the mobile and the web apps are developed by different individuals, who may not always keep pace with each other.
In my case I’ve not yet had time to verify whether the scenes are working properly or not, have you? My scenes replicate other home/away functionality so it requires disabling that to see if they are really working.
I think the scenes are executing properly. I am not 100% sure as there are inconsistent behavior with the execution of my scene (e.g. geofence enter/exit times are different each time). Because of these inconsistencies, I haven’t been able to have a robust test case to make sure the scene is as I want it. Overall I think it’s ok.
I emailed support and their response (below) is “this is a feature not a bug”. I guess I can see where they are coming from - the WebUI would not know anything about the geofence(s) that you have set up. It’s more of a hassle than anything…
Hello John,
Please note that whenever you use the geofencing feature, it will only be available for the mobile device interface, and not for the web interface. As such, if you modify a scene that includes geofencing, it will not be available anymore for the web interface, but rather only for the mobile interface.
You are not doing anything wrong, it is a design feature implemented by the development team. This is because a mobile device is usually provided with a GPS module, which is required for the geofencing feature to work.
Please let me know if you require further assistance.
Sorry for the slow response, just noticed your reply John.
Yes I found this as a ‘fix’ mentioned in the change log. I do however disagree with MCV - it would be trivial to show info related to the geofence trigger, but not allow this to be edited.
I do however wish to be able to view and edit the other triggers (manual, device, schedule) as well as the actions for these scenes, even when not using a mobile device.
Also, my scenes are also triggered manually, sometimes from the web interface, sometimes from Imperihome. I can’t do this if they are not present in the web interface, or if their room association is removed, causing them to disappear, until I divine that that is what has happened and reconfigure Imperihome to show the ‘no room’ group (which people would normally hide).
Hopefully they will reverse this ill thought through decision when they work out the real world implications of adding geolocation to apre- existing scene.