The same one I used to register and update the two other shelly devices last week.
Andrew
The same one I used to register and update the two other shelly devices last week.
Andrew
Finally got it to update firmware, but through the desktop web app, and only on edge.
Finally added to Homey, but no functions available other than battery voltage actions.
Read the instructions from the first post. There is a generic trigger action card available under the app instead of the device.
Anyone?
Hi @Phuturist,
Just installed the test version of the app.
All my 14 Shelly Devices keep working.
I have Dimmer2, Plugs, 1L and 1 Shelly devices installed in different setups.
Some control the lights directly (dumb bulbs) and some control Hue Bulbs.
I will keep the test version installed.
If you want me to test something specific, let me know!
Looks good for my shellies, I only dislike the warning, understand why, but âŚ
DIagnostic report: 00b7752d-9f22-468d-8b8c-540c3c9a1028
When I go to my Shelly I3 device in homey app popup shows up which says that This type of device might not be supported in the future.
Is support going to be removed for these?
Hi,
I am a brand new user and I just bought my first Shelly 1. After reading the instructions, I followed the steps closely to add the device to my home network and the app, but itâs not sccessful.
Now it is located under âhidden devicesâ as Offline / Pending connection.
This device is brand new from the store and has never been connected to a network before.
This happened the first time also so I have reset the device (5 times on/off sw) once before.
Now I need some help because I just canât get any further.
Itâs a 2.4 GHz network, I find the device and connect to it through the app. Then the AP network shows up on my wifi and I connect to that also. That is basically where I am at now.
Regards
Hi Phuturist, Iâm happy to do some tests with my Shelly Plus 1 PMâs. Iâm planning to buy a few more Shelly devices⌠I like your app and support you provide
One question. On my Homey Pro I donât see the power changing. It shows the value of 3 days ago. The Shelly app does show the correct valueâŚ
issue is resolved⌠power is updating properly. I removed de devices and added them again under the new Shelly App (beta)
All my installed devices works, but I have just bought 2 pcs. Shelly Door/Window2 and I canât connect themâŚ
The app reports this error :
Error: No suitable device config found. This device might not be supported yet, please report this to the developer.
Could you post the output from http://shellyip/shelly and http://shellyip/settings. Iâll fix it when I get back from holiday. Canât wat l wait that long and have not added devices with the new generic driver you can switch back to the live version (3.9.12). That will probably still work.
Correct with live version 3.9.12 it worksâŚ
Here are output from the first device
{âtypeâ:âSHDW-2â,âmacâ:â10521C078313â,âauthâ:false,âfwâ:â20220209-093605/v1.11.8-g8c7bb8dâ,âdiscoverableâ:false,âsleep_modeâ:true}
{âdeviceâ:{âtypeâ:âSHDW-2â,âmacâ:â10521C078313â,âhostnameâ:âshellydw2-078313â,âsleep_modeâ:true},âwifi_apâ:{âenabledâ:false,âssidâ:âshellydw2-078313â,âkeyâ:ââ},âwifi_staâ:{âenabledâ:true,âssidâ:âIoTâ,âipv4_methodâ:âdhcpâ,âipâ:null,âgwâ:null,âmaskâ:null,âdnsâ:null},âwifi_sta1â:{âenabledâ:false,âssidâ:null,âipv4_methodâ:âdhcpâ,âipâ:null,âgwâ:null,âmaskâ:null,âdnsâ:null},âmqttâ: {âenableâ:false,âserverâ:â192.168.33.3:1883â,âuserâ:ââ,âidâ:âshellydw2-078313â,âreconnect_timeout_maxâ:60.000000,âreconnect_timeout_minâ:2.000000,âclean_sessionâ:true,âkeep_aliveâ:60,âmax_qosâ:0,âretainâ:false,âupdate_periodâ:30},âcoiotâ: {âenabledâ:true,âupdate_periodâ:15,âpeerâ:â192.168.0.4:5683â},âsntpâ:{âserverâ:âtime.google.comâ,âenabledâ:true},âloginâ:{âenabledâ:false,âunprotectedâ:false,âusernameâ:âadminâ},âpin_codeâ:ââ,ânameâ:âShelly DW no1â,âfwâ:â20220209-093605/v1.11.8-g8c7bb8dâ,âdiscoverableâ:false,âbuild_infoâ:{âbuild_idâ:â20220209-093605/v1.11.8-g8c7bb8dâ,âbuild_timestampâ:â2022-02-09T09:36:05Zâ,âbuild_versionâ:â1.0â},âcloudâ:{âenabledâ:true,âconnectedâ:true},âtimezoneâ:null,âlatâ:500.000000,âlngâ:500.000000,âtzautodetectâ:true,âtz_utc_offsetâ:0,âtz_dstâ:false,âtz_dst_autoâ:true,âtimeâ:ââ,âunixtimeâ:0,âled_status_disableâ:true,âdebug_enableâ:false,âallow_cross_originâ:false,âactionsâ:{âactiveâ:false,ânamesâ:[âreport_urlâ,âdark_urlâ,âtwilight_urlâ,âopen_urlâ,âclose_urlâ,âvibration_urlâ,âtemp_over_urlâ,âtemp_under_urlâ]},âdark_thresholdâ:100,âtwilight_thresholdâ:300,âsleep_modeâ:{âperiodâ:12,âunitâ:âhâ},âled_status_disableâ:true,âtilt_enabledâ:true,âtilt_calibratedâ:true,âvibration_enabledâ:false,âvibration_sensitivityâ:50,âreverse_open_closeâ:false,âlux_wakeup_enableâ:true,âsensorsâ:{âtemperature_thresholdâ:1.0,âtemperature_unitâ:âCâ},âtemperature_offsetâ:0.0}
Here are output from the second device
{âtypeâ:âSHDW-2â,âmacâ:â10521C078812â,âauthâ:false,âfwâ:â20220209-093605/v1.11.8-g8c7bb8dâ,âdiscoverableâ:false,âsleep_modeâ:true}
{âdeviceâ:{âtypeâ:âSHDW-2â,âmacâ:â10521C078812â,âhostnameâ:âshellydw2-078812â,âsleep_modeâ:true},âwifi_apâ:{âenabledâ:false,âssidâ:âshellydw2-078812â,âkeyâ:ââ},âwifi_staâ:{âenabledâ:true,âssidâ:âIoTâ,âipv4_methodâ:âdhcpâ,âipâ:null,âgwâ:null,âmaskâ:null,âdnsâ:null},âwifi_sta1â:{âenabledâ:false,âssidâ:null,âipv4_methodâ:âdhcpâ,âipâ:null,âgwâ:null,âmaskâ:null,âdnsâ:null},âmqttâ: {âenableâ:false,âserverâ:â192.168.33.3:1883â,âuserâ:ââ,âidâ:âshellydw2-078812â,âreconnect_timeout_maxâ:60.000000,âreconnect_timeout_minâ:2.000000,âclean_sessionâ:true,âkeep_aliveâ:60,âmax_qosâ:0,âretainâ:false,âupdate_periodâ:30},âcoiotâ: {âenabledâ:true,âupdate_periodâ:15,âpeerâ:â192.168.0.4:5683â},âsntpâ:{âserverâ:âtime.google.comâ,âenabledâ:true},âloginâ:{âenabledâ:false,âunprotectedâ:false,âusernameâ:âadminâ},âpin_codeâ:ââ,ânameâ:null,âfwâ:â20220209-093605/v1.11.8-g8c7bb8dâ,âdiscoverableâ:false,âbuild_infoâ:{âbuild_idâ:â20220209-093605/v1.11.8-g8c7bb8dâ,âbuild_timestampâ:â2022-02-09T09:36:05Zâ,âbuild_versionâ:â1.0â},âcloudâ:{âenabledâ:true,âconnectedâ:true},âtimezoneâ:null,âlatâ:500.000000,âlngâ:500.000000,âtzautodetectâ:true,âtz_utc_offsetâ:0,âtz_dstâ:false,âtz_dst_autoâ:true,âtimeâ:ââ,âunixtimeâ:0,âled_status_disableâ:true,âdebug_enableâ:false,âallow_cross_originâ:false,âactionsâ:{âactiveâ:false,ânamesâ:[âreport_urlâ,âdark_urlâ,âtwilight_urlâ,âopen_urlâ,âclose_urlâ,âvibration_urlâ,âtemp_over_urlâ,âtemp_under_urlâ]},âdark_thresholdâ:100,âtwilight_thresholdâ:300,âsleep_modeâ:{âperiodâ:12,âunitâ:âhâ},âled_status_disableâ:true,âtilt_enabledâ:false,âtilt_calibratedâ:false,âvibration_enabledâ:false,âvibration_sensitivityâ:50,âreverse_open_closeâ:false,âlux_wakeup_enableâ:true,âsensorsâ:{âtemperature_thresholdâ:1.0,âtemperature_unitâ:âCâ},âtemperature_offsetâ:0.0}
Hi
I bought a shelly button 1.
If i like to add it tomy homey pro it adds the device but seems not to recognize it and add it correctly.
After adding there are no actions available.
Any one experience the same issue? Any solution?
Thanks
There is a trigger card under the app (not the device) which you can use.
Trying out 3.10.1 is very hard with 100+ devices since all show in the pairing list at no particular order and only partial IPâs are shown for most devices. By the time I find what I think might be the device I want to add, the session has timed out Being able to search for IP would help.
Hmmm, I see. Itâs a corner case since not that many people will have that many Shelly devices. Adding a search filter is not up te me though, that would have to be added by Athom to the pairing wizard. Iâll post a feature request.
[EDIT]
fyi. Trying to add the new Motion 2 and H&T plus in 3.10.1, throws error âDevice not supported, contact developerâ
Thanx, Iâll look into after my vacation. Itâs weird though as I own both devices and for sure have tested the PlusHT. Perhaps the production version is different from my test device.
Could you post the output of http://shellyip/rpc/Shelly.GetConfig and http://shellyip/rpc/Shelly.GetDeviceInfo for both devices.
Iâll improve that error to include the device model which is supposedly not supported for easier troubleshooting.