MFBra

Just to inform I've found a solution... Removed and reinstalled everything on my RPi and at this time, don't ask me why... the option "SSL" in the ISY node server configuration was unchecked again, but now it was somehow "respected".... Did it several times before in the previous install. Thank you all for the great help ! Wish you all a Great 2023!

Hi, Thanks @Geddy Had a great support from Michael, but unfortunately it's related to TLS and no luck so far. Brief description about the environment * ISY (5.3.4) - DHCP Enabled - Portal Working / On the ISY dashboard / networking config : TLS set to V1.2 both on server and client (haven't changed) - option to Verify Unchecked * Raspberry PI v4b : - PolyGlot V2 Installed - MQTT Node Installed After setup, I can see the node server on ISY, I create all the nodes and update its status coming from MQTT/Polyglot. But if I try to send ON/OFF from ISY or even click on Re-Discover or Query (inside the node controller) I receive those messages posted in the begginig. I've shared all the logs with @xKing and today with Michael. It's confirmed ISY can receive updates (as I can see) and with the ISY errors that is related with TLS. Now I'm digging the web to find a solution.. trying sites like this to source information : https://sites.google.com/site/cartwrightraspberrypiprojects/home/steps/disable-unsecure-tls-and-ssl?pli=1 I'm just don't believe a simple environment ("vanila Raspberry PI") can create so much difficulties. Hopping someone already solved this in the past and may have clue.

Thanks.. 1) Firmware 5.3.0 but same behavior on 5.3.4 2) UI and firmware match on both cases, and now double-checked on 5.3.4 3) It's a node server to control lamp switches. So ON/OFF is just to turn them on/off... 4) Trying to do it on the java console, ISY is connected to Node Server, the status of each item on node server get updated to ISY (physically turning them on, gets updated to isy, but I cannot send any command from isy to them, so no programing or scenes are possible 5) Yes MAC OS, but I'm a long term user of it, never created any problem for me with ISY over more than ~10 years 6) Yes, from Brazil Already looked into the errors but found no clue in how to fix it. Tried with @xKing because it's involving a node server wrote from him, but after sharing some info, the issue was narrowed down to a point where ISY receives updates from the node, but cannot "start or send" communication/commands. I've really digged into several pages here, could not find some clear answer to it... I don't recall having to open a ticket so far, but I'll do it. THANKs !!!!

A new error I got today.

I've been struggling to solve this issue and thanks to xKing (really thanks), we've narrowed down the issue a point that without ISY knowledge I cannot move forward. So thanks for the valuable help from this community. It's a node server issue, where the ISY receives all node information, but when I try to issue commands (ON/OF) or query from ISY, I get this error. And here the error log. I filtered out the repeated lines Thank you in advance! Qui 2022/12/29 13:39:59 System -170001 [Network] Established Qui 2022/12/29 13:40:00 System -5006 uuid:99 Qui 2022/12/29 13:40:00 System -60001 a.st1.ntp.br Qui 2022/12/29 13:41:09 System -170001 [TCP-Conn] -256/-140002, ISY ... Qui 2022/12/29 13:41:17 System -50010 smtp.gmail.com Qui 2022/12/29 13:42:21 System -170001 [TCP-Conn] -256/-140002, ISY ... Qui 2022/12/29 13:51:03 System -50010 smtp.gmail.com Qui 2022/12/29 16:21:46 System -170001 [TCP-Conn] -256/-140002, ISY .. Qui 2022/12/29 16:30:53 System -170001 [UDSockets] RSub:21 error:6 <= Probably here is the issue ..... Qui 2022/12/29 16:31:16 System -5012 26 Qui 2022/12/29 16:33:42 System -5012 28 Qui 2022/12/29 16:33:42 System -5012 29 Qui 2022/12/29 16:38:36 System -170001 [UDSockets] RSub:28 error:6 <= Probably here is the issue Qui 2022/12/29 16:38:36 System -170001 [UDSockets] RSub:29 error:6 <= Probably here is the issue ...... Qui 2022/12/29 16:39:00 System -5012 30 Qui 2022/12/29 16:39:00 System -5012 31 Qui 2022/12/29 16:41:29 System -170001 [UDSockets] RSub:19 error:6 <= Probably here is the issue Qui 2022/12/29 16:41:29 System -170001 [UDSockets] RSub:25 error:6 <= Probably here is the issue ..... Qui 2022/12/29 16:41:49 System -5012 32 Qui 2022/12/29 16:41:49 System -5012 33 Qui 2022/12/29 16:44:23 System -170001 [UDSockets] RSub:24 error:6 <= Probably here is the issue Qui 2022/12/29 16:44:23 System -170001 [UDSockets] RSub:32 error:6 <= Probably here is the issue ..... Qui 2022/12/29 16:44:38 System -5012 34 Qui 2022/12/29 16:44:38 System -5012 35 Qui 2022/12/29 16:54:53 System -170001 [UDSockets] RSub:24 error:6 <= Probably here is the issue Qui 2022/12/29 16:54:53 System -170001 [UDSockets] RSub:30 error:6 <= Probably here is the issue Qui 2022/12/29 16:54:57 System -5012 36 Qui 2022/12/29 16:54:57 System -5012 37 Qui 2022/12/29 16:58:42 System -170001 [TCP-Conn] -256/-140002, ISY .... Qui 2022/12/29 17:01:21 System -170001 [UDSockets] RSub:24 error:6 Qui 2022/12/29 17:01:21 System -170001 [UDSockets] RSub:28 error:6 .... Qui 2022/12/29 17:01:37 System -5012 38 Qui 2022/12/29 17:01:37 System -5012 39 Qui 2022/12/29 17:06:24 System -170001 [UDSockets] RSub:21 error:6 Qui 2022/12/29 17:06:24 System -170001 [UDSockets] RSub:32 error:6 Qui 2022/12/29 17:06:29 System -5012 40 Qui 2022/12/29 17:06:29 System -5012 41 Qui 2022/12/29 17:09:13 System -170001 [UDSockets] RSub:25 error:6 Qui 2022/12/29 17:09:13 System -170001 [UDSockets] RSub:32 error:6 ..... Qui 2022/12/29 17:09:23 System -5012 42 Qui 2022/12/29 17:09:23 System -5012 43 Qui 2022/12/29 17:16:47 System -170001 [TCP-Conn] -256/-140002, ISY

I’ve fixed It by disabling the auto-open option here. https://9to5mac.com/2019/06/25/mac-automatically-opening-downloads/

Installed on my Pi2 and everything went ok, but I'm struggling to get my 2 Insteon Dual On/Off Outlet (2663-222), its a dual outlet but homebridge only show the first outlet (of each of them) in the assessories and they do not show up in HomeKit neither. In the home bridge log it seems to be ok for both of them. (Software versions are bellow) homebridge.log shows [7/24/2020, 6:12:48 PM] [isy-nodejs] Porta Retrato (34 68 99 1): RelayLampSwitch_ADV [7/24/2020, 6:12:48 PM] [isy-nodejs] Porta Retrato (34 68 99 1): Property Status (ST) initialized to: 100 (On) [7/24/2020, 6:12:48 PM] [isy-nodejs] Sending request: http://ISY-IP/rest/nodes/34 68 99 1/notes/ Calling: http://ISY-IP/rest/nodes/34 68 99 1/notes/ [7/24/2020, 6:12:48 PM] [isy-nodejs] Porta Retrato (34 68 99 1): The friendly name updated to: Porta Retrato [7/24/2020, 6:12:48 PM] [isy-nodejs] Tv Sala (34 68 99 2): RelayLampSwitch_ADV [7/24/2020, 6:12:48 PM] [isy-nodejs] Tv Sala (34 68 99 2): Property Status (ST) initialized to: 100 (On) [7/24/2020, 6:12:48 PM] [isy-nodejs] Sending request: http://ISY-IP/rest/nodes/34 68 99 2/notes/ Calling: http://ISY-IP/rest/nodes/34 68 99 2/notes/ [7/24/2020, 6:12:48 PM] [isy-nodejs] Tv Sala (34 68 99 2): The friendly name updated to: Tv Sala [7/24/2020, 6:12:54 PM] [isy-nodejs] Porta Retrato (34 68 99 1): Update event triggered, property Status (ST) is unchanged. [7/24/2020, 6:12:54 PM] [isy-nodejs] Tv Sala (34 68 99 2): Update event triggered, property Status (ST) is unchanged. [7/24/2020, 6:12:47 PM] [isy-nodejs] Tv Rodrigo (34 6A 15 1): RelayLampSwitch_ADV [7/24/2020, 6:12:47 PM] [isy-nodejs] Tv Rodrigo (34 6A 15 1): Property Status (ST) initialized to: 0 (Off) [7/24/2020, 6:12:47 PM] [isy-nodejs] Sending request: http://ISY-IP/rest/nodes/34 6A 15 1/notes/ Calling: http://ISY-IP/rest/nodes/34 6A 15 1/notes/ [7/24/2020, 6:12:47 PM] [isy-nodejs] Tv Rodrigo (34 6A 15 1): The friendly name updated to: Tv Rodrigo [7/24/2020, 6:12:47 PM] [isy-nodejs] Camera_Rodrigo (34 6A 15 2): RelayLampSwitch_ADV [7/24/2020, 6:12:47 PM] [isy-nodejs] Camera_Rodrigo (34 6A 15 2): Property Status (ST) initialized to: 100 (On) [7/24/2020, 6:12:47 PM] [isy-nodejs] Sending request: http://ISY-IP/rest/nodes/34 6A 15 2/notes/ Calling: http://ISY-IP/rest/nodes/34 6A 15 2/notes/ [7/24/2020, 6:12:48 PM] [isy-nodejs] Camera_Rodrigo (34 6A 15 2): The friendly name updated to: Camera_ Rodrigo [7/24/2020, 6:12:54 PM] [isy-nodejs] Tv Rodrigo (34 6A 15 1): Update event triggered, property Status (ST) is unchanged. [7/24/2020, 6:12:54 PM] [isy-nodejs] Camera_Rodrigo (34 6A 15 2): Update event triggered, property Status (ST) is unchanged. Thanks if the experts here have already dealt with this issue in the past and can share the learnings... MF homebridge-config-ui-x v4.24.0 / homebridge-isy v0.5.0-rc22 / Raspbian GNU/Linux Buster (10) / node.js v10.21.0

Just to confirm i got it working yesterday with Brazilian Portuguese, also helped a friend here and both are 100% functional without issues ! Thanks !!!

Sorry if you consider it off topic, but i had 2 Dimmers failing exactly in the same way. Lost comm with PLM and when i try to switch on the light it “ramp up” but stops, turn off light and ramp up again indefinitely... The first failed probably 2 months ago, and the second just did. Everything else is working reliably. I’m wondering if it can be some sort of capacitor failure... Unfortunately I’m not experienced to replace them but i can find someone here in Brazil to do it. Extras : Both were operating with incandescent load, one of them with 2x50w lamps and the other with 4x50w, one of them with ~10years and the other ~2years. None of them with constant usage, I’d say around 1-2hs/day maximum. Thanks!

For the technical aspects probably wont be able to help, but for translation if you want help you can DM me. Really glad to help.

Thanks Michael, good to know. Can you inform when you get the certification ? Is there any translation issue or requirements you may need help to accomplish?

Hi, I'm preparing to setup my ISY within Amazon Alexa but I could not find ISY Skills. My Amazon account was setup in Brazil, is it necessary to release the skill for each country ? Do you have plans for that ? Can I help in any way to speed it up ? Thanks in advance.

Hi Techman I'm on 4.6.2 Firmware and UI. No ZWAVE. The other thread solved ! THANKS !!!! Enviado do meu iPhone usando Tapatalk

Yes, backing up to a local hard drive as I did several other times. Rebooted both, no luck at all same error. Thanks Enviado do meu iPad usando Tapatalk

My backup started to present an error. It runs all over the files and stops at around 64% and presents an error "Could not retrieve File /CONF/DISCLAIM.UDI" and therefore another Error "Could not Create the ZIP File". Besides that everything seems to be ok Running on version 4.6.2. I have several other backup done on the same MAC OS machine. Thanks in advance.

Michael, Based on the ISY capability to detect a faulty PLM I thought it would be the cheaper, easier and maybe the best way to "assume" power failure, with the GREAT side effect of having the ability to notify if there is a total failure with the PLM... At the end, just food for thought... Thanks Enviado do meu iPad usando Tapatalk

Never considered this route because when I lost my PLM the ISY entered in a "kind of" failure state (sorry I don't remember how do you call it). How fast is the "not responding" detection? Enviado do meu iPad usando Tapatalk

It's on a UPS and the "messages" would be over pushover or similar and dispatch some scripts on other hardwares. Enviado do meu iPad usando Tapatalk

Sorry to reopen this thread... Is it possible to have ISY detecting and reporting an event "PLM" down ? It could work as a simple power failure detection for the ones who relies on UPS only for the ISY. I know a "side effect" could be detect and notify a possible PLM failure... of course with a disclosure explaining that further analysis would be required. It would help me to have proper notification prior to loose home monitoring and also dispatch "shutdown" commands to other equipment that lacks this detection, and finally run query all when power returns. Enviado do meu iPad usando Tapatalk

Being a single purpose account I'd agree. Just additional info regarding this, as the SMS can be very slow here sometimes I decided to get google authenticator, it keeps generating the 6 digits validation password, so you'll need a second device, but it's just copy the digits, without having to wait for sms... MFBra

Good point, as you know security is always something difficult to assure. By having the 2 factor you increase the difficulty to access your account, having app password create some risk, but without any probability calculation I just "believe" that with 2 factor for general access and limited number of app password is more than do not have it. Maybe we can ask UDI to be complaint to googles 2factor in the future? MF_Bra

Yes, it became your ISY gmail password, you can have several specific passwords, one per App you want. Thanks Mwareman for providing the directions. MF_Bra

I did for security reasons and you may create app specific password for each client you want. Created one for ISY and works flawlessly. MF_Bra

Take a look at shipito.com they have several locations, offer shipment consolidation with multiple service tiers, an initial free account that you pay per usage. They did well shipping to Brazil and at a reasonable cost. Extras : They take pictures of all packages upon arrival so the user can see and decide what to do. And offer other options and you can simulate the freight prior to sign up. MF_Bra

I believe most users have been "working around" to achieve the desired behavior or "almost desired " but if we could adjust some options "on the fly" we could accomplish. Thanks MFBra