Kevin

The problem is both Antennas have no color band they are plain black.

I just saw this post and went to check on my Zmatter to make sure the antennas where right. My Z-Matter seems to be working good except the range on my zigbee is not as good as I would like. I have found that the antennas look the same. I don't remember if the antennas where attached when I got it or if I connected. How do I know if they are correct.

Ok Michel I just put in a ticket. Techman thanks so much for your advice

I have the log file in debug and blue tooth is not showing any signs of receiving a sound file. 2024-07-21 16:08:11.130 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2024-07-21 16:08:11.130 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2024-07-21 16:08:11.130 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2024-07-21 16:09:11.133 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll in the audio player I show it being sent out, I think? 2024-07-21 16:32:11.043 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2024-07-21 16:32:11.043 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2024-07-21 16:32:11.043 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2024-07-21 16:32:11.043 Thread-43 (poll) udi_interface INFO audio-player:poll: short poll 2024-07-21 16:32:19.922 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2024-07-21 16:32:19.922 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2024-07-21 16:32:19.923 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': '0', 'cmd': 'PLAY', 'value': '4', 'uom': '25', 'query': {}} from Polyglot 2024-07-21 16:32:19.923 Command udi_interface INFO audio-player:processCommand: Got command: {'address': '0', 'cmd': 'PLAY', 'value': '4', 'uom': '25', 'query': {}} 2024-07-21 16:32:19.923 Command udi_interface INFO audio-player:processCommand: Playing #4:./sounds/chime.mp3 2024-07-21 16:32:19.923 Command udi_interface.node DEBUG node:getDriver: 0:AudioPlayer ST - 0 :: getting dv ST 2024-07-21 16:32:19.924 Thread-44 (audio_player_thread) udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set ST to 1 to Polyglot 2024-07-21 16:32:19.924 Thread-44 (audio_player_thread) udi_interface.node DEBUG node:reportDriver: Updating value to 1 2024-07-21 16:32:19.924 Thread-44 (audio_player_thread) udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV0 to 4 to Polyglot 2024-07-21 16:32:19.924 Thread-44 (audio_player_thread) udi_interface.node DEBUG node:reportDriver: Updating value to 4 2024-07-21 16:32:19.924 Thread-44 (audio_player_thread) udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV3 to 100 to Polyglot 2024-07-21 16:32:19.924 Thread-44 (audio_player_thread) udi_interface.node DEBUG node:reportDriver: Updating value to 100 2024-07-21 16:32:19.930 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'ST', 'value': '1', 'uom': 25, 'text': None}]} 2024-07-21 16:32:19.930 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV0', 'value': '4', 'uom': 25, 'text': None}]} 2024-07-21 16:32:19.930 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV3', 'value': '100', 'uom': 51, 'text': None}]} 2024-07-21 16:32:19.963 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: ST to 1 UOM 25 2024-07-21 16:32:20.048 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV0 to 4 UOM 25 2024-07-21 16:32:20.091 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV3 to 100 UOM 51 2024-07-21 16:32:20.446 Dummy-45 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set ST to 0 to Polyglot 2024-07-21 16:32:20.447 Dummy-45 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-07-21 16:32:20.447 Dummy-45 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV0 to 0 to Polyglot 2024-07-21 16:32:20.447 Dummy-45 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2024-07-21 16:32:20.448 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'ST', 'value': '0', 'uom': 25, 'text': None}]} 2024-07-21 16:32:20.448 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV0', 'value': '0', 'uom': 25, 'text': None}]} 2024-07-21 16:32:20.481 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: ST to 0 UOM 25 2024-07-21 16:32:20.572 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV0 to 0 UOM 25

OK I unpaired my speakers then restarted audio player the restarted bluetooth and repaired the speakers still the speakers did not acknowledge the pairing. then rebooted eisy and went to audio player in the admin console set it to blue tooth and nothing still.

I don't know if this is what you are looking at. Arduino_Mqtt in the I put it in the NON-PRODUCTION of the plugin store This BETA version and is used to add node service to an Adruino project. works with ISYarduin.h and can be added to your lib dir. It was written for my use in making projects and will have limited support. But if you have any questions please email me at kevin@kevin-graff.com I will be happy to help. Also feel free to change and modify and parts to fit your needs in both programs. The ISYarduino.h file can ether be in your LIB or just in your currient folder https://github.com/n2uns/ISYandrino Please report any problems to me in by email or the Form but I don't follow the form offten. Thanks and good luck.

that did not seem to change anything. I rebooted my eisy and then went to unpaired my speakers then repaired them and tried to send an audio file to the bluetooth and it just locked up the audioplayer and just showed that the file was playing. The stop button would not even stop it. I had to restart my audio player NS to get it to work again Thanks anyways.

I am having a problem with the Bluetooth 1.0.7, but there doesn't seem to be a forum for that NS. I have installed audio player 1.3.5 and if I plug a speaker into the audio out jack it all works well. But with the bluetooth my speakers showup. When I put the speakers in pairing mode and press the pair button it will come back paired. But my speakers stay in pairing and never acknowledge the connection. I have tried this with my bluetooth headphones as well and get the same results

Thanks for getting back to me I did find the problem. I had an old polisy in my portal that I used to test and write my NS but since the I have unplugged it and put it away. For some reason the Ring keep coming back with that UUID instead of the UUID for my eisy. I deleted the polisy from my portal and rebooted then reinstalled Ring and it works good.

I get both ring door bells to install with 2 nodes for each doorbell Front Door and node Front door (motion) when I try to run the test it comes back with failed 024-07-20 16:37:58.724 Command udi_interface INFO controller:test: Ring API call is successful. 2024-07-20 16:37:58.724 Command udi_interface INFO ringInterface:getPostbackUrl: Store is Production: Using hostname my.isy.io for webhook url 2024-07-20 16:37:58.613 Command udi_interface INFO oauth:getAccessToken: Refresh tokens is still valid, no need to refresh 2024-07-20 16:37:58.724 Command udi_interface INFO controller:test: Ring API call is successful. 2024-07-20 16:37:58.724 Command udi_interface INFO ringInterface:getPostbackUrl: Store is Production: Using hostname my.isy.io for webhook url 2024-07-20 16:37:58.842 Command udi_interface ERROR ringInterface:testWebhook: MQTT connection not online. On my.isy.io, please check Select Tool | PG3 | Remote connection. It has to be active. If you don't see the option, your device does not support it. Make sure you are using an eisy at 5.6.0 or more recent, or a Polisy using PG3x. 2024-07-20 16:37:58.842 Command udi_interface ERROR controller:test: Test Ring API call failed: Error sending event to Portal webhook 2024-07-20 16:37:58.842 Command udi_interface ERROR ringInterface:testWebhook: MQTT connection not online. On my.isy.io, please check Select Tool | PG3 | Remote connection. It has to be active. If you don't see the option, your device does not support it. Make sure you are using an eisy at 5.6.0 or more recent, or a Polisy using PG3x. 2024-07-20 16:37:58.842 Command udi_interface ERROR controller:test: Test Ring API call failed: Error sending event to Portal webhook 2024-07-20 16:37:58.842 Command udi_interface.node DEBUG node:setDriver: controller:Ring Reporting set GV0 to 4 to Polyglot 2024-07-20 16:37:58.843 Command udi_interface.node DEBUG node:reportDriver: Updating value to 4 2024-07-20 16:37:58.853 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'GV0', 'value': '4', 'uom': 25, 'text': None}]} 2024-07-20 16:37:58.842 Command udi_interface.node DEBUG node:setDriver: controller:Ring Reporting set GV0 to 4 to Polyglot 2024-07-20 16:37:58.843 Command udi_interface.node DEBUG node:reportDriver: Updating value to 4 2024-07-20 16:37:58.853 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'GV0', 'value': '4', 'uom': 25, 'text': None}]} 2024-07-20 16:37:58.884 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV0 to 4 UOM 25 2024-07-20 16:37:58.884 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV0 to 4 UOM 25 I have checked my portal and it say's that remote connection is true UUID: 00:21:b9:02:65:86 Alias: eisy Remote connection feature available: Yes Remote connection configured: Yes Remote connection active: Yes Please if anyone can tell me what I am doing wrong

I don't really know a lot about this subject but pfSense is an open source firewall and is most likely to be filtering out the broadcast. most gateways don't allow 255.255.255.255 broadcast for security reasons. i would start looking there.

SONOFF SNZB-03 ZigBee Motion Sensor https://www.amazon.com/dp/B08BFFJ69V?ref=ppx_yo2ov_dt_b_product_details&th=1

Haozee MmWave Human Presence Sensor,Zigbee Millimeter Wave Radar Detection Sensor,Requires TUYA HUB,Support Zigbee2mqq Home Assistant https://www.amazon.com/dp/B0BZCVHYR8?ref=ppx_yo2ov_dt_b_product_details&th=1

@gweempose I have tried everything I can think of and I still no longer get any status updates but the inside buttons. I have given up

My FE599 would receive User number any time the door was unlocked from the out side. I moved over to eisy and Zmatter now I also no longer receive any kind of updates from the locks except from the inside lock and unlock buttons. I have not tried to go back to my Z-wave Z700 yet. Z-matter seams to have lost something.

Ok that is the problem. You are using Tsmota and my node server will not work with it as it is. You should be using MQTT by xking in the production store it was written for that. I created my own Arduino lib for my NS, I didn't care for the Tsmota for the hardware I was building. I don't use SonOFF I use ESP surfs mount modules on my boards that I build.

the mqtt_***** are all the ISY Mqtt broker settings. mqtt_topic is the name of you ESP and needs to match. I don't know about your ESP settings If you look at my https://github.com/n2uns/ISYandrino you will see the diffrent progroms I worte for some of my boards. It uses the ESPMQTT lib and some addtions I have int the .h file. The main one I am useing is the shed program but the https://github.com/n2uns/ISYandrino/tree/main/sonoff4chpror3 Uses an ESP8266

I was told it dose not matter. To be hornist with you I only understand about half of the program I wrote. LOL I am a hardware person and most of it was done with copy and past. I used a program called MQTT_Explorer that is a free download if you have it connect to your ISY MQTT you can watch the transactions between you ESP and the NS. The node server should send a "1" to the topic of Discover and the ESP should responds with a list of your Analog in and out along with the names you gave the also the Digtal in and out, After that The esp should send a Status topic every time an in put or output changes.

The first discovery is done on the NS start up. But you have to have the ESP Board up and running before you start the NS. it makes a node in the admin by default named Arduino_Mqtt in that node is the rediscover button.

if it is responding to the discovery . but after the nodserver runs and dose the discover the admin has to be restarted. for the to repropagate . also it only makes one NS for each ESP board. any time you make changes to your ESP board ie add inputs or out puts you need to do a rediscover and restart the admin console.

Hi, In your config file what is the ip address and port your are using? For me it is mqtt_server 192.168.18.185 and mqtt_port 1884 these are the ip and port for the eisy and polisy built in mqtt broker.

I have created a NS and an include file for interfacing Arduino ide ESP chips. I even have a cupule of examples if that helps you out. The node server is Arduino_MQTT and is on the Bata store also the source is at my github https://github.com/n2uns/Audrino_Mqtt https://github.com/n2uns/ISYandrino

Added a simple Arduino program for the SONOFF 4CH Pro see read me for flashing https://github.com/n2uns/ISYandrino

Tested on Wemos D1 R3 gives warnings but compiles and works

I found that when you install the node server you need an Arduino running with the LIB connected to the broker or the node server will time out waiting for the discovery.