I’ve noticed that since I’ve upgraded to the latest beta, when I refresh I get “ERROR: Refresh failed. Please check your settings. (java.lang.NullPointerException)”
As it is in beta, things are still changing a lot. Sometimes, when necessary, an upgrade may reset the database. Please re-do the setup. That should resolve this issue.
Edit: typos
As with the version previous to this one, when first opening the app, any command or refresh would initially fail until you refreshed it.
It’s almost like Vera’s asleep until the second time you try something.
What causes this and is there any way to fix it?
[quote=“Canadian EC, post:63, topic:170787”]As with the version previous to this one, when first opening the app, any command or refresh would initially fail until you refreshed it.
It’s almost like Vera’s asleep until the second time you try something.
What causes this and is there any way to fix it?[/quote]
Hmm, I haven’t seen that problem. When you say it fails, what happens exactly? Does it prompt you to do a full refresh? Force close? Do you see any errors?
Does anybody else have this issue?
I dont see all my devices, in particular my VirtualSwitch and WakeOnLan devices. I can understand not showing the IPSerial devices, but how do you decide which devices to show and not show?
Plugins are a different case for integration into 3rd party apps like HomeBuddy and AutHomation, etc. They would require adding additional support for each particular plugin. So for rakstar, if he has not already added support for those plugins, he would need to write additional code to support them. In which sometimes it can be a pain to do so. And of course this would be his decision to support them or not.
- Garrett
Plugins are a different case for integration into 3rd party apps like HomeBuddy and AutHomation, etc. They would require adding additional support for each particular plugin. So for rakstar, if he has not already added support for those plugins, he would need to write additional code to support them. In which sometimes it can be a pain to do so. And of course this would be his decision to support them or not.
- Garrett[/quote]
@slushpupie Garrett is absolutely right. If you send me your user data and maybe some screenshots though, I could TRY to add support for it. It should be straightforward to implement if the plugin is informational only, but if the device takes commands, I may need some Vera logs as well (requires some SSH and CLI know-how).
Working fine for me. The auto refresh will be nice otherwise no issues here.
Hi All,
I just released a new beta build. Note that you will need to clear data after upgrading. Some fun changes in this one…
Changelog:
- Added camera streaming
- Speak a scene (experimental)
- Now restores room expand/collapse state after full refresh
- Fixed WindowCovering, DoorSensor, and SmokeSensor
- Some performance optimizations
Let me know what you think!
Downloaded. No luck on camera image.
Sent from my MB860 using Tapatalk
Can you provide more details? What’s your camera? Can you send me your user data?
I have a Panasonic BL-C131a so that’s what I got it working with. Can anyone else report successes/failures?
[quote=“rakstar, post:64, topic:170787”][quote=“Canadian EC, post:63, topic:170787”]As with the version previous to this one, when first opening the app, any command or refresh would initially fail until you refreshed it.
It’s almost like Vera’s asleep until the second time you try something.
What causes this and is there any way to fix it?[/quote]
Hmm, I haven’t seen that problem. When you say it fails, what happens exactly? Does it prompt you to do a full refresh? Force close? Do you see any errors?
Does anybody else have this issue?[/quote]
I’ll try and recreate the error in Local mode, but Local is usually more reliable. I upgraded to the Mar 24 update this morning. In remote, I couldn’t connect on either server this morning, unistalled and reinstalled and still couldn’t connect.
Had a chance to try again just now, full refresh failed repeatedly on both servers (no socket error or NullPointerException), and then finally switched into remote mode about the 5th try in (I turned the WiFi on the phone off during all attempts. When both WiFi and Network are enabled, Home Buddy can’t seem to choose.) After the switch to remote, one scene executed in a normal amount of time (between 5-8 seconds) with confirmation, and the scene physically executed (lights came on). On the second command, it told me “Executed (Command)”, but the scene didn’t physically execute (All lighting off). Sometimes when I tap on the command, nothing happens, other times, it gives me a fail, usually it just says "executed (command) but after 20 or so tries it actually executed.
Also, at some point it loses its memory of how it was connected, while the app remains open. It’ll be either in remote or local, the letter inside the refresh symbol disappears, and it takes shutting down and restarting the app to get connectivity again, with the same type and number of errors.
It’s almost like the 2-way communication doesn’t exist anymore, or just fails to connect.
Upgraded to the latest beta and have found the Cameras are not working 5-Foscam FI8918W and 4-Foscam 8904 cameras. Tested with another native program and Vera and they all are working under UI5 1.5.346 Got error Message: ERROR: Unable to retrieve camera image
Just out of curiosity I uninstalled the new beta and reinstalled the older one in Google Play market.
I wanted to eliminate any chance of it being my network or Vera3 before plodding on. The old version works A-OK, except for the refresh glitch when switching from local to remote or back again.
The strange thing is, looking at my WiFi router (which I connect both locally and remotely through), with the new HomeBuddy version the light for Vera’s LAN output blinks, just as it does in the old version. It’s almost like it’s getting mostly through but getting stuck somewhere along the line.
Thanks for the app and your work on it Rakstar!
Thanks for the information. I’ve contacted MCV to see if they can give me a test instance to play with. Hopefully they do, I don’t have these cameras so I don’t know of any other way to test.
[quote=“Canadian EC, post:74, topic:170787”]Just out of curiosity I uninstalled the new beta and reinstalled the older one in Google Play market.
I wanted to eliminate any chance of it being my network or Vera3 before plodding on. The old version works A-OK, except for the refresh glitch when switching from local to remote or back again.
The strange thing is, looking at my WiFi router (which I connect both locally and remotely through), with the new HomeBuddy version the light for Vera’s LAN output blinks, just as it does in the old version. It’s almost like it’s getting mostly through but getting stuck somewhere along the line.
Thanks for the app and your work on it Rakstar![/quote]
Do you think you can send me some logs right after it fails? An app called aLogcat can help with this:
https://play.google.com/store/apps/details?id=org.jtb.alogcat
That’s really the only way I can diagnose without access to your system. I’d appreciate the help. Thanks!
Let me know if I can provide additional info. I missed adding that Home Buddy fails right after the error message
Please try the latest build (Tue 27 Mar 2012 03:17:04 PM EDT), I added a toast message and logs when streaming fails. This should at least give us a better idea of what’s going on.
Are you accessing your cameras from local or remote? If remote, please try local and let me know if it still fails for you.
Also, if you know your camera’s device id, try the following URL in a browser, replacing all the bits in “<>” with the correct info:
https://fwd1.mios.com////data_request?id=lu_camera_port&DeviceNum=
You can do this on a PC, doesn’t have to be your phone. If fwd1 doesn’t work for you, try fwd2. The response should give you your video streaming URL. Click on that URL and see if you can view it from your browser.
Installed the new beta and I have access to these cameras now. I noticed that I can now open several of them in sequence which is great. There is a very frequent refresh occuring which is beneficial but would be great if it could be sub-tasked and hidden except for a blinky button somewhere on the screen. Also while I’m at it is it possible to hide devices/scenes which shouldn’t be used in the client interface (wife) and shouldn’t be touched. Motion sensors, energy measurement, security, etc. I have set up two ASUS Transformers to provide user control of stuff that is permitted but the rest should be hidden. This is a very good app for my purposes and I congratulate you on the design and capabilities demonstrated in it. It is refreshing to see some professional development work being performed. Thank you for your efforts and please keep up the good work 
Whew, glad to hear that it works for you now 
With regards to hiding stuff… you can use the “Favorites” functionality to accomplish this. Hit the star next to devices/scenes that you want flagged as a favorite then in the Menu, select “Filter Favorites”. Let me know whether this is sufficient or not for your use case. Thanks.