tmorse305

In chasing down some communication issues in a new house I discovered a different eisy behavior on i3 vs earlier versions. I have a program that turns off the backlight on an i3 keypad. The program was not always successful so I was troubleshooting using the event viewer. What I found was that only the first time the program is run, the actual command is sent. Subsequent attempts to run the program do not send the command again. See the log excerpt. Wed 01/10/2024 08:03:23 AM : [ Time] 08:03:29 2(0) Wed 01/10/2024 08:03:23 AM : [All ] Writing 2 bytes to devices Wed 01/10/2024 08:03:23 AM : [INST-TX-I2CS] 02 62 60 7A 97 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 01/10/2024 08:03:23 AM : [INST-ACK ] 02 62 60.7A.97 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 01/10/2024 08:03:23 AM : [INST-SRX ] 02 50 60.7A.97 70.8F.46 2F 2F 00 (00) Wed 01/10/2024 08:03:23 AM : [Std-Direct Ack] 60.7A.97-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 01/10/2024 08:03:23 AM : [INST-ERX ] 02 51 60 7A 97 70 8F 46 15 2F 00 00 01 0F FF 00 A2 1D 70 8F 46 FF 1F 03 9D Wed 01/10/2024 08:03:23 AM : [Ext-Direct ] 60.7A.97-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Wed 01/10/2024 08:03:23 AM : [60 7A 97 1 ] Memory : Write dbAddr=0x4001 [09] cmd1=0x20 cmd2=0x09 Wed 01/10/2024 08:03:23 AM : [INST-TX-I2CS] 02 62 60 7A 97 1F 20 09 00 00 00 00 00 00 00 00 00 00 00 00 00 D7 Wed 01/10/2024 08:03:23 AM : [INST-ACK ] 02 62 60.7A.97 1F 20 09 00 00 00 00 00 00 00 00 00 00 00 00 00 D7 06 (09) Wed 01/10/2024 08:03:24 AM : [INST-SRX ] 02 50 60.7A.97 70.8F.46 2F 20 09 (09) Wed 01/10/2024 08:03:24 AM : [Std-Direct Ack] 60.7A.97-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 01/10/2024 08:03:24 AM : [60 7A 97 1 ] Memory : Write dbAddr=0x0264 [7F] cmd1=0x2E cmd2=0x00 Wed 01/10/2024 08:03:24 AM : [INST-TX-I2CS] 02 62 60 7A 97 1F 2E 00 01 07 7F 00 00 00 00 00 00 00 00 00 00 4B Wed 01/10/2024 08:03:24 AM : [INST-ACK ] 02 62 60.7A.97 1F 2E 00 01 07 7F 00 00 00 00 00 00 00 00 00 00 4B 06 (00) Wed 01/10/2024 08:03:25 AM : [INST-SRX ] 02 50 60.7A.97 70.8F.46 2F 2E 00 (00) Wed 01/10/2024 08:03:25 AM : [Std-Direct Ack] 60.7A.97-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 01/10/2024 08:03:25 AM : [INST-SRX ] 02 50 60.7A.97 70.8F.46 23 2E 00 (00) Wed 01/10/2024 08:03:25 AM : [Std-Direct Ack] 60.7A.97-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 <second run of program> Wed 01/10/2024 08:03:40 AM : [All ] Writing 0 bytes to devices I see the same behavior on the i3 paddle as well. If I send a different command set (turn on backlight) that is sent ok and then I can run the above program and it will send the commands one time. I looked at an i2 device and the commands are sent every time. Is it a bug or intentional behavior? 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

Hi @IndyMike, that is interesting. I double checked and it is definitely going to 100%. The i3 devices are the latest versions coming from Insteon.

@IndyMike, thanks for taking the time to run the experiment. I also don't see it every time either so I think your theory about a second delayed communication is a good one. Also the fast on does yield a 100% result not 20%. The device is programmed to go to 20% with an normal on. I was sending the fast on commands from the AC.

I'm setting up an eisy in a new home. I was looking at the event viewer to get an idea how good the communication was by checking hop counts. See attached, I'm trying to understand the final communication in this sequence. The device is a standalone i3 Paddle. It looks like it turns on correctly with hops left=3. Bu then there is an addition communication and the ack from from the switch is hops left=0. What is that 2nd communication for and is hops left=0 in this case a sign of communication troubles? 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