Update bridged scenes

Plugins & Plugin Development openLuup
1

Hi akbooer,

I just updated to the latest development version of openLuup to make sure the Vera’s get addressed used port_3480. That works fine for the variables etc.

However, I looked at the bridged scenes and there I see an issue. First I see much more scenes than expected. The Vera has 33, VeraBridge reports 40, and on the ALTUI screen I see 48. All scenes I do not see on Vera are in Room 0. Some as they have a Geofence as trigger and thus are not shown on the Vera Web GUI, and others are notifications, not really scenes.

Last more serious the URLs in the bridged scenes LUA code still have :3480 in them. For me they even have old IP addresses I had in an earlier setup. The VeraBridge devices have the correct IP address, but the scenes do not.

For example this is in the LUA code now with the old IP address
luup.inet.wget “http://192.168.178.40:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=50”

But I would expect with port_3480 and the new IP address
luup.inet.wget “http://192.168.142.200/port_3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=50”

Is there a refresh option?

Cheers Rene

2

By default, linked scenes are not purged by the bridge… you may have added timers, or devices watches, or whatever locally.

To purge, you need to turn BridgeScenes off, reload, turn them on, and reload again.

The mismatch between reported and Vera scene numbers may be due to some notifications, which on Vera are scenes, but hidden.

Give the above process a whirl and let me know. The new bridge definitely uses port_3480 for linked scenes.

3

Hi akbooer,

As always you are right ;D. Worked like a charm.

Cheers Rene