After last firmware upgrade - can’t restore z-wave devices.
Downgrade to working version - and now all working fine
download.mios.com/rt3662_betafirmware/rt3662_Luup_ui7-1.7.947-en-mios.squashfs
[quote=“Cadet, post:21, topic:197627”]After last firmware upgrade - can’t restore z-wave devices.
Downgrade to working version - and now all working fine
download.mios.com/rt3662_betafirmware/rt3662_Luup_ui7-1.7.947-en-mios.squashfs[/quote]
This the right thread for that update?
Very frustrating. The sound systems in the house are not working for months. Nerves and lost money …
Has anyone made any progress with this at all ?
Previously I never had the Discovery patch installed ever, as I didn’t seem to need it, for it to detect my DLNA devices.
I have checked the J_DLNAMediaController1.js file and the line:
new Ajax.Request (data_request_url, {
Is already changed to that, perhaps I did that previously.
I created a new DLNA device in Vera and nothing is discovered still.
I then installed the Discovery Patch and now it is detecting Kodi PC’s running DLNA on them.
However it no longer detects any Logitech Squeezebox devices which it use to in the past.
With the Kodi PC’s basic transport controls are working on their DLNA device in Vera, Play / Pause / Stop etc.
I was wondering if the DLNA plug-in would detect my new Google ChromeCast devices? Its not.
On the existing Kodi DLNA devices in Vera under their Settings area it does say:
UPnP event proxy: proxy is in use
Thanks
Has anybody escalated this issuer to Customer support line? - This is quite frequently used feature within Vera Users, so I can’t understand why it is still not fixed. Will try to raise ticket today.
No I haven’t contacted support about it. Doubt they will fix a 3rd party add-on someone else wrote ?
And its still not discovering UPNP / DLNA devices properly for me. 
I think Vera themselves should start to show interest in this.
For a home automation system to have no functional dlna system is pretty terroble. Especially considering it was working but a change they implemented broke it.
Hello all,
Somewhere in early January, we have notified all the registered developers about the upcoming changes. A topic in this sense has also been posted in the development forum.
All the developers have our full support in updating their plugins based on the new API changes. Some of them are already discussing with us.
Non-maintained plugins are being analyzed as we speak, to see what is their impact on our users base and if is there any possibility of updating them ourselves. This is not a process with a definitive time frame.
[quote=“Sorin M., post:28, topic:197627”]Hello all,
Somewhere in early January, we have notified all the registered developers about the upcoming changes. A topic in this sense has also been posted in the development forum.
All the developers have our full support in updating their plugins based on the new API changes. Some of them are already discussing with us.
Non-maintained plugins are being analyzed as we speak, to see what is their impact on our users base and if is there any possibility of updating them ourselves. This is not a process with a definitive time frame.[/quote]
Hi Sorin
The other thread you linked to also mentions port 3480.
I use HTTP Json commands from other devices and apps on my LAN to control devices in Vera.
For example this command turns on my ceiling light and I have used this http command in Yatse (Kodi remote control) app as a “custom command”
http://VERA-IP:3480/data_request?id=lu_action&output_format=xml&DeviceNum=140&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1So are you saying these types of http commands sent to Vera will stop working?
If so that is going to be a massive problem !
Thanks.
It looks like we may just need to adjust the http command slightly ! Which I guess I can live with if I edit all my incoming commands.
Are the guys at Imperihome app aware of these upcoming changes? As most people use that app on their mobile devices to control Vera. EDIT: Yes they are they just told me they are aware.
Solution
This issue can’t be fully fixed by the plugin developers, however, it’s necessary that all the data_requests are made on port_3480, and NOT directly on port 3480, or on port 49451, or on port_49451.
So, any request that looks like this:
http://VERA_IP:3480/data_request?id=SOME_VALUE
http://VERA_IP:49451/data_request?id=SOME_VALUE
http://VERA_IP/port_49451/data_request?id=SOME_VALUE
Must be rewritten to look like this:
http://VERA_IP/port_3480/data_request?id=SOME_VALUE
I’ve just tried the new command in a web browser and it works already
http://VERA-IP/port_3480/data_request?id=lu_action&output_format=xml&DeviceNum=140&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1So guess I should start now updating all my LAN devices and apps that use these types of http commands send to Vera.
When running a command in the browser to run a scene it works and the scene is run but there is an error in the brower.
http://VERA-IP/port_3480/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=14This page contains the following errors:
error on line 2 at column 46: xmlns:u: ‘Unknown Service’ is not a valid URI
Below is a rendering of the page up to the first error.
OK
However when running a command to control an actual device I do not get any errors in the browser it says something like:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<u:SetLoadLevelTargetResponse xmlns:u=“urn:schemas-upnp-org:service:SwitchPower:1”>
5511
</u:SetLoadLevelTargetResponse>
Although I’m a fairly technical person, it’s not my area of expertise as I’m not a developer.
But if you are a developer and find discrepancies or issues, in working with the API please use the email in the https://goo.gl/P6k4bP to bring it to our guy’s attention.
This is the response I had from tech support via email
"Please note that we have introduced in our firmware a restriction on the port 49451 for security reasons so yes, each plugin that is using that port won?t work no more but a solution to this would be a downgrade to the version 1.7.23.
I will kindly ask you to tell us what Vera do you have so we can send you the downgrade link exactly."
I then said I didn’t want to downgrade and was hoping the developers at Vera could take a look at the DLNA plug-in to see if they could fix it.
"I?m sorry but this is not possible, this decision was made already and unfortunately there is no way back, the only solution is to downgrade the version of the firmware and to stay on it.
Thank you for understanding."
damn! thanks for the continued up dates on this CW-Kid. Don’t know why but I stopped receiving email updates so didn’t realise there were new posts.
Yeh I can’t really downgrade as their are some devices I use now which have support was only added in recent firmware versions.
Guessing we can only hope the developer updates the plugin now that the issue is known!
[quote=“Quixote, post:19, topic:197627”]I would be interested in a solution as well, particularly for the TTS announcements.
Looks like yet another reason I purchased the Vera for has gone by the wayside. >:/
Seems like if we give this thing another year or two, it’ll just be another router with Zwave operations.[/quote]
TTS annoucements with the DLNA plugin have been problematic for some time, with the Microsoft and Google TTS engines.
However I previously modified some of the DLNA plug-in files to allow you to use the “RV” (Responsive Voice) TTS engine in Vera scenes.
See my original post about that here.
My TTS broke again recently, probably due to me reinstalling the DLNA plug-in / or me uploading DLNA plug-in files again to Vera for the issues raised in this thread.
I then remembered I previously edited two files to add support for the “RV” TTS engine and I have uploaded those files again today and now my TTS is working again.
I have also included the suggested line change in this thread.
[code]OLD line
new Ajax.Request (command_url+‘/data_request’, {
by NEW line
new Ajax.Request (data_request_url, {[/code]
So attached here below are the modified files you would need to use the “RV” TTS engine in your Vera scenes.
Look at the RV-in-Scene.png to see how to use the RV engine in the Vera scenes advanced editor.
TIP:
I only now use the DLNA plug-in for TTS to send to one device in my Kitchen, for one particular scene.
For all other TTS announcements from Vera, I have been using the Imperihome plug-in for Vera and the Imperihome control app on an always on wall mounted Android tablet.
In your Vera scenes advanced editor, you can select the Imperihome device and select the function SAY and when that scene is run the TTS announcement goes to the tablet running Imperihome app etc. I then connected the tablet via Bluetooth to the Amazon Echo speaker in my living room, so all the Vera TTS announcements are now heard on that one Echo speaker device.
That’s one down side of using Imperihome for TTS though, the announcements can only be sent to one device, I think?.
But its much more reliable than TTS in the DLNA plug-in ever was.
I’ve tested the “RV” TTS engine in the DLNA plug-in with two devices.
I have a SqueezeLite emulated Squeezebox running on my WHS 2011 server, this is connected to an amp / speakers in my kitchen. This presents itself as a DLNA device.
And I have a LibreElec Kodi HTPC in my daughters room and again this presents itself as a DLNA device.
I have two scenes in Vera now, to send TTS via the DLNA plug-in.
One scene for the kitchen device that says “Beer Assistant” and one scene for the Kodi PC in my daughters room, that says “Turn off the TV and go to bed please”.
I’ve tested running both scenes and both worked OK and the TTS was played on the target device.
Did you end up Down grading CW-Kid? and that is how you are using the DLNA plugin with the other TTS engine as mentioned in your above posts?
I might submit a ticket to Vera on this one as well, can’t hurt to pepper them a bit on this.
The Imperihome scenario does sound like an option for me as I do have a Sony Andriod tablet but in reality I don’t want to add in another point of failure by having to have that “always on” and having it linked to just one speaker isn’t much good either kinda defeats the purpose of DLNA being able to point at any device that you want to render the announcement.
No I never downgraded the Vera units firmware.
Then how is the DLNA plugin working for you?