MiCasaVerde Vera UI5, UI6, UI7 Plugin

[kgschlosser]

not sure what that error is, i do not have a vera plus. they may have changed the way the data comes across. i am going to have you test something.

what I need you to do is open a web browser and then paste this into the address field, when the page loads i need you to copy the whole thing and paste it into a file save the file and attach it to a a post in this forum thread. that way i can review it.

there are 2 ways the vera can talk 1 is with xml the other is with json the latter of the 2 was easier to parse the data. so i may have to recode that end of it if the vera no longer sends out json with the newer versions.

i am hoping they didn't break backwards compatibility with a change they may have made.

to be honest i think these things are crap and don't run properly.


that company has been know to do that to their plugin devs so i don't put it out of the realm of something they would do. that's why no one is really making plugins or updating them any more for the vera that is.

i am willing to fix the problem but i do not have a vera plus and i am not going to buy one either. if i ever get around to it i am going to code a whole plugin for eg to take care of the lighting.

so if that is in fact the case i am willing to help. but it's going to be a royal pain if i have to keep on sending you files to try and explain the output. so the easiest way would be for me to either be able to vpn into your network or if you have a machine i could use the rdp connection on.

so i know i am already planning for the worst but i am pretty sure that's whats going on.


here is that address i need you to test out for me. and get that data back. and i will see if it's something simple
you need to know the ip address of your vera unit

http://VERAIPHERE:3480/data_request?id= ... ormat=json

make sure the :3480 is there. that is the usual port of the vera unless you changed it somehow.

i am going to have you send off a couple of commands. there are a couple of different ones that will work but this one had all the data i needed without a heap of info i didn't need

so lets see if they may have changed the output type first.

we will see if they want us to use xml from now in

so next command is

http://VERAIPHERE:3480/data_request?id= ... format=xml


ok, now i am going to give you the vera command to send us every piece of information it has. see if that wotks. same deal json and xml commands are as follows

http://VERAIPHERE:3480/data_request?id= ... ormat=json

and now xml

http://VERAIPHERE:3480/data_request?id= ... format=xml

so get those 4 back to me or tell me if there is an error with a screen shot of the error. we will start there.

you can try this one as well if you like

http://VERAIPHERE:3480/data_request?id= ... ormat=json
http://VERAIPHERE:3480/data_request?id= ... format=xml


K

[kgschlosser]

Maybe because some of the class names are the same?

Yes, this is a common reason

I changed the Vera pluginbase class name to VeraK, ( after the artist ), from Vera, and voila, no more clash with the old plugin, i.e. neither are renamed to #2.

The ramp feature works well now too. It would be a cool feature to be able to abort the sequence, eg. if it's gradually dimming, and someone decides they need a brighter light, they don't have to fight against the rampable sequence.

it should abort if another command is sent from eg for the same switch, i could maybe try to have it monitor the responses from the vera to see if the light goes the opposite direction. but there is no guarantee that will work. it's hard to test every possible scenario before i ship out the plugin so you all are the guinea pigs.

and the reason i didn't change the pluginbase class name is because of breaking backwards compatibility for people.

but then again this is a new and much better plugin then the old and so far the consensus is i should change it.

not really sure as to why you would want the old and new running at the same time.

but meh that's what you want to do.

K

[kgschlosser]

On an upgrade topic.


you all are going to love this one.

ok. so i have designed a whole OSD menu system, i am still ironing out 1 kink but it's working like a champ.

it's been made to accept HUGE amounts of menu data, nested menus as many layers deep as you like.

now, i have been able to also accommodate variable data (meaning data that changes) you are able to load a menu and at the moment if you back out of the manu and then go back in the data is refreshed.


so what does that mean for us.

i have also coded a means to have the vera dump it's data right into this menu. and i have also coded a mean to trigger events from this menu.


like for changing the heat, or turning on and off a light.

it's able to be used on a computer or even as an OSD for a TV

has separate actions for each menu movement. so you can associate key combinations with it.

i have not bothered with interactivity with is as far as like mouse clicks and key strokes directly. i kinda figured it would be better to use like an IR remote, of you can put in you own key setup instead of a hard coded one.

you have the ability to send any kind of data to it.

i have every single command for every single piece of equipment in my house in it. for every single device attached to EG.

the menu i have running is over 2000 menu items and nested something like 5 levels

i am still working out some video abnormalities with when it first opens not showing the menu items until you move the line.

i will update the vera code to have the module installed into it so you can just make a call to the vera plugin and if the OSD Menu program is installed it will bring up the menu for ya.

it builds the menu by room name then device.

tells you if the device is on or off and what % it's at and what the heat is and so on and so forth


and when coupled with TCP events the data can be sent to another computer from the machine running the vera plugin so it can display the data there and have it controllable from that screen as well..

i think this is a much worthy add on.

let me know what ya think

K

[kgschlosser]

ok ladies and gents,

i got the OSD program fully functional.

tonight i am going to add the code needed to the vera plugin to make the call to the osd program i am going to add a few actions to this.

one that will be able to call the osd program directly and run the menu.

another to pass the data in a payload in an event

with it being in a payload a plugin such as TCPEvents will be able to send it to a remote computer running the OSD program on it.
how that would work is, instead of having 2 computers runninng EG with the Vera plugin (that would be very demanding on the vera).

setup:

2 or more computers, each with EG on it
each computer has the TCP Events plugin installed
each computer has the OSD plugin installed

1 computer has the vera plugin installed


you set something up so that one of the remote computers would send a request to the computer running the vera data
that computer would send menu data back to the remote computer and the remote computer would put it into the OSD plugin.

to make life super simple i would set all the receiving ports for TCPEvents to be the same and tick the box for show the IP

so the ip address of the computer requesting the data will be in the payload and using that and having the same port setup it's easy to send the data back to the computer that asked for it.
K

[kfxo]

not sure what that error is, i do not have a vera plus. they may have changed the way the data comes across. i am going to have you test something.

what I need you to do is open a web browser and then paste this into the address field, when the page loads i need you to copy the whole thing and paste it into a file save the file and attach it to a a post in this forum thread. that way i can review it.

there are 2 ways the vera can talk 1 is with xml the other is with json the latter of the 2 was easier to parse the data. so i may have to recode that end of it if the vera no longer sends out json with the newer versions.

i am hoping they didn't break backwards compatibility with a change they may have made.

to be honest i think these things are crap and don't run properly.


that company has been know to do that to their plugin devs so i don't put it out of the realm of something they would do. that's why no one is really making plugins or updating them any more for the vera that is.

i am willing to fix the problem but i do not have a vera plus and i am not going to buy one either. if i ever get around to it i am going to code a whole plugin for eg to take care of the lighting.

so if that is in fact the case i am willing to help. but it's going to be a royal pain if i have to keep on sending you files to try and explain the output. so the easiest way would be for me to either be able to vpn into your network or if you have a machine i could use the rdp connection on.

so i know i am already planning for the worst but i am pretty sure that's whats going on.


here is that address i need you to test out for me. and get that data back. and i will see if it's something simple
you need to know the ip address of your vera unit

http://VERAIPHERE:3480/data_request?id= ... ormat=json

make sure the :3480 is there. that is the usual port of the vera unless you changed it somehow.

i am going to have you send off a couple of commands. there are a couple of different ones that will work but this one had all the data i needed without a heap of info i didn't need

so lets see if they may have changed the output type first.

we will see if they want us to use xml from now in

so next command is

http://VERAIPHERE:3480/data_request?id= ... format=xml


ok, now i am going to give you the vera command to send us every piece of information it has. see if that wotks. same deal json and xml commands are as follows

http://VERAIPHERE:3480/data_request?id= ... ormat=json

and now xml

http://VERAIPHERE:3480/data_request?id= ... format=xml

so get those 4 back to me or tell me if there is an error with a screen shot of the error. we will start there.

you can try this one as well if you like

http://VERAIPHERE:3480/data_request?id= ... ormat=json
http://VERAIPHERE:3480/data_request?id= ... format=xml


K

kgschlosser thanks so much for your help. I ran the first four commands. All produced output except the last one. I copied the output from each into a .txt file. I would attach it but I'm worried there may be information that I don't want to share with the world. Maybe send it to you privately somehow?

A snippet of the xml request

<rooms>
<room name="Basement" id="3" section="1"/>
<room name="Garage" id="6" section="1"/>
<room name="Kitchen" id="7" section="1"/>
<room name="Laundry" id="1" section="1"/>

a snippet of the json request

"rooms": [ { "name": "Basement", "id": 3, "section": 1 }, { "name": "Garage", "id": 6, "section": 1 }, { "name": "Kitchen", "id": 7, "section": 1 }, { "name": "Laundry", "id": 1, "section": 1 }, { "name": "Living Room", "id": 4, "section": 1 }, { "name": "Main Foyer", "id": 8, "section": 1 }, { "name": "Master Bath", "id": 9, "section": 1 }

[kgschlosser]

sent ya a PM with my e-mail in it.

K

[kgschlosser]

actually never mind about the e-mail, i know where the error is. I am going to try something and post a change to the plugin and see if it work, that company that makes this thing really annoys me.

they changed the header data so now it's longer and i was slicing the original header off and since it is longer now some characters are being left behind

i just looked at the error you got again, so now i know how many to slice off because it shows so let me make a change and post the plugin back up and see what happens.

K

[kgschlosser]

ok I updated the plugin again, this is a trial to see if this fixes the problem i believe it should,


i also corrected well slowed down the errors that pop into the vera window every night at 2:00 am or so, that is because the vera does a rebuild of the whole zwave network so i have it slow down the the refresh cycle for that period to once every 15 seconds or so. next time i see it i will note how long it takes and try to dial in that timer more accurately but i believe it's going to be variable based on how many zwave devices you have.

i may put in something so the user can adjust if it bothers that much


i also updated the error response so that it plops the recieved data out there so i get alittle more information about what's going on. that way you will have a complete picture of the header of the data sent, the stuff i cut off because i don't need it and it causes a problem... but if there are stray characters unless you have a raw http receiver your browser cuts the data off also.

LOL

so at any rate if this doesn't work at least it will give us the next clue.

it looks as tho the actual data portion of it is formatted the same it's just that they changed up what looks like one line of text at the very beginning of the data

so now it seems at tho their header for the newer units is 49 characters instead of 39

new file attached, i haven't changed the version info for this and it has no additional bells and whistles.

i am going to incorporate that menu crap now. or at the very least get it to dump the information if i can't get it to load the OSD plugin directly

K

[kfxo]

ok I updated the plugin again, this is a trial to see if this fixes the problem i believe it should,


i also corrected well slowed down the errors that pop into the vera window every night at 2:00 am or so, that is because the vera does a rebuild of the whole zwave network so i have it slow down the the refresh cycle for that period to once every 15 seconds or so. next time i see it i will note how long it takes and try to dial in that timer more accurately but i believe it's going to be variable based on how many zwave devices you have.

i may put in something so the user can adjust if it bothers that much


i also updated the error response so that it plops the recieved data out there so i get alittle more information about what's going on. that way you will have a complete picture of the header of the data sent, the stuff i cut off because i don't need it and it causes a problem... but if there are stray characters unless you have a raw http receiver your browser cuts the data off also.

LOL

so at any rate if this doesn't work at least it will give us the next clue.

it looks as tho the actual data portion of it is formatted the same it's just that they changed up what looks like one line of text at the very beginning of the data

so now it seems at tho their header for the newer units is 49 characters instead of 39

new file attached, i haven't changed the version info for this and it has no additional bells and whistles.

i am going to incorporate that menu crap now. or at the very least get it to dump the information if i can't get it to load the OSD plugin directly

K

Dude, good stuff. Fixed the initial error I was reporting. However, when I attempt to add an action to the tree I get traceback errors such as:

23:26:41 Traceback (most recent call last) (1722):
23:26:41 File "C:\Program Files (x86)\EventGhost\eg\Classes\TaskletDialog.py", line 59, in ProcessingTask
23:26:41 self.Configure(*args, **kwargs)
23:26:41 File "C:\Program Files (x86)\EventGhost\eg\Classes\ConfigDialog.py", line 165, in Configure
23:26:41 treeItem.Configure(*args)
23:26:41 File "C:\Program Files (x86)\EventGhost\eg\Classes\ActionItem.py", line 101, in Configure
23:26:41 return self.executable.Configure(*args)
23:26:41 File "C:\Program Files (x86)\EventGhost\plugins\MiCasaVerdeVera\__init__.py", line 206, in Configure
23:26:41 exec(self.plugin.ActionConfig('DimmSt', devc))
23:26:41 File "C:\Program Files (x86)\EventGhost\plugins\MiCasaVerdeVera\__init__.py", line 548, in ActionConfig
23:26:41 for name, devID in self.ACL[DevType]:
23:26:41 KeyError: 'Dimmable Light'

[kgschlosser]

sorry, that one is a typo on my part, you may have a version now that i haven't released into this forum. so there are probably more things in it then the one on the first page.

let me check the one i have posted on the first page and make the changes to that copy, i believe i gave you a test copy i have running on my machine, i tend to make all of the modifications as ideas come to me and i have so many copys of the damn thing sometimes i forget who's who.

But the good news is the modification fixed the error, and it is just as i thought, those idiots at MiCasaVerde changing things about, it's frankley the reason why i don't upgrade the firmware on mine, i have tried in the past and it broke all sorts of things, so i just stick with what i know works.

LOL

OK let me go digging and see what i can find.

sorry about that

K

[blaher]

it should abort if another command is sent from eg for the same switch, i could maybe try to have it monitor the responses from the vera to see if the light goes the opposite direction. but there is no guarantee that will work. it's hard to test every possible scenario before i ship out the plugin so you all are the guinea pigs.

I'm sure we're all happy to be guinea pigs. Thanks for all your work. If an abort is not possible, I might be able to fudge it by using the 'sl_SceneActivated' variable of my Fibaro Z-Wave switch. So if a button is pressed I can get Vera to send a trigger to EG, which can then send a signal back, (lights 100%), if the rampable dimmer was the last event. I'll just use the rampable event to enable a folder that contains a 100% signal and triggers on any button press, and disable the folder again once it's happened.

not really sure as to why you would want the old and new running at the same time.

but meh that's what you want to do.

As I said here: viewtopic.php?f=9&t=8090#p39340 I have a fairly complicated tree, so I didn't want to delete the old one, before I had a chance to duplicate my actions in the macros.

To remove a plugin, you have to delete all the actions in your tree associated with it, and it wasn't backward compatible for me, so I couldn't just replace the old plugin.

[kgschlosser]

ok here is what i have, i am going to make the changes to the copy i posted in the beginign of this thread, now i know it's still not going to work, because there is no mistake in it, and i checked it on my system so i believe there is a data change send over those files to me so i can look

K

[kgschlosser]

it should abort if another command is sent from eg for the same switch, i could maybe try to have it monitor the responses from the vera to see if the light goes the opposite direction. but there is no guarantee that will work. it's hard to test every possible scenario before i ship out the plugin so you all are the guinea pigs.

I'm sure we're all happy to be guinea pigs. Thanks for all your work. If an abort is not possible, I might be able to fudge it by using the 'sl_SceneActivated' variable of my Fibaro Z-Wave switch. So if a button is pressed I can get Vera to send a trigger to EG, which can then send a signal back, (lights 100%), if the rampable dimmer was the last event. I'll just use the rampable event to enable a folder that contains a 100% signal and triggers on any button press, and disable the folder again once it's happened.

not really sure as to why you would want the old and new running at the same time.

but meh that's what you want to do.

As I said here: viewtopic.php?f=9&t=8090#p39340 I have a fairly complicated tree, so I didn't want to delete the old one, before I had a chance to duplicate my actions in the macros.

To remove a plugin, you have to delete all the actions in your tree associated with it, and it wasn't backward compatible for me, so I couldn't just replace the old plugin.

true true true, never thought about that.

hmmm.... dunno how I would be able to handle that one, i think you are going to be stuck changing the class name every time i come out with a new one now, because there are a few people using the plugin and it would mess things up for them.

but there has to be a way for me to check, i am going to do alittle research on that, usually the thing to do would be to have an EG xml file for each one edit the file and just move the things over or change them accordingly

or if you have another computer to copy the tree and all the plugins to that one as well, RDP into that machine and then just copy and paste the things about as needed

[blaher]

i think you are going to be stuck changing the class name every time i come out with a new one now, because there are a few people using the plugin and it would mess things up for them.

No worries, I've already done it. I was just curious as to why it said #2 in the beginning, but mystery solved!

[kgschlosser]

Yeah well your killing me over here tho, because of your issue this menu thing i am coding trying to incorporate it into the vera plugin without the use of the class name for triggering the device command is killing me.


i am going to try to get it to add the location of the class into a string payload that can be simply executed.

i don't know if it will work, i just don't want to make this difficult for someone to set up or have a second set of actions just for the Menu stuff.

i could add something into the device fields of the dropdown indicating it's for the menu, but again there would have to be a set of actions just for menu use instead of you being able to add a simple python command like "try: exec(eg.event.payload): except: pass"


now there is a thought, if this works i am going to make the event the same for every item that can be fired, and that way if will just run the code and only for the menu

no added actions or anything the user would have to make a macro with the event and then add the plugin command action and key in that line. and voila it's done.

kewl, the other neat thing is if this works the payload data can be sent off and because it already has the class name embedded into the string it should still be able to fire it.

i am going to have like 4 different event names tho just for the sake of being able to restrict who has access to change what

sweet

i got a plan

K