tmorse305

@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.

I had tried a restart a few times this morning but no luck. When I saw your post I tried it again and it's now running.

Mine is not working either. The error that I think is the issue is: 2023-11-19 10:12:10,140 Thread-2 udi_interface ERROR vue:parameterHandler: Discovery failed: 500 Server Error: Internal Server Error for url: https://api.emporiaenergy.com/devices/132567/locationProperties I think something was up with the Emporia api server. I had a similar problem last weekend that resolved itself.

I see a lot of hops left=0 so it might be communication problems. Can you move the 2856D2 close to the PLM and try to restore that one?

What type of devices are they?

On Point#1, I have the exact same problem. Every time I add anything in the portal it is not found after 'discover devices'. It's been this way for as long as I can remember. The fix for me is to unlink/relink the ISY skill, then discover devices. That works every time. Funny I just assumed that happened to everyone. There was a thread about this a long time ago but I doubt I can find it. It's interesting that it works for some people.

BTW, has anyone told you lately how great this NS is? I find new uses for it all the time. My latest was using a plug to monitor my air compressor cycle in conjunction with an eisy program to purge my irrigation system for the winter. Just launch the program and it waits for the compressor to recharge (not a very big compressor) then fires off the next zone. Thanks again!

Thanks Bob, When I went back to check, everything was now working fine. I made no changes. Maybe there was a problem at the Emporia end of things.

Hi @bpwwer, I can't control my emporia plugs from the AC. Log attached, there are a bunch of errors recorded. I tried a reinstall but no improvement. Thanks for your help. VUE_11-11-2023_94729_AM.zip

ecobee has a wireless remote sensor that includes a motion sensor. You can include or exclude the remote sensor from the operation of the main thermostat. You can't exclude the main sensor. I used to have Venstars with remote sensors and lots of programs to control them. Then I switched to ecobee and ended up deleting most of my programs and letting the thermostat take control. The thermostat has impressive capabilities and does a great job mostly on it's own. You should check it out and see if it can work for your situation.