LFMc

The "IF" in only one program (the active one) is evaluated daily, but the TimeData node server DST flag doesn't change but twice a year. The first time the DST flag switches state is the only incident that occurs because the program (now True) then disables itself and enables the next DST program to watch for the next time it changes back. Please feel free to show me if that is not the case. I don't see the need for a variable at all, the TimeData DST flag is your variable replacement. The only concern I have is the "IF" time and maybe instead of 2 seconds after DST shifts, it might be better to wait one minute to give the node server time to respond.

@gzahar If you look in the Internet Header of the email you got from your ISY, it contains the ISY private and public IP address in it. Simple to find the IP that way. In Outlook, you click File/Properties to see it. Sat, 10 Apr 2021 09:15:16 -0700 (PDT) Received: from [xx.xx.xx.xx] ([xx.xx.xx.xx]) The first is the private IP and the second is the public.

Sorry for the late reply to your issue. I have 5 Insteon stats (2 zones, 2 wired master zone stats and 2 remote stats and one wired stat used for damper control) and none of them do what you are experiencing. But, I do not use the "program auto" mode, just heat, cool, auto and off. In fact, I have never programmed one locally. All of my Insteon thermostats are run by ISY programs (except remote wireless ones which don't matter). So when I locally override the temp or mode, it will change back only much later when the time comes for it to do so per the ISY program. Hope this helps.

With the TimeData node server, couldn't these programs might be much simpler with just two alternating programs and no variables needed? Such as: DST Spring Forward If Time is 3:00:02AM And 'Nodeservers / ISY Time Data' DST is True Then // insert programs to restart and notifications here Enable Program 'DST Fall Back' Disable Program 'DST Spring Forward' Else - No Actions - (To add one, press 'Action') ======================== DST Fall Back If Time is 1:00:02PM And 'Nodeservers / ISY Time Data' DST is False Then // insert programs to restart and notifications here Enable Program 'DST Spring Forward' Disable Program 'DST Fall Back' Else - No Actions - (To add one, press 'Action')

Amazing reference material. Didn't know it existed.

Not that it might help, but I had an Outdoor Insteon module that had a mind of it's own after a couple of years. Sometimes it would work, sometimes it wouldn't. It got to where it was finally non-responsive to anything but a local button push and then that went away. So I cracked open (literally) the sealed plastic case and found the typical shoddy Insteon soldering job with flux everywhere, piles of it. Being I know this is bad and totally unacceptable from my military electronics design days, I took some denatured alcohol and scrubbed off the flux with a brush. I let it dry and then it started working just fine. I have seen this flux issue on almost every insteon device I have opened. I would have thought the industry is well aware of this issue by now and that a de-fluxing bath on the production line would be standard procedure.

Thanks for the detail. They do put a bit of a heavy requirement for direct access. Almost as they don't want to have to deal with end users like us. Where did you see the once per 30 minute max inquiry you mentioned? I didn't find anything in the document other than 3k per day.

https://www.smartmetertexas.com/Smart_Meter_Texas_Interface_Guide.pdf It appears to be open to all to view. If you have any troubles, lmk and I will download it for you. If implemented for the ISY, this would be a great add on module that I would be willing to pay for in the future. The section that reads the meter real time is called ODR or On Demand Read vs. the Green Button D/L of data that is always a day behind.

UPDATE: After about 2 weeks, I got a call from a tech at ONCOR in response to my email asking for support. He apologized profusely about the delay getting back to me and was extremely helpful in resetting the HAN link on my meter to get my ISY ZS working with the meter again. He asked me about the brand of my gateway and he recognized the UD brand immediately and was very complimentary of it. So, it seems that ONCOR is still at least servicing the existing HAN customers. I have no idea what might happen if we move to a new home in the ONCOR area, but thankfully there are no plans for that right now. Not being a hard core programmer, I am looking for a way to run an automated query of the smarthometexas.com web site to retrieve the "get meter reading now" button response. I have no idea if this is possible with something like CURL or not (or maybe a custom node in Node-Red), but it would replace the need to even have a ZS card in my ISY if I could program it. Looking at their API doc, it says they allow up to 3000 queries a day (about 2 queries per minute), but the rest of the info in the doc is over my head for the most part. If anyone is interested, I will post a link to the API doc.

More depressing news. Some how the TDU's have convinced the Texas Legislature that HANs are not needed for "new" customers. Now you have to go the the SMT web site and click on the "green" button to get a "demand" reading. Totally useless and is nothing but a gimmick to appease some users. How would you ever know that your billing rate just peaked to 1000x higher for the next hour? We are going backwards. https://www.utilitydive.com/news/texas-regulators-approve-new-smart-meter-rules-limiting-access-to-real-tim/576093/

I agree, obviously. I think this is possibly a legal issue, at least in Texas. The consumers had smart meters forced on us in the name of "money saving" and ability to manage usage. In addition we have to all pay a fee every month for the benefit of having a smart meter. Given the onslaught of bad press this last week about people being billed $10,000 for power because they were on "wholesale" contracts, this refusal to support HAN devices will make them look even worse in the public's eyes. I guess now would be the time to bring this issue up with the media and with the legislature.

Just Googled Oncor han support and saw this article. I pray it is not true. But who knows. https://www.rainforestautomation.com/state-texas-residents/

Hi V, welcome to the confusing world of HAN devices. :-9 After Texas shut down HAN management via SmartMeterTexas.com, I have had no interaction with them. About 4 weeks ago, I somehow accidentally reset my ISY trying to copy the SD card in preparation of upgrading it to 5.x. After restoring it, the ISY no longer talks to my meter. My SEP repeater does still talk to my meter, so I probably need to ask Oncor to open up the "join" feature on the meter so my ISY can reconnect to it. So, you are ahead of me trying to get Oncor to respond. I have had actual phone discussions in the past with Oncor engineers and they did send a tech out to my house once to check the meter's HAN function. So they are responsive to me prior requests. It seems that once or twice a year my meter's HAN function locks up and stops feeding data to me. It turns out if power is removed from the meter (i.e. hard reset), then the HAN function returns to normal for another few months. So when that happens, I have to wait for a power outage or go through the trouble of convincing the Oncor service person that I know what I am talking about and cajole them into humoring me and resetting my meter. Of course that shuts down the power to the house for about 1 second and resets everything. ? Simply rebooting my internal HAN devices never fixes the problem. I will probably call them this week and cross my fingers that I get someone that even knows what a HAN is. Please let me know how you contact them and how it goes. If I succeed before you, I will post it also. As to your last question, I have no idea if there has been any change releasing them from the PUC ruling that they have to support HAN devices.

Great to hear the good outcome and good support help. But do you mind sharing any root causes you/Brad found that solved your problems so others don't stumble on the same issues?

Inseon switches cannot be combined with standard switches to control a single load. Each switch in a multi-way must be replaced. I have instances in my house where I have dual and triple switches that just are not used. On these I put in one insteon and cap the others off. Then If I want to have another second or third switch, I will put in a KPL 6 button switch as a primary to another light and use one of the soft keys as a secondary switch to the primary of the other 2 or 3 way. Also, even if you have multiple panels, I would think you still only have two legs of power (110x2 in the US). So technically only one bridge would be needed to support PL signaling. But PL losses on long runs to and from any power panel is a possible problem. One way to minimize this is to put your ISY PLM in an outlet right at the power panels to cut the PL signaling losses in half. But this also may put your PLM in an area that is "off center" to the rest of your Insteon wireless devices making the chance of more wireless hops probable. It depends on the configuration of your house and if the power panels are centrally located or not. The PLM doesn't have to be right next to the ISY. Also, do not forget the whole house surge protector! Cheap insurance.

One year on, and Oncor is still sending my ZS data without any issues. Have you heard anything further?

Until you can ping the IP, there is nothing else to do. In a direct PC to ISY connection, there is no DHCP to even give the ISY an IP address. Have you looked up the default IP on the ISY so you know your computer is on the right sub net?

Was it on a static IP or still using DHCP? Any chance the IP changed? Maybe something going on with your DHCP server? If you have it direct to the computer port, there may not be a DHCP connection. If the ISY defaults to it's own default IP, your computer may not even be on the right sub net. Also, have you researched the blinking light to know what it is telling you?

How does the Global Cache IP2IR compare with the Harmony Hub? I guess one difference is the IP2IR doesn't need Polyglot? Other differences? I am still using 4.7.3 and don't have a polyglot server.

ELK is an insteon compatible security system. My KPL shows the same thing it must be some alternate address for the ELK option. The ELK address given looks like the old "X-10" address scheme. When I add my KPL-A button (on my 8 button KPL and my 6 button KPL) to Google Home or Alexa in the portal, it's category switches to "Light". So yours doesn't? I probably can't help much from here other than to tell you to reset the KPL to factory default and re-add it to your ISY. It might not hurt to know your exact model number of your KPL also.

I use cURL.exe in a windows command line to do this. I think Libcurl version works for Linux variants, but can't be sure in your situation. Here is a link to libcurl: https://linux.die.net/man/3/libcurl Hope this helps unless someone has a better way.

Michel, I seem to think your interpretation of the SMT 2.0 notice shows some concern about participation of the ISY going forward. I did do some more research and I do not read into it any reduction in the HAN connection services based on device type. It seems the vast majority of this change is centered around the Green Button initiative to reduce the effort needed by a consumer to get access to their data or to give 3rd party access to their data. The additional item in this change is moving the process of opening HAN permissions for the customer to add a device to the TDU. I think the statement about "existing" customers can be taken incorrectly, not as a grandfathered requirement but just as a current user permission requirement. I.E. you have to be an Oncor customer before they can let you add a device to the HAN. I cannot find anything, at least yet, that shows any weakening or watering down of the requirement by the PUC in Texas that mandates allowing customers real time access to the meter data via the HAN or the optical plug in, regardless of the device type. Are you seeing or know of something else that concerns you in this area? I know you mentioned something previously in this thread. I'd be glad to further research it with some input/direction from you.

Yes, I think we are reading it the same way. They will offer Green Button data access so users do not have to create an SMT account. Also, smartmetertexas.com (which technically is for all TDU's customers if the TDU subscribes to it) is not going to handle HAN provisioning and the TDU has to do it themselves. I can't see them eliminating access in any way for HAN customers as it would cause so many devices to no longer work. Hopefully they are not taking away anything, just rerouting access permissions. Yes on the 24 hour delay also. Which really works out to "up to" 48 hours of delay as it has a 24 hour wait that starts from the last day's end. Hopefully this will not be the case going forward.

Latest on SMT 2.0 which is rolling out soon. https://tcaptx.com/legislative-watch/blog-puc-green-lights-smart-meter-texas-2-0-expected-in-2020 The one item that is of close interest to me is the removal of using the SMT web site to gain HAN permission and attachment. Looks like the ball is being handed off to the local TDU. "Smart Meter Texas 2.0 will no longer support Home Area Network functionality, although individual transmission and distribution utilities must maintain access for existing customers who request it. Home Area Network devices include smart thermostats and smart appliances that work with digital smart meters."

BTW, I got this email from SmartMeterTexas.com yesterday. It appears that Oncor may be expanding their offerings to us involved in meter watching. With them being able to provide data via an API, would this mean we can (possibly) dump Zigbee and consume the data directly over the internet via a (future) nodeserver? Probably just a hypothetical question at this point. But reading between the lines, this may be an attempt to dump dealing with Zigbee in the future (as your previous message alluded to). Right now I am getting data every 30 seconds and have the option of polling more often. I bet that any API they allow to see their data directly will never allow polling that often. I will have to do some more research on what the details are in this "approval" from the PUC involves, after all, "the devil is in the details". There are lots of very vague claims in the email. Another interesting issue occurred in August. Some Oncor users are buying power through brokerage wholesalers who pass along "the cost" of the electricity for a flat fee of $10 per month. What they don't tell you is they are buying power hourly on the spot market. Last August during a particularly hot day, the spot market for power in Texas jumped to $9.10 per KWHr for an hour in the peak power hour of the day. My friend uses one of these brokers called "Griddy" and his bill for electricity was $135, for one hour! Ouch! I did't pay that much for the entire month. Email from SMT: "Due to recent approval by the Public Utility Commission of Texas, Smart Meter Texas will be releasing new functionality on December 10, 2019. A few key highlights of improvements and changes are the following: Ability to receive your data via an Application Programming Interface (API) Ability to receive your energy data via email Enhanced mobile awareness Enhanced to display 24 months of data Improved access to generation information An improved customer experience with a new website look and feel Watch for future emails for additional information and action required. Thank you for being a Smart Meter Texas user. Regards, Smart Meter Texas Team"