Dub

Thank you @MrBillI do want to be clear as possible when tagging Jimbo and appreciate your help always. Yes I am using Pushover. Would really like to hear your methods as it was another post of yours about Jimbo's Notification NS that helped me see the value and robustness of it.

Thank you. That seemed to be the case at first when I only had one room. After I added some additional lights, rooms, and Play setup with the TV none of my scenes seemed to work. Not even my first 2 that had previously worked. I could see the new lights in the NS and tried a few times to resync. I haven't had a lot of time to dig back into that, but I will take another look. At first I had 2 scenes so it wasn't that bad, now I have several across the 3 rooms, and I dont remember what order I added them, so it would take some going back and forth to verify and then document which one did what.

Thank you. I am just starting to work with NR some and was keeping an eye on this thread. Looks like you had some rubber duck debugging on this one!😀

@JimboAutomates Just got this setup and working last night thanks to a suggestion from @MrBill in another thread to someone else. I was just at the point of starting some notifications and didnt like the depending on email or text. Great job! Lots of Options and Highly Configurable. Also thank you for the ability to use Network Resources and custom content. Very well thought out. Great documentation too. I like how in the NS Config page it brings my specific variables like my IP address and Pushover Service Node Names in. Is it expected behavior to not see a subject line when using Custom Notification from Polisy? I get the api app name that I created in the pushover dashboard. I changed the name in pushover and it changed in the subject line on the next test send. Also, there may be a small typo on the PG3 NS config page that produces the same behavior as above, but for Network Resources. The parameter for the Subject line is capitalized in the example for the path, but changing it to lowercase seems to correct the issue and will send the custom subject line. This is when using Network Resources to send a request to the node server. From the config guide on PG3: /send?node=po_dub&Subject=My+Subject&monospace=1&device=1&priority=2 With lowercase s this sends the subject line: /send?node=po_dub&subject=My+Subject&monospace=1&device=1&priority=2 *Edit(Add) went back and looked at the config documents on Github, the "subject" parameter there is in lower case in the example code. My assumption is now this a typo on the NS config page and hopefully this helps someone. I accidentally typo'd a parameter experimenting with pure NS to Pushover api with similar results before installing this NS. This is the example of the Network Resource that does send a subject line:

I have hesitated responding as the Node Server is free and you gotta be a genius to write something as great as this. I really appreciate the efforts of this developer, the time, and effort needed to produce a great product like this. My one request and this is not a complaint, but would be the ability to call the scene by name. As changes are made on the Hub the scenes seem to move to other generic names. Currently I am using NR to call the scene by the unique ID in the Hue Hub, thanks to a write up on the Hue forums I was able to identify all the variables. In the spirit of the upcoming eisy aka easy, I think this would make the adoption better for users that may not be able to get the variables and use the network resources. I can currently see the scene names and the variables in the logs, but thats the limit of my technically ability as far as mapping them back in the interface. It's a great node server! Thank you!

I updated my second switch today the method @Athlon mentions of using HA. A few observations and heads up for anyone that tries this. 1- Upgrading in HA is easy and quick 2- First switch firmware update in HA did not recognize my firmware correctly before or after upgrade 3- Today HA recognized my firmware correctly before update, but took a reboot of HA to get the new version to show 4- HA could not update the variables after an exclusion and inclusion back in to HA. I tried on the device and in the Developer Tools, with the call service option 5- To do OTA on HA, I had to remove the Zooz Zen 77 from my Polisy. Once the update was done an inclusion was needed again on Polisy ***Most if not all of these observations @Athlonhas mentioned, but I wanted to verify a second time and try a few other things to see if I could get different results. ***Warning doing this method you will get a new device ID in Polisy, so any programs etc won't recognize the old device id. If someone reads this and can't get their device updated, but still needs the ramp rate adjustment this could be done with a couple of programs to fade up or fade down. Its not perfect, but will get someone by that may not be able to do this otherwise. Thank you @Athlonfor the fun project. Definitely learned a few things along the way and learned an appreciation for Insteon with the ramp rate built in years ago.

Yes there are a couple of threads discussing problems. That is one in particular. The Network Resources option might be the easiest to get going since you are having issues with the NS. Edit: Link to UDI Wiki to setup Pushover Network Resources. https://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Mobile_Notification#Pushover

Thanks Michel! I was having problems last night and went down the rabbit hole on forum posts trying to see if it was me and my config. Can confirm I can sync purchases now too. You guys rock!!

I think so too. I'm using Ameridroid/Odroid dedicated hardware now, but started with Virtual Box. It was pretty straightforward. You will need to make sure (if you use Virtual Box) to add the USB port to the VM so it gets exposed to the VM. One trick that I learned on Virtual Box and I think helped @Athlon yesterday was once the Z-Wave USB Stick is exposed to the VM, it still needs to be configured in HA. I had to when I first configured HA, remove the Z-Wave USB Stick to create an error in the logs to expose the path HA needed to use the Z-Wave. Yesterday when I tested this it was the Supervisor Logs(HA has lots of log options). Thats probably the biggest hangup I had when doing Virtual Box, but it should work pretty well and hopefully that can save you some headache. I'm doing another test today with another Dimmer, because I'm not sure I could use the new firmware features on HA without excluding/including in HA. Ultimately I want to better understand the process, but the firmware update in HA went smoothly.

Great find!! I did an update of my Zooz USB stick with the simplicity studio. I’m still not sure how I got it upgraded.? Something wasn’t really clear to me about the additional modules(my words) that Simplicity Studio needed Wishing you good luck on this and anxious to see what you find!

@bpwwerthank you for your transparency. This information is good and a lot of what I suspected from other threads. I have a background in technology, and commonly see that efforts to bring a working a solution to completion can be undervalued and a lot of folks don't understand the cost of the time or the amount of time that it takes. It makes me hesitate to get completely dependent on node servers for my day to day needs since the node servers tend to be supported by a single resource. Also if there isn't an ROI for the time, its really easy for me to understand when time doesn't permit to continue developing or enhancing node servers. Time is definitely precious. I would like to see a sustainable model for the developers and the node servers. I know subscription models are frowned on based on some Insteon Hub blowback for the new paid service. I don't know of a good way to keep these models profitable or at least break even(if thats all the developer wants, but I think you guys should make a profit). Sorry a bit off topic, but I saw your post and appreciated the transparency.

Michel stated in a thread recently(I can't find it though) that the failure rate of their devices is extremely low(my words, his were more actual numbers). Since you have waited and not gotten Polisy, I would probably wait and get a eisy. I see several mentions in different threads about failures, power outages, surges, etc...Several years ago when I was a lurker, probably on Insteon/SmartHome boards, I saw a recommendation of a whole home surge protector. I had one installed and haven't looked back. I have only had 1 failure of a device since and that was an outdoor module in my attic. I actually consider my use as abuse with the heat in the attic. I don't see much mention of this anymore, but my whole home surge protector has served me well. I also have my Polisy, Router, Switch, and PLM on a battery backup, with a surge protector. I know these devices in some cases can cause interference/noise, but I have a dual band outdoor module in the same bank of plug ins. I don't see any consistent communication issue..maybe once in a blue moon something is missed...but not often enough to be annoying or to dig in to troubleshoot. We don't have a lot of power outages, but we do have brief sags or brownouts occasionally and I gotta think the UPS keeps my devices healthy.

@lilyoyo1thank you for responding. Learned something new on that one. I'm adding that to my list of frustrations with Z-Wave. @Prana electric I get frustrated with Z-Wave not working the same consistently across devices. Since you have Insteon as well, thats one of the things I appreciate about it. If you are interested in swapping to a Z-Wave switch that works without querying status with Polisy, the Zooz line I'm using keeps the status up to date. There are posters like lilyoyo1 that know way more about this and may have better recommendations.

Im using Polisy and when I flip my Z-Wave switches on and off the status immediately changes in the Admin Console just like my Insteon devices. Did you by chance add the ISY as a secondary controller to an existing network? The reason I ask I did this initially for some testing with another system and the secondary system in my setup would not get status updates without querying...I tried automating the querying, but it seemed really inefficient. The more I read the less well supported Z-Wave secondary controllers are and this seemed to be the expected behavior....If not well this can be eliminated as a problem...

Interesting good catch. I was only trying at the switch. You and I both use HA so I’m testing from there. I created a scene in Polisy, added my Zooz Zen 77, changed the scene to send a command with “On”, Defined a Fade rate of 20 seconds to get the light to 100%. It seemed to work when I turned the light on through my HA app on my phone. (Edit) Correction on the behavior when I turn the scene off in HA and a typo above regarding 20 seconds(I had 20%). When I turn the scene off in HA, the lights connected to the Zooz Zen 77 go off at their normal speed, not at the 20 second ramp rate. One other behavior to not is when I turn the switch not the scene off in Polisy, the scene shows off in HA. I'm not sure that 2 scenes is is the cleanest way to get the ramp rate to work on power on and power off...but that is my next thought....and I hate it! I can keep looking on side for options unless we hear from someone with more experience with Zooz.

I was following you, its probably my poorly worded response. . Thats what got me me to think to give more details about my process, so I appreciate the extra info. All information is relevant....it sometimes might just let you know you have a bad source haha. Since you can change by program on the LED based off the light status, have you tried changing the ramp rate with a program? If the program changes it, we could isolate the problem down to the process for manually changing the parameters vs a problem with the Z-Wave device. I swear I had this problem with ramp rate on this dimmer on the first one I installed, but I have had so many changes recently I can't pin point what could have made any difference. I can tell you everything(Polisy, HA/Ameridroid..etc) has been restarted and the breaker turned off and back in for that room...but it could have been me changing the parameter wrong a few a weeks ago. What I do to query the parameter after I set it, is changed the field to something else then query....the response will be from the switch from what I can tell. I did this when I tested this morning....I changed the ramp rate parameter to 20, hit set, then changed the parameter to 19, but hit query, not set and then saw the parameter came back as 20.

I just tried with the new dimmer and the old. I set 9 to 20. Both work as expect with a 20 second ramp rate for power on and power off the light. The way I set it was right light the Dimmer in the Left Pane of the Admin Console. Then clicked "Set Configuration Parameter". That menu I can easily query the value as well. In your post above you are setting one by a program and I assume the other from the Main Admin Console on the switch itself. I think this may have been my issue before, I have been making so many changes, but do remember having a similar issue.

Good morning @Athlon! I had the same issue myself a few weeks ago. I only had 1 dimmer in the kids bedroom, so I haven't spent much time on it. I installed a second one in another room this week. I will give it a try and report back if I have the same results as you. If I remember correctly I could set the default on level, but couldn't get the ramp rate set correctly. I only started with Z-Wave a few weeks ago. One thing I tried to do after setting the parameter was query the parameter to make sure it was set to what I expected it to be.

Did you join the Z-Wave network as a secondary controller on your ISY?(asking to help clarify for someone that may know more than me. I have a Qolsys with Alarm.com, and joined as a secondary controller. It took several tries and both had to be really close to get the other Z-Wave devices to show. Really close as in 15 ft. I dont know a lot about the Primary/Secondary controller relationship...but it was a pain. I never could see Arm/Disarm status, and didn't really expect too as I think of the Z-Wave side of my Qolsys as different than the alarm functions since they are 2 separate protocols.. I could see Z-Wave device status, but not in real time since it was the secondary controller. I had to query the primary for updates. There is an integration on Home Assistant, but its custom and uses MQTT, but I couldn't get that going with my HA either. I'm hoping someone here knows of a way to do this too....

Great! I was thinking there was free trial, but couldn't find something quickly to validate. Thats exactly how I felt about the Sonos NS that comes from the same developer. Good luck with It and I am glad you are getting value out of it quickly.. These developers external and internal are great here! Lots of folks in these forums are always willing to pitch in too

Very much so from what I can tell. There is an account here for Simplex Tech that is a frequent poster and always helpful. I recently purchased the Sonos NS. Simplex Tech gives great and fast help.

One point of clarification about the developers notes from my point of view....I think it is great to have direct access to so many people and developers that make themselves directly available here in the forums to help. I have gotten a lot of value from many posters and it encourages me to answer questions that I might can help with.

I have trouble with the developers notes too, but thats my gap of not understanding. I was mainly curious if there was anything else you saw the NS needed on features. I just started testing it and this thread and the comments got my attention. I didn't take is as critical myself, and agree with supporting the developers that provide solutions that provide value for us.

Zooz has several smart relay's if I understand your question. Are you looking for something to trigger momentary switch like an I/O link can trigger a garage door in the Insteon world? If yes take a look at the Zooz website at the Smart Relays section. I have one of their relays. You can also Google search for advanced settings and the specific model number to find some of the custom settings. I can verify I was able to set these with my Polisy.

@Kentinada I have a Chamberlain that does NOT allow me use a simple button press, but did see a write up somewhere like what Mr Bill is talking about. The writer opened his controller and found the appropriate contacts there, not at the opener. I have the Zooz Zen16(the 3 channel model) and it works well for other things. I don't use it on my garage door. If you Google for "Zooz Zen17 advanced settings", you should see all the configuration parameters available. I was able to set these parameters with my Polisy.