garybixler

Just installed the Tesla-EV yesterday and all went well. The only things that I am noticing are that my Trunk and Frunk stats always show open. The car has been driven and the trunk has been opened and closed several times but the state always shows open. If I do the Actuate Trunk I get the following error. I can honk the horn and toggle HomeLink. Car is awake as I am watching the app for any changes. Thanks Gary 2022-06-05 17:39:03,421 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2022-06-05 17:39:03,423 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2022-06-05 17:39:03,423 Command udi_interface INFO TeslaEVStatusNode:evOpenTrunk: evOpenTrunk called 2022-06-05 17:39:03,424 Command udi_interface DEBUG TeslaCloudEVapi:teslaEV_TrunkFrunk: teslaEV_Doors for 1492932395099962 2022-06-05 17:39:03,426 Command udi_interface ERROR TeslaCloudEVapi:teslaEV_TrunkFrunk: Exception teslaEV_FlashLights for vehicle id 1492932395099962: local variable 'cmd' referenced before assignment 2022-06-05 17:39:03,426 Command udi_interface ERROR TeslaCloudEVapi:teslaEV_TrunkFrunk: Trying to reconnect

@dbroere The additional two RJ45 ports can be configured as switchports. Network Switch Mode in the ISY system configuration.

Just a question about 'Upgrade Packages'. If it is not grayed out does that mean there are packages that can be upgraded? If packages are up to date will it then be grayed out? Thanks Gary

I also have that text appearing at the bottom of the screen. Never paid any attention to it.

@hart2hart Try the discover button on the Bond Node Server.

@Goose66 I updated and all works perfectly now. Thanks so much.

I needed to clear Java and reload start.jnlp.

@Goose66 Thanks, but for whatever reason I don't have the discover button. I had tried reinstalling the NS but no discover button. Everything is at the latest versions. Also rebooted the Polisy.

From this post time where I did the send to when the email arrived was about 30 minutes.

Just checked my email and they did show up. Just took a long time.

That's odd. When I did this before it was just sent to my email. But I do see now that they are requesting an email for verification.

I installed using the device codes that can be downloaded from Global Cache. Just copied and pasted into the node server. Commands that I wouldn't use I just didn't copy paste. Was very easy and has been performing great. Thanks Gary

@Goose66 Hi, I just installed Bond Bridge under PG2 and the Bond Bridge node came right up. Then I did a power reset for discovering the addition devices and they all came up. Something about Bond running on PG3. Thanks Gary

I'm sorry but I don't see any discover button on the PG3 Dashboard just all the node servers. Could you be more specific? However I am adding static values so I didn't think a discovery would be necessary just a restart. But the bridge pro node doesn't show up in the Node Server. Is there a port requirement? I am using the POE Ethernet port. Thanks Gary

@Goose66 Hi, I just received a Bond Bridge Pro and can't seem to be able to get it loaded into the Bond NS. No nodes show up on the NS. Bond Pro 2.19.12 Bond NS 3.0.9 PG3 3.0.56 My NS config: also added Log. Thanks Gary EDIT The other thing I noticed was that there is no discover button on the NS that I could find. I tried restart instead after power cycling the Bond Pro but 0 nodes are loaded. New Text Document.txt

Any grid based solar panels with Enphase micro inverters?

The specs just say it can cover 2500 sq. ft. and the pro 3500 sq.ft. Just testing with the remote I am able to control a somfy blind 45+ ft. away between floors.

The bond bridge looks very promising. I think I will go that way. Probably with the pro version because of the direct Ethernet POE connection.

Hi Hi, Just wondering if there would be any interest in creating a Somfy node server on PG3. I think the info can be found here: somfysystems.com/en-us/somfy-synergy-api Thanks Gary

In the custom configuration parameters it doesn't look like the host parameter is pointing to the IP address of the ELK M1 EXP. Example: 172.16.1.xx:2101

When I went back to PG3 5.0.46 from PG3 5.0.50 I had to reinstall the ELK NS for it to work again. All other servers worked fine. Everything worked fine again after upgrading to PG3 5.0.51 from PG3 5.0.46 including ELK. In my case I reinstall the ELK NS. Certainly not the best option.

Having the same problem after 3.0.50. Submitter log for ELK wich is having the same problem.

@JimboAutomates Unfortunately after upgrading to PG3 3.0.5 ELK and Wireless Tag NSs among others come up with errors and won't run. Thanks Gary ELK log attached New Text Document (2).txt

Using a browser and hovering over the dBm value it will show TX power. Don't see it on the app however.

Thanks @JimboAutomates I was able to add back the leak sensor and all works great now. There is one unimportant issue. The Tx power on the Admin Console doesn't match what is shown at the tag web site. The AC value is roughly doubled plus. Thanks again. Gary