sjenkins

@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

I am now ready to do a pull request to the MQTT plugin / node-server which adds a Radgo device. Just need to update the config documentation. if you want to see and tryout the code before it's published then checkout my fork of the mqtt plugin. (garage branch) https://github.com/sejgit/udi-mqtt-pg3/tree/garage Have it working well at home ; let's see in the field !!

1884 is the required port using the IP of your Polisy/Eisy

mine arrived and its wired and working! I can get both status and control it manually through the MQTT server on the EISY Below is a screen shot from MQTT Explorer which is a client I can use to read/write to the MQTT server. Works like a charm! I may set up a manual python program first or may go right at the MQTT plug-in and make a device!!

The current MQTT doesn't do garage door openers but it is pretty easy & open to pull requests. A few years ago I added I think three different devices. You just set-up standard in/outs and they type of data. I am told my ratgdo has now shipped; so my plan was to get it up and going then work on the MQTT plugin.

Nice setup. I have a well (as well) and considered this option. Went with the Yo-Link as it was cheaper and less wiring (and I'm an electrical engineer). But I really appreciate this as the 'ideal' solution in many ways. My well pump is 40A as its on-demand pressure so would have required a bit beefier setup.

Hard to compare if you buy only one. I can say I’ve had the yo-link high torque robot for over a year now. It has been exorcised numerous times both through direct pairing with yo-link leak sensors as well as indirectly through eisy & node server from Insteon and zwave leak sensors.

Ordered one a little over a week ago. Over the weekend I moved my MQTT from a pi over to my eisy. I have used the MQTT “plugin” quite a bit over the last few years, adding some devices to it. Would be easy to add a special ratdgo device as well. So just staring at my mailbox now as no tracking on the ratdgo site. lol.