photogeek54

UPDATE: I setup a program to send SMS to tmobile every 5 minutes. My Eisy sent the messages every 5 minutes for about 20 times (missing 2 of the messages towards the end) then became highly irregular. So yes it works somewhat but is definitely rate limited.

Seeing some progress in support for simple matter device I upgraded to 5.9.1_18 and tried to add a Tapo s505 simple on/off matter WiFi switch. I used the ud mobile app to add via QR code . Go this error: Could not Write characteristic: 18EE2EF5-263D-4559-959F-4F9C42 9F9D11: The specified UUID is not allowed for this operation. This may be caused by an iOS security measure that requires developers to install a developer profile see https://docs.silabs.com/mobile-apps/latest/mobile-apps-matter-demos/05-enabling-developer-mode

Yes adding an app password was the answer, thanks for the tips. SMTP now works. I suspect that that tmobile is rate limiting the messages coming from UD. I am able to send some texts via the phone@tmomail.net gateway using my gmail SMTP but may be rate limited too. I'll update if I figure that out.

@sdynak that is a Gmail account. I have my own domain setup in a Gmail workspace. I can’t use pushover as. I send to many people and don’t want to make each of them get a pushover app.

So I've confirmed that the t-mobile email to SMS gateway is still working when I send to it from my personal email address. I suspect they have blocked the default UD SMTP server. I tried using my own gmail login in the admin console but get smtp error -1 (see below). Do you see anything wrong with my settings?

I have the paid for notification app, never used pushover. Some of the notifications go to family members and they seldom read emails, that is why I want to send SMS.

It sounds like this may have stopped working a while ago and I haven’t noticed. Anyone know of another way to send sms messages from iOX? Maybe the notification plugin?

notifications to [phone-number]@tmomail.net are no longer working. I'm using the default smtp settings and the "send notification to" action.

So I upgraded to standard to fix the problem. FYI, what had me confused is that I didn't realize the "6249 Southridge greens event" was continuing to cause the "reached max daily message count" messages. In fact I had forgot I was the one causing those notifications to happen. I thought the 6249 messages had stopped and the max daily message count notifications were just stuck in a loop. I also didn't expect the limit on the free version to be so small (about 8 per day?). It's my lack of understanding and I'm sure that was obvious to you but not to me. Thanks for taking the time to look at it.

Yes it sent that message and a few others today. But then I got about 100 “reached max daily message count” messages https://photos.app.goo.gl/Dk56N8EHQdbDBNrX9

here's another debug log package Notification_1-30-2025_10619_PM.zip

I turned off the plugin but would like to turn it back on, wondering if you found anything. I’m happy to just purchase the paid version but thought you might want to look at it before I did.

The notifications started again this morning. I got a debug log this time. Notification_1-19-2025_111616_AM.zip

Have only setup 1 program to send a notification to ud mobile but it has only sent a few during testing https://photos.app.goo.gl/FBGbqaCWchUoaUDb9

It kept sending the messages all day till 3pm and then just stopped, weird

I don’t know what the daily Limit is in the free version but I must have reached it yesterday while trying out the notification plugin for the first time. Even though I haven’t sent any notifications today I’m getting “Reached max daily message count, please upgrade to standard version” every 5 minutes. I don’t think I need many features so not sure I even need the standard version .

Thanks, looks like I wasn't signed up for news and announcements but I am now.

I have the MAC addresses of 2 iphones configured in unifipresence. Starting several weeks ago these MAC addresses started going offline a few hours after I start the plugin. I'm not changing The wifi network on the phones. The log looks like the phones just left the network normally but they are still on the network and functioning normally. If I restart the plugin they show online again. Has anyone else seen this problem? Here's an excerpt from the debug log. They go offline at 23:02:46 2024-12-30 23:02:31.280 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2024-12-30 23:02:31.280 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2024-12-30 23:02:31.281 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2024-12-30 23:02:31.281 Thread-616 (poll) udi_interface.node DEBUG node:setDriver: controller:UnifiCtrl No change in ST's value 2024-12-30 23:02:31.332 Thread-616 (poll) udi_interface.node DEBUG node:setDriver: 08e68991dc26:08e68991dc26 No change in GV1's value 2024-12-30 23:02:31.351 Thread-616 (poll) udi_interface.node DEBUG node:setDriver: 141ba02a0601:141ba02a0601 No change in GV1's value 2024-12-30 23:02:31.368 Thread-616 (poll) udi_interface.node DEBUG node:setDriver: 6c1f8aaa354c:6c1f8aaa354c No change in GV1's value 2024-12-30 23:02:31.385 Thread-616 (poll) udi_interface.node DEBUG node:setDriver: c82add87d78d:c82add87d78d No change in GV1's value 2024-12-30 23:02:31.402 Thread-616 (poll) udi_interface.node DEBUG node:setDriver: 0298647559fe:0298647559fe No change in GV1's value 2024-12-30 23:02:31.419 Thread-616 (poll) udi_interface.node DEBUG node:setDriver: 66ad0b5f3510:66ad0b5f3510 No change in GV1's value 2024-12-30 23:02:31.436 Thread-616 (poll) udi_interface.node DEBUG node:setDriver: daf3559f989e:daf3559f989e No change in GV1's value 2024-12-30 23:02:45.143 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message longPoll 2024-12-30 23:02:45.143 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING longPoll 2024-12-30 23:02:45.143 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS longPoll message {} from Polyglot 2024-12-30 23:02:45.143 Thread-617 (poll) udi_interface DEBUG unifi_poly:heartbeat: heartbeat: hb=1 2024-12-30 23:02:45.152 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'command': [{'address': 'controller', 'cmd': 'DOF'}]} 2024-12-30 23:02:45.179 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2024-12-30 23:02:45.180 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2024-12-30 23:02:45.180 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': 'controller', 'success': True} from Polyglot 2024-12-30 23:02:46.288 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2024-12-30 23:02:46.288 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2024-12-30 23:02:46.288 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2024-12-30 23:02:46.288 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: controller:UnifiCtrl No change in ST's value 2024-12-30 23:02:46.293 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 08e68991dc26:08e68991dc26 No change in GV1's value 2024-12-30 23:02:46.293 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-12-30 23:02:46.297 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 141ba02a0601:141ba02a0601 Reporting set GV1 to 0 to Polyglot 2024-12-30 23:02:46.297 Thread-618 (poll) udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-12-30 23:02:46.297 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-12-30 23:02:46.298 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '141ba02a0601', 'driver': 'GV1', 'value': '0', 'uom': 2, 'text': None}]} 2024-12-30 23:02:46.301 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 6c1f8aaa354c:6c1f8aaa354c Reporting set GV1 to 0 to Polyglot 2024-12-30 23:02:46.301 Thread-618 (poll) udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-12-30 23:02:46.301 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-12-30 23:02:46.305 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: c82add87d78d:c82add87d78d No change in GV1's value 2024-12-30 23:02:46.305 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-12-30 23:02:46.309 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 0298647559fe:0298647559fe No change in GV1's value 2024-12-30 23:02:46.309 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '6c1f8aaa354c', 'driver': 'GV1', 'value': '0', 'uom': 2, 'text': None}]} 2024-12-30 23:02:46.309 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-12-30 23:02:46.313 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 66ad0b5f3510:66ad0b5f3510 No change in GV1's value 2024-12-30 23:02:46.313 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-12-30 23:02:46.317 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: daf3559f989e:daf3559f989e No change in GV1's value 2024-12-30 23:02:46.317 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-12-30 23:02:46.327 MQTT udi_interface.interface INFO interface:_message: Successfully set 141ba02a0601 :: GV1 to 0 UOM 2 2024-12-30 23:02:46.419 MQTT udi_interface.interface INFO interface:_message: Successfully set 6c1f8aaa354c :: GV1 to 0 UOM 2 2024-12-30 23:03:01.289 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2024-12-30 23:03:01.289 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2024-12-30 23:03:01.289 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2024-12-30 23:03:01.290 Thread-619 (poll) udi_interface.node DEBUG node:setDriver: controller:UnifiCtrl No change in ST's value 2024-12-30 23:03:01.294 Thread-619 (poll) udi_interface.node DEBUG node:setDriver: 08e68991dc26:08e68991dc26 No change in GV1's value 2024-12-30 23:03:01.295 Thread-619 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-12-30 23:03:01.298 Thread-619 (poll) udi_interface.node DEBUG node:setDriver: 141ba02a0601:141ba02a0601 No change in GV1's value 2024-12-30 23:03:01.298 Thread-619 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-12-30 23:03:01.302 Thread-619 (poll) udi_interface.node DEBUG node:setDriver: 6c1f8aaa354c:6c1f8aaa354c No change in GV1's value 2024-12-30 23:03:01.302 Thread-619 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-12-30 23:03:01.306 Thread-619 (poll) udi_interface.node DEBUG node:setDriver: c82add87d78d:c82add87d78d No change in GV1's value 2024-12-30 23:03:01.306 Thread-619 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-12-30 23:03:01.310 Thread-619 (poll) udi_interface.node DEBUG node:setDriver: 0298647559fe:0298647559fe No change in GV1's value 2024-12-30 23:03:01.310 Thread-619 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-12-30 23:03:01.314 Thread-619 (poll) udi_interface.node DEBUG node:setDriver: 66ad0b5f3510:66ad0b5f3510 No change in GV1's value 2024-12-30 23:03:01.314 Thread-619 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-12-30 23:03:01.318 Thread-619 (poll) udi_interface.node DEBUG node:setDriver: daf3559f989e:daf3559f989e No change in GV1's value 2024-12-30 23:03:01.318 Thread-619 (poll) udi_interface INFO unifi_poly:update: update: 0

Thanks for the tip about settings only available on the thermostat. I hadn't found them. I've adjusted the temp there down by 1.5 degrees and is tracking well now.

Many of the devices I have purchased recently support Matter and threads so I'm waiting patiently for Matter support on Eisy. They all work with their own apps but Eisy support will make them even better. I know UD is working hard on this and I hear its quite difficult but any thoughts on when a beta of Matter support might be coming would be appreciated.

This is VERY helpful! The web site explains a lot. I find that my 2 remote sensors disagree on temperature by .7 degrees F when put in the same place and the main thermostat sensor register 3.3 degree hotter than the remotes. The thermostat itself feels warm from the electronics which probably explains that difference. Is there a way to calibrate the sensors or apply an offset to get them more accurate?

I’d love to download a detailed spreadsheet, I’ve looked on their website but don’t see such a thing. Where do you find it?

Just installed an ecobee premium and the ecobee plugin. I'm figuring out what all the settings and variables mean but I'm guessing there is some kind of reference material somewhere that would make my learning easier. For example: How does the "Home/my ecobee" sensor work (the child of the main ecobee in admin console)? It shows a temperature that is higher than what shows on the thermostat display or the 2 remote sensors. Which sensor is it using to actually decide when to activate the furnace (I have all 3 enabled in the "home" comfort setting ). How long does it take for a sensor to see motion and decide the room is occupied, is it time in the room or does it need to see some minimum amount of motion? How does it decide when the room is unoccupied? Is there a way to enable more advanced/HVACprofessional settings? I see lots of settings/values in the debug log that I cannot set in the ecobee ios app. What causes the ecobee to go into these Eco+ states? Mine normally uses 0, 6 and 7 not 1. EN_ECOHCS-0 = Idle EN_ECOHCS-1 = Heat EN_ECOHCS-6 = AuxHeat EN_ECOHCS-7 = AuxHeat2 EN_ECOHCS-8 = AuxHeat3

inovermyhead is asking about PG2 not PG3 I have the same problem I have an rpi running some pg2 node servers. http://"rpi IP address":3000 doesn't work http://"rpi IP address":8080 doesn't work

I decommissioned my ISY994 and have migrated to Eisy but I still have a few node servers running on my Rpi under PG2. How can I reach to GUI for PG2 on the Rpi? I've tried browsing to rpi URL at port 3000. but no luck.