sjenkins

I have Samsung tv’s and use the Alexa routines. Unfortunately if the SmartThings app falls off your phone (due to lack of memory or something) it will stop working. Have not invested the time to make this work with preferrred paths. My marantz behaves much better with my isy. Love to hear of someone who put the time into this one without killing power to the Samsung , I know how to do that but then you lose standby “features”.

@Michel Kohanim, very cool. Let me attempt the next two Todo's. Is there timing for the next 'blash'? TODO tap into gateway events - this, I believe, works like a push for updates when the move starts and is completed for scenes and shade moves. TODO remove parameters based on shade capability (primary, secondary, tilt) - this I don't know how to do without creating a separate node for each shade type. Effectively I want to have inputs for only the parameters the shade has capability for. It means the profile nodedef is different. Can the controller if/then which nodedef is picked using the same python code? I have not asked the crew on discord this question yet as up until now I didn't know how to word the question

I think this plug-in is pretty stable at this point. I am using it in my home now. Removed the need for the user to know which gateway is primary & added automatic switching between the gateways if primary changes, which I am told can happen. Updated configuration instructions & added link to this forum. Feedback is welcome. VERSION = '0.1.0' """ 0.1.0 DONE handle multiple gateways automatically, picking primary & switching if required DONE updated configuration instructions as well as link to the forums add to future version: TODO tap into gateway events TODO remove parameters based on shade capability (primary, secondary, tilt) past versions: 0.0.9 DONE fix uom for positions(100) & ids(107) DONE more notices clean-up DONE shade naming to include room as scenes DONE remove status based on shade capability (primary, secondary, tilt) 0.0.8: DONE handling of notices individually DONE polling 5s short-poll 30s long-poll DONE status for programs (positions etc) 0.0.7: DONE faster status updates when command is given DONE bug fix DONE re-order of parameters displayed 0.0.6: DONE move shade by specific amounts DONE bug fix scenes not activating 0.0.5: DONE change shortpoll to 30s DONE update shades on shortpoll DONE clear start notice at shortpoll DONE clean up error proofing in get DONE fix updating variables with shortpoll DONE limit device ping to 5s 0.0.4: DONE discover when new gatewayip is entered DONE poll status regularly using shortpoll DONE update required after nodes added to get status DONE notice when gateway get error """

A few refinements for updating as well as presentation. Based on capability no longer presenting irrelevant data. Need to do the same for the parameter input, just not sure how to do that without making a new node. I think I finally have the right uom's for the parameters. Input is welcome! VERSION = '0.0.9' """ 0.0.9 DONE fix uom for positions(100) & ids(107) DONE more notices clean-up DONE shade naming to include room as scenes DONE remove status based on shade capability (primary, secondary, tilt) add to future version: TODO remove parameters based on shade capability (primary, secondary, tilt) TODO handle multiple gateways in case primary switches TODO tap into gateway events past versions: 0.0.8: DONE handling of notices individually DONE polling 5s short-poll 30s long-poll DONE status for programs (positions etc) 0.0.7: DONE faster status updates when command is given DONE bug fix DONE re-order of parameters displayed 0.0.6: DONE move shade by specific amounts DONE bug fix scenes not activating 0.0.5: DONE change shortpoll to 30s DONE update shades on shortpoll DONE clear start notice at shortpoll DONE clean up error proofing in get DONE fix updating variables with shortpoll DONE limit device ping to 5s 0.0.4: DONE discover when new gatewayip is entered DONE poll status regularly using shortpoll DONE update required after nodes added to get status DONE notice when gateway get error """

Fixed notices so they come and go individually, polling modified to match shade updates. Fixed statuses so they can be used in programs. Feedback is welcome! VERSION = '0.0.8' """ 0.0.8: DONE handling of notices individually DONE polling 5s short-poll 30s long-poll DONE status for programs (positions etc) add to future version: TODO remove parameters based on shade capability (primary, secondary, tilt) TODO version update notices past versions: 0.0.7: DONE faster status updates when command is given DONE bug fix DONE re-order of parameters displayed 0.0.6: DONE move shade by specific amounts DONE bug fix scenes not activating 0.0.5: DONE change shortpoll to 30s DONE update shades on shortpoll DONE clear start notice at shortpoll DONE clean up error proofing in get DONE fix updating variables with shortpoll DONE limit device ping to 5s 0.0.4: DONE discover when new gatewayip is entered DONE poll status regularly using shortpoll DONE update required after nodes added to get status DONE notice when gateway get error """

Worked on status updates, some bug fixes as well as ordering the parameters so they look nicer. Feedback is welcome! VERSION = '0.0.7' """ 0.0.7: DONE faster status updates when command is given DONE bug fix DONE re-order of parameters displayed add to future version: TODO remove parameters based on shade capability (primary, secondary, tilt) TODO version update notices ; are they provided by polyglot now? past versions: 0.0.6: DONE move shade by specific amounts DONE bug fix scenes not activating 0.0.5: DONE change shortpoll to 30s DONE update shades on shortpoll DONE clear start notice at shortpoll DONE clean up error proofing in get DONE fix updating variables with shortpoll DONE limit device ping to 5s 0.0.4: DONE discover when new gatewayip is entered DONE poll status regularly using shortpoll DONE update required after nodes added to get status DONE notice when gateway get error """

@Michel Kohanim, I was. The docs are really coming together lately as far as requirements to make a plug-in work and resources to make it better. I find as I write programs I like to dig into the library routines I am calling / relying on. In this case udi_interface. Helps a lot to know what it's doing (it's actually commented not too bad). Maybe it is somewhere but any more self documentation of the libs & system helps me get the big picture as well as perhaps generating ideas for improvement in the minutia. As I say it may be in some of the files I haven't dug around in yet. Looking back on this paragraph I know I am not clear in my ask. I think it's just a "keep going, the docs are getting much better". It really helps the better they are to speed development but also to help us part-timers go deeper too ; and maybe help make the system better. This stuff is a lot of fun & me/we would love to help make it better.

@Michel Kohanim thanks for working on the docs! They really are starting to bring together the disbursed info (both over space and time). It does currently make it quite a treasure hunt to find stuff. It is nice when other plugin developers leave their code public as well. I have learned a tonne off of them. I know the incentives don't align, but would many people "steal" and not pay for a plunin? Some would I know. If I could request, knowing you are busy, to continue rounding up the explanation of the interface. I have started going through it function by function myself, but always helpful if it is commented well. Again, thanks to the whole team!

Bugfix & added moving shades by specific amounts. Interested in feedback! VERSION = '0.0.6' """ 0.0.6: DONE move shade by specific amounts DONE bug fix scenes not activating add to future version: TODO faster status updates when command is given TODO remove parameters based on shade capability (primary, secondary, tilt) TODO version update notices ; are they provided by polyglot now? past versions: 0.0.5: DONE change shortpoll to 30s DONE update shades on shortpoll DONE clear start notice at shortpoll DONE clean up error proofing in get DONE fix updating variables with shortpoll DONE limit device ping to 5s 0.0.4: DONE discover when new gatewayip is entered DONE poll status regularly using shortpoll DONE update required after nodes added to get status DONE notice when gateway get error """

Still more to do here but we have nodes for shades and scenes. The ability to activate scenes. Can open / close / stop or tilt open / close shades. Going forward I am looking to clean up parameters which do not belong with certain types of shades, as well as add the ability to move shades to specific locations. Open to feedback and / or requests. VERSION = '0.0.6' """ 0.0.6: TODO think about status updates when command is given TODO remove parameters based on shade capability (primary, secondary, tilt) TODO move shade by specific amounts add to future version: TODO version update notices ; are they provided by polyglot now? past versions: 0.0.5: DONE change shortpoll to 30s DONE update shades on shortpoll DONE clear start notice at shortpoll DONE clean up error proofing in get DONE fix updating variables with shortpoll DONE limit device ping to 5s 0.0.4: DONE discover when new gatewayip is entered DONE poll status regularly using shortpoll DONE update required after nodes added to get status DONE notice when gateway get error """

Thanks @dbwarner5! you gave me at least 3 ideas for my favourites which is didn’t have. 1. folder for rooms temperature 2. enable / disable folder 3. forecast folder

If you read and reread the developer docs, my suggestion is to set up eisy samba server so you can use it as a drive. Then you can develop from your computer & test often on the Eisy. Some develop using eisy as the computer, I like doing above & ssh so I can sit in my chair in my living room and code. How to do all the above is in the developer docs, which are even starting to look good (not sure who on the team @Javi is responsible for that).

Note: Scope of this plugin/nodeserver is PowerView-G3 HunterDouglas ; G2 is out of scope. Feedback is welcome. Update: VERSION = '0.0.5' """ 0.0.5: DONE change shortpoll to 30s DONE update shades on shortpoll DONE clear start notice at shortpoll DONE clean up error proofing in get DONE fix updating variables with shortpoll DONE limit device ping to 5s add to future version: TODO think about status updates when command is given TODO move shade by specific amounts TODO version update notices ; are they provided by polyglot now? TODO remove parameters based on shade capability (primary, secondary, tilt) past versions: 0.0.4: DONE discover when new gatewayip is entered DONE poll status regularly using shortpoll DONE update required after nodes added to get status DONE notice when gateway get error """

@Michel Kohanim, You caught me cutting onions ; my mum passed with Alzheimer's , this is tremendous use of home automation.

Kind of thought this might be use case. Not to belabour, but as this is local notification what kind of things make sense in your situation?

I can see this being a plugin/node server with many uses. Can the author give their use cases? And perhaps others chime “haha” in as they play with it?

It does but it only writes when detected. Currently does not clear after a time. I have been thinking of clearing it manually in the mqtt periodically after detection as a stopgap.

Agree about the firmware. If you check out his git you can see them & he does seem to be knocking them off so I feel good he’ll get there. I still have the on off issue where status is good but control doesn’t always work. Motion is just a detected & never goes to clear status. When you trigger the light by walking in front of the motion, the light status gets reversed in mqtt. Great base product & he is active in the issues area so I think he will get there.

I think your current thoughts are spot on.

Just in my pull was accepted so the MQTT plugin is up to version 0.11 and now has a Ratgdo device. Looking at @Goose66 's plugin, it is much more professional, but my "baby" is pretty too! (I see in your todo to change the requirement of naming, I would change that). This community is a lot of fun, isn't it?

Looks like @xking took the pull. Thanks again buddy!! So as you say in the production store the Ratdgo device has been added! @TriLife I took a look in the non-production store and see your git-hub. Assuming no core changes I am happy to do a pull request there with the changes. Not sure the plan to "bring it all together" but get a hold of me on the discord, I am headrom there.

I just did a pull request to add the Ratgdo garage device to the MQTT plugin. I may be out of date as I forked and added to the @xKing site, but I am seeing @TriLife a lot here now. Its been a while since I added devices to this plugin. Anyway right now the mods are waiting in a pull request, if there is somewhere else they need to go, let me know. I have tested in developer mode on my Eisy and Liftmaster. Feedback is welcome!

As @Goose66 and @EWhite it was very easy to hook up and get it sensing on my Liftmaster with 2.0 security. I did have one blip for those out there. Mine loaded up with 2.51 and I could not get the control to work. Needed to upgrade to 2.55 and all was well. I agree the motion seems to be a work in progress. I did a mod to the MQTT plugin and added a device for Ratgdo. No doubt Goose's is a better deal but I had fun writing it anyway for those who are already using the existing plugin it means saving a slot ???? Ya I know. Nice to flip the finger to the MYQ people!

Thanks as always @Goose66 I have added devices to the MQTT plugin before, and still use it so it made sense ; still took me too long, lol. Yours will likely be better for those just using the Ratgdo, as the MQTT plugin is a bit of a cyborg now with so many devices on it. Fun to do anyway. I did the pull request to @xKing tonight.

motion has been weird. the odd time it flips but I'm not sure if its coming from my sensor or not. so I just pass the status onto the isy. if you look at ratdgo's GitHub it should be 'clear' for the opposite of 'detected' I think I am done my testing & going to do a pull request to @xKing