photogeek54

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.

updated to a new cloud gateway and new version of the OS so I could create a local user. Seems like I had success, but may be short lived. The node server correctly shows my status on the network for several hours! then at 22:07:23 in the log below you see it start showing MAC addresses as going offline. These devices are still on the network. Any ideas what might be going on? 2024-07-18 22:07:22.551 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message longPoll 2024-07-18 22:07:22.551 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message longPoll 2024-07-18 22:07:22.551 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING longPoll 2024-07-18 22:07:22.551 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING longPoll 2024-07-18 22:07:22.551 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS longPoll message {} from Polyglot 2024-07-18 22:07:22.551 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS longPoll message {} from Polyglot 2024-07-18 22:07:22.552 Thread-617 (poll) udi_interface DEBUG unifi_poly:heartbeat: heartbeat: hb=1 2024-07-18 22:07:22.552 Thread-617 (poll) udi_interface DEBUG unifi_poly:heartbeat: heartbeat: hb=1 2024-07-18 22:07:22.552 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'command': [{'address': 'controller', 'cmd': 'DOF'}]} 2024-07-18 22:07:22.552 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'command': [{'address': 'controller', 'cmd': 'DOF'}]} 2024-07-18 22:07:22.579 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2024-07-18 22:07:22.579 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2024-07-18 22:07:22.579 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2024-07-18 22:07:22.579 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2024-07-18 22:07:22.579 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': 'controller', 'success': True} from Polyglot 2024-07-18 22:07:22.579 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': 'controller', 'success': True} from Polyglot 2024-07-18 22:07:23.326 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2024-07-18 22:07:23.326 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2024-07-18 22:07:23.326 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2024-07-18 22:07:23.326 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2024-07-18 22:07:23.326 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2024-07-18 22:07:23.326 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2024-07-18 22:07:23.327 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: controller:UnifiCtrl No change in ST's value 2024-07-18 22:07:23.327 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: controller:UnifiCtrl No change in ST's value 2024-07-18 22:07:23.331 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 08e68991dc26:08e68991dc26 Reporting set GV1 to 0 to Polyglot 2024-07-18 22:07:23.331 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 08e68991dc26:08e68991dc26 Reporting set GV1 to 0 to Polyglot 2024-07-18 22:07:23.331 Thread-618 (poll) udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-07-18 22:07:23.331 Thread-618 (poll) udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-07-18 22:07:23.331 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.331 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.331 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '08e68991dc26', 'driver': 'GV1', 'value': '0', 'uom': 2, 'text': None}]} 2024-07-18 22:07:23.331 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '08e68991dc26', 'driver': 'GV1', 'value': '0', 'uom': 2, 'text': None}]} 2024-07-18 22:07:23.335 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 70b30604389b:70b30604389b Reporting set GV1 to 0 to Polyglot 2024-07-18 22:07:23.335 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 70b30604389b:70b30604389b Reporting set GV1 to 0 to Polyglot 2024-07-18 22:07:23.336 Thread-618 (poll) udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-07-18 22:07:23.336 Thread-618 (poll) udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-07-18 22:07:23.336 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.336 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.340 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 5c3e1b5753e6:5c3e1b5753e6 Reporting set GV1 to 0 to Polyglot 2024-07-18 22:07:23.340 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 5c3e1b5753e6:5c3e1b5753e6 Reporting set GV1 to 0 to Polyglot 2024-07-18 22:07:23.340 Thread-618 (poll) udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-07-18 22:07:23.340 Thread-618 (poll) udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-07-18 22:07:23.340 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.340 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.344 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: c82add87d78d:c82add87d78d No change in GV1's value 2024-07-18 22:07:23.344 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: c82add87d78d:c82add87d78d No change in GV1's value 2024-07-18 22:07:23.344 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '70b30604389b', 'driver': 'GV1', 'value': '0', 'uom': 2, 'text': None}]} 2024-07-18 22:07:23.344 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '70b30604389b', 'driver': 'GV1', 'value': '0', 'uom': 2, 'text': None}]} 2024-07-18 22:07:23.344 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.344 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.344 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '5c3e1b5753e6', 'driver': 'GV1', 'value': '0', 'uom': 2, 'text': None}]} 2024-07-18 22:07:23.344 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '5c3e1b5753e6', 'driver': 'GV1', 'value': '0', 'uom': 2, 'text': None}]} 2024-07-18 22:07:23.349 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 0298647559fe:0298647559fe No change in GV1's value 2024-07-18 22:07:23.349 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 0298647559fe:0298647559fe No change in GV1's value 2024-07-18 22:07:23.349 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.349 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.353 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 66ad0b5f3510:66ad0b5f3510 No change in GV1's value 2024-07-18 22:07:23.353 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: 66ad0b5f3510:66ad0b5f3510 No change in GV1's value 2024-07-18 22:07:23.353 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.353 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.357 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: daf3559f989e:daf3559f989e No change in GV1's value 2024-07-18 22:07:23.357 Thread-618 (poll) udi_interface.node DEBUG node:setDriver: daf3559f989e:daf3559f989e No change in GV1's value 2024-07-18 22:07:23.357 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.357 Thread-618 (poll) udi_interface INFO unifi_poly:update: update: 0 2024-07-18 22:07:23.361 MQTT udi_interface.interface INFO interface:_message: Successfully set 08e68991dc26 :: GV1 to 0 UOM 2 2024-07-18 22:07:23.361 MQTT udi_interface.interface INFO interface:_message: Successfully set 08e68991dc26 :: GV1 to 0 UOM 2 2024-07-18 22:07:23.450 MQTT udi_interface.interface INFO interface:_message: Successfully set 70b30604389b :: GV1 to 0 UOM 2 2024-07-18 22:07:23.450 MQTT udi_interface.interface INFO interface:_message: Successfully set 70b30604389b :: GV1 to 0 UOM 2 2024-07-18 22:07:23.490 MQTT udi_interface.interface INFO interface:_message: Successfully set 5c3e1b5753e6 :: GV1 to 0 UOM 2 2024-07-18 22:07:23.490 MQTT udi_interface.interface INFO interface:_message: Successfully set 5c3e1b5753e6 :: GV1 to 0 UOM 2

I'm going to try a local access only user but apparently my cloudkey 1's version of network server doesnt support local users so I have to fix that first.

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. Ideas?

I’m logging into my UniFi at the local ip but seems to still check the MFA I setup on the web site.

In preparation for ubiquity starting to require multi factor authorization on 7/22 I enabled it. Unfortunately when I restarted my EISY, the Unifipresence plugin could no longer log in to my Unifi controller. I understand that this plugin no longer has support but I was hoping there might be some workaround to feed an MFA token in maybe via a configuration variable? Any thoughts? This was the best way I could find to tell EISY when I was home or not. Thanks

Steve, nothing has changed from the version you had running so I’m not sure why it wouldn’t install. I haven’t had time to work on it since v 1.1.04. Was your old version in the non production store too?

Just had another trisensor battery die so I got to try all your suggestions. No luck. The battery level reported as 85 % but stopped responding at 8am this morning. The battery tested at only 1 volt so much lower than 85%. The trisensor had completely reset itself so none of the suggestions worked. had to re-add it with a brand new node number and find dozens of bad references in the programs, ugh.

Got a Tuya Zigbee water sensor, It paired and added a node. The interview found a number of parameters but so far the parameters are blank and even though I simulate water, the state does not show up in the admin console. I have restarted the admin console. Tue, Nov 14, 2023 at 10:06 PM.pdf

purchased a Tuya smart 1ch Zigbee 3.0 switch module from Aliexpress. Only $8.70 works great.

looks like chamberlain has shut off the myQ API https://www.theverge.com/23949612/chamberlain-myq-smart-garage-door-controller-homebridge-integrations

I should know the answer to this having used Z-wave for 10+ years. I have several Aeotec trisensors that do not accurately display their battery % so they regularly go dead before I realize the low battery. This often means they often lose their stored information and have to be re-added to the z-wave network. Then I have to try to find all the programs that referenced that node and update them to the new node number. Isn't there some way to re-add them at the old address, it would save a lot of headaches?

Solved the problem by restarting the unifpresence node server

I’m running 7.2.95. Only update that shows available is 7.2.97

I’ve been using unifipresence for some time now but it seems the behavior has changed. My iPhone shows as on the network even hours after I have left the house. I think the problem is in UniFi not unifipresence. Has something changed? Is there a setting somewhere I need to change so it shows me off the network shortly after I leave the house?

Looks like the -Xmx512m did it. I had that set so I didn’t think to check it again. Maybe some update deleted it. thanks!

Start.jnlp was just loaded from UDI. Cache fully deleted. UI is also 5.7.0

I just updated all the packages yesterday, rebooted several times and still have the problem from before the reboots.

Yes and yes downloaded from udi wiki