Shelly1 ver2

[EWhite]

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

 

Edited July 19, 2023 by EWhite
added log

[EWhite]

found this after digging on shelly website....

http://192.168.33.1/rpc/Shelly.GetStatus

is what it need to be to get xml parsed info.....

 

[EWhite]

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..

 

[Geddy]

@EWhite just unlocked the old topic. Not sure who the developer is (Showing TangoWhiskey1 on the store, but no user here with that name). Might be better to raise an issue on the github - https://github.com/UniversalDevicesInc-PG3/udi-shelly-poly/issues. Developer might not be active on the forums or might have abandoned the node server. 

This might be another one that @bpwwer migrated from PG2 to PG3, but doesn't appear to have any updates since 2022.

[bpwwer]

Yes, I ported it from PG2 to PG3 but don't have any devices and can't really provide much in terms of support for this node server.

[EWhite]

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

[EWhite]

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

 

[Goose66]

Have you tried Network Resources? Can you flash it with Tasmota and use the MQTT node server?

Edited September 25, 2023 by Goose66

[bpwwer]

There are a number of node servers that were originally written for PG2 but then abandoned by the author.  UDI ported those to PG3 (mostly done by me).  For a couple, I've taken on the support/maintenance of them but I don't have the time to support all of them. 

When I ported them, I placed them in https://github.com/UniversalDevicesInc-PG3 area.  So if that's where the more info button points and that's where it installs from, then it is likely a UDI ported node server.

For help with these node servers, you should go directly to UDI.  Submit a ticket and let them figure out what to do about it.  In fact, for any node server where you don't get a response from the author, submit a ticket. 

[EWhite]

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

Thanks

 

 

[Goose66]

What's your need here? I am close to releasing a Tasmota node server (testing on PG3x now) specifically for Martin Jerry switches and modules, but could be expanded to support the Shelly products for simple control and monitoring if the devices have Tasmota installed as the firmware. Let me know what devices you have and if they have Tasmota installed (or you would be willing to flash them with Tasmota).

Also, there is an MQTT node server (and an MQTT broker running on recent versions of PG3 and PG3x) that I haven't used but I believe can be configured to communicate with specific devices over MQTT via Custom Configuration Parameters without having to change out the firmware.

Don't know if any of this fulfills your needs, but just let me know.

Edited September 29, 2023 by Goose66

[EWhite]

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!

 

[Goose66]

I flashed my Shelly 1 to Tasmota, and it was pretty easy. Followed the instructions here: https://tasmota.github.io/docs/devices/Shelly-1/. I needed a USB-to-TTL device that also supplied 3.3v, so I got this one: https://www.amazon.com/gp/product/B07WX2DSVB. Worked great!

Anyway, the Tasmota node server is published and supports the Shelly 1 device. Hope to add additional Tasmota support soon.

Edited October 12, 2023 by Goose66