Michel Kohanim

Hello Mr. Armstrong, We have not gotten any closer. The main issues we are grappling with are: 1. The number of customers who would actually buy a weather station is very low 2. There's no ROI for us to implement this solution So, what we are doing instead is making integration with ISY even easier such that other devices can publish their events into ISY for processing. In this case, then, you can have any weather station feeding ISY. With kind regards, Michel

Hi PalChgo, Please contact me via email and attach what you already have and I'll try to help .. (support@universal-devices.com). With kind regards, Michel

Hi blademan, I think the two are related. For those buttons to show, Admin Console must be subscribed to ISY and it seems that you have problems with that. Do you have a firewall software on your computer? If so, you must put ISY's IP address in the exclusion list in your firewall. With kind regards, Michel

Hi Ron, Not yet. With kind regards, Michel

Hello sanders2222, This means that ISY has a hard time getting on the network. Two causes: 1. Communications with the router including the cable and the possibility that the router is not letting ISY get an IP address 2. If you have setup your ISY with a static IP address, then the issue is probably IP conflict with something else With kind regards, Michel

Hi beernutmark, I am so very sorry to hear. First of all, there's certainly an issue with ISY getting out to the Internet. If you have setup your ISY with a static IP address, I strongly recommend going back to DHCP. Or, if you wish, you can try Google's public DNS servers: 8.8.4.4 or 8.8.8.8 As far as resetting the variable, are you choosing Run Then on the program that resets the variables? With kind regards, Michel

Hello austin_john, If you are using our default settings, it could be very well possible that: 1. Our server is overloaded 2. Your ISP does not like universal-devices.com domain I strongly recommend using your own SMTP settings. If you already are, then please send us the error log to support@universal-devices.com. With kind regards, Michel

Hi sanders2222, This is a known bug with releases 4.0.2 and below. In short, if you don't wait long enough to the time to change (after you apply settings), then ISY will block any other attempt at changing the time. To fix: 1. Reboot ISY 2. Change DayLight Saving or any other time settings 3. Wait a couple of seconds and make sure you do NOT have the System busy before you do anything else With kind regards, Michel

Hello gamard, Thanks for the feedback. Comments below. This has been the case since ISY was introduced. There are no changes to the UI. This is there just for you to be able to apply the same settings to many devices at the same time. The behavior is 100% normal. Can you please post the link to the other post? ISY firmware does not change device characteristics on its own. If you could not at all communicate with them and now you can, then I will have to conclude that the problem has NOT gone away and that it will eventually reappear; it sounds a lot like communication issues to me. With kind regards,

Hi Daniel, so very sorry ... thanks SO very much for your contribution. With kind regards, Michel

Hi GMD99, Please send an email to sales@universal-devices.com for instructions. With kind regards, Michel

Hi jmed999, Unfortunately it seems that it was lost during migration to the new site. I will try to look in the archives but it does not look hopeful since our last site didn't really keep good archives. I do apologize. With kind regards, Michel

Hi Gene, Thank you. I specifically asked them about the size of Install Code and they said all should be supported. Thanks so very much for the link. I will ask them again. With kind regards, Michel

Hi Gene, Not at all. SDG&E/SCE both use Itron meters and we have two of them in the lab. We did go through SDG&E HAN Validation 8 months ago, but we failed simply because ISY was not categorized properly. I have spoken with the HAN Validation team again and we are going to resubmit by middle of next month. With Oncor, they didn't expect us to run tests against a test harness and we should be validated shortly. We are already validated for SCE and should show up on their website shortly. With kind regards, Michel

Hi danielt, What seems to be the problem? Can you please elaborate? From my experience, any time you want to turn backlights on/off, it's best to add a delay especially if the status is based on the load on the same KPL. With kind regards, Michel

Hi PalChgo, No, you also need the following: subscribestr="REUSE_SOCKETinfinite" And, you need to remove a few headers. It's best to simply copy the whole function as-is again. With kind regards, Michel

Hi PalChgo, Thanks so very much. Please replace class ISYeventer(asynchat.async_chat) with the following: class ISYeventer(asynchat.async_chat): """Telnet engine class. Implements command line user interface.""" def __init__ (self, host, port, username, password, plugin): asynchat.async_chat.__init__(self) self.set_terminator("\n") self.data = "" self.host=host self.port=port self.username=username self.password=password self.plugin=plugin # connect to ftp server self.create_socket(socket.AF_INET, socket.SOCK_STREAM) eg.RestartAsyncore() self.connect((self.host, self.port)) def handle_connect(self): # connection succeeded subscribestr="REUSE_SOCKETinfinite" self.push("POST /services HTTP/1.1\r\n") self.push("Host: " + str(self.host) + ":" + str(self.port)+"\r\n") self.push("Content-Length: "+str(len(subscribestr))+"\r\n") self.push("Content-Type: text/xml; charset=\"utf-8\"\r\n") self.push("Authorization: Basic "+ base64.encodestring('%s:%s' % (self.username, self.password))) self.push(subscribestr+"\r\n") def handle_close(self): self.plugin.TriggerEvent("Subscription-Closed", str(self.host)+":"+str(self.port)) self.close() def handle_expt(self): # connection failed self.plugin.TriggerEvent("Subscription-Error", str(self.host)+":"+str(self.port)) self.close() def collect_incoming_data(self, data): # received a chunk of incoming data self.data = self.data + data def found_terminator(self): # got a response line data = self.data if data.endswith("\r"): data = data[:-1] self.data = "" if (data.find("HTTP/1.1 200 OK") > -1): self.plugin.TriggerEvent("Subscribed", str(self.host)+":"+str(self.port)) if (data.find(" -1): epx=data.find(" eprops=data[epx] eprops=eprops[eprops.find(">")+1:] #print "E:",eprops status="None" node="None" Heartbeat="None" RunProg="None" Program="None" icmd="None" econtrol="None" eaction="None" enode="None" if (eprops.find("") > -1): econtrol=eprops[eprops.find("")+9:eprops.find("")] if (eprops.find("") > -1): eaction=eprops[eprops.find("")+8:eprops.find("")] if (eprops.find("") > -1): enode=eprops[eprops.find("")+6:eprops.find("")] if (eprops.find("") > -1): eeventinfo=eprops[eprops.find("")+6:eprops.find("")] if (eeventinfo.find("[") >-1): enode=eeventinfo[eeventinfo.find("[")+1:eeventinfo.find("]")].strip() icmd=eeventinfo[eeventinfo.find("]")+1:].strip() if (eeventinfo.find("") >-1): Program=eeventinfo[eeventinfo.find("")+4:eeventinfo.find("")] if econtrol=="_0": self.plugin.TriggerEvent("Heartbeat") elif econtrol=="ST" or econtrol=="RR" or econtrol=="OL": self.plugin.TriggerEvent("Status",str(enode)+":"+str(eaction)) self.plugin.xlightmap[str(enode)]=str(eaction) for index, sublist in enumerate(self.plugin.devices): if sublist[0] == str(enode): sublist[2]=str(eaction) color=str(hex(int(eaction)))[2] sublist[3]=color+color+color elif econtrol=="_1": if Program=="None": self.plugin.TriggerEvent("Command."+str(enode)+":"+str(icmd)) else: self.plugin.TriggerEvent("Program."+str(Program)) # This processes pre-2.6 beta commands if (data.find("") > -1): eprops=data[data.find(" # print "E:",eprops status="None" node="None" Heartbeat="None" RunProg="None" Program="None" icmd="None" while (eprops.find("")>-1): dpoint=eprops[eprops.find("")+12:eprops.find("")] eprops=eprops[eprops.find("")+13:] tpoint=dpoint[dpoint.find("")] dpoint=dpoint[dpoint.find(">")+1:dpoint.find(""+tpoint+">")] #print "Type: ",tpoint, "Data: ",dpoint if (tpoint=="node"): node=dpoint elif (tpoint=="ST"): status=dpoint #if (tpoint=="RR"): # status=dpoint elif (tpoint=="_0"): Heartbeat="Heartbeat" elif (tpoint=="_1"): RunProg=dpoint elif (tpoint=="eventInfo"): if (dpoint.find("[") >-1): node=dpoint[dpoint.find("[")+1:dpoint.find("]")].strip() icmd=dpoint[dpoint.find("]")+1:].strip() if (dpoint.find("") >-1): Program=dpoint[dpoint.find("")+4:dpoint.find("")] else: status=tpoint+":"+dpoint if (node != "None" and status != "None"): self.plugin.TriggerEvent("Status",str(node),str(status)) self.plugin.xlightmap[node]=status if not(str(node) in eg.globals.excludedinsteondevices): for index, sublist in enumerate(self.plugin.devices): if sublist[0] == str(node): sublist[2]=str(status) if (Heartbeat == "Heartbeat"): self.plugin.TriggerEvent("Heartbeat") if (RunProg != "None" and Program != "None"): self.plugin.TriggerEvent("Program."+str(Program)) if (icmd != "None" and icmd != "None"): self.plugin.TriggerEvent("Command."+str(node)+":"+str(icmd)) With kind regards, Michel

Hi Teken, I had to send my GEM back because of WiFi issues. This said, Ben at Brultech is using 4.0.4 and 2.00 firmware on GEM. You MUST have their 2.0 firmware otherwise nothing will work. With kind regards, Michel

Does anyone else have the source for this plugin? With kind regards, Michel

Hello kaisersoze, Thanks so very much for the feedback. Last week WB had problem with backyard stations and that caused major problems in ET calculations since ISY was not getting correct data points. Based on this event, IM suggested that we allow selection of algorithms either Penman-Montieth or Hargreaves-Saman. PM method is much more error prone in case of WB data not being there. HS is much more resilient. Ra is calculated on a daily basis and applied to ETo for that day. With kind regards, Michel

Hi bobrme, Unfortunately a known issue related to GEM support and ECM/GEM detection. Please do be kind enough to send an email to support@universal-devices.com and we'll send you a link to our next beta. With kind regards, Michel

Hi Ed, Questions: 1. Can you get to your ISY using https and port 44443 locally? i.e. https://your.isy.ip.address:44443 ? 2. Are you sure port 80 is not being used by any other device on your network? With kind regards, Michel

Hi Alan, No, only ECM1240 Only in the Zigbee version Ethernet only works with ECM and you need to have ISY poll. In Zigbee version ECM/GEM publish events to ISY Time spent in polling; no nodes. Zigbee version is a coordinator and ECM/GEM always publish to coordinator With kind regards, Michel

Thanks Gene. Sent a PM. With kind regards, Michel

Hi GuitarBuilder, Thanks so very much for your input. We have indeed considered all facets. Again, I must emphasize that just because ISY is SEP 1.1 certified, it should automatically work with PG&E and it does (Walt is the case in point). We shall certainly reconsider ... arw01, If we were to do anything on kickstarter, it would be for much more interesting and ground-breaking ideas currently baking in Chris' head (our CTO) than to contribute $10K to SSN - a multi-billion dollar company! With kind regards, Michel