samara

22860

Javi, I submitted a ticket with the UDM log file attached.

Javi, It seems to me if UD Mobile is not aware of the phone's location when the app is running in the background (or is not allowed to communicate with the IoX device unless actively running in the foreground) it has very little utility for geofencing. My experience has been that the app "stores" the geofence status changes while running in the background/suspended/not-started and them reports them all to the IoX device when I open the app in the foreground -- not very helpful. Interestingly, MobiLinc HD works just fine with both the Polisy and i994 ZW IR Pro when running in the background/suspended/not-started. I guess Apple allowed them to use the iOS location for geofencing.

I have the same issue: I updated packages to 5.7.0 via the AC. In SSH uname -a still reports OS as 13.1 The SSH banner also reports version 13.1

Smartenit IoT8-Z – Model # 3012A Input Output Controller: https://smartenit.com/shop/iot8-z/ Full control of relays and status of inputs Enbrighten Zigbee Dimmer #43080: https://www.amazon.com/gp/product/B08428GDS8/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&th=1 MHCOZY 1 Channel 5V 12V ZigBee Smart Relay: https://www.amazon.com/dp/B08X218VMR?psc=1&ref=ppx_yo2ov_dt_b_product_details

I've had the same problems with Prowl notifications as described above. I have a solid install running 5.3.0 since late 2020. Everything was running well until January 10, 2022 when Prowl pushes started to fail. Many different error messages thrown by the ISY. The Prowl API works fine using reqbin.com and sending the same POST request and content as used on the ISY. I've moved my critical notifications to Pushover. Everything works as advertised on that platform. I have tried all of the fixes noted above with no success. I have found that I can successfully send push notifications via Prowl if I use HTTP on port 80 instead of HTTPS and port 443. Could this be a certificate problem in the ISY??