glarsen

US units have been changed to GPM. Requires at least ISY on Polisy version 5.4.0

Did you figure this out? in PG2 where you used :${sys.node.n014_timedata.GV10}, the PG3 version now uses: ${sys.node.n014_controller.GV10}

Sorry, as the nodeServer name and docs imply, it only supports the PureCool. I have no means of testing any changes that support another model as I only have a TP07. I can try making some changes for you to test, but it might take some time. I had planned to eventually add further settings for the oscillation function when time permits.

@jwagner010, sorry for the late reply, I didn't know that this thread existed, or i would have been following it. That looks for some reason like PG3 doesn't like something in the nodeserver installation. Could you please PM the pg3 logfile to me? I'll take a look at it.

Hi @Javi, As far as I can tell the node setup in both the ISY and PG look normal. This happens with a NS I'm developing, as well as any of the others I have installed, whether or not they're mine. If you'd like to try the remote diagnostic I'm open to it, I am indeed connected to the Portal. Thanks. G

@Javi, no, I don't have multiple instances operating. PG2 is connected to my isy994, and PG3 is connected to IoP. PG2 and PG3 are both operating on the Polisy.

Sorry, I missed this message. It's been a couple of weeks now....have you had any success in getting this NS to run? What version of ISY, PG3 and TimeData are you using? Thanks.

Sorry, @Javi, I'm not sure what you mean by "will any of the node servers work without hardware". The fault does seem to be specific to PG3 nodeservers - I have a couple of the same ones running on both PG2 and PG3. Another thing I notice is that it seems to be related somehow to editors or nls. I haven't checked enough times yet to confirm but it seems that when the item being set/changed/cleared has a uom of 25 with text in the nls, the error occurs. Doing something like changing a temperature setpoint for instance, with a pure number, doesn't cause an error. If you like I can send you the profile files of one of my PG3 nodeservers that is exhibiting this behaviour. Thanks, G

@Javi, same thing with both ELK and Hue disabled. I don't recall what the last version of PG3 was before installing 3.0.40. Each time I make attempt this is all that appears in the ISY error log: Time User Code Message Thu. 2022/02/10 04:29:00 PM 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> Thu 2022/02/10 04:30:10 PM 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope> Thanks, G

Hi @javi, it's for PG3, 3.0.40, isy on polisy v5.3.0. And it is persistent across reboots, both ELK and Hue are installed.

Hi @javi, I'm running into an error when changing setttings. The request seems to execute properly, as the setting on the device does change, and the display is updated with the new value. It seems to happen on several nodeservers that I've tried including some of my own. The error is: java.lang.Error: Error: 404. URL:http://my.polisyurl.here:8080/rest/nodes/n022_controller/cmd/POWER/0/25. 404. This is on the Android version. I thought at first I had made an error in a profile config, but I see the same with other's nodeservers as well. As I said, the command executes, only this error is returned. If I manually enter the listed URL above in a browser I also get 404. Any thoughts?

It will ultimately change to gpm when the uom is available

There is an update posted, though I don't think I made any changes that will affect this. But, I think you should use 'Status' instead of 'Control' for testing the state in your IF statement. The flowrate units have been changed back to cfm or m3/hour, with selectable units. Again, as soon as UDI advises that GPM has been added I will change that again.

That usually means your RainMachine can't be reached on the network.

it's a little less trivial than I first thought. I will work on it in the next few weeks. It may only be available in the PG3 version, depending on how much work is involved.

It should change after midnight on the day of the season change. The algorithm is a bit fuzzy, so it may have calculated that the solstice was on the 22nd this time. I'll have to have a look at it. Unfortunately, it's a bit hard to test.

The RainMachine API does offer a variable by zone which reports GPM or M3/hour. I think it is a calculated number that is based in data you input to the RM when you set it up. I can take a look at it see if it's of any value, adding the data to the nodeserver is trivial. But, it will be after New Year's before I will be able to get to it most likely.

Hmm, you learn something new every day. Thanks.

I'm not familiar with them - Weiser & Kwikset are the same thing?

Hello all, does anyone have any knowledge of the Weiser Home Connect 620 ZWave 700 Push Button Deadbolt and whether it will work properly with the ISY? Thanks!

Fixed. The clue was in the order of the headers. For some reason the first one had host first, then POST. Comparing it to the original and @Randyth's, they are reversed. Created a new resource and started over, the POST was first and then host, and all works ok. Don't have any idea why the first one was reversed.

Thanks. I'll double check, but really I just copy and pasted from the other AC where the same code works. And it works with curl.

No, it was manually entered in the AC for the ISY on Polisy.

I am still having a similar problem as @randyth, the Network Resource works as expected in ISY994, but not on ISY on Polisy. I'm on isy-5.2.0_58. Error log: NR: What am I missing?

I just set this up on my Android device and all the fields populate properly, so the only thing I can think of is that it must be something specific to the IOS version. I don't own an IOS device to test on.