Jimbo.Automates

Thanks, I don't use Mobilinc, but I find all my 5012 errors are coming from HueEmulator nodeserver which uses PyISY, and all others seem to be UDMobile loosing connections. But, not sure why the connections are getting lost.

Did you figure this out? I've just started having issues with subscribers loosing connections, UDMobile, and lots of -5012 errors in my error log. Sent from my Google Pixel Slate using Tapatalk

I guess I got some bad ones, or their gable fans are not as good as the WHFan's. I assumed they were the same thing, mine have bad vibration causing noise that I can't stop with big damper washers, and when turned are even noisier until they reach full speed. I have the pressure sensor option so it shuts down if pressure in the house increases compared to outside, which means not enough windows are open. But, ISY also knows how many are open from ELK NS, so we get a notification if the fan is turned on and no windows/doors are open, and if nothing is done for a couple minutes, it turns back off. I also get notice when it's cooled off and warmed up outside saying if windows/doors should be open/closed. I wish I could automate opening and closing windows Not really...

Great, glad you didn't mind injecting my opinion That's why I picked the Airscape, it has wall mount controller, and RF remotes, along with the IP controller, so new owner would not be required to use ISY. But once ISY functionality is in Polisy it's back to one box to control it all. I've never even thought about seeing if the Airscape will work with my Bond Bridge, but without 2-way communication, the ISY/NS connection is best.

Personally I would suggest https://airscapefans.com/ I've had mine for a couple years and it's great. Ten speed, wireless controls, hardwired control, and IP interface which has a nodeserver. I think a couple other people on here have them as well. Also, I think the IP controller is not on the website anymore, so you have to call to order it. I have 2 quietcool fans as gable fans, and they are not quiet... Will be replaced soon.

I have them as well and have thought about it, but haven't had time. Sent from my Pixel 3 XL using Tapatalk

Well I just opened it again and it didn't crash, but then when tried to go back using the gesture it crashed Sent from my Pixel 3 XL using Tapatalk

Ok, I'd hoped it would show all the devices that were in the scene [emoji16] Yes crashing every time, but never asks if I want to send the report. Latest version has been doing that a lot. Sent from my Pixel 3 XL using Tapatalk

Ok, that works. But when I go into the scene after changing to a folder it says no items in this folder, then crashed. Sent from my Pixel 3 XL using Tapatalk

After adding the scene, how do you change it to a folder? Can't seem to figure that out? Sent from my Pixel 3 XL using Tapatalk

The android version allows you to add a widget and that goes to the favorite screen. The percentage on is a great idea, or even just a count of not off devices. Sent from my Pixel 3 XL using Tapatalk

Thanks, yes I am looking at their responses, but not all 400 responses should retry. I was testing by creating a bad formatted post just to see that my retry works, but in reality a bad formatted post should not retry. I was more just curious if you were seeing something other than a 400.

Any feedback on those issues? Also, do you are anyone have a nodeserver log showing what error happens when the message is not sent? If so, please add to the issue https://github.com/jimboca/udi-poly-notification/issues/19

I like your spreadsheet method, very cool. I'd really like to allow adding those as a custom message string, but Chris is going to allow custom notifications defined in the ISY to be parsed and passed to nodeservers someday so I'm trying to wait for that... 1. Retry send on http fail. Yes, this has been on the list for a while https://github.com/jimboca/udi-poly-notification/issues/19 2. default attributes for Custom Messages that can be over-ridden on a per use basis. Will think about this one, let me know your thoughts https://github.com/jimboca/udi-poly-notification/issues/22 3. ability to change the sound attribute, including new custom sounds. Added: https://github.com/jimboca/udi-poly-notification/issues/21 I can't say when I can get to this because the ELK nodeserver is highest priority right now and I don't have much free time for that, but I will try.

Thanks@MrBill much appreciated, I'm traveling today but will review this in detail when I get a chance. No offense taken, I can be direct in my responses which can come across offensive or defensive when not intended which I don't mean. Sent from my Pixel 3 XL using Tapatalk

I was commented because you had said: My biggest problem with all of the above tho is that neither the ISY nor the nodeserver do anything on fail, the message is just lost. So I was just saying that the nodeserver does do something, you could send a message via another method when you see there was a failure. yes, you won't know what message failed but something happened... I know it's not ideal right now, but I will try to get to it when my work calms down a little. Yes, that's details for custom short messsages, there are also Notify Nodes and I was just commenting that it's not necessary, add the node then set the defaults on the node and trigger the node. Mostly I'm trying to understand how adding a new NR is easier than using the Notification NS to eventually improve it... Someday when Chris adds the ability for nodeservers to access custom messages it will get better...

The NS does set the error status when a message fails to send, it doesn't ignore it, but as of now it has no retry on failure. Will get to that someday. Also, adding a notification to a program shouldn't be that many steps, create a custom message, restart the NS and add that new node to your program. Sent from my Pixel 3 XL using Tapatalk

You mean the Nodeserver log messages? If so, just set debug mode to warning on the controller in the AC. Sent from my Pixel 3 XL using Tapatalk

That sounds correct thanks@MrBill I don't like to let nodeservers delete nodes since it could be unintentional or missed in the API somehow... Sent from my Pixel 3 XL using Tapatalk

Faster response. But if node names are all ported over so I don't have to change all my 100s of programs then maybe not a huge deal. Sent from my Pixel 3 XL using Tapatalk

I would vote to very much keep current Insteon support with the port from ISY.

Thanks, I have had 2 of those working just fine and pretty sure one has to go thru a repeater, an old aeotec but I'll check next week when I get home. I asked model because I've been considering a new 469ZP for my lake house but one of the doors is pretty far from the ISY so likely needs a repeater. Sent from my Pixel 3 XL using Tapatalk

Great information and effort. Which Schlage lock do you have? Sent from my Pixel 3 XL using Tapatalk

Nice. @Michel Kohanim just released it this morning and I hadn't had time to test the official release. Thanks for confirming. Sent from my Pixel 3 XL using Tapatalk

Yes, counters and lighting are on the list https://github.com/jimboca/udi-poly-elk/issues