DennisC

I'm still having issues, as late as this afternoon. This was after installing another Python Interface update this morning. @bmercier is aware of this and has been working on a solution. I sent him additional log information this afternoon.

Don't be surprised if you continue to have this issue after reinstalling the plugin. There is still an issue UD is working on correcting.

If you go to the plugin store in PG3, click on a plugin you are interested in, and then select more information, you should be taken to the plugin page. Many developers list configuration info there and some offer examples on how to use the plugin in programs and notifications.

While I am still using CAO Wireless tags in the refrigerator with the extended rechargeable batteries, yes the YoLink devices can be used inside the refrigerator. They have two lines of T&H devices. The original device is about $25. They have a newer X3 device which adds an extended life batteries, extended data logging, and storage for power outages. Of course they are more expensive.

The YoLink plugin allows the sensor to be used in programs and notifications, just like Insteon devices. Once the plugin is connected to YoLink, all that needs to be done is add the device to the hub, then restart the plugin.

Not sure what you mean by this? Are you looking for more than the Node Server / Plugin can do?

And they have a full line of complete water isolation valves, as well as add on devices to control existing valves. I have been very impressed with Yolink. They are very responsive and have good range. The only negative is it is cloud based. With the help of the YoLink plugin, I started replacing my CAO Wireless Tags that monitor T&H around the house with Yolink devices, which even have a display on them. All of their devices have a better price point then other vendors. I believe today is the last day of their sale. I found that with the discount coupon the pricing on their website was better than Amazon.

@Michel Kohanim, This is not something missing, but as I started reading through the documents, a clarification did come up. Under Development Environment is the following statement: "You can do plugin development directly on the Polisy/eisy." Then you go on to give detail information on what needs to be done (this is good and much appreciated). However, all of the information is centered around eisy, with a few paragraphs for using Windows. Is the development on Polisy exactly the same as on eisy, or are some of the steps to setup different? Thank you!

170001 messages are nothing to worry about. Read this post and look for two messages from Michel.

Do you know how to ssh in to eisy? If so, ssh in to eisy with the admin console open. Enter the following in to the ssh window: sudo tail -f /var/udx/logs/log Then in the admin console click on upgrade packages under the configuration tab. This time, watch the log displaying on the ssh screen to eisy. Let us know what is displayed in the log.

@Michel Kohanim It appears the page displays differently on a tablet than on a computer. I have been accessing the page on a tablet using the menus at the bottom of the page for convenience. When I just accessed the site from my computer and tried the top menu, the links work. However, even using a computer, the menu at the bottom of the page will take you to Getting Started, but the hyperlinks on the page for developer, development environment, & developing & testing do not work. Here are some examples:

@Michel Kohanim, it appears several of the links are broken on https://developer.isy.io/ Under Getting Started, items 1, 2, & 3 have broken links. I believe I reported something similar on Discord, but there was no response.

I recently started looking at it.

@bpwwer, sometimes when you create something, it is hard to evaluate if everything is included/covered. We (human mind) tend to fill in the gaps as we read when we know the topic matter. Don't get me wrong, I think the documentation you have created is great, from the perspective of already knowing how it's done. When you are just starting out, the step by step roadmap you created above is extremely helpful, at least to me. Thank you

Yes, it is extremely helpful and I appreciate you taking the time to spell it out for me. I have read some of the documents and think they will be helpful. Polisy is what I will be attempting this on. While I would not ask this of anyone, I think there would be some interest in a one time Zoom session (maybe recorded so it is available for review) that takes you through the process of creating a simple plugin, or maybe just walks through one of the example plugins. I very much appreciate you taking the time to explain all of this.

I am not sure I follow how you restored ISY backup from PG3? Correct procedure is a little different depending on if you have only Insteon, ZWave, or both. You need to read and follow the directions. Here are the migration directions: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration In addition, if you have Insteon, you require a USB PLM or an adapter cable. If you have ZWave, are you using UD ZMatter dongle?

Try power cycling your ISY.

I can use all the help I can get! As I explained above, I was looking more for the steps that need to be completed, rather than how to do the steps. I very much appreciate you taking the time to make these, and for reposting them so I can benefit from your tutorials. Thank you.

Hi Bob, I fully understand what you are saying. I wasn't suggesting a step by step procedure on how to program. I was suggesting a high level snapshot of how to setup to create the plugin's using UD's tools. I feel that is what is missing. Learning a programming language is a lot easer today then it was when you did it. There are plenty of tutorials and guides for each language, that wasn't what I was looking for. I have read some of the available documentation for creating a plugin and I think it will be most helpful during the actual development process. Before getting to that, however, you need to complete certain steps that I haven't been able to find documentation for. As an example, I have a spare Polisy that I planned to use to attempt a plugin development with. I know to click on the Developers tab and add that. There information there that will be helpful, but what I feel is missing is where to go from there. What is the next step before starting to code. Not so much a step by step of the development process, but more of a high level guide on what steps need to be taken prior to coding, followed by high level goals or milestones. Not so much the how to setup and develop but the "what must be done" to setup & develop. I hope that makes sense and is somewhat clear.

Thanks for reposting, I will watch as soon as I can. One of the things UD is missing, is a video demonstration of how to get setup and started to developing a node server/plugin. If you haven't done it before, its hard to understand how to get started. Hoping this fills the gap.

I just sat down to watch your video and see it is unavailable. Too bad, I was interested in seeing how to get started.

Once you get eisy to your portal account, migrating of plugins, formerly node servers is explained here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migrating_Node_Servers_to_PG3x

If I understand you correctly, I believe you are interested in setting up custom notification substitutions. Take a look at this: https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables Specifically, the following: For example ${sys.node.11 22 AA 1.name} would use the name of the device node whose address is 11 22 AA 1 Instead of specifying a fixed address, the special character # may be used to reference the element in the event that caused the program to run. (Does not work in network resources) For example, if a status event for node 11 22 AA 1 caused a program to run, then ${sys.node.#.name} would use 11 22 AA 1 as the address.

Zwave can add several nodes, some of which don't work with ISY. To help sort it out, right click on a device and look for group devices. Group only appears for the main node. That will arrange sub nodes under the main node. From your screenshot, the ZW's are in the name, not the address. The name can be anything you want. Typically, unused nodes can be placed in a folder and labeled so you know they are not in use. If you delete them, they usually return.

It might be time to give UD Mobile a try. It is actively being developed with great support.