MMAltair

I was on 1.5.16 when I first tried this and then upgraded to 1.6.2 to see if it helped, no joy. The fact that it works for you is interesting. Which version of IoX are you running?

I went ahead and implemented the math to do the conversion in each of the programs that read Yolink temperature data and this worked just fine. Problem solved. Thanks again!

Thanks for the feedback. It does appear to be related to the console since I can select Fahrenheit in the drop down box but it doesn't get applied when the Action is applied. As I mentioned in my first post I have an Ambient Weather system and have the plugin for this system installed. When I create a program using this plugin it allows me to select Fahrenheit or Celsius and the correct selection gets applied when the Action is added to the Then or Else clause. I think this means that it is possible for this to work but perhaps it means, as you said, all of the temperature values would need to be duplicated in the node. It would take looking into the Ambient Weather plugin to see how it is done there. I'm surprised no one else has run into this? My next step is to try and implement the math to do the conversion in the program. Thanks again!

Update - After investigating some more I'm even more confused. When I look at the Yolink temperature sensor node in the administrative console it shows the correct value in Fahrenheit, which is what is selected in the Yolink plugin in PG3. What I have noticed is that when I select Fahrenheit in the Program settings dialog box it does not reflect this setting when added to the Then clause in the program. Ex - The Yolink Node is at version 1.6.2 and is installed in slot 9 in PG3. I have noticed recently that when I synchronize UD Mobile with EISY it is complaining about a Status Name being missing for Node server 9. I'm not sure what this is about.

I think there is possibly a bug in selecting the Fahrenheit temperature reading for a Yolink temperature sensor in a program. I'm working on displaying various Yolink temperature sensors in UD mobile. I have a program that reads a temperature sensor and assigns the temperature to a variable. When I check the variable it always shows the Celsius temperature regardless of selecting Fahrenheit or Celsius in the drop down box. When I check the node in PG3 it shows the correct temperature in Fahrenheit. I also have an Ambient Weather station and if I select Fahrenheit for it's temperature sensor I gets the correct number. In the PG3 Yolink configuration I have TEMP_UNIT set to F Is this correct? How does this interact with the Program dropdown selection of Fahrenheit vs Celsius?

To add a bit more detail. After the 3 hr long internet disruption last night I have now figured out that the ELK Plugin was no longer communicating with EISY even after the internet access was restored. After I restarted the ELK Plugin things are back to normal. I have noticed this happen in the past (the ELK Plugin not communicating with EISY) but did not connect it with a loss of Internet connectivity. When this happened in the past restarting the plugin always fixed it. Loss of internet connectivity isn't always noticed unless someone is impacted by it, for example, if it happens in the middle of the night or if the disruption only lasts a few seconds. The next time the ELK plugin hangs up I'll check my router logs to see if an internet connection disruption has been logged.

Thanks, this helps my understanding of how UD Mobile works with in a local only environment. I checked the UD Mobile local IP settings and the IP address was incorrect, likely due to some changes I had made to my network in the past. I do have static IP addresses for EISY and ELK in my network so in the future I should be able to have UD Mobile local access when the internet is down. I think my other question is still unanswered. Should EISY and Polyglot plugins be able to continue operating (communicating) when the internet connection is down? The functionality that isn't working is all over the local network through static IP address. Also, everything is connected with ethernet cables, not WiFi. If the UD Mobile local access will work (now) I can try an experiment of disconnecting the internet from my router and see if EISY and the ELK plugin are communicating properly. If the answer to this question is already known that would also help.

Not sure if this is the right place to post this but I think this might be related to Polyglot so here goes. Our internet access has had intermittent outages recently (Xfinity) likely related to work being done by T-Mobile to install fiber in the neighborhood (how ironic). Each time there is an outage I lose functionality in the EISY system which I wouldn't expect to happen. I have not tried to debug this by creating outages but that's the next step if needed. Here are the details - I have an EISY system running IoX 5.9.1. I also have an ELK security system and the Polyglot ELK plugin for communication between the ELK system and EISY. I use the condition of ELK motion and door sensors to control various functions (like turning Insteon lights on and off, and relaying status through UD mobile of status events like a garage door opening). I understand that any functionality related to UD Mobile will not work during an internet outage but I would expect that internal network functionality would continue to work during the outage. I have a Unifi DM Pro network and I know the network is working properly during the outage. I can access IP cameras on my network as well as access local computers on my network and other local IoT devices. Am I missing something on expected local functionality during an internet outage? One other thing I have noticed is I can't launch the IoX Launcher during an internet outage. It tries to launch but eventually the application shuts down. Is this expected behavior?

I only have 1 hub in each house that support all of the devices for that house. If these hubs were changed to the local control hubs (I understand the local hubs are not available currently?) would the local control work for each place independently? My goal is to make sure the water supply can be turned off automatically, without internet, if a leak is detected (similar to how YoLink supports this with the D2D functionality of their water valve motor).

@Panda88, Thanks for the help getting this figured out. I purchased the YoLink plugin for the EISY system in the 2nd home and spent a few hours splitting the YoLink devices between the two houses. Everything is functioning properly now. I continue to be impressed by the YoLink wireless reliability (way better than Z-Wave) and have switched all of my water and temperature monitoring over to these devices (about 40 devices at this point). I am anxious for the local control to be finalized. Mike

One more question. Can you explain how the separate credentials work? I went ahead and created a 2nd home in the App but don't see a way to have separate access credentials. The API access credentials seem to be unique to the Account, not to a Home instance. Thanks

I wasn't aware that you could designate more than one home in the app but see that option now. Thanks for pointing this out. Will you still get notified in the App if there is an issue at either home?

I use YoLink devices extensively at 2 homes (temperature and water sensors). I have an ESIY system at each home and duplicate many of the plugins as needed to manage the 2 places separately. UD Mobile supports this quite well but YoLink creates a unique challenge since the Yolink App is unique to a mobile device and everything needs to be under 1 account. I currently only use the YoLink plugin on 1 of my EISY systems to provide local automation (automatically shutoff the water if a leak is detected). Here's the question. Is there any reason why I can't have the YoLink plugin on both EISY systems connected to the same API? I am aware that all of the YoLink devices would show up on both systems but I can programmatically choose which sensors to use with each independent system. Eventually I would like to move to the local API when this becomes available so would need to consider how this impacts the independent systems. Thanks Mike

I did finally get a shade paired with EISY by not following the Bali motorization instructions. As defined in the manual I first deleted all Z-Wave pairing in the shade by pressing the 'program' button for 7 seconds (basically a 'reset' function to delete all previous pairing). I then had to 'exclude' the shade from pairing with the remote using the exclude function in the remote and again pressing the 'program' button on the shade (this is a new step not specified in the Bali manual). Once I did this I could then 'add' the shade to EISY using the Z-Wave 'add' commend. There must be some residual pairing left in the shade even after doing the Z-Wave the 'reset' function in the shade. My guess is the Bali instructions only apply to a shade that has never been included in a Z-Wave network in the past. Unfortunately I had already added all the other shades back to the remote without EISY first being added as the primary controller and didn't have time to go back through all the excluding and including again. As a result I wasn't able to test the functionality of both EISY and the Bali remote being able to control the shades independently. When I have more time I'll go back and try this again as I want the functionality EISY provides in addition to having the Bali remote for control. Mike

I purchased Bali blinds about a year ago and purchased the Bali Z-Wave controller. I was able to pair the blinds with the Bali controller without problems and then paired the blinds with the remote as a secondary controller (associate), again no problems. Over the past year the Bali controller has been a problem and I no longer use it to control the blinds, just the remote. Now the batteries need to be recharged so I decided to try and pair the blinds with my EISY/Z-Wave/Matter and so far am not having any luck getting the shades to pair with EISY. My shades have to pair through a Z-Wave extender (AEOTEC range extender 6) due to the distance from the Matter device. The range extender shows a good connection to the Z-Wave network so I don't believe it is a problem. Is it possible to pair the Bali shades through a range extender (which supports S0/S2 inclusion)? I know that my Schlage locks have to be paired right next to the Matter controller but then work fine through a range extender which has secure inclusion (S2). If I manage to get the shades paired with EISY I'll try to duplicate the problem reported by walkman9999. Mike