Messages

If you are able to get me the logs I can help diagnose where it went wrong on your system. I do not have all the different devices to test with. I was most worried about the thermostat, as there was a lot of code in there for that and I do not have one of those. I tried keeping most of the old code in there to fall back on. What version of LMCE are you using? I have this running on 12.04.

I attached all the files in a zip. Just open the files with any text editor and update your Insteon PLM device template.

To use the the EZflora part of it, if it does not auto detect it. Add device 'Standard Irrigation Controller' and add the insteon id to it. Then from there, to use it, the 'On' Command takes 2 parameters, #98, set to 'V' for a valve or 'P' for program. Then #97 set to the valve or program that you wish to start(Valve: 1-8, Program: 1-4). The Command 'Set Delay' you can use which sets the timers for programs but the parameters must be in the hex format. The parameter #102 is as follows to 2 digit program #, then 2 digits for each of the 8 zones. So 001E1E1E1E1E1E1E1E will set the first program to 30 minutes each zone. The rest works as expected with Next and Pervious.

Let me know if you need anything changed or if it broke anything with your setup.

Just to be clear, this is for Insteon PLM device template #1932 which is different than the Insteon PLM DCE(ID 2103 on my system) device template which includes the Insteon Plug In package. The only changes for template #1932 was the ruby code.  Where as #2103 would need the c++ src code change which I did not take on, so for this I would not need the git account for, to my knowledge, but correct me if I am wrong on that, please. Is sqlCVS a better approach to submit that for review?

The easiest way for you to update the template yourself through the webadmin page. If you go to Advanced>Configuration>Device Templates, then type in the device template id 1932 in the bottom field and hit go, then after that you click "Pick Device Template", then in window that comes up, click Edit Ruby Codes.

In there you can copy and paste the code into the correct fields which I will attach here hopefully today. I have decided to finish up the response portion that I was working on since you motivated me to get back on it. 

Yeah, not a problem on getting it up to git for them to look at. I will clean it up a bit today as I was playing around with some other stuff in there that is not production ready.

ggmce, let me know if you want it before that, so you can get on it right away as sprinkler season is upon us. I can send you mysql scripts to import it in to your system if you would like.

I am using that device for my sprinklers(Older branded one by simplehomenet, but looks like it is exact same with same commands). I use the INSTEON SERIAL MODEM INTERFACE(2412S) controller with the Insteon PLM #1932 device template. I noticed there was no support for that device in that template. So I updated that template and also I created a child template for the device itself. If you use that #1932 device, I can send you my template. I did kind of over haul the template to fit my needs better and support more insteon devices. But at least you can check it out to see if it will help you. I set it up to be able to start\stop programs or valves.

Thanks for the support. I am going through the ticket system now to learn how that works so I can start with a lot of that and get some updates pushed out. I will let you know if I have any questions or need help with anything.

thanks again

I will definitely add some patches for some of these things when I am more confident that all my changes have not affected the system in any other way.

I am going through the code and finding where all this stuff is implemented when installed. When I find it all, I will update it and add some patches to the system to take care of it. There are a couple other things I had to get fixed also that help my install run better. I was also thinking about adding a couple device data fields to the MythTV_Plugin to allow someone to run any version of MythTV they would like. I am still in the early stages of that though to know how much work that would take and if it is even worth while.

I am not quite sure if I am ready to take ownership over the MythTV integration yet, but willing to help out any way that I can.

I updated to .27 by adding the myhtbuntu repositories

deb http://ppa.launchpad.net/mythbuntu/0.27/ubuntu precise main
deb-src http://ppa.launchpad.net/mythbuntu/0.27/ubuntu precise main

ran the commands
sudo apt-get update
sudo apt-get install mythtv

Then I had to update the MythTv_Plugin by downloading the source for it and updating MythBackEnd_Socket.cpp to change the protocol from 72 to 77 and also the token from D78EFD6F to WindMark. I then recompiled MythTV_Plugin.so and copied that to /usr/pluto/bin

It has been working pretty well for me since then. I had to change a few other settings in the MythTv setup as well. To fill the guide, I changed the command mythfilldatabase to /usr/pluto/bin/MythTvDailyFillDB.sh and also added Job #1 back in to save the recordings to the linuxmce database.

I was having that issue also. I am not sure if it is related or not because I upgraded my install Myth to .27 and it may have reset some of the default settings that should be there normally. But in MythTV setup, in the general section. The backend IPv4 was set to the local loopback(127.0.0.1). I found somewhere on the internet that said that the backend only responds to requests on that ip address. So I changed the backend ip to the local LAN ip address(default: 192.168.80.1). After that I was able to access it on my MD as well as my phone using mythtv frontend.