EWhite

I think someone is working on a RATGDO nodeserver...

from what i can tell HA devices use MQTT in a different way from Tasmota. atleast from what i can tell using MQTT sniffer

in the process of creating a node server for this.. why not make it work with ALL HA MQTT messages... im vert surprised we dont have this already. after playing with this and a few other HA compatible devices, the MQTT stuff is the same from all of them, just a slightly different format from tasmota standard MQTT. just a thought....might open up alot of new devices, might not... just tested HA automation on shelly modules...MQTT is all there...just like for the ratgdo...

just saw an article where you can get a tuya m100 presence sensor and change out a chip in it and load Tasmota on it. https://templates.blakadder.com/ZY-M100.html for the template and how-to... It then spits out home assistant MQTT info. would be nice to have a HA nodeserver to handle it.. hehe

one per...

im thinking you would have to do that via a program....would be fairly easy Since the ratgdo can control lights and etc..add a beeper of some kind if you want.. I dont have any young kids around anymore...so i aint too worried about that.

i ordered a few... Just FYI.. you can install the firmware on any wemos d1 mini....so you could play with it, etc. I did it.. of course it wont work or anything without the daughter board, but it gives you all the MQTT stuff for maybe building a node server.

the more i see posted on this ratgdo the more im liking it...love the idea of getting away from the "cloud" and having local control. What is the time frame on the backorder for these?

i just installed from non production store....i dunno why it isnt working.. above my paygrade

im using MQTT for a few things now..just didnt on this item since there was a node server for it.. that i thought worked.. it does work.. just doesnt report right..so i cant do anything'with it programmatically I will have to pull it out of the wall and flash tasmota on it, was just trying to not have to do that. Thanks!

yea.. i guess thats what im gonna have to do.. i have to pull it out of wall to do it tho. Thanks

no activity on this for over a year...i guess its dead? shame... is there any way i can change it, or can i pay someone to? Thanks

thanks much guys.. i will hollar at him on github and go from there.

my other post on this got closed with no explanation...so here it goes again.. Just tried the shelly1 version 2 with latest firmware. The webserver does not parse a status xml anymore.....or am i missing something? the node server is trying to go to http://shelly_ip/status this does not exist....so node server cannot report status of switch. it DOES however still control the switch. 2023-07-18 21:46:07,513 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-07-18 21:46:07,515 Thread-691 udi_interface DEBUG Shelly1_Node:updateStatuses: Node: updateStatuses() called for SHELLY1_80646FDA9E38 (s1921681030) 2023-07-18 21:46:07,543 Thread-691 udi_interface ERROR Shelly1_Node:updateStatuses: Node: updateStatuses: 404, message='Not Found', url=URL('http://192.168.10.30/status') 2023-07-18 21:46:12,609 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll the update status needs to be updated to support the newer firmwares... found this after digging on shelly website.... http://shelly_ip/rpc/Shelly.GetStatus is what it need to be to get xml parsed info..... please..

AWESOME job buddy! that did it.. thanks much!

ok.. last complaint.. for now.. hehehe It shows that i have version .11 beta, and keeps asking me to update, but i have.. obviously its working now.. it just keeps showing to upgrade to .12 beta, is there a versioning miss somewhere? could it be just that te store is wrong? or PG#x is fubar?..just curious.. i have one other node doing the same thing..its on the latest and greatest, just doesnt know it for some reason.

yes.. its working great so far! Thank you!

nevermind.. im an idiot....forgot to restart the AC...

ok.. i may have screwed up.. i didnt remove nodes in this before when updating... i did this time to fresh start . problem is analog is not working at all..showing a status of false with a reading of 0 maybe its a configuration problem? what the config line for what you have above?

yes.. i was...the max of 1024. When in actuality the voltage(range) was 1280 to 1420 (lithium battery)

no problemo! Thanks!

bug bug....hope you had a good vacay!

OK... i understand now....so yes.. with this one wemos device i am running temp and humidity, a switch(relay), and the analog for battery sense. It is inside of my chicken coop, monitoring temp. Idea is to monitor temp, humid, battery and run a fan as temp rises, but if battery drops to a point then stop the fan. battery is charged via solar, but wemos also runs of same battery. so far everything works as i planned it, other than the battery range issue, which you are graciously trying to fix. i will be more than happy to be the ginnea pig for ya.. and enjoy your vacay!! Thanks!

found this in editor.xml <editor id="ANALOG"> <range uom="56" min="0" max="1024" prec="0" /> </editor>

also.. i dunno what MqttCounts is.. i have 3 different devices....but only need the analog on one of them... 2023-07-27 22:21:26,664 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-07-27 22:21:29,612 Thread-5 udi_interface DEBUG mqtt-poly:_on_message: Received {"Time":"2023-07-27T22:21:28","ANALOG":{"Range":1248},"AM2301":{"Temperature":90.3,"Humidity":56.9,"DewPoint":72.9},"TempUnit":"F"} from tele/Temp1/SENSOR 2023-07-27 22:21:29,614 Thread-5 udi_interface.node DEBUG node:setDriver: temp1:Temp1 Reporting set ST to 1 to Polyglot 2023-07-27 22:21:29,615 Thread-5 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2023-07-27 22:21:29,616 Thread-5 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'temp1', 'driver': 'ST', 'value': '1', 'uom': 2, 'text': None}]} 2023-07-27 22:21:29,618 Thread-5 udi_interface.node DEBUG node:setDriver: temp1:Temp1 Reporting set CLITEMP to 90.3 to Polyglot 2023-07-27 22:21:29,620 Thread-5 udi_interface.node DEBUG node:reportDriver: Updating value to 90.3 2023-07-27 22:21:29,621 Thread-5 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'temp1', 'driver': 'CLITEMP', 'value': '90.3', 'uom': 17, 'text': None}]} 2023-07-27 22:21:29,622 Thread-5 udi_interface.node DEBUG node:setDriver: temp1:Temp1 Reporting set CLIHUM to 56.9 to Polyglot 2023-07-27 22:21:29,623 Thread-5 udi_interface.node DEBUG node:reportDriver: Updating value to 56.9 2023-07-27 22:21:29,625 Thread-5 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'temp1', 'driver': 'CLIHUM', 'value': '56.9', 'uom': 22, 'text': None}]} 2023-07-27 22:21:29,803 MQTT udi_interface.interface INFO interface:_message: Successfully set temp1 :: ST to 1 UOM 2 2023-07-27 22:21:29,873 MQTT udi_interface.interface INFO interface:_message: Successfully set temp1 :: CLITEMP to 90.3 UOM 17 2023-07-27 22:21:29,912 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2023-07-27 22:21:29,914 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2023-07-27 22:21:29,993 MQTT udi_interface.interface INFO interface:_message: Successfully set temp1 :: CLIHUM to 56.9 UOM 22 2023-07-27 22:21:30,014 Thread-5 udi_interface DEBUG mqtt-poly:_on_message: Received ON from stat/Temp1/POWER 2023-07-27 22:21:30,015 Thread-5 udi_interface.node DEBUG node:setDriver: temp2:Temp2 No change in ST's value and then i did a query on it and it posted this in the log 2023-07-27 22:22:26,668 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-07-27 22:22:26,669 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-07-27 22:23:26,686 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-07-27 22:23:26,688 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-07-27 22:24:17,761 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message query 2023-07-27 22:24:17,763 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING query 2023-07-27 22:24:17,764 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for Temp3(temp3) 2023-07-27 22:24:17,765 Command udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'temp3', 'driver': 'ST', 'value': '1', 'uom': 2, 'text': None}, {'address': 'temp3', 'driver': 'GPV', 'value': '1024', 'uom': 56, 'text': None}]} 2023-07-27 22:24:17,998 MQTT udi_interface.interface INFO interface:_message: Successfully set temp3 :: ST to 1 UOM 2 2023-07-27 22:24:17,999 MQTT udi_interface.interface INFO interface:_message: Successfully set temp3 :: GPV to 1024 UOM 56 so i dont think it parsed the info....