Announcement

Collapse
No announcement yet.

Stopped Updating

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Stopped Updating

    I've recently purchased the plugin but unfortunately I'm having problems with the data. I did have a faulty sensor which I've switched out and the Engage Dashboard is now showing the correct data. However Homeseer is not updating the energy database or showing the data in the device list correctly. The current usage appears to be updating but the other data is not.

    Click image for larger version

Name:	Capture.JPG
Views:	58
Size:	62.8 KB
ID:	1279048

    Click image for larger version

Name:	Capture2.JPG
Views:	57
Size:	39.7 KB
ID:	1279049

    Any idea what the issue is and how to fix it please?

    Thanks

    Mark

  • #2
    if the adapter has been changed, the identifier has changed, i am presuming that is the case? does the log just display errors about null reference exceptions? if so i would just delete all devices and restart the plugin and then re-auth the plugin by entering your username and password again.

    Comment


    • #3
      Originally posted by fuzzysb View Post
      if the adapter has been changed, the identifier has changed, i am presuming that is the case? does the log just display errors about null reference exceptions? if so i would just delete all devices and restart the plugin and then re-auth the plugin by entering your username and password again.
      Thanks, yes the adapter has changed. So I've deleted all devices and restarted the plugin (in re auth).

      Now looks like this:

      Click image for larger version

Name:	Capture3.JPG
Views:	54
Size:	141.3 KB
ID:	1279591

      Comment


      • #4
        rascasse Ok please restart the plugin and provide me the debug logs.

        Comment


        • #5
          Jan-27 16:29:49 DEBUG Writing the Log to File Level Debug to the EfergyEngage config file EfergyEngage.ini
          Jan-27 16:30:04 INFO Shutting Down EfergyEngage plugin
          Jan-27 16:30:12 INFO EfergyEngage version 1.0.0.108
          Jan-27 16:30:15 DEBUG Updating Device Efergy Engage Root Device Value Pairs
          Jan-27 16:30:15 DEBUG Updating Device 375 value in HomeSeer
          Jan-27 16:30:16 DEBUG Updating Device 376 value in HomeSeer
          Jan-27 16:30:16 DEBUG Updating Device 377 value in HomeSeer
          Jan-27 16:30:16 DEBUG Updating Device 378 value in HomeSeer
          Jan-27 16:30:16 DEBUG Updating Device 379 value in HomeSeer
          Jan-27 16:30:16 DEBUG Updating Device 380 value in HomeSeer
          Jan-27 16:30:17 DEBUG Updating Device 381 value in HomeSeer
          Jan-27 16:30:17 DEBUG Updating Device 382 value in HomeSeer
          Jan-27 16:30:17 DEBUG Updating Device 383 value in HomeSeer
          Jan-27 16:30:17 DEBUG Updating Device 384 value in HomeSeer
          Jan-27 16:30:18 DEBUG Updating Device 385 value in HomeSeer
          Jan-27 16:30:18 DEBUG Updating Device 386 value in HomeSeer
          Jan-27 16:30:18 DEBUG Updating Device 387 value in HomeSeer
          Jan-27 16:30:18 DEBUG Updating Device 388 value in HomeSeer
          Jan-27 16:30:19 DEBUG Updating Device 389 value in HomeSeer
          Jan-27 16:30:19 DEBUG Updating Device 390 value in HomeSeer
          Jan-27 16:30:19 DEBUG Updating Device 391 value in HomeSeer
          Jan-27 16:30:19 DEBUG Updating Device 392 value in HomeSeer
          Jan-27 16:30:19 DEBUG Updating Device 393 value in HomeSeer
          Jan-27 16:30:20 DEBUG Updating Device 394 value in HomeSeer
          Jan-27 16:30:20 DEBUG Updating Device 395 value in HomeSeer
          Jan-27 16:30:20 DEBUG Updating Device 396 value in HomeSeer
          Jan-27 16:30:20 ERROR Object reference not set to an instance of an object.
          Jan-27 16:30:20 DEBUG at InuY0wX7WdkoRASBPp.iULUI5QODe7p3Qe7hK.tU8PbO3AIH(getDevices , Api )
          at InuY0wX7WdkoRASBPp.iULUI5QODe7p3Qe7hK.<UpdateEnergyDevices>d __113.MoveNext()
          Jan-27 16:30:21 ERROR Object reference not set to an instance of an object.
          Jan-27 16:30:21 DEBUG at InuY0wX7WdkoRASBPp.iULUI5QODe7p3Qe7hK.tU8PbO3AIH(getDevices , Api )
          at InuY0wX7WdkoRASBPp.iULUI5QODe7p3Qe7hK.<UpdateEnergyDevices>d __113.MoveNext()
          Jan-27 16:30:22 ERROR Object reference not set to an instance of an object.
          Jan-27 16:30:22 DEBUG at InuY0wX7WdkoRASBPp.iULUI5QODe7p3Qe7hK.tU8PbO3AIH(getDevices , Api )
          at InuY0wX7WdkoRASBPp.iULUI5QODe7p3Qe7hK.<UpdateEnergyDevices>d __113.MoveNext()
          Jan-27 16:31:24 ERROR Object reference not set to an instance of an object.
          Jan-27 16:31:24 DEBUG at InuY0wX7WdkoRASBPp.iULUI5QODe7p3Qe7hK.tU8PbO3AIH(getDevices , Api )
          at InuY0wX7WdkoRASBPp.iULUI5QODe7p3Qe7hK.<UpdateEnergyDevices>d __113.MoveNext()
          Jan-27 16:31:24 ERROR Object reference not set to an instance of an object.
          Jan-27 16:31:24 DEBUG at InuY0wX7WdkoRASBPp.iULUI5QODe7p3Qe7hK.tU8PbO3AIH(getDevices , Api )
          at InuY0wX7WdkoRASBPp.iULUI5QODe7p3Qe7hK.<UpdateEnergyDevices>d __113.MoveNext()
          Jan-27 16:31:26 ERROR Object reference not set to an instance of an object.
          Jan-27 16:31:26 DEBUG at InuY0wX7WdkoRASBPp.iULUI5QODe7p3Qe7hK.tU8PbO3AIH(getDevices , Api )
          at InuY0wX7WdkoRASBPp.iULUI5QODe7p3Qe7hK.<UpdateEnergyDevices>d __113.MoveNext()
          See above. I also renamed the energy DB, so it created a new one. But it's not logging anything. Thanks.

          Comment


          • #6
            Same problem here. Showing status Offline. Token OK.

            Comment


            • #7
              rascasse Mobileum The issue was caused by an error in the Efergy Engage API as the Tariff request returns a null response. I sent a message to them asking them to resolve. it's exactly the same issue that occured the week after i initially released the plugin. and they fixed after roughly 2 weeks, however they still haven't fixed this, so to work around this i have release v1.0.0.109 Beta, which is in the beta section of the updater. please update the version and try.

              You will not see the tariff updating, but if you had a value there, then it will work i think without issue, but if not, please check the Energy DB input as i don't know what the impact will be, does it still set the value or not?

              Comment


              • #8
                I am now Online. Good. But all "Estimates" are empty, and I know nothing about how to check the Energy DB input.

                And "Root Device" is Off...

                Comment


                • #9
                  yes the estimates are dependant on the Tariff information, which is the current issue with the Engage platform as this returns a null response

                  Comment


                  • #10
                    Mine also working thanks - but no device is appearing in the Energy DB though...

                    Click image for larger version

Name:	Capture 4.JPG
Views:	55
Size:	63.7 KB
ID:	1281024

                    Comment


                    • #11
                      Ok let me work on a new beta version tomorrow. I will have to prompt you in the settings for your tariff price and if this issue persists or happens again it will fall back to that value. Then it should all work consistently

                      Comment


                      • #12
                        rascasse ok the new beta is up, you now just goto your settings and enter your cost per KWH to match the same as in your Efergy Engage Settings and this will ensure that this now works again uploading values to the HS3 Energy DB, it will prevent this error occuring even if the issue persists on the EfergyEngage platform returning a null entry. so now it uses the value from Efergy, but if that fails, like it has been for the last few weeks it will use the value below.

                        Comment


                        • #13
                          Installed, but the cost will not be updated, and revert to zero as soon as I exit Config. I am using "kr" as currency.

                          Comment


                          • #14
                            It should be fine. What does your ini file now show?

                            Comment


                            • #15
                              [EFERGYENGAGE]
                              access_token=xxxxxxx
                              [EFERGYCOST]
                              per_kw_cost=¤0.00

                              Should I update it here?

                              Comment

                              Working...
                              X