tmorse305

Hi @Javi, Thought it was fixed but there is one thing not quite right. The High Temp display status that I mentioned previously will not update automatically from a fresh start of UD Mobile. It's blank but if I tap on it the device details come up and show that they are populated, then when I return to the favorite the value is now populated. I have the 3 update status turned on. It is only this specific one that is not working. All other favorites update correctly after a restart of UD Mobile. Something about this device must be different. It's no biggie but I thought you would like to know. Thank you for the great support!

Fixed! Thank you very much!

I'm local to one of the eisy's so I configured it for "Only use local connection" . Same result, no values displayed.

It appears to just be node servers affected. I just checked on a 2nd eisy I have and it has the same problem

@Javi, No there is no data for the device, see screen shot. There is data when I look at it from the AC. Synchronize does not fix it.

Hi @Javi, I just tried 1.1.60 and the error has been corrected. However the Favorite does not show the selected value. See screen shots. Thank you.

Hi @Javi, I've run into a problem with my favorites, specifically Display Status. Here is an example but it happens for all types of favorites. I create a favorite for a variable. I use the default value for the Display Status and it's all good, see screen shot. But if I try to create it with a different value for Display status or go back and try to change the Display status I get the the word REQUIRED! in the display status and then I'm stuck. It will not accept any value at this point. Suggestions? Thank you.

Hi @Panda88, I'm stuck in a loop trying to authenticate. I start the NS and the log says invalid pin. A few seconds later Blink texts me a new code. I enter that into the NS configuration and save, hit restart but it fails again and Blink sends a new code. I also tried not restarting but the result is the same. The NS periodically tries again and I get a new code from Blink each time. Any suggestions? Thanks 2024-04-21 15:13:31,915 Thread-7 udi_interface INFO BlinkSystem:auth: Auth key required 2024-04-21 15:13:32,384 Thread-7 blinkpy.auth ERROR auth:send_auth_key: Invalid PIN 2024-04-21 15:13:32,384 Thread-7 blinkpy.auth ERROR auth:send_auth_key: Invalid PIN

Thanks Bob, I'll adjust the poll times if the problem continues. For my purposes, I only need an update once a day.

@bpwwer, thanks for your reply. Does the query occur on the short or long pole? I am not explicitly doing a query with a program. I don't see that option. The only choice is 'remove notices'

Hi @bpwwer, the forecast does not update reliably everyday. If I restart the NS, it does update although there is an error reported: 2024-02-01 07:45:54,472 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2024-02-01 07:45:54,472 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 0021b902658a_6.cert key: 0021b902658a_6.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2024-02-01 07:45:54,472 MainThread udi_interface.interface INFO interface:addNode: Adding node Climacell Weather(controller) [None] 2024-02-01 07:45:54,472 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status. 2024-02-01 07:45:54,522 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2024-02-01 07:45:54,522 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:8a_6 - MID: 2 Result: 0 2024-02-01 07:45:54,565 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2024-02-01 07:45:54,597 Thread-2 udi_interface ERROR climacell:parameterHandler: ***** Entered parameter handler.... Could it be related to that? Thank you.

Hi @Jimbo.Automates, I'm trying to figure out how to use System custom messages for Telegram. There doesn't seem to be a way to specify which custom message you want to send. If I click the send button on the node, it sends a null message to my phone. Same issue if you try to create a program. Thank you

@bpwwer, Thank you for the quick fix!

Hi Bob, That works:

Update: I was able to send the offending url request and got this response: "The plan is restricted and cannot perform this action. Adjust action and try again: Querying '5m' timestep is not allowed in the current plan" It looks like you can't use this NS with the Climacell free plan.

I just installed Climacell and it seemed to install correctly. When I check in the AC I can see the forecast data for tomorrow but there are no current conditions. There is an error in the log: 2023-12-31 20:03:42,480 Thread-16 udi_interface DEBUG query:query_conditions: request = https://api.tomorrow.io/v4/timelines?location=28.54,81.77&timesteps=5m&units=imperial&apikey=BcPxt5D2md********Y96yTtKBz9W3mF&fields=precipitationIntensity,precipitationType,temperature,temperatureApparent,dewPoint,windSpeed,windGust,pressureSeaLevel,visibility,humidity,windDirection,cloudCover,cloudCeiling,cloudBase,solarGHI,weatherCode,epaIndex 2023-12-31 20:03:42,618 Thread-16 udi_interface ERROR query:query_conditions: Current observation update failure @bpwwer, Any suggestions? Configuration attached. Thank you.

That did the trick, Thanks @tazman!

I added it but it's still looking for the boto3 module. Hopefully @bpwwer can help.

No I didn't. Do I need it for this NS? I don't recall needing to install it on my other eisy.

Hi @bpwwer, I tried to install the NS on a new eisy but I'm get this error: 2023-12-30 19:51:30,822 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b902658a_5/vue.py", line 10, in <module> import pyemvue File "/var/polyglot/pg3/ns/0021b902658a_5/pyemvue/__init__.py", line 2, in <module> from pyemvue.pyemvue import PyEmVue File "/var/polyglot/pg3/ns/0021b902658a_5/pyemvue/pyemvue.py", line 8, in <module> import boto3 ModuleNotFoundError: No module named 'boto3' PG3x Version 3.2.17 Status: Connected Frontend Version: 3.2.17 IoX Version: 5.7.1 Thank you

add me to the list, one eisy is connected to the portal, my other eisy is not. Both are connected via eero routers. Tried a reboot but not luck. Went offline at 2:14 AM EST.

I just setup the Rachio NS. I can start up the zones from the AC. I noticed a couple of issues in the log I was looking to understand. See log file, when I start a zone there are multiple entries that the zone has started yet there is only one entry in the log file. There is also a recurring error in the log file. Second question, how do I stop a zone early? I tried setting the zone time to 0.0 minutes but that doesn't seem to do anything. Thank you. debug.log

@Geddy and @bmercier, thank you for responding. Well everything is working fine now. I'm glad I took that screen shot or you would have thought I was nuts. I have tried all combinations of preferred ISY and ISYs for Alexa but it is rock solid. I'll let you know if it returns but it's all good right now.

Hi @bmercier, I setup a second eisy with its own portal account. See other post from yesterday where I initially had a problem finding it but then the problem resolved itself. I don't know if this is related. I set up 2 Alexa definitions last night and they worked fine. Today when I went into the portal they were gone. Curiously they still work. I tried to add another one and this was the result, see screen shot. Something seems to be messed up. Thanks for your help.

I recently brought a second eisy online. I have a 2nd portal license for it. I created a webhook but when I send the web hook(via PostMan) I get a reply that says Requested ISY cannot be found. What am I missing? Related question but not exactly a portal issue, I was going to use network resources to communicate between the 2 eisys. That's why I'm trying to get a web hook setup. Is there a better way to do this? Thank you Update: I just tried it again and it is now working. I made no changes just waited a while and tried it again. A mystery for sure.