Where to start?

I like the concept. But the documentation is less than useful.

I consider myself pretty smart. But, the Verde modified itself in the middle of the night. I have the box picking up wireless, and bridging it to the Direct-TV box and a media computer “Through a wi-fi access point. Vera is a bridge.”
I woke up yesterday and found the Verde box was lost. Spent a few hours and finally reset it to factory defaults. Then I had to relearn how to get my cameras to work again. I woke up this morning and again, it is lost (off the network). When I logged into the box via the ethernet locally, I found the box has set itself to “Through another gateway on my network. Vera is a switch”. Does this mean the box is seeing the ehternet connection and self adjusting?

The documentation (Wiki), if you can call that documentation, states the ports for Verde are 80, 22, and 23. But in the wiki file it was talking about the verde listens on http://ipaddress:3480/. Should this be port forwarded also?

I am willing to learn Lua or LUUP, I still haven’t figured out what the difference is, but there is no clear documentation as to where to start. There is no beginners guide? There is no discussion as to which files need to be added to make my own control for a camera, I see there are a couple of cameras and a few files, but nothing said which file does what, and nowhere does it talk about the wrt and how to control it.

I like a challenge but this is not very promising. I can’t believe this even sold as a consumer device. With the exception of a few light switches, this is far too difficult for the general user. Even the thermostat control doesn’t work as described.

[quote=“Rick-OH, post:1, topic:165841”]I like the concept. But the documentation is less than useful.

I consider myself pretty smart. But, the Verde modified itself in the middle of the night. I have the box picking up wireless, and bridging it to the Direct-TV box and a media computer “Through a wi-fi access point. Vera is a bridge.”
I woke up yesterday and found the Verde box was lost. Spent a few hours and finally reset it to factory defaults. Then I had to relearn how to get my cameras to work again. I woke up this morning and again, it is lost (off the network). When I logged into the box via the ethernet locally, I found the box has set itself to “Through another gateway on my network. Vera is a switch”. Does this mean the box is seeing the ehternet connection and self adjusting?[/quote]

I don’t know that could be causing your intermitent problems. If they persist, please file a support request, preferably using the form in Vera. That way you can (if you wish) open a support ‘backdoor’ to directly check and diagnose your own unit.

As for the bridge/switch issue, these are the same thing. An ethernet switch is in fact nothing more than a multiport bridge.

are you port-forwarding to Vera? note that it’s normally not required for remote control, since the Vera will reach our servers where you can login, and not the other way around.

In any case, the ports 3480 and 49451 are used only locally. The UI uses internal redirection (urls like [tt]http://address/port_3480/…[/tt] are sent to port 3480), so all that’s really needed is port 80.

Lua is a general purpose scripting language; it was chosen as the scripting engine for Vera because it is very efficient and lightweight.

Luup is the Vera internal engine, written in C++. It handles the UPnP communications and call Lua scripts to perform most tasks.

If you want to write new device plugins, check the [tt]Luup Intro[/tt] and [tt]Luup Plugins[/tt] wiki pages. To put it shortly, it requires 3 files:

[ul][li]A device description XML file. This defines what your device is and can do. There are several standard descriptions defined by the UPnP consortium, and some others defined by MiCasaVerde. Chances are that you can use one of these for your device, or at least copy and modify one.[/li]
[li]A services definition XML file. This defines the state variables and actions of your device. Again, you can probably reuse some standard ones. A device description can also reference more than one service file, so you can extend functionality.[/li]
[li]An implementation file. This is also an XML file, but the contents are mostly Lua code. You can attach this code to the actions defined in the previous file, or to some Input/Output port. To communicate with the rest of the system, and with the real world, you can use the functions listed on the [tt]Luup Lua extensions[/tt] wiki page.[/li][/ul]

Also, be sure to post any development questions on the ‘Luup and Development’ section of the forum, there are several other users willing to help you.

Thank you for the informative response.

I would have expected to see that information in the documentation, like I said I am not real impressed with the lack of documentation.

As with everything, the more things I change, the less I know which one caused the failure.

As far as the Vera box changing the option to “Through another gateway on my network. Vera is a switch”, it seems that every time it does this it no longer has internet access (and therefore not accessible)

The port forward was an attempt to find out why I couldn’t access the box. Not to mention the Direct-TV would disappear also.

I will open a ticket, but I am assuming it is not a failure in the device, more a failure in the configuration. Or maybe it cannot function over the wifi and bridge the wifi to the ethernet ports.

Thank you again.