bpwwer

PG3 has multiple queues and a queue hierarchy. Each node server has it's own queue and those queues feed to a common queue. It's mostly the common queue that will determine how fast requests are sent to the ISY. It is certainly possible to push the ISY beyond what it is capable of handling and it seems like you have. If it is really taking 10-12 seconds to update just WeatherFlow data then I think you're pushing the ISY way to hard. The WeatherFlow hub sends out data once a minute (that's not configurable) and on mine, all of the data that needs updating is handled within 1 second. You can look at the PG3 log and look for lines like: ISY Response: [Try: 1] [00:0d:b9:4e:3a:44] :: [200] :: 5.08479ms ..... Those lines provide information on: 1) How many tries it took before the ISY accepted and responded to the request. PG3 will make up to 3 attempts. If you're seeing a lot of 2 or 3 try responses, that's because the ISY is dropping the requests PG3 is sending. 2) How long it took the ISY to respond to the request. The example above took 5ms. The time it takes the ISY to respond should correlate with how busy the ISY is. It may be interesting to look for periods where it takes a long time to respond and see if you can determine what the ISY was doing (from the ISY log/event viewer) a those points in time. That may give some insight into what's really causing the issues.

@JimboAutomates version 1.0.2 of Caseta node server is available. Let me know about the remote buttons. Currently, it creates 5 button nodes, each will trigger on DON. But it may be better to have one node with triggers on the correct type (open/close/raise/lower/preset) if those are the buttons that are sent through. Also, I'd need to know which button (A-E) corresponds to what button on the remote.

I thought I had kept all the shade support from the PG2 version. Are you sure this wasn't something you added locally? This is what I see in the PG2 version. if device.get('type') == "SerenaHoneycombShade": NodeType = SerenaHoneycombShade elif device.get('type') == "QsWirelessShade": NodeType = QsWirelessShade if not NodeType: LOGGER.error("Unknown Node Type: {}".format(device)) continue In any case, I added the TriathlonRollerShade so it should be recognized in version 1.0.2. I've also added some support for the remote. But I'm not at all sure about that. The SmartBridge is showing that it has 5 buttons, but when I look up the device, it looks like it has 10 buttons. So I have no idea which of the 10 button states are actually getting reported by the SmartBridge. I suspect it is probably the open/close, raise/lower, preset that are passed through the bridge, but you'll have to experiment with it and let me know. My distributor doesn't seem to carry that product and my on-line searches haven't really found much other than it's a special order device. I'll let you know when I push out version 1.0.2 for you to test with.

This has nothing to do with the node server, it has no control over how the data is displayed in the AC.

Fri 08/12/2022 11:02:52 AM : [D2D EVENT ] Event [n001_48711] [WINDDIR] [90] uom=76 prec=0 Fri 08/12/2022 11:02:52 AM : [ n001_48711] WINDDIR 90 (uom=76 prec=0) Fri 08/12/2022 11:02:52 AM : [D2D*CMP 000F] STS [n001_48711] WINDDIR B Cannot convert values (from=0E to=4C) Fri 08/12/2022 11:02:52 AM : [D2D-CMP 000F] STS [n001_48711] WINDDIR op=5 Event(val=90 uom=76 prec=0) >= Condition(val=1 uom=14 prec=0) --> false Fri 08/12/2022 11:02:52 AM : [D2D EVENT ] Event [n001_48711] [GV3] [90] uom=76 prec=0 Fri 08/12/2022 11:02:52 AM : [ n001_48711] GV3 90 (uom=76 prec=0) This is what I see in the Event Viewer. It looks like the IoP isn't handling the comparison of UOM for wind direction properly. @Michel Kohanim, @Chris Jahn The WINDDIR status value is set to UOM 76 (wind direction degrees) but it seems to be comparing against UOM 14 (degrees) and failing. My program is simply doing "if winddir >= 1". Just like @johnnyt's program above.

Yes, but... the ISY and IoP don't really communicate state between them. So while the ISY can continue to manage z-wave devices having them interact with other devices (scenes, programs, etc.) on the IoP isn't going to work. Given what you posted about your setup initially, I don't think you want to try and do this. I haven't read through everything about, but it sounds like you're trying to decide if you should spend the money on a z-wave stick for the Polisy now or wait for the new UDI z-wave dongle. My question is, what is compelling you to want to migrate now (as opposed to waiting a few months)? Is there something specific that IoP will solve now that the ISY isn't able to do? The big difference between Polisy and Eisy is performance. There are some I/O differences as well but those will really only effect limited use cases. For node server development, there should be very little difference. Node server development doesn't typically run into performance limitations on the Polisy. Just for reference. For doing PG3 development, the UI build takes about 5 minutes on a Polisy and I expect that to improve by at least 10x on an Eisy.

Thanks, that answers the question as to where the failure is. To me, it looks like the first program should evaluate to true and the second to false. You're saying it is doing the opposite. So either we're missing something or the logic is failing. Someone better versed in ISY programs will have to look at this. You could also try creating programs for each condition separately and see how they evaluate. Or try setting a variable to the value to the eto value in the then or else sections. The node server doesn't have anything to do with the program evaluation other than providing the value, which it seems to be doing correctly.

I don't believe the ISY/IOP rounds the value. I think it just truncates the display to the number of decimal places the node server specifies. The node server is rounding the value to 3 (maybe 2) decimal places. If the ISY/IOP was rounding up, the second program wouldn't be true. @CoLongplease just post the value the node server sends, that's what's important here.

Either the program logic is correct and the value is between .270 and .299 and the displayed value is truncated or the program logic is failing and the displayed value is correct. It either case, it's not a problem with the node server so there's nothing I can do about it. Looking at what the node server actually sends to the IOP will tell us which of those cases is true and the appropriate ticket can be raised to UDI.

Yes, UDI's upgrade script failed. As part of that upgrade it is supposed to re-install all the python packages so that all the 3.9 versions are installed, but that doesn't seem to have happened. I don't believe there's any user accessible way to fix this, right @Michel Kohanim. Other than removing and re-installing each node server.

What is the actual value of ETo being sent to the IOP? You're seeing what the AC displays, but not what the node server sent. My guess is that the value is between .270 and .299. It looks like the AC isn't honoring the display properties the node server requests. The node server says that value should be truncated to 2 decimal places, but it looks like it's truncating it to 1.

Just FYI, the "errors" in the node server log aren't really errors. I just forgot to change them to debug message.

@Michel KohanimWhat would cause the AC to show writing to a node server node? Would there be something in the log or error log to explain why it's doing this?

Not that I know of. The precipitation info uses a different query from the rest of the weather data. It seems just the query used for the precipitation data had changed.

Yes, not having direct access to the equipment can make developing a node server more difficult. But more than that is the time it takes to develop and support it when you don't have easy access to the equipment. The bottom line with node servers is that unless the developer plans to use the node server themselves, it's just not real cost effect to develop one. A professional software developer makes something like $100-$150 per hour. Creating a node server will take between 50-100 hours. So the upfront cost to develop one is between $5000 - 15000. That means that to try and break even, they'd need to sell a minimum of 100 copies at $50 per copy. From the sales data I have for the past 7 months, my highest selling node server is less than 40 copies. I don't have access to any other developer's sales number, nor do we track installations to know the quantity of "free" node servers that are in-use. So I don't really know the size of the potential market for any given node server. That being said, my criteria for developing a node server isn't really based on the ROI, I do most of them because I like developing them. I would certainly consider working on expanding the existing Vue node server to handle their other devices, but I really don't have the time right now to do that.

It's not something I have time to take on at this time.

Yes, it is the same issue. Version 3.0.23 should fix it.

The Vue node server only support the VUE utility connect energy monitor. https://www.emporiaenergy.com/how-the-vue-utility-connect-works It doesn't support the any of the other VUE energy monitor devices.

No idea what that means. From what I understand of that state, it means the ISY is trying to update the node configuration and that should only be possible for Insteon and z-wave nodes. If you restart the AC does it continue to display that?

Verstion 2.0.7 of the node server should fix this. AERIS changed the format of the precipitation data in the query response.

This is the problem: 24:00:46 [pg3] error: ISY Response: [Try: 1] [00:0d:b9:53:d8:14] :: [404 - OK] :: 18.856618ms - http://192.168.2.117:8080/rest/ns/7/nodes/n007_controller/report/status/ETO/2.903759505852784/106 The ISY is rejecting it. A 404 error means "not found". I did some experiments and it seems the ISY rejects it if there are too many digits of precision in the value. I just pushed out version 3.0.22 that rounds the value so this should be fixed. If you refresh the node server store, and then restart the WeatherFlow node server, it should auto-install the update.

The setup looks correct. If PG3 is displaying a value and that value is changing from day to day, then the node server is working correctly. The node server never talks to the ISY directly, everything goes through PG3. So if PG3 has the right value and the ISY doesn't, it's not an issue with the node server. You didn't mention any other problems, but if it's just that one value that isn't getting sent to the ISY, that would be very, very strange. The only thing I can think of that might cause something like that would be if the node server's profile file on the ISY was missing the ETo definition, but the AC does get the proper definition. You can try re-sending the profile files to the ISY (PG3, node server details, upload profile button) and see if that helps. Otherwise, I'd suggest checking the node server log and look for when it sends the ETo value to PG3, should happen within a minute or so of midnight. Using the timestamp from that, check the PG3 log for the same time and see what it does with it. There should be log entries there showing it sending the value on to the ISY. Then at least we know if the value is making it to the ISY or not.

ETo is set to zero if there isn't any forecast data. The node server will enable the ETo calculation only if the custom parameter "Forecast" value matches a station ID returned when it queries the WeatherFlow servers for station meta data.

Unless you have a backup of Polyglot, you can't. The information about node servers is stored in a database, when you factory reset the Polisy, you removed that database. If you have a Polyglot backup, restore it and you should be good. Otherwise, you'll have manually remove the node servers from the ISY (node servers -> configuration -> slot #, and click delete) and then re-install them from Polyglot.

The query isn't returning data in the format expected. If you turn on debug level logging, the log will show the actual URL that is being used to query AERIS. Note, that URL will contain your secret API key. But I'd need to see the output from that query to know specifically why it's failing.