http://forum.micasaverde.com/index.php?topic=6270.0
John.
Right, it’s the problem with having a single “Beta” upgrade URL, and then publishing that publicly (even at public Checkpoints).
A URL with [tt]?beta=[/tt] would be a better way to publish phased Betas, publicly, whilst still retaining the ability to have private betas (or a different URL)
Right now, I imagine there’s a ton of people “scattered” across all the variant Beta releases.
scattered across all betas
I’m really trying to get a formal release out so everybody can have one clean, stable starting point. The 1245 was mentioned in another thread. It has the fix for myhomeserver Schlage lock getting unconfigured. But he reported other issues with 1245, which is why we didn’t announce it.
@aaron, I think you’d benefit from having a small “set” of URLs to do the upgrades. As an example:
[ul][li]http://micasaverde.com/vera2
Regular Production Upgrade[/li]
[li]http://micasaverde.com/vera2?beta=1
Public Beta Upgrade, fixed at some version that’s formally “announced”, only updated when a public announcement is made (somewhere…)[/li]
[li]http://micasaverde.com/vera2?beta=42
Private Beta Upgrade, updated “at will” but preferably with an announcement in the Private Beta forum.[/li]
[li]http://micasaverde.com/vera2?beta=911
Nightly Build, use at your own risk and with no support.
[/li][/ul]
Separately, I sent a note to Ovidiu, Alfonso and Florin on Friday on some recommendations for Forums restructure that will better separate “Public Beta” comments from those of regular users to lessen the confusion that’s caused by mixing Production vs Public Beta vs Private Beta version discussions.
Guessed,
Good idea, its a mess in the forum right now…a firmware frenzy!
Even I don’t know what firmware I am supposed to be on??? I am new …what’s the protocol here?
I have been waiting for an announcement for Beta Testers…did I miss it?
Regards
Tim Alls
[quote=“TimAlls, post:5, topic:168137”]Guessed,
Good idea, its a mess in the forum right now…a firmware frenzy!
Even I don’t know what firmware I am supposed to be on??? I am new …what’s the protocol here?
I have been waiting for an announcement for Beta Testers…did I miss it?
Regards
Tim Alls[/quote]
Tim,
1.1.1243 was the last announced to us, but as Aaron indicates above th 1245 version wasn’t made widely available due to some issues. The [Private] Beta announcement for that release is listed here in this forum.
If you read through these, you’ll get a sense of what’s presented with each private-Beta label, along with the occasional updates on the Wiki. based Release notes (not always Sync released, which I can understand since it’s Public):
http://wiki.micasaverde.com/index.php/Release_Notes
PS: Right now I’m struggling with a 2nd jacked Vera2 unit (reporting memory errors in [tt]logread[/tt]) so I’m not as “active” as I might otherwise be with these Betas (or fixing my Plugins, for that matter)
1245 has been held up while investigating the issues myhomeserver reported. Unfortunately, there hasn’t been any progress. I checked his logs and Vera did do what it was supposed to, the problem was simply that during neighbor node discovery all nodes reported themselves as having no neighbors. The next steps were to get a Zniffer onsite and see if that shed any clues, since whatever’s going on, it’s at the Zwave protocol level and not something that’s visible in the logs.
Given that other users haven’t reported this and the demand for a new release, I’m going to move 1245 to a public beta, and if there are no regressions, make it a formal release.
@MCV,
Could you elaborate a bit on
[ul][li]19. Implement a new Infrared learning, identifying, transmitting engine.[/li]
[li]38. Add new scene recorder feature for easier scene creation.[/li]
[li]47. Add decoding of infrared signals to extract the protocol, device and button codes from a learned i/r signal[/li]
[li]67. Keep a log of polling history and success/fail, report to central server to assist tech support.[/li][/ul]
Can the USB-UIRT be used to learn IR codes?
Thanks in advance!
Ap15e, I have attached the specs we used for the developers for the tricktv mobile apps. It lists all the screens, and in the .rtf file, for each screen, you’ll see the i/r commands.
Yes, it works with the USB UIRT. Yes, it supports learning. It also supports “identifying”, where you learn one button and we figure out this is an ‘nec’ protocol used by ‘Samung’ with the device id=x and buttoncode=y and it does a lookup online and figures out what codesets contain that button so you don’t have so much trial and error and learning to do, and you can fetch the whole codeset, including toggle codes.
Post moved here:
http://forum.micasaverde.com/index.php?topic=6426.msg39630#msg39630
Given some of the more recent saga’s on the Public forum, with people “randomly” downloading from the [MCV Published Beta URL] maybe it’s time again to consider this suggestion…
[quote=“guessed, post:4, topic:168137”]@aaron, I think you’d benefit from having a small “set” of URLs to do the upgrades. As an example:
[ul][li]http://micasaverde.com/vera2
Regular Production Upgrade[/li]
[li]http://micasaverde.com/vera2?beta=1
Public Beta Upgrade, fixed at some version that’s formally “announced”, only updated when a public announcement is made (somewhere…)[/li]
[li]http://micasaverde.com/vera2?beta=42
Private Beta Upgrade, updated “at will” but preferably with an announcement in the Private Beta forum.[/li]
[li]http://micasaverde.com/vera2?beta=911
Nightly Build, use at your own risk and with no support.
[/li][/ul][/quote][/list]
Not only downloading them but getting into trouble afterwards!!
http://forum.micasaverde.com/index.php?topic=7204.msg45871#msg45871
Who’s the little bird that told @wangzang?
Aaron, we really need some professionalism here from MCV or we might as well just give everyone in the open forum “Beta Testers” titles as the links will continue to be passed from user to user. Does tech support give out the beta URL when someone calls for tech support? If so, they should make the upgrade for the user rather than telling them.
Is it too much trouble to change the beta URL as @guessed suggested?
John.
+1, most definitely.
I was thinking the same thing: time to hide the beta stuff. Every so often it comes up that someone downloaded a non-public beta. Annoying. Does not normally lead to issues, but this time it did. More annoying.
Not sure we can always blame the user, as it does not seem unreasonable to expect the beta=1 link to always point to something that is kosher. It should be the only public link. (If folks want to experiment and increment build numbers in the real link, or the beta link, so be it; that’s clearly at their own risk.)
Yes, that makes sense, and this is what we’ll do from now on. And we’ll also remove old beta links so if an old beta link is exposed in the wild it won’t continue to work once that beta has been superseded.
I seem to remember a time where there was a third URL that we used… or did I imagine that?
There was never a 3rd URL, only the vera2 and vera2?beta=1
I had an extensive talk about that with @mcvmirela just before i went to Africa for my work.
Glad something is about to be done about it.
Ive even tried reporting all the message threads that showed beta urls or even custom download links (worse IMHO)
But on the latter i agree with @oTi!
I reverted back to 1.1.1245 due to the thermostat issue in the latest beta but…
I’m now having “Save” & USB issues.
1st issue: I’m making changes to some Luup and just general device name changes and which room devices are in. After saving the changes it all reverts back the way it was before I changed it, and I’ve tried dozens of times with the same result.
2nd issue: I’m using Vera’s port 2 for a USB squid (5 tentacle hub) for the thumb drive, AdemcoVista alarm plugin and now trying to add the RFID reader.
Vera’s port 1 is for the Aeon dongle.
Vera wont boot to the GUI. The Thumbdrive LED does not come on.
But Vera is accessible via SSH.
Switch the thumb drive with the Aeon dongle (thumbdrive now in it’s own port, the dongle on the squid) Vera boots, but now I get Z-Wave failed to start or No Z-Wave dongle.
Unplug the Aeon dongle from the squid (Vera’s Z-Wave LED goes out) plug it back in and Vera’s Z-Wave LED comes back on. But Vera displays No Z-Wave dongle.
Vera sees the AD2USB (through the squid) for the AdemcoVista Alarm plugin.
Remove the AD2USB hit save and the Aeon dongle is visible through the squid, but now I cant get both to work let alone the third device.
John.
*Edit. I’ve tried to submit a ticket again, but it still stops at compressing logs. (which I’ve reported before several times with no response)
Reporting issue from ap:
Collecting logs…
. Network…
Done.
. System…
Done.
. Kernel…
Done.
. Zwave Status…
Done.
Compressing logs…
John,
A couple of comments/questions:
a) If your USB-Squid Bus powered?
Vera has a limit to the amount of power that it’ll supply, and the Squid effectively “splits” that amoungst all the attached devices, along with consuming some itself.
If it’s Bus-powered, you may be reaching those limits. Try powering it independently of Vera. I’ve had cases where chaining a few devices will stop Vera from booting (presumably not enough power drain protection)
b) Was the Squid recently added?
The location of where things ‘end up’ in Linux is dependent upon their Bus location (more or less). If you plug things directly into Vera you might get one address, and plugging them into the Squid you might get another.
This will be particularly interesting for the Z-Wave controller, since we have to specify exactly where it is for Vera to talk to it.
c) Was the AD2USB recently added?
… and is it Bus Powered, or does it power itself from the 12v line that’s attached to it from the Ademco?
d) Do a “[tt]lsusb[/tt]” as well as a “[tt]dmesg | grep -i usb[/tt]” and let’s see the data.
It’s possible that the AD2USB is getting assigned an address “prior” to the Aeon, and is messing with your Z-Wave Device/Options setting for “where” the Aeon is located (/dev/eieio/1 etc)
a) If your USB-Squid Bus powered?Yes, but it worked before with two thumbdrives and the Insteon PLM.
b) Was the Squid recently added?Yes, but again, it was attached before, removed it back in March? after Aaron disabled all my Insteon devices.
The location of where things 'end up' in Linux is dependent upon their Bus locationBut their locations are not able to be reassigned after boot up?
c) Was the AD2USB recently added?To this Vera yes, transferred it over from my test Vera. The AD2USB is seen but I cant save the assignment as nothing is saving right now or prior to adding the hub.
d) Do a "[tt]lsusb[/tt]"Bus 001 Device 001: ID 0000:0000 Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 003: ID 14cd:6700 Super Top Card Reader Bus 001 Device 004: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Bus 001 Device 008: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device Bus 001 Device 009: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
as well as a "[tt]dmesg | grep -i usb[/tt]" and let's see the data.
Vera just crashed.
*Edit.usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
SB USB20H init
SB USB20H resetting
USB20H fcr: 0x64
USB20H shim cr: 0x8f7
usb-ohci.c: USB OHCI at membase 0xb8003000, IRQ 6
usb-ohci.c: usb-00:03.0, PCI device 14e4:471a
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
uhci.c: USB Universal Host Controller Interface driver v1.1
usb-uhci.c: $Revision: 1.275 $ time 08:29:03 Jun 1 2010
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
hub.c: new USB device 00:03.0-1, assigned address 2
hub.c: USB hub found
usb.c: registered new driver acm
acm.c: v0.21:USB Abstract Control Model driver for USB modems and ISDN adapters
usb.c: registered new driver serial
usbserial.c: USB Serial support registered for Generic
usbserial.c: USB Serial Driver core v1.4
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
usbserial.c: USB Serial support registered for Belkin / Peracom / GoHubs USB Serial Adapter
belkin_sa.c: USB Belkin Serial converter driver v1.2
hub.c: new USB device 00:03.0-1.1, assigned address 3
usbserial.c: USB Serial support registered for CP210X
usbserial.c: USB Serial support registered for FTDI SIO
usbserial.c: USB Serial support registered for FTDI 8U232AM Compatible
usbserial.c: USB Serial support registered for FTDI FT232BM Compatible
usbserial.c: USB Serial support registered for USB-UIRT Infrared Tranceiver
usbserial.c: USB Serial support registered for Home-Electronics TIRA-1 IR Transceiver
ftdi_sio.c: v1.3.5:USB FTDI Serial Converters Driver
usbserial.c: USB Serial support registered for PL-2303
pl2303.c: Prolific PL2303 USB to serial adaptor driver
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: USB 2.0 Model: SD/MMC Reader Rev:
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
hub.c: new USB device 00:03.0-1.2, assigned address 4
hub.c: USB hub found
hub.c: new USB device 00:03.0-1.2.2, assigned address 5
usbserial.c: CP210X converter detected
usbserial.c: CP210X converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
John.