Brad

Bad Paul.... j/k... Been there, done that.

Entire portal seems to be down. No Alexa connectivity and can't log in via web page which was extremely slow to display on desktop browser.

I installed the UD Mobile app. It's not near as nice as Agave, but I think Agave may be in it's death throes since support is difficult to get. That's a shame since I paid for the lifetime family subscription. But honestly, I only use it to poke one favorite button to tell the house to go to sleep "after" the wife is in bed. I don't want Alexa mistaking what I'm saying and think it's the "both of us going to bed" routine and turn on the bedroom lamps.

I'm having a similar issue with an Android phone upgrade from Android 10 to Android 11. It looks like the Storage permission is for Media only and not the entire SD card. Therefore, Agave can neither create the Agave_Backup folder nor can it read it if it's created manually and the backup file from the old phone placed there.

There is no physical connection between Polisy and the URTSII. Here is how I have it set up: Polisy with Somfy node server communicating via the network An iTach Flex WiFi module is the target of the communication from the node server. This module receives commands from the Somfy node server to open/close curtains. The iTach module has a serial interface built into it that I plugged into an ethernet port in my home run closet. The URTSII is in the room with my drapes and plugged into the other end of the ethernet run from the closet. I tried leaving the URTSII in the closet but it was too far from the drapes and too many intervening walls. You can use a regular ethernet run to push serial data. I believe the iTach came with a couple versions of cable (crossed, not crossed), but I can't really remember at this point. All I remember is looking at the pinout at one point. I may have even made my own cable with the proper wire order to go between the URTSII and ethernet wall jack. So, in summary: Polisy with Somfy node server configured for network commands => iTach => URTSII => Drape Motor

@gspitale As you probably noted earlier in this thread I'm using the iTach IP to serial with the URTSII. It functions perfectly until I get a power outage. After that, I just have to manually open or close the drapes by pushing a button on the URTSII. It's almost like the URTSII loses it's mind and doesn't respond on the serial line until it gets "poked". Other than that and the short range required between the URTSII and the motor, using it with the Somfy nodeserver (which I just recently migrated off my RPi onto Polisy) works great with ISY/Alexa control.

Thanks for the responses. At least it's just not me having a problem. It's just odd how I've had these Z-Wave devices for several years and it just recently started happening.

Had a weird thing happen to me tonight when adding an Insteon On/Off module. After linking the Insteon module, a new Z-Wave device appeared in the device list. I have a Z-Wave outlet module that was registered as ZW002_1. I've had it linked for over a year with no problems. After adding the new Insteon device, the mystery Z-Wave device has an address of ZW002_184 and is listed as a Barrier device. I have no barrier devices that I'm aware of. The only other Z-Wave devices I have are a thermostat (ZW004_1) and an alarm panel(ZW003_1) and a sub-device of the alarm panel(ZW003_119). The ZW002_1 device is linked to the alarm panel so I can monitor the armed/disarmed state of my security system. Could one of the automatic updates of the security panel firmware have caused a virtual device to have been created? ISY 994i/IR Pro Firmware: 5.0.16C Z-Wave: 21100

Ah, ok. I haven't messed with using the serial interface with the Somfy nodeserver for this very reason. The only thing I can suggest is to plug in a serial monitor on that port to see what exactly, if anything, is being sent out on that serial port. You may have to do some research/work on determining if you need a crossed or straight through cable too. It was quite a while ago that I hooked up my ITachFlex WiFi to Serial gizmo to the URTSII but I'm vaguely recalling I had to work through that problem.

@Dean what is your exact setup? Is the Somfy nodeserver configured to use a local serial port on a raspberry pi? Is the nodeserver configured to send a TCP command with serial data to a TCP/Serial converter?

I believe the way the Portal works, is that your ISY makes an outbound connection to the Portal which then keeps a socket open back to the ISY. What sort of "external URL" are you talking about? You normally don't need one unless you are pointing a domain name to your ISY and then punching holes in your routers firewall to access it.

I've been using this setup since 2017. Somfy Node Server (WiFi) -> Global Cache ITach Flex WiFi -> URTSI (serial port) I've had this running on a Raspberry Pi 3 in one room, ITach sitting next to my router in the home run closet and URTSI in the room with the drapes. The URTSI had range problems when sitting in the home run closet 2 rooms and a hallway away. Fortunately I had a spare ethernet port in the room with the drapes to solve the range problem easily.

In addition to what has already been said, mine work fine, but I don't have as many as I used to because when I first set up around a dozen of them, Amazon decided to update their system and I lost all of them. I was a bit upset when that happened and only recreated a couple since I didn't want to have to keep recreating them everytime they had a whim to do a destructive update. With that being said, they've never caused that to happen again.

In January, when I first installed my somfy curtains, I didn't think the open/close would work for that exact reason, but I tried it for giggles. It worked! I was surprised and assumed Amazon was being smart about curtains. But something changed within the last few weeks and now it's not working. The "turn off/on" does work as it always has. Fixed it by adding "open/close curtains" as a routine.

Today I discovered that the Open Curtains command to Alexa didn't work. Normally my curtains open an hour after sunrise and close at sunset automatically. When I got up today, they weren't open (most likely because my somfy setup became confused because I rebooted my router before going to bed last night). So I told Alexa to open the curtains like I normally do when there's a hiccup in the automatic setup. Alexa responds with "Curtains doesn't support that". Is this a portal issue or did Amazon change something on the Alexa side recently? Unfortunately, I can't pinpoint exactly when this stopped working because normally the automatic open/close works and I can't remember when the last time was that I had to ask Alexa to do it. Edit: Tried "Turn on/off curtains" and that works